Guest

Preview Tool

Cisco Bug: CSCus38404 - Extended conference is terminated for the original end time

Last Modified

May 04, 2015

Products (1)

  • Cisco TelePresence Management Server

Known Affected Releases

14.5

Description (partial)

Symptom:
Extended conference is terminated for the original end time.

Conditions:
Book and edit conferences with the following steps.

1. Book a conference(ConfA).
- Participants: EndpointA and MCU.
  - The participant EndpointA call to the MCU by SIP.
  - SIP URI is sip:1000@example.com
- Start Time: Jan-1 2:00 PM
- End Time: Jan-1 2:30 PM

2. Book another conference(ConfB).
- Participants: EndpointB and MCU.
  - The participant EndpointB call to the MCU by SIP.
  - SIP URI is sip:1000@example.com
    -> This SIP URI is same as the ConfA because the conference time is not duplicated with the ConfA.
- Start Time: Jan-2 2:30 PM
- End Time: Jan-2 3:00 PM

3. Edit the ConfB's Start/End Time.
- Start Time: Jan-1 2:30 PM
- End Time: Jan-1 3.00: PM
- SIP URI is still 1000@example.com because the conference time is not duplicated with the ConfA.

4. The ConfA is started for Jan-1 at 2:00 PM as scheduled. The EndpointA place a SIP call to the MCU with the SIP URI - sip:1000@example.com.

5. Edit the ConfA's End Time to Jan-1 2:40 PM. Then, SIP URI for the ConfA is changed to sip:1001@example.com on the TMS. However, the conference which has the SIP URI sip:1001@example.com is not created on the MCU.

6. The ConfB is started for Jan-1 at 2:30 PM as scheduled and the ConfA is disconnected.
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.