Guest

Preview Tool

Cisco Bug: CSCtf24102 - RLT-CT: Late MDCX ACK for slave call will cause hung call

Last Modified

Apr 30, 2010

Products (1)

  • Applications for Cisco Unified Application Environment

Known Affected Releases

9.8(1)RLT

Description (partial)

Symptom:
Late MDCX ACK for slave call will cause hung call

Conditions:
1. SS7(ANSI) -> PGW -> SIP1
2. SIP1 send REFER to trigger call transfer to SIP2
3. PGW local handled the call transfer
Scenario1:
On the slave call from PGW to SIP2,
180 comes with no sdp, when MDCX ACK is received in master call for 180, the 200 OK comes with sdp1, and then a re-invite with sdp2 immediately arrives after PGW sending out ACK meanwhile master call is waiting for the MDCX ACK for 200 OK.
 The MDCX ACK for 200OK was delayed for 2 seconds, PGW didn't send out the 2nd NOTIFY to the first SIP leg and we got a hung call there.
Scenario2:
180 comes with sdp1, 200 OK comes immediately before the MDCX ACK for 180 in master call, and then a re-invite with sdp2 immediately arrives after PGW sending out ACK meanwhile master call is waiting for the MDCX ACK for 180.
The MDCX ACK for 200OK was delayed for 2 seconds, PGW didn't send out the 2nd NOTIFY to the first SIP leg and we got a hung call there.
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.