Preview Tool

Cisco Bug: CSCuj88210 - CSEQ out of order for multiway

Last Modified

Jul 13, 2019

Products (1)

  • Cisco Jabber Video for TelePresence (Movi)

Known Affected Releases

4.5 4.6 4.7

Description (partial)

VCSC X7.2.2, Conductor XC2.2 and TPS 7010 3.1(1.80), MX300 TC6.2.0 and jabber for video clients. Conductor is configured with B2BUA with VCS. CU is trying multiway using Conductor and the merge only join one of the jabber video client.

Recreated the issue in the lab by setting FindMe to tac2.lab and jabber video registrations as vc.tac2.lab. VCS is setup with AD database with NTLM authentication set to Auto.
MX300 calls jabber client 1, puts on hold and then calls client 2. After merging, only one client joins the conference while MX300 and second client still remains on hold.

MOVI sends CSeq: 501 NOTIFY
VCS Challenges with 407 Proxy Authentication Required
Retry with 502 NOTIFY
Second 407
Retry with 503 NOTIFY

MX receives 503 NOTIFY then receives 502 INVITE and kills the 502 INVITE which terminates the entire call.  Reading RFC, this seems to be ok here from MX side.  MOVI should have generated 504 INVITE and not a CSEQ lower then the previous request.
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.