jabber for voice call disconnected

[tahirjamil]

Hi Everyone,

I have an issue of call disconnecting only from jabber (both android and ios). The call ringing but when any party accept the call the call get disconnected. All other phones and 3rd party phones are working fine. the issue is only with jabber for mobile. I didn't try jabber for windows

I am attaching a sample call logs please help me to find the issue as I have wasted 3 days to fix it but still couldn't find any lead to fix up.

Here are the details.

CUCM version 8.6

Calling party 6365 (Android jabber)

Called party 7270 ( sccp 6941 phone)

Regards

Tahir

[Nithin Eluvathingal]

Can you explain bit more about your setup? is there a firewall in between deskphone and  WIFI subnet.  

From the log there is  SIP/2.0 503 Service Unavailable with Reason: Q.850;cause=47

Both Jabber and deskphone are they on same device pool ? are they both in same region ?

[tahirjamil]

There is no any firewall between ip phone and Wireless. I tried even call between both jabber devices on same wireless network. Every time behaviour is same. Region device pool css everything is same. I have tested these jabber devices a year earlier without any issue. Only jabber version is different and strange why it is disconnected.
Whata about codec negotiation. I couldn't find any info from log that which codec is being negotiated.

[Nithin Eluvathingal]

Your invite sends g722, after 180 ringing you are receiving 503 service unavailable. if it was working with old jabber version, stick with the same version. because your  CUCM version is outdated and EOL.

[Scott Leport]

Hi there,

Having reviewed your log file I see the following disconnect cause code:

SIP/2.0 503 Service Unavailable
Via: SIP/2.0/TCP 10.11.204.42:51702;branch=z9hG4bK4eb441cd
From: "Naushad Ahmad" <sip:6365@10.1.100.11>;tag=a3b4e230e9ad00250ed37dcd-5ee82555
To: <sip:7270@10.1.100.11>;tag=4936898~0e952dd0-d0d8-4c9f-859c-c6dc8d9543ad-47091735
Date: Thu, 03 Jun 2021 08:01:40 GMT
Call-ID: a3b4e230-e9ad0017-172c4fee-5e339e24@10.11.204.42
CSeq: 101 INVITE
Allow-Events: presence
Reason: Q.850;cause=47
Content-Length: 0

Typically that's codec or media resource related. Do you have Media Termination point selected on the Jabber for Android device?

[tahirjamil]

Yes, 

media recourse group list contained MTP into, other soft phones like zoper/xlite are working without any issue on same network. the issue is only with jabber devices i.e android/IOS

[Vaijanath Sonvane]

Hi,

The logs indicate that the extension 6365 is registered as a TCT device which is used for Jabber for iPhone:

REGISTER sip:10.1.100.11 SIP/2.0
Via: SIP/2.0/TCP 10.11.204.42:51702;branch=z9hG4bK2aebcb10
From: <sip:6365@10.1.100.11>;tag=a3b4e230e9ad002429e58066-1a50be07
To: <sip:6365@10.1.100.11>
Call-ID: a3b4e230-e9ad0014-0c6a520e-18311b80@10.11.204.42
Max-Forwards: 70
Date: Thu, 03 Jun 2021 08:01:32 GMT
CSeq: 112 REGISTER
User-Agent: Cisco-TCT
Contact: <sip:a14a7fbc-9993-ffce-e068-6f347f3c2c86@10.11.204.42:51702;transport=tcp>;+sip.instance="<urn:uuid:00000000-0000-0000-0000-a3b4e230e9ad>";+u.sip!devicename.ccm.cisco.com="TCT-NAUSHAD";+u.sip!model.ccm.cisco.com="562";video;bfcp
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,X-cisco-graceful-reg,X-cisco-duplicate-reg,X-cisco-voicepush-status
Expires: 3600
Content-Length: 0

You mentioned 6365 as Android Jabber. If it is Android then you need to configure it as BOT. Do you have correct phone profile configured?

[Vaijanath Sonvane]

1. Are you facing this issue only when calling from Android/iPhone Jabber to Cisco 6941 SCCP Phones and vice versa.
2. Does Jabber to Jabber calls work?

[tahirjamil]

Yes,

Jabber to Jabber and jabber to other devices. other 3rd party apps are working fine

[tahirjamil]

You are correct, 
I tried same user with both BOT and TCT. these logs were generated when I used IOS. it I think device wouldn't registered if I may use wrong profile.

Regards

Tahir

[Sergio Quezada]

Hello Tahir,

Also remove the - should Device Name should be BOTNAUSHAD. Also make sure that your Security Profile is configured properly and make sure you associate the profile to your End User Profile
Configuring CUCM End Users

The CUCM end user configuration is a crucial step in deploying Jabber for iPhone as many of Jabbers features are dependent on this configuration. The image below depicts all the Jabber configurations that are dependent on the CUCM end user configuration.

https://www.cisco.com/c/en/us/support/docs/unified-communications/jabber-iphone/213950-jabber-for-iphone-quick-start-guide.html

Regards,
Sergio Quezada