Cisco Bug: CSCvs92936 - Jabber takes around 2 seconds to respond to a SIP INVITE during an escalation to ad-hoc conf
Mar 09, 2020
- Cisco Jabber for Windows
Known Affected Releases
Symptom: When adding a Jabber client to a ad-hoc call, it takes a around 2 seconds for Jabber to reply to one of the SIP INVITE flow is following: - Endpoint 1 calls Endpoint 2 - call is established between Endpoint 1 and Endpoint 2 - Jabber calls Endpoint 1 - The "Add" button is used on Endpoint 1 to answer the call from Jabber and escalate it to ad-hoc call directly - in the SIP messages, we can see that Endpoint 1 replies to the INVITE from Jabber with 200 OK. Then ACK is sent by Jabber. - Endpoint 1 then puts the call with Jabber on hold in order to merge. To do so, Endpoint 1 sends another SIP INVITE with the a attributes for each media set to inactive in the SDP. - Jabber takes 2 seconds before replying to that INVITE. Conditions: .
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