Guest

Preview Tool

Cisco Bug: CSCvu16257 - Sip participants disappear from WB3 browser roster when on hold

Last Modified

Jun 22, 2020

Products (1)

  • Cisco Meeting Server

Known Affected Releases

2.9

Description (partial)

Symptom:
Its is noticed that Sip participants drops from WB 3 (webrtc connected participants roaster) when sip participant places call on hold. It appears back when call is resumed. This is not the case in using web bridge 2.

========================================
Steps to reproduce

Setup WB3, make a call from WB3 browser client to space id 222

Setup Wb2 on same CMS, make a call from WB2 browser client to space id 222 (Setting up WB2 not mandatory step) it is to compare Webrtc behaviour.

Dial from Jabber into space 222
Dial from Sip C 60 device to 222
       
all participants are in call now (WB2 client , WB3 client, Jabber, C 60)


Place call on hold from Jabber. 

On WB3 browser client call, you would notice Jabber has disappeared from roaster list (not dropped)
(User experience every one  thinks Jabber Dropped the call)

On WB2 browser call, you would notice jabber is still present.

Resume Jabber call,
Jabber comes back in WB3 roaster list.
-----------
Tested same thing with C 60, Dialied into space from C 60
Placed C 60 call on hold
C 60 Dropped from WB3 call roaster list.
(User experice every one thinks C 60 Dropped the call)
C 60 stayed in WB2 roaster list.

Resumed call from C 60, C 60 appeared on Wb3 client roaster list.

So Sip calls are affected when placed in hold.

Conditions:
Its is noticed that Sip participants drops from WB 3 (webrtc connected participants roaster) when sip participant places call on hold. It appears back when call is resumed. This is not the case in using web bridge 2.

========================================
Steps to reproduce

Setup WB3, make a call from WB3 browser client to space id 222

Setup Wb2 on same CMS, make a call from WB2 browser client to space id 222 (Setting up WB2 not mandatory step) it is to compare Webrtc behaviour.

Dial from Jabber into space 222
Dial from Sip C 60 device to 222
       
all participants are in call now (WB2 client , WB3 client, Jabber, C 60)


Place call on hold from Jabber. 

On WB3 browser client call, you would notice Jabber has disappeared from roaster list (not dropped)
(User experience every one  thinks Jabber Dropped the call)

On WB2 browser call, you would notice jabber is still present.

Resume Jabber call,
Jabber comes back in WB3 roaster list.
-----------
Tested same thing with C 60, Dialied into space from C 60
Placed C 60 call on hold
C 60 Dropped from WB3 call roaster list.
(User experice every one thinks C 60 Dropped the call)
C 60 stayed in WB2 roaster list.

Resumed call from C 60, C 60 appeared on Wb3 client roaster list.

So Sip calls are affected when placed in hold.
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)
  • 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.