Cisco Bug: CSCum77559 - Jabber should not register with mode Cellular when no MI configured
Oct 30, 2014
- Cisco Unified Mobile Communicator
Known Affected Releases
Symptom: Jabber for Android is unable to register as a VoIP phone when using the cellular network for connectivity. The client logs will show the following response from Unified CM when Jabber attempts to register: csf.ecc.sipcc][_SIPCCLoggerFunction] sipio-recv<--- SIP/2.0 400 Bad Request The Unified CM SDL trace will indicate the following: AppInfo |DMMS: (0000909) - isMobileClientDMIConfigured, no MI configured And the SIP register response signal will show: ccbID= 45057342 --TransType=3 --TransSecurity=0 PeerAddr= 172.18.106.225:5061 respCode= 400 action= 2 device= Conditions: Occurs when a Jabber client is configured with Dial via Office enabled, but not Mobile Identity (MI) has been configured on the device and the client is attempting to register through Collaboration Edge while on a Cellular (not WiFi) network.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases