DefinityG3R
Technical User
Current call flow:
SIP Trunk:
Avaya version 5.x >Cisco CUPS (stateless proxy) > Call Manager version 6.x
Call setup appears to work fine. In addition, RTP is established without issue.
The problem I've been trying to solve for the past few weeks is concerning Avaya tearing down the call properly. Everything works fine, but if CUCM sends a "BYE", the Avaya system never returns an "OK". This results in a hung call leg on Avaya. The CUCM call will eventually tear down once my timers expire.
Has anyone seen this behavoir from Avaya when working with a SIP trunk from CUCM? I've looked over the "BYE" message I send to Avaya and don't see any issue with it. I've confirmed the Avaya does in fact see the "BYE" with wireshark but for whatever reason Avaya never sends an "OK" response.
Can someone take a look at the BYE message I'm sending to Avaya and see if anything is out of place? Anyone seen this before?
BYE sip:10.240.x.x:5060;transport=tcp SIP/2.0
Route: <sip:10.240.x.x;lr;transport=tcp>
Date: Tue, 12 May 2009 20:23:29 GMT
From: "1997960003" <sip:1997960003@10.240.x.x>;tag=146fd5a0-c8f5-4688-a298-2edf23d2f4d7-17270199
Content-Length: 0
User-Agent: Cisco-CUCM6.1
To: "Station for Agent 7941021" <sip:anonymous@anonymous.invalid>;tag=80fe9451d24a de1d3c49f9bd1d00
Call-ID: 80fe9451d24ade1d4c49f9bd1d00
Via: SIP/2.0/TCP 10.240.x.x:5060;branch=z9hG4bK1267fd44c4
CSeq: 101 BYE
Max-Forwards: 70
SIP Trunk:
Avaya version 5.x >Cisco CUPS (stateless proxy) > Call Manager version 6.x
Call setup appears to work fine. In addition, RTP is established without issue.
The problem I've been trying to solve for the past few weeks is concerning Avaya tearing down the call properly. Everything works fine, but if CUCM sends a "BYE", the Avaya system never returns an "OK". This results in a hung call leg on Avaya. The CUCM call will eventually tear down once my timers expire.
Has anyone seen this behavoir from Avaya when working with a SIP trunk from CUCM? I've looked over the "BYE" message I send to Avaya and don't see any issue with it. I've confirmed the Avaya does in fact see the "BYE" with wireshark but for whatever reason Avaya never sends an "OK" response.
Can someone take a look at the BYE message I'm sending to Avaya and see if anything is out of place? Anyone seen this before?
BYE sip:10.240.x.x:5060;transport=tcp SIP/2.0
Route: <sip:10.240.x.x;lr;transport=tcp>
Date: Tue, 12 May 2009 20:23:29 GMT
From: "1997960003" <sip:1997960003@10.240.x.x>;tag=146fd5a0-c8f5-4688-a298-2edf23d2f4d7-17270199
Content-Length: 0
User-Agent: Cisco-CUCM6.1
To: "Station for Agent 7941021" <sip:anonymous@anonymous.invalid>;tag=80fe9451d24a de1d3c49f9bd1d00
Call-ID: 80fe9451d24ade1d4c49f9bd1d00
Via: SIP/2.0/TCP 10.240.x.x:5060;branch=z9hG4bK1267fd44c4
CSeq: 101 BYE
Max-Forwards: 70