BOT and TCT calls

[SAIFUDEEN C .K]

We have a cluster with cucm 8.6.

When the call is made or answered from jabber for android or iphone, its getting disconnected.

Its working fine with CSF profile.when we connect the CSF profile with the same wireless network its working fine.please suggest.

When i checked the logs, reason for disconnection is "call answered elsewr"

[Jonathan Schulenberg]

CUCM 8.6 is _long_ past end of SW Support; Cisco hasn’t tested Jabber against it in years.
https://www.cisco.com/c/en/us/products/collateral/unified-communications/7800-series-media-convergence-servers/eos-eol-notice-c51-730843.html

With that disclaimer out there, here are a few ideas:
1. Make sure SNR is disabled, at least to rule it out as the cause. Improperly set Answer Too Soon timers could cause this. Consider using Mobile Identity instead of an RDP to anchor the RD.
2. Verify the Service Parameter is set properly:
https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/12_0/cjab_b_on-premises-deployment-for-cisco-jabber-12/cjab_b_on-premises-deployment-for-cisco-jabber-12_chapter_01010.html#CJAB_TK_IB7EEAEF_00
3. Verify the SIP Profile is set correctly:
https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/12_0/cjab_b_on-premises-deployment-for-cisco-jabber-12/cjab_b_on-premises-deployment-for-cisco-jabber-12_chapter_01010.html#CJAB_TK_CAA01A90_00

Don’t forget that you’ll need to upgrade CUCM to support APNS if Apple sticks by it’s timetable to deprecate the VoIP sockets API this year. Without that Jabber cannot stay registered in the background.

[SAIFUDEEN C .K]

Thank you so much for your prompt response.

I have updated the SIP timers and now the incoming calls re working fine.Now the problem is with outgoing calls.

attached is the call manager logs

calling number 6645

called number 940040289

BOT profile IP:192.168.103.20

BOT profile name:BOTHUSSAMTEST

CUCM version :8.6

Please help

[HARIS_HUSSAIN]

1) Looks like issue with H323 Configuration on Gateway. Try to cahnge MTP Required checkbox on H323 Gateway page.

10:34:51.071 |!!ERROR!! -SIPInterface-(11936)::sendMXErrorIfNoCapsInAnyMLine - an mLine has 0 caps, sending MXError|2,100,68,11936.1^*^*


*** Please rate helpful posts & Accept Solution if applicable
Thanks,
Haris

[SAIFUDEEN C .K]

Thanks for the response.

But the call is failing foir the internal calls as well.

Attached the logs for the internal calls

calling number:6645

Called number:6746

Thanks

[HARIS_HUSSAIN]

Looks like coded mismatch issue. Test by moving both Device in Same Device Pool & Region.

[SAIFUDEEN C .K]

Its already tested.

Also there is only one region in the cluster that is the default one.

[HARIS_HUSSAIN]

1) You need to create a separate SIP Profile for BOT and TCT.

Please rate helpful posts

[SAIFUDEEN C .K · Accepted solution]

The problem resolved after downgrading the jabber version to 10.5

Thank you so much for your support.

[HARIS_HUSSAIN]

Good to know that issue is resolved.