Android tablets supported for Cisco Jabber for Android 10.5 ?

Exist a list with tablets support for this realease ?
In release notes only include smartphones.
Anoher question, is about version android client, in google play exits a old version, but not 10.5, any reason for this ?
Thanks in advance.

The tab listed for support is " Google Nexus 10 (Android OS 4.4.x) ". Please refer to the following link for more information;
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/10_5/CJAB_BK_D6497E98_00_deployment-installation-guide-ciscojabber/CJAB_BK_D6497E98_00_deployment-installation-guide-ciscojabber_chapter_011.html#CJAB_RF_D3CF90B1_00
Quoting the following link; https://play.google.com/store/apps/details?id=com.cisco.im&hl=en ;we have got the J4A 10.5 listed on the playstore.
- please rate if this helps.

Similar Messages

Contacts search for cisco Jabber for Windows & MAC

Hello,
Please assist on given below query !!
System Deatails of CUCM & IM Presence Server
CUCM:
1> System version: 9.1.1.20000-5
2> VMware Installation: 2 vCPU Intel(R) Xeon(R) CPU X5650 @ 2.67GHz, disk 1: 80Gbytes, 4096Mbytes RAM
3> Physical Server UCS210 M2
4> Already Integrated with IM & Presence
IM & Presence:
1> System version: 9.1.1.20000-5
2> VMware Installation: 1 vCPU Intel(R) Xeon(R) CPU X5650 @ 2.67GHz, disk 1: 80Gbytes, 2048Mbytes RAM
3> Physical Server UCS210 M2
4> Already Integrated with CUCM
Requirement:
1> User Search base for Cisco Jabber for Windows & MAC Client
2> Will we able to get contacts list(Jabber For windows & MAC) as like "Lotus Sametimes" for all users?
Every reply would highly Appreciated!!

Hi Karthik,
Thanks for your reply!
I have gone through the link but query is different actually, please assist on below query and provide any document links if possible.
1> The contacts does not appear when I perform a search
2> Do I required to integrate LDAP for same? If Yes Then Do I need to perform integration with CUCM Or IM & Presence? Or Only CUCM? Or only IM & Presence? (Please post a link to perform same)
3> Please also provide If any specific system requirement for LDAP server.
4> Is it possible without LDAP integration?
It is really urgent and every post would highly appreciate..........

Cisco Jabber for Windows Client SDK

Is there an SDK for Cisco Jabber for Windows client? I could only find the Web SDK. Are there no other SDKs that would let me control features of the Jabber Windows Client?

And in order to avoid TAPI limitation, they say they have started using Jabber which controls all phone functionalities through an Application User connected to the Call Manager.
Assuming they are referring to the normal Jabber for Windows/Mac/iOS/Android applications then this is wrong. Jabber - the client, not the IM&P servers which are part of the CUCM cluster (if you're familiar with Lync consider CUCM+IM&P servers a Front End Pool) - do not use an Application User at all. When a user starts Jabber, assuming SAML SSO is off, they supply an email address. This is used to find the servers via DNS SRV records, or the Mobile and Remote Access Expressway (roughly analogous to a Lync Edge pool) to tunnel through the firewall. After the email address they are prompted for their End User username and password. This is then used to access several APIs on the server, namely the User Data Service to discover what the user has. This would include what the user has configured/available to them. After this is done the Jabber client does one of three things with respect to phone functionality:
If the user has no phone devices provisioned for them - physical or software - it becomes an IM&P client only.
If the user has a software phone phone provisioned, it registers as that using SIP. In this way Jabber is the actual phone. This is called a CSF device for Jabber Windows/OS X.
If the user has a desk phone assigned to their End User account AND administrative policy is to default to desk phone control, it registers to CTI Manager on the CUCM server to control the user's physical phone.
A user can toggle between option two and three, if appropriately provisioned, but cannot have both simultaneously. In other words, Jabber is either controlling a physical phone over CTI or is a phone itself using SIP. The difference is where the audio/video media is sent from/to.
All of this happens using that human's End User credentials.
Now, if you wanted to have a server control the user's phone - either a physical one or Jabber - you would use the TSP as an interface to CTI Manager on the CUCM server and receive real-time events (e.g. the user went off-hook, the phone is ringing with this caller ID, etc.) and issue commands to that phone (e.g. make a call to X). This is done using an Application User account because the server would need to do this for multiple users simultaneously. If you also use the Super Provider concept, the CUCM administrator doesn't have to take the extra step of associating every phone to your Application User manually. Instead, you can simply issue CTI subscriptions to see any/all device activity you want.
This is all assuming you wanted to do the integration server-side to avoid having to update the Cisco TSP application on every user PC (which also limits your WPF application to machines capable of running the TSP) every time the CUCM administrator patches the servers. If you don't care about that, then you can do this all client-side on the user's PC, and have them supply their End User credentials.
Of course, you could also reconsider the Jabber SDK and just embed the make/receive call functionality directly into your application instead.

A list of supported Android Phones for Cisco Jabber Client.

Hi there,
I opened a discussion before about the Cisco Jabber Client for Android phones.
This product from Cisco is only official support bij a several mobile Android telephones. (very poor)
As everyone knows is that the mobile market is continious in development. Since a half year the official support phone list is still the same, but a lot of new Adroid phones are now on the market.
It's even so worse that some of the Cisco supported phones, are not available anymore in the market.
- Samsung Galaxy S2 becomes a Samsung Galaxy S3
- Samsung Galaxy TAB is still there
- Samsung Galaxy S (are not available anymore) The S1 or S Plus are now becoming the Samsung Galaxy S Advanced.
At what are the alternatives?
Still the list on the documentation is out-dated.
See:
Samsung Galaxy S International (GT-I9000) with Android operating system (OS) Version 2.2.1 or 2.3
Samsung Galaxy Tab International (GT-P1000) with Android 2.2.1 or 2.3
Samsung Galaxy S II (AT&T) with Android 2.3
To use Cisco Jabber for Android on the Samsung Galaxy S device, it is important that you upgrade your handset OS to Android Version 2.2.1 or 2.3. See the manufacturer/carrier site for more information about how to update the OS on your device. Minor voice quality issues may be experienced depending on the device used.
So hopefully Cisco is still working on the Cisco Jabber solution, and a lot of mobile Android phones will be supported so the road to success will be open.
Hopefully someone can help me to list of tested and supported phones (Official bij Cisco)
Kind regards,
Edgar

The official list of tested Android phones is what you've already discovered. With the next release of Cisco Jabber for Android, I'm sure it will be updated.
While the official list of what we tested is short, the client will work on many Android devices and TAC will provide support if you run into technical issues; provided the issue is with the Cisco Jabber client itself, and not with the OS of the manufacturer.
If there is a specific Android phone you are looking to have officially tested by Cisco, PM me with that information and I'll work with you to see what we can do to get it added.

Cisco jabber for android no ask outgoing call

Is available:
1) cucm 8.6
2) The samsung galaxy S4 mini smartphone (android 4.2.2) with the client of cisco jabber for android v 9.1.4
On the smartphone, in the cisco jabber settings, it is specified - to ask for each outgoing call through what to ring.
If to open the address directory of phone and to click a call, the call is made through SIM a card.
How to set up, what the request through what to make an outgoing call would be output?

Take in mind the supported list of devices, in my experience it can be troublesome if you want to uses some of the brands not listed (I played with a Huawei and a LG without luck)
Check http://www.cisco.com/c/en/us/products/collateral/unified-communications/jabber-android/data_sheet_c78-649887.html (Device and OS Requirements)
Regards.
Rolando Valenzuela.

Cisco Jabber for Android 4 (Ice Cream Sandwich)?

Hi,
I'm curious to know if there are any plans to make an Android 4 version of the Cisco Jabber client. If so, do you have any estimates on release date?
Best regards,
Pauli

So the Case with TAC came to nothing. Tehy finally came back with the list of the 3devices that they support and nothing more. Here's their response:
"This is a follow up to our conversation over the phone. I apologize for the inconvenience with regard to the compatibility of the Jabber for Android client. I hope that I have provided the support that you expected. Below is the link to the release notes which talks about the supported devices with Jabber for Android -
http://www.cisco.com/en/US/partner/docs/voice_ip_comm/jabber/Android/8_6/Cisco_Jabber_Android_8_6_4_RN.html#wp46650
"Requirements for users and devices
The following Android devices are supported:
*Samsung Galaxy S International (GT-I9000) with Android 2.2.1 or 2.3
*Samsung Galaxy Tab International (GT-P1000) with Android 2.2.1 or 2.3
*Samsung Galaxy S II (AT&T) with Android 2.3"
I will resolve this case now, but don't hesitate to contact GTC or contact me directly
anytime if you have any further issues. Thanks again for all your time and patience.
It was a pleasure working with you."
It was more than a little disappointing to say the least!

Hi Team, I wuold like to know if you have any app to make Firefox OS working with cisco Call Manager 10.5. Something like Cisco Jabber for Android or iOS.

I'm interesting on buying a Firefox Smart Phone, but
I would like to know if are any app to install on Firefox OS smart phone in order to work with cisco call manager 10.5.
Something like Cisco Jabber for Android o iOS.
Thanks,

Hi Itech,
If Cisco Jabber has a webapp, or mobile version of their website available, you should technically be able to access it through Firefox OS.
You may also search Firefox Marketplace for an alternative solution:
* [https://marketplace.firefox.com/]
- Ralph

Cisco Jabber for Blackberry

Hi Jabber Experts,
I was trying with Cisco Jabber IM for Blackberry(9700) , i had manually loaded the application on the device and chose the CUPS(On-Premise) mode installation. I was able succesfully login with my CUPC login credentials. I could see all my contacts, presence info and chat. But Iam not able to place a call. I tried to search one of the contact profile and see no information there, though my desktop(cupc) application all the contact profiles populated with required informations(work phone, cell,email)
We have a LDAP integration on CUPS.
Please advice how can i place a call from my Cisco Jabber Application?
Regards
John

Hi Binu,
Cisco Jabber for Blackberry probably has similar causes for failure to register as the Android version. You may wish to check out the "Cisco Jabber Registration Fails" section at the following URL for ideas:
http://www.cisco.com/en/US/docs/voice_ip_comm/cumc/cisco_jabber/Android/86/Cisco_Jabber_Android_8.6.x_Admin_Guide.html#wp170272
Kind regards,
Craig

Cisco Jabber for Mac - Directory Lookup and Contact Fields

Hello,
After having issues myself with Cisco Jabber for Mac 9.2 specifically with Active Directory lookups not working, or contact information not populating (and therefore not being able to call users from the contact list as no telephone information exists) I am including a sample jabber-config.xml file that works for me.
Please note: there are many different ways to configure this. What I will be showing is the method that works for me and my deployment, which is pretty standard.
As always and as a disclaimer, once again, this is what has worked for my deployment scenario. Always keep backups of your configuration files, and always be mindful of anything you have configured already, especially in the jabber-config.xml file.
Background
My deployment is based on CUCM 9, with 1 publisher and 2 subscribers. I also have a CUCM IM & Presence 9.0 server. This assumes that you have already configured your deployment and Jabber is functioning already, albeit with the aforementioned issues.
As for Active Directory, my deployment will be based on Windows 2008 R2 Domain Controllers running in native 2008 mode. For this example, we will be searching directly against one of the DCs with a Global Catalogue role. Please be aware that in large deployments you will have to plan accordingly with regards to lookup traffic from Jabber clients to the DCs.
Also, as of Cisco Jabber for Mac 9, the client no longer can search via the CUCM internal directory (which may be made of local end users, Active Directory synced users, or a mix of both) and this must be done via a LDAP mechanism.
Scenario
In this deployment scenario, Cisco Jabber for Windows is working properly - you can search and add people from Active Directory, and contacts in your contact list have all the appropriate fields populated from Active Directory. However, when trying the same with Jabber for Mac, Jabber for iPhone or Jabber for iPad you notice that you cannot perform a directory lookup, and if you add people directly (for example, [email protected]) the user only has the IM field populated. No telephone, email or additional information is displayed.
Solution
Whereas Cisco Jabber for Windows uses the EDI mechanism (native Windows), whereby when running from a computer that is on the domain (or in the event that you are search for contacts in another Active Directory domain where a domain trust exists) , Jabber for Mac / iPhone / iPad uses the BDI mechanism.
In this case, you will need to provision a jabber-config.xml file that you will upload to your TFTP server (or Publisher) that will be "downloaded" by your Jabber for Mac client and also used by the iPhone and iPad client. You can configure many options in the jabber-config.xml file, but for this example we will place just the information that we need to order for these clients to request and display Active Directory information.
Please note that the configuration may vary depending on your deployment, but at the very least we will be:
- Configuring a DC where we will perform the lookup.
- Configure credentials that will be used to perform the lookup. This will be an Active Directory account that has read rights on the Active Directory domain. Please note that these credentials are saved in plain text in the file, so ensure that the account that you will be using is not privileged.
- Configure the server port that we will be using to perform the lookup.
- Configure the Search Base. This is basically where we want the directory lookup to happen. You can either choose for this lookup to start at the "base" of the domain (and therefore the search will iterate through all the user accounts and and OUs below the root base) or define a specific OU where you want to search.
Caution!
- There is a current limitation with Cisco Jabber for Mac whereby you can only have 1 search base configured. Please keep this in mind if, like me, you have multiple OUs (like an OU for each company in your organization) and under these OUs you have sub OUs as a user account container.
- If using the top level search base, unless you specify a filter, you will potentially be able to search for all user accounts in the domain. You will need to configure the <BDIBaseFilter> parameter if you want to fine tune your search ability.
Steps
These are the steps I have followed. Other steps or considerations may vary.
- Log in to your TFTP server and download the jabber-config.xml file and keep it as a backup. If you are already using the jabber-config.xml file for other purposes, do not worry - you can add your BDI information parameters inside.
- Remove the jabber-config.xml file
- Edit the jabber-config.xml file and configure thus:
<?xml version="1.0" encoding="UTF-8"?>
<config version="1.0">
    <Directory>
        <DirectoryServerType>BDI</DirectoryServerType>
        <BDILDAPServerType>AD</BDILDAPServerType>
        <BDIPrimaryServerName>DOMAIN CONTROLLER IP ADDRESS</BDIPrimaryServerName>
        <BDIPresenceDomain>YOUR PRESENCE DOMAIN</BDIPresenceDomain>
        <BDIServerPort1>3268</BDIServerPort1>
        <BDISearchBase1>YOUR SEARCH BASE</BDISearchBase1>
       <BDIConnectionUsername>[email protected]</BDIConnectionUsername>
        <BDIConnectionPassword>PASSWORD</BDIConnectionPassword>
        <BDIEnableTLS>0</BDIEnableTLS>
   </Directory>
</config>
For example, let´s assume the following:
- Domain controller IP address is 10.1.1.2 .
- Your presence domain is test.local .
- Your search base will be test.local using the top level of the domain.
- Your username with which you will be doing your searches is called walt . Usually you can either identify walt as test.local\walt or [email protected] . It is always best, in these sort of scenarios, to use the UPN convention so we will be configuring a [email protected] .
- The password is the Active Directory password for the account walt .
- I have disabled TLS in my case. There are issues with the Jabber for Mac client when using other security methods.
<?xml version="1.0" encoding="UTF-8"?>
<config version="1.0">
    <Directory>
        <DirectoryServerType>BDI</DirectoryServerType>
        <BDILDAPServerType>AD</BDILDAPServerType>
        <BDIPrimaryServerName>10.1.1.2</BDIPrimaryServerName>
        <BDIPresenceDomain>test.local</BDIPresenceDomain>
        <BDIServerPort1>3268</BDIServerPort1>
        <BDISearchBase1>DC=test,DC=local</BDISearchBase1>
       <BDIConnectionUsername>[email protected]</BDIConnectionUsername>
        <BDIConnectionPassword>walt01!</BDIConnectionPassword>
        <BDIEnableTLS>0</BDIEnableTLS>
   </Directory>
</config>
One you have configured the jabber-config.xml file, you will now need to upload it to you TFTP server. Once uploaded, you will need to restart the Cisco TFTP service. Again, my TFTP server is on my CUCM publisher, so:
- I go to Cisco Unified OS Administration on my Publisher server, TFTP File Management and I upload jabber-config.xml to / directory
- I then go to Cisco Unified Serviceability on my Publisher server, I locate the Cisco TFTP service and I restart the service
Once this is done, you can figure up your Jabber for Mac client. As a test, on your Mac (using Terminal) go to:
/Users/username/Library/Application Support/Cisco/Unified Communications/Jabber/Config
In here you will see several files, but what we want to see is jabber-config.xml . As soon as you start the Jabber for Mac client and log in, the jabber-config.xml file will download from your TFTP server and get saved here. When you see it appear, just type in your terminal window more jabber-config.xml and make sure that the output is the same as the xml file you created.
From there, try doing directory search. If you have previously added contacts and they still lack attribute information, you will need to remove them (sometimes it will not refresh properly) and add them again from the directory.
I will be updating this guide and ammending anything that is incorrect, but this is meant to be a quick checklist and steps to get this, at least in the most very basic version, up and running for Jabber for Mac.

Hello,
Thanks for this post! It works, I can do lookup and also I can add found contact to contact list and get information about contact from LDAP.
One more question: - I can't get all information about contact. I don't get e.c mobile phone number and more others attributes. I have tried to expand your file as follows:
<?xml version="1.0" encoding="UTF-8"?>
<config version="1.0">
<Directory>
<DirectoryServerType>BDI</DirectoryServerType>
<BDILDAPServerType>AD</BDILDAPServerType>
<BDIPrimaryServerName>IP of AD</BDIPrimaryServerName>
<BDIPresenceDomain>Presence Domain</BDIPresenceDomain>
<BDIServerPort1>3268</BDIServerPort1>
<BDISearchBase1> Search Base</BDISearchBase1>
<BDIConnectionUsername>User</BDIConnectionUsername>
<BDIConnectionPassword>Password</BDIConnectionPassword>
<BDIEnableTLS>0</BDIEnableTLS>
       <BDISipUri>msRTCSIP-PrimaryUserAddress</BDISipUri>
       <BDIPhotoSource>thumbnailPhoto</BDIPhotoSource>
       <BDIBusinessPhone>telephoneNumber</BDIBusinessPhone>
       <BDIMobilePhone>mobile</BDIMobilePhone>
       <BDIHomePhone>homePhone</BDIHomePhone>
       <BDIOtherPhone>otherTelephone</BDIOtherPhone>
       <BDITitle>title</BDITitle>
       <BDICompanyName>company</BDICompanyName>
<BDILocation>co</BDILocation>
<BDIPostalCode>postalCode</BDIPostalCode>
       <BDICity>l</BDICity>
       <BDIState>st</BDIState>
       <BDIStreetAddress>streetAddress</BDIStreetAddress>
</Directory>
</config>
But it didn't help.
When I capture lookup via Wireshark, I can see that Jabbers sends search request with bunch of attributes, but from LDAP answer contains only 8 attributes. (see attached screenshots)

Call/video not working between Cisco jabber for Windows and VCS control C40s

Hello,
I've been struggling with no luck how to make a call using Cisco Jabber for Windows 9.6.0 registered to CM 8.6.2 with intercluster ICT to another CM 8.6.2 where we have a VCS Control 7.0.2 via GK H225, and all C40s are registered as H.323.
The VCS has interworking between H323 and SIP, however not sure if there is any problem with that. Assuming it is ok, not sure either if I'm facing any interoperability issue because in my remote site I have C40 (H323 registered at VCS and SIP listening mode) and cisco jabber for windows which is SIP based.
If is not possible, would I be able to change my C40 from H323 to SIP at VCS, or have both H323/SIP registered at VCS? If so, will I need to change as well instead of GK I'll have to establish a SIP Trunk between the CM and VCS?
Another thing I do not believe either I would be able to have one VCS connected with two clusters, right?
I'm just trying to find a solution in case my current topology is not compatible, but feel free if you have any better idea to make it work.
Anyway here is what is happening:
When I make a call from my cisco jabber windows to C40 using alias number. The call is being redirected just fine to the C40 and it rings, however when someoene or the auto answer picks it up, the call dropped right away.
However, if I enabled the MTP in my CSF device, the call gets longer before dropping. I was even able to see my jabber " start video" turns green, before was grayed out all the time and the call dropped faster. I hear a fast busy tone.
I'm able to provide SDI traces, logs, diagnostic sip/h323 calls from VCS in order to know for sure if this is an incompatible issue or something I can workaround.
Let me know if someone of you are interested in read these logs or could point me on the right direction.
Thanks!

Ok,
I have looked at both logs. I have to mentinon though that you didnt
provide the log that shows the h323 setup between cucm and the VCS. This
is most likely because the call originated from a different cucm than
the ones you provided the logs from.
The call would have orginated from the first cucm in the cucm group of
this trunk: Name=RL_TRUNK_VIDEO
The cucm ip will be : 10.252.53.10.
This is the VCS log that confirms where the h323 request originated
from:
pr 10 22:50:29 TWELDVCS01 tvcs: UTCTime="2014-04-11 01:50:29,187"
Module="network.h323" Level="DEBUG": Src-ip="10.252.53.10" Src-
port="54000"
Received RAS PDU:
Having said that here is my analysis of the logs that you sent..
Jabber sent an INVITE to CUCM and advertised all the codecs (audio and
video it can support)..
Observer that Jabber says it doesnt support G729 anexB
21:55:16.576 |//SIP/SIPTcp/wait_SdlReadRsp: Incoming SIP TCP message
from 10.223.20.73 on port 54677 index 90661 with 2220 bytes:
[862370,NET]
INVITE sip:[email protected];user=phone SIP/2.0
Via: SIP/2.0/TCP 10.223.20.73:54677;branch=z9hG4bK000029d3
From: "4122107" <sip:[email protected]>;tag=00059a3c78000011000070b0
-00000e65
To: <sip:[email protected]>
Call-ID: [email protected]
Max-Forwards: 70
Date: Fri, 11 Apr 2014 01:55:16 GMT
CSeq: 101 INVITE
User-Agent: Cisco-CSF/9.4.1
m=audio 19252 RTP/AVP 0 8 18 105 104 101
c=IN IP4 10.223.20.73
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:105 G7221/16000
a=fmtp:105 bitrate=24000
a=rtpmap:104 G7221/16000
a=fmtp:104 bitrate=32000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv
m=video 28878 RTP/AVP 97
c=IN IP4 10.223.20.73
++++Now lets observer the capabilites exchange during h245 negotiation
between cucm and VCS++++
Here CUCM advertises its caps to VCS (afterreceiving caps from VCS)
Note that G729A, G729AB, G729 is all advertised..
Apr 10 22:50:31 TWELDVCS01 tvcs: UTCTime="2014-04-11 01:50:31,017"
Module="network.h323" Level="DEBUG": Src-ip="10.252.53.10" Src-
port="45660"
Received H.245 PDU:
value MultimediaSystemControlMessage
::= request : terminalCapabilitySet
capabilityTableEntryNumber 2,
       capability receiveAudioCapability :
g729wAnnexB : 6
       capabilityTableEntryNumber 3,
   capability receiveAudioCapability : g729AnnexAwAnnexB : 6
       capabilityTableEntryNumber 4,
       capability
receiveAudioCapability : g729 : 6
capabilityTableEntryNumber 5,
       capability receiveAudioCapability :
g729AnnexA : 6
++++++
After doing MSD (master slave determination, we move to the OLC phas e..
Here we see that the far end..c40 wants to use G729AB for media++++
Apr 10 22:50:31 TWELDVCS01 tvcs: UTCTime="2014-04-11 01:50:31,783"
Module="network.h323" Level="DEBUG": Src-ip="10.224.114.11" Src-
port="11163"
Received H.245 PDU:
value MultimediaSystemControlMessage
::= request : openLogicalChannel :
   forwardLogicalChannelNumber 1,
forwardLogicalChannelParameters
     dataType audioData :
g729AnnexAwAnnexB : 20,
     multiplexParameters
h2250LogicalChannelParameters :
+++Next VCS sends G729AB as the codec to use to CUCM+++
Apr 10 22:50:31 TWELDVCS01 tvcs: UTCTime="2014-04-11 01:50:31,784"
Module="network.h323" Level="DEBUG": Dst-ip="10.252.53.10" Dst-
port="45660"
Sending H.245 PDU:
value MultimediaSystemControlMessage
::= request : openLogicalChannel :
   forwardLogicalChannelNumber 1,
forwardLogicalChannelParameters
     dataType audioData :
g729AnnexAwAnnexB : 20,
     multiplexParameters
h2250LogicalChannelParameters :
++++The next thing we get is an OLC reject from CUCM and this is where
th call drops++
Apr 10 22:50:31 TWELDVCS01 tvcs: UTCTime="2014-04-11 01:50:31,790"
Module="network.h323" Level="DEBUG": Src-ip="10.252.53.10" Src-
port="45660"
Received H.245 PDU:
value MultimediaSystemControlMessage
::= response : openLogicalChannelReject :
forwardLogicalChannelNumber 1,
   cause dataTypeNotSupported : NULL
Apr 10 22:50:31 TWELDVCS01 tvcs: UTCTime="2014-04-11 01:50:31,790"
Module="network.h323" Level="INFO": Dst-ip="10.224.114.11" Dst-
port="11163"
Detail="Sending H.245 OpenLogicalChannelRejResponse
+++We then receive a call release from cucm with cause code of 47:
resource unavailable++++
Apr 10 22:50:32 TWELDVCS01 tvcs: UTCTime="2014-04-11 01:50:32,365"
Module="network.h323" Level="DEBUG": Src-ip="10.252.53.10" Src-
port="50913"
Received H.225 PDU:
Q931
   Message Type: Release
Complete
   Call reference flag: Message sent from originating side
Call reference value: 0x7b
   Info Element : Cause
     Location: Usr
   Cause Value: Resource unavailable
   Info Element : User User
   Length = 22
Suggestions:
Change the region setting between the ICT trunk to VCS and Jabber to use
G711 and test again.

Defined Groups for Cisco Jabber Group Chat

I dont think it is possible based upon this document but wondering if anyone knew any secrets out there. Is it possible to create predefined groups in Jabber for Windows preferably as defined in Active Directory or on the client side? We want to have chat groups automatically created for Sales, Engineering, etc. so users dont have to add other chat recipients users manually and can reach any engineering team member without knowing who is actually part of the engineering team for example.
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/Windows/9/JABW_BK_C56E95B6_00_feature-guide.html

Hi,
Jabber for Windows 9.7 supports Persistent Chat end user participation.
Our next Release, 10.5 will add Room Administration and Moderator features, including room creation.
Persistent Chat Rooms
Users in your organization can use persistent chat rooms to share ideas and information in a chat room. The chat rooms look like group chats, except that the chat rooms stay active even after participants leave the room. When participants come back to the room, they can scroll back to read the messages that they missed.
Participants can manage their chat rooms by browsing the existing rooms and joining open rooms, or being added to a room by an administrator. When they are in the chat rooms, participants can create mentions for other users, which notifies the mentioned user if they are a member of the room. They can also search chat rooms for particular keywords or senders by creating filters.
Administrator tasks include creating, configuring, and deleting chat rooms, and adding or removing users from chat rooms. In this release, chat room administration and moderation must be performed with a client that supports persistent chat room administration. Cisco Jabber for Windows will provide administrative capabilities in a future release.
Cisco Unified Communications Manager IM and Presence Version 10 is a software prerequisite for persistent chat rooms.
For end user information about persistent chat rooms, see the chapter on Chats in the Advanced Feature Guide.
For administrator information about enabling persistent chat rooms, see the Installation and Configuration Guide and the Server Setup Guide.
Link for the same:
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/Windows/9_7/JABW_BK_CF8F083D_00_cisco-jabber-for-windows-97/JABW_BK_CF8F083D_00_cisco-jabber-for-windows-97_chapter_00.html
Regards,
Swathi

Softphone feature for Cisco Jabber Client

Hello everyone,
I have a CUCM cluster v.8.6.2 and a CUPS v.8.6.4. I've installed my full CUWL licenses as well as my CUP Licenses AND the Jabber for Everyone COP file. I've managed to install Jabber on Mac and on Windows and have all the features such as Chat, Desktop phone integration and Visual Voicemail with Cisco Unity Connection working as well. The only feature I'm having a huge hassle getting to work is the Softphone feature. I've tried adding a CUPC device with the user (btw everything is integrated and uses LDAP for authentication) as the digest account for it as well as the Owner ID. I've tried adding a CSF device as well (I remember reading it somewhere) but the Jabber client never discovers a Softphone device and all of the options on the client are grayed out for me to put in the device settings. I thought I saw it once looking for a device name CSFACILLI (ACILLI being my username) in the System Diagnostics for the Jabber for Mac client but now it just shows:
   Soft Phone Server
Server Address:           cucm02.mycompany.net
Server Port:                     2748
Server Protocol:           --
Device:                               --
Line ID:                               --
Status:                               Disconnected
Any help or thoughts on this would be greatly appreciated! Thanks!
Tony

Aaron,
Here's the bit I found interesting from the reporting function:
-- 2012-07-25 08:31:01.000 DEBUG [0xacab02c0] - CCUCMClient::downloadConfig -- begin:
-- 2012-07-25 08:31:01.000 DEBUG [0xacab02c0] - CCUCMClient::getCnfFile -- begin: , strDeviceName.c_str()=CSFacill, bHttp=FALSE
-- 2012-07-25 08:31:01.000 DEBUG [0xacab02c0] - CTFTPClient::Get -- begin: , remotefile=CTLFile.tlv, host=cucm02.mycompany.net, bIsAsyMode=TRUE, port=69
-- 2012-07-25 08:31:01.000 DEBUG [0xb038d000] - TFTP_Error Select error
-- 2012-07-25 08:31:01.000 DEBUG [0xb038d000] - TFTP_Error Can't get packet, retrycount=3
-- 2012-07-25 08:31:01.000 DEBUG [0xb038d000] -   CTFTPClient::ContinueGet -- end!
-- 2012-07-25 08:31:01.000 DEBUG [0xacab02c0] - CTFTPClient::Get -- end!
-- 2012-07-25 08:31:01.000 DEBUG [0xb038d000] - CTFTPClient::ReceiveData -- end!
-- 2012-07-25 08:31:01.000 DEBUG [0xacab02c0] - CCUCMClient::getCnfFile -- end!
-- 2012-07-25 08:31:01.000 DEBUG [0xacab02c0] - CCUCMClient::downloadConfig -- end!
-- 2012-07-25 08:31:01.000 DEBUG [0xacab02c0] - CPhone::setPhoneMode -- end!
-- 2012-07-25 08:31:01.000 DEBUG [0xb030b000] - CTFTPClient::ReceiveData -- begin: , nCookie=5, bIsAsyMode=TRUE
It looks like it's trying to get CTLFile.tlv from my TFTP servers (which are my subscribers). I went under TFTP File Management under OS Administration on the Subscribers and no such file exists. Is this something I have to download from Cisco? It does look like it's trying for the correct device, just can't get the Configuration File it needs... Your thoughts?
Thanks,
Tony

Cisco Jabber for Windows Voicemail issue

At this I'm in processing of implementation Cisco Jabber UC solution for big Company.
I use CUCM 9.1.2, Cisco IM and Presence 9.1.2, CUC 9.1.2, Cisco Jabber for Windows 9.6.1.
I have issue in Cisco Jabber with VoiceMail Integration - when I leave voice message for any user,
than this message is arrived only him Cisco IP Phone, but not in him Cisco Jabber.
From Cisco Jabber Connectivity status in help menu I see that VoiceMail service is successfully connected
and I see VoiceMail button in Cisco Jabber.
How can I resolve this issue?

Have you configured the UC Service profile on CUCM with both Voicemail server and mailbox servers?

Cisco Jabber for Windows 9.2.6 (setting registry keys)

All,
I would like to be able to set the general option for Cisco Jabber to force the client to, "Start Ciso Jabber when my computer starts" option. Is this a registry setting I can force? I'd also like to force calendar intergration with Microsoft Outlook by default as well. We are using SCCM to push Jabber via RAP. Are these registry settings HKCU or HKLM? Thanks Phillip

Hi Phillip,
you may find more details on Installation and Configuration guide how to set Start_Client_On_Start_OS parameter in jabberConfig file.
Keep in mind that values set in JabberlocalConfig.xml have presedence over value set in jabberConfig.xml file from TFTP server.
Regards,
Nebojsa

Cisco jabber for mac over fortigate vpn problem

Hi all,
We have installed the cisco jabber for mac successfully.Jabber client able to register locally successfully.
Calling and other features working properly. Jabber IM also working fine.
But when we try over vpn its shows error."services are missing".All the ports are open on fortigate firewall.

If you have detailed diagnostics from the Jabber Mac client, this would provide some more context to why it's displaying those errors. (Help > Detailed Logging enabled) (Help > Report a problem)
Another thing to check for would be DNS resolution of the configured servers when the Mac is VPN'd in. If Jabber cannot resolve the DNS name, it will not know where to connect to.
If the diagnostics are pointing towards a connectivity problem, but the firewall says it's wide open, then taking a packet capture on the Mac where Jabber is trying to register may illustrate what's going on at the network layer.

Android tablets supported for Cisco Jabber for Android 10.5 ?

Similar Messages

Maybe you are looking for