Guest

Preview Tool

Cisco Bug: CSCsg40555 - Wrong Number Connection after conference

Last Modified

Jul 04, 2017

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases

6.0

Description (partial)

Symptom:
Wrong Number Connection after conference


Conditions:
"Wrong Number Connection after conference - when a non controller(SIP TNP Phone) adds party to conference"

In Muster callp branch 6.0.0.9301-98, when a non controller (SIP TNP Phone) tries to add another party to the conference [using CoferenceByNonController function] it gives an error "Wrong Number Connection after Conference"

The Advanced ad-hoc conference is set to True.
The same scenario works fine with SCCP IP Phones.

Scenario:
A(6000) calls B(6001)
B answers
B consults with C(6002) for Conference
C answers
B completes the conference
C consults with D(6003) for Conference
D answers
C does ConferenceByNonController to add a party to the conference.

Here ConferencyByNonController is failing with the error "Wrong Number Connection after Conference"

*Traces/Logs in file attachments section
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.