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.

Similar Messages

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 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!

Cisco Jabber for Android on a Samsung Galaxy Xcover (GT-S5690)

Hello there,
Yesterday we installed the Cisco Jabber client for Android on the Samsung Galaxy Xcover (GT-S5690) phone.
First we had some issue's with one-way voice, but suddenly this problem was occured.
Another problem, which is still there, is when you wants to check your compagny Voicemail (Unity) with the Cisco Jabber client.
We can access the Voicemail system (Unity), the we must fill-in the pincode followed by hash.
As you can see in the attached file, this can't be done.
Samsung Galaxy xCover (GT-S5690)
Samsung Galaxy S2
The reason is the screen size of the display of the difference of the phones.
Hopefully can this small issue be fixed. Our customer ordered 150x Samsung Galaxy XCOVER (GT-S5690) for working with Cisco Callmanager.
Technical Information:
Cisco Callmanager version 8.6.20000
Samsung Galaxy XCover (GT-S5690)
Android version: 2.3.6
If someone knows a solution of can support me, please let me kwon!
Kind regards,
Edgar Verbaten
Elkor Telecom & ICT
[email protected]

Hi Edgar
How does this phone work with the Jabber ?
I have a customer which about a dozen of these phones and it only vibrates on incoming calls but doesn't ring.
Same Android version : 2.3.6 -
Regards
Andri

Cisco Jabber for Windows unable to make calls in softphone mode

Hi,
I am facing an issue when I make a call from jabber in softphone mode to another jabber client my call fails and using wireshark traces I see SIP2.0 503 Service Unavailable.
I have followed the guide and was able to deploy it once before successfully. This is a lab environment and we don't have any CSS or partitions.
If someone can please guide me :)
Regards
Hassan

Hi Hassan,
I found four calls in the trace file with the same calling/called numbers. I analyzed one of them.
Calling party - 42001
Called party - 42002
00267676.002 |17:15:14.335 |AppInfo |SIPTcp - wait_SdlReadRsp: Incoming SIP TCP message from 122.129.75.131 on port 23600 index 689 with 2610 bytes:
[7525,NET]
INVITE sip:[email protected];user=phone SIP/2.0
Via: SIP/2.0/TCP 192.168.1.60:54441;branch=z9hG4bK00005d94
From: "42001" <sip:[email protected]>;tag=3c77e6734e8e00180000789e-000014f2
To: <sip:[email protected]>
Call-ID: [email protected]
Max-Forwards: 70
Date: Tue, 21 Apr 2015 11:29:56 GMT
CSeq: 101 INVITE
User-Agent: Cisco-CSF
Contact: <sip:[email protected]:54441;transport=tcp>;video;bfcp
Expires: 180
Accept: application/sdp
Allow: ACK,BYE,CANCEL,INVITE,NOTIFY,OPTIONS,REFER,REGISTER,UPDATE,SUBSCRIBE,INFO
Remote-Party-ID: "42001" <sip:[email protected]>;party=calling;id-type=subscriber;privacy=off;screen=yes
Supported: replaces,join,sdp-anat,norefersub,resource-priority,extended-refer,X-cisco-callinfo,X-cisco-serviceuri,X-cisco-escapecodes,X-cisco-service-control,X-cisco-srtp-fallback,X-cisco-monrec,X-cisco-config,X-cisco-sis-7.0.0,X-cisco-xsi-8.5.1
Allow-Events: kpml,dialog
Recv-Info: conference
Recv-Info: x-cisco-conference
Content-Length: 1469
Content-Type: application/sdp
Content-Disposition: session;handling=optional
v=0
o=Cisco-SIPUA 5552 0 IN IP4 192.168.1.60
s=SIP Call
b=AS:4000
t=0 0
m=audio 21996 RTP/AVP 9 104 105 0 8 18 101
c=IN IP4 192.168.1.60
a=rtpmap:9 G722/8000
a=rtpmap:104 G7221/16000
a=fmtp:104 bitrate=32000
a=rtpmap:105 G7221/16000
a=fmtp:105 bitrate=24000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv
m=video 25898 RTP/AVP 126 97
c=IN IP4 192.168.1.60
b=TIAS:4000000
a=rtpmap:126 H264/90000
a=fmtp:126 profile-level-id=42E01F;packetization-mode=1;level-asymmetry-allowed=1;max-fs=3601;max-rcmd-nalu-size=32000
a=imageattr:126 recv [x=[32:1:1280],y=[18:1:720],par=1.7778,q=1.00]
a=content:main
a=label:11
a=rtpmap:97 H264/90000
a=fmtp:97 profile-level-id=42E01F;packetization-mode=0;level-asymmetry-allowed=1;max-fs=3601
a=imageattr:97 recv [x=[32:1:1280],y=[18:1:720],par=1.7778,q=1.00]
a=sendrecv
m=video 32652 RTP/AVP 126 97
c=IN IP4 192.168.1.60
b=TIAS:4000000
a=rtpmap:126 H264/90000
a=fmtp:126 profile-level-id=42E01F;packetization-mode=1;level-asymmetry-allowed=1;max-fs=4099;max-rcmd-nalu-size=32000
a=content:slides
a=label:12
a=rtpmap:97 H264/90000
a=fmtp:97 profile-level-id=42E01F;packetization-mode=0;level-asymmetry-allowed=1;max-fs=4099
a=sendrecv
m=application 5070 UDP/BFCP *
c=IN IP4 192.168.1.60
a=floorctrl:c-s
a=confid:4
a=floorid:2 mstrm:12
a=userid:4
a=setup:actpass
a=connection:new
a=sendrecv
00267702.007 |17:15:14.342 |AppInfo |Digit analysis: match(pi="2", fqcn="42001", cn="42001",plv="5", pss="", TodFilteredPss="", dd="42002",dac="0")
00267702.008 |17:15:14.342 |AppInfo |Digit analysis: analysis results
00267702.009 |17:15:14.342 |AppInfo ||PretransformCallingPartyNumber=42001
|CallingPartyNumber=42001
|DialingPartition=
|DialingPattern=42002
00267709.001 |17:15:14.343 |AppInfo |LBMIF: CI: 30582939 ASSOC    30582940
00267709.002 |17:15:14.343 |AppInfo |LBMIF: CI: 30582940 ASSOC'   30582939
00267715.000 |17:15:14.343 |SdlSig   |CcSetupReq                             |restart0                       |LineControl(1,100,174,27)        |Cdcc(1,100,219,42)               |1,100,14,10382.36^122.129.75.131^CSFHASSANRAZI |[R:N-H:0,N:2,L:0,V:0,Z:0,D:0] CI=30582940 CI.branch=0 sBPL.plid=65 sBPL.l=1 sBPL.pl=5 sBPL.msd=0 FDataType=0opId=0ssType=0 SsKey=0invokeId=0resultExp=Fbpda=F pi.piid=30 pi.l=0 pi2.piid=30 pi2.l=0 pi3.piid=30 pi3.l=0 FQCGPN=ti=1nd=42001pi=0si1 preXCgpn=tn=0npi=0ti=1nd=42001pi=0si1 cgPart= cgPat=42001 cgpn=tn=0npi=0ti=1nd=42001pi=1si1 cgpnVM= unXCgpn=tn=0npi=0ti=1nd=42001pi=1si1 cName=locale: 1 Name: UnicodeName: pi: 1 DD=tn=0npi=1ti=1nd=42002User=42002Host=192.168.201.101Port=5060PassWord=Madder=Transport=4mDisplayName=RawUrl=sip:[email protected];user=phoneOrigPort=0pi=0si1 origDD=tn=0npi=1ti=1nd=42002User=42002Host=192.168.201.101Port=5060PassWord=Madder=Transport=4mDisplayName=RawUrl=sip:[email protected];user=phoneOrigPort=0pi=0si1 preXCdpn=tn=0npi=0ti=1nd=42002pi=0si0 preXTagsList=SUBSCRIBER preXPosMatchList=42002 cdPart= cdPat=42002 cdpn=tn=0npi=0ti=1nd=42002pi=1si1 cdpnVMbox= localPatternUsage=2 connectedPatternUsage=2 itrPart= itrPat= LRPart= LRPat=42002 LR=tn=0npi=0ti=1nd=42002pi=0si1 LRVM= LRName=locale: 1 Name: UnicodeName: pi: 0 FQOCpdn=ti=1nd=42002pi=0si1 fFQLRNum=ti=1nd=42002pi=0si1 oPart= oPat=42002 oCpdn=tn=0npi=0ti=1nd=42002pi=0si1 oCdpnVM= oRFR=0 oName=locale: 1 Name: UnicodeName: pi: 0 ts=SUBSCRIBER posMatches=42002 withTags= withValues= rdn.l=0IpAddrMode=0 ipAddrType=0 ipv4=122.129.75.131:23600 region=Default capCount=7 ctiActive=F ctiFarEndDev=1 ctiCCMId=1 cgPtyDev=CSFHASSANRAZI callInst=0 confCallInst=0 OLF=1Supp DTMF=3DTMF Cfg=1DTMF Payload=101isOffNetDev=F bc.l=4 bc.itr=8 bc.itc=8 bc.trm=6 bc.tm=16 maxForwards=69 cgpnMaskedByRedirect=F callingDP=1b1b9eb6-7803-11d3-bdf0-00108302ead1 featCallType=0 callingUserId= UnicodeName: muteEnabled=0 associatedCallCI=0 featurePriority=1 nonTargetPolicy=0 unconsumedDigits= suppressMOH=F numPlanPkid =6807b55c-7ab5-4f8d-8fba-db383ecfaaa4 networkDomain= bitMask=0 SetupReason=0 routeClass=1 sideACmDeviceType=4 protected=1 ControlProcessType=0 tokens=0 isPresent=F transitCount=0 geolocInfo={geolocPkid=, filterPkid=, geolocVal=, devType=4} locPkid=29c5c1c4-8871-4d1e-8394-0b9181e8c54d locName=Hub_None deductBW=F fateShareId=StandAloneCluster:30582939 videoTrafficClass=Desktop oFromAnalogDvc=F bridgeParticipantID= callingUsr= remoteClusterID= isEMCCDevice=F lHPMemCEPN= cHPMemCEPN= uri=ti=1User=Host=Port=0PassWord=Madder=Transport=4mDisplayName=RawUrl=<sip:[email protected]:54441;transport=tcp>OrigPort=0pi=0si1 param=;video;bfcp M=Unknown ;rc=26624 Hdrs= CanSupportSIPTandN=true TransId=0 AllowBitMask=0x7bf UserAgentOrServer=Cisco-CSF OrigDDName=locale: 1 Name: UnicodeName: pi: 0 mCallerId= mCallerName=LatentCaps=null icidVal= icidGenAddr= oioi= tioi= ptParams= receivedPAID= routeHdr= routeCepn= requestURI= PCVFlag=F originallyHadISUP=F isIMSFinalRoute=F IMSMode=0 SideABibEnabled= 0 isCgpnNonPreemptable=F isCdpnNonPreemptable=F origDP=1b1b9eb6-7803-11d3-bdf0-00108302ead1 lastRedirectingDP=1b1b9eb6-7803-11d3-bdf0-00108302ead1 originalLRG= lastRedirectingLRG= nwLoc=0 rstr= FarEndDeviceName=CSFHASSANRAZI hdrMOH=0 CAL={v=ffffffff, m=ffffffff, tDev=F, res=F, devType=0}
00267715.001 |17:15:14.343 |AppInfo |LineControl(27) - 0 calls, 0 CiReq, busyTrigger=2, maxCall=6
00267715.002 |17:15:14.343 |Created |                                       |                               |LineCdpc(1,100,175,74)           |LineControl(1,100,174,27)        |                                         |NumOfCurrentInstances: 2
00267758.001 |17:15:19.364 |AppInfo |//SIP/Stack/Info/0x0/ccsip_process_sipspi_queue_event: ccsip_spi_get_msg_type returned: 2 (SIP_NETWORK_MSG), for event 55 (SIPSPI_EV_SEND_FAILURE_MSG)
00267758.002 |17:15:19.364 |AppInfo |//SIP/Stack/Info/0x0xe5136ad8/ccsip_spi_process_event: Send Error for event(0xe5139420)
00267758.003 |17:15:19.364 |AppInfo |//SIP/Stack/Error/0x0/act_idle_send_msg_failure: Send Error to 192.168.1.172:54901 for transport TCP
00267758.004 |17:15:19.364 |AppInfo |//SIP/Stack/Info/0x0xe5136ad8/ccsip_set_cc_cause_for_spi_err: Categorized cause:38, category:186
00267758.005 |17:15:19.364 |AppInfo |//SIP/Stack/Info/0x0xe5136ad8/sipSPIInitiateDisconnect: Initiate call disconnect(38) for outgoing call
00267758.006 |17:15:19.364 |AppInfo |//SIP/SIPHandler/ccbId=4212/scbId=0/ccsip_api_call_disconnected: ccb->cc_disc_cause (38); ccb->sip_disc_cause(503)
00267794.001 |17:15:19.367 |AppInfo |SIPTcp - wait_SdlSPISignal: Outgoing SIP TCP message to 122.129.75.131 on port 23600 index 689
[7527,NET]
SIP/2.0 503 Service Unavailable
Via: SIP/2.0/TCP 192.168.1.60:54441;branch=z9hG4bK00005d94;received=122.129.75.131
From: "42001" <sip:[email protected]>;tag=3c77e6734e8e00180000789e-000014f2
To: <sip:[email protected]>;tag=4211~132b515c-f941-ca80-8023-9423185ada2d-30582939
Date: Tue, 21 Apr 2015 12:15:14 GMT
Call-ID: [email protected]
CSeq: 101 INVITE
Allow-Events: presence
Server: Cisco-CUCM10.5
Reason: Q.850; cause=41
Content-Length: 0
Seems like a network issue. TCP connection can't be established with the called jabber client, which as per the trace is 192.168.1.172.
Check for firewalls blocking the connection.
You may take a pcap on the called jabber client side or probably from the call manager, and check for TCP issues.
You mentioned the jabber client's IP as 192.168.1.60 but I see incoming invite from 122.129.75.131. What this IP?
HTH,
Atul

Cisco jabber for android crashes on samsung s5 mini when proxy is configured

We are a facing a strange problem with samsung galaxy s5 mini, android 4.4.2 and the latest Cisco Jabber client available on play store.
Cisco Jabber crashes on startup every time because in the wifi connection we manually configured a proxy.
If we disable the proxy in the wifi settings, cisco jabber works!!
No traffic is passed to proxy, we also tried to configure a non-existent proxy and Jabber crashes again...
Any help would be appreciated!

Hi Edgar
How does this phone work with the Jabber ?
I have a customer which about a dozen of these phones and it only vibrates on incoming calls but doesn't ring.
Same Android version : 2.3.6 -
Regards
Andri

Can I change font in Cisco Jabber for Android client

I have Cisco Jabber 10.6.0.xxxxx on my Android phone.
My team tells me that the font they see when I use this is tiny (like 6 point) compared to when I jabber from my desktop.
I cannot find where this can be changed and I need to make this font larger or this is largely useless functionality. Messaging isn't much use if it's too tiny for people to read.
Can someone describe how to make this to at least 8 or perhaps 10 pt.?

Text files have no concept of font. They contain (generally) 8-bit characters represented in ASCII.
If you want to store font information, you need to coose a format that supports this like html or pdf.

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.

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.

Cisco Jabber for Windows in Extend and Connect mode and making outbound calls

Hi guys,
I've set up Cisco Jabber for Windows to use Extend and Connect to control a remote PBX endpoint. I've configured the required CTI-RD device, remote destinations, associated the users to the line and added the devices to end-user controlled device. The extend and connect part is working flawlessly without any issues. I'm able to receive inbound calls on the remote PBX endpoint and control the call (hold, resume, transfer etc.) using the Jabber call window that pops up.
However, I'm unable to make any outbound calls via the Jabber client when in extend and Connect mode. Reading the Extend and Connect guide, I need to configure Dial Via Office (DVO) Reverse. So when the user initiates a Dial-Via-Office reverse call, CUCM calls and connect to the Extend and Connect device (CTI-RD). CUCM then calls and connects to the number the user dialled and finally connects the two call legs.
After attempting to configure DVO-R for Jabber for Windows in Extend and Connect mode following the CUCM feature services guide, i'm unable to get any outbound calls working. From RTMT, i am receiving the following Termination Cause Code: (27) Destination out of order. What i also notice is that there is no calling number for that trace either. I would've thought that the calling party would've been the Enterprise Feature Access (EFA) number.
Has anyone got this working or can provide some guidance?
Thanks.

Hi guys,
I've set up Cisco Jabber for Windows to use Extend and Connect to control a remote PBX endpoint. I've configured the required CTI-RD device, remote destinations, associated the users to the line and added the devices to end-user controlled device. The extend and connect part is working flawlessly without any issues. I'm able to receive inbound calls on the remote PBX endpoint and control the call (hold, resume, transfer etc.) using the Jabber call window that pops up.
However, I'm unable to make any outbound calls via the Jabber client when in extend and Connect mode. Reading the Extend and Connect guide, I need to configure Dial Via Office (DVO) Reverse. So when the user initiates a Dial-Via-Office reverse call, CUCM calls and connect to the Extend and Connect device (CTI-RD). CUCM then calls and connects to the number the user dialled and finally connects the two call legs.
After attempting to configure DVO-R for Jabber for Windows in Extend and Connect mode following the CUCM feature services guide, i'm unable to get any outbound calls working. From RTMT, i am receiving the following Termination Cause Code: (27) Destination out of order. What i also notice is that there is no calling number for that trace either. I would've thought that the calling party would've been the Enterprise Feature Access (EFA) number.
Has anyone got this working or can provide some guidance?
Thanks.

Transfer VOIP Calls Between Cisco Desk Phone and Cisco Jabber For IPhone 9.5

Does anyone know how to transfer an active voip call from a Cisco IP Desk Phone to Cisco Jabber for IPhone? I can transfer a call from Cisco Jabber for IPhone to my Cisco IP Desk Phone no problem. I put the call on hold and then click "Resume" on my Cisco IP Desk Phone. However I cannot do the same but the other way around. If I put the call on hold on my Cisco IP Desk Phone, I see "no active call" on my Jabber client. The only information I could find slighlty relevant was using the Mobility Key/Remote Destination Profile feature however this defeats the object as this will forward to an external number, e.g. mobile and I just want to transfer the call within the VOIP environment between the two devices that are using the same directory number.
I am using Cisco Call Manager 9.1(2), Cisco Presence 9.1 and Cisco Jabber for IPhone 9.5.
Any help would be greatly appreciated.
Kind Regards,
Paul Parker.

Did you ever find an answer to this ?
I am seeing the same behavior and trying so see if I can put calls on hold and pick them up both ways also.
The only answer I seem to have found is to use park instead
That would/should work but I would just prefer to hold/unhold
Just not sure why we would not be able to hold/unhold on what is essentially a "shared" line
Does anyone have this working for them ?

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 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.

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)

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.

Cisco jabber for android no ask outgoing call

Similar Messages

Maybe you are looking for