[Home]

Summary:ASTERISK-02485: Asterisk does not respond to BYE message when context is set to canreinvite=Yes
Reporter:tschroer (tschroer)Labels:
Date Opened:2004-09-27 13:54:37Date Closed:2011-06-07 14:10:26
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Channels/chan_sip/Interoperability
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) asterl3.02.txt
Description:When inbound carrier context is set to canreinvite=yes, asterisk will not respond to BYE messages sent.

The configuration consists of Carrier A sending an INVITE to * which in turn routes it to a proxy (SNOM4S).  The call progresses normally until the Calling party (PSTN side in this case) hangs up (sends a BYE).  The context for Carrier A is set up to canreinvite=yes.  Asterisk Version CVS-HEAD-06/04/04-11:43:17

When a call comes into * from the Carrier and subsequently hangs up first, it will issue a BYE several times to which * will not respond.  In other words, * should respond back to the BYE with an OK and send a BYE message to the UA (In this case via a SNOM proxy) however, it does not.  It (*) only appears to respond after it has received a BYE from the UA.  See attached uploaded sip_scenario file.

Below is the BYE message * receives from the Carrier.  I have seen some other comments in the mail forums on improper Contact field formation in the BYE message as being problematic, however, this does not appear to be the case in this situation.

SIP MESSAGE 24   11.10.10.2:53125() -> 12.10.10.1:5060()
UDP Frame 9265     27/Sep/04 11:08:48.5483 TimeFromPreviousSipFrame=19.2678 TimeFromStart=33.7414
BYE sip:+18665551212@12.10.10.1 SIP/2.0
Via: SIP/2.0/UDP 11.10.10.2:5060;branch=z9hG4bK50603522629634-1095983230725
From: <sip:+19725551000@11.10.10.2>;tag=VPSF50603522629634
To: <sip:+18665551212@12.10.10.1:5060>;tag=as504a4cb2
Call-ID: DEN05020040927160824001615@11.10.10.214
CSeq: 103 BYE
Contact: <sip:11.10.10.2:5060;transport=udp>
Max-Forwards: 69
Content-Length: 0

SIP debug comes back with the following message after receiving the BYE from the Carrier:
Sep 27 14:27:45 DEBUG[1116957488]: chan_sip.c:6303 handle_request: Ignoring out of order packet 103 (expecting 2)


NOTE: When context is set to canreinvite=no, * will properly respond to the BYE by responding back with an OK and sending a BYE to the other UA.

****** ADDITIONAL INFORMATION ******

Below is a summary example of the call flow between ...

11.10.10.2 <--->12.10.10.1:5060 <----> 192.10.10.1:5060
Carrier A          Asterisk               SNOM Proxy

Source Destination Info
11.10.10.2 12.10.10.1 Request: INVITE sip:+18885551212@12.10.10.1:5060, with SDP
12.10.10.1 11.10.10.2 Status: 100 Trying
12.10.10.1 192.10.10.1 Request: INVITE sip:8665551212@mydomain.net, with SDP
192.10.10.1 12.10.10.1 Status: 100 Trying
192.10.10.1 12.10.10.1 Status: 180 Ringing
12.10.10.1  11.10.10.2 Status: 180 Ringing
192.10.10.1 12.10.10.1 Status: 180 Ringing
192.10.10.1 12.10.10.1 Status: 180 Ringing
192.10.10.1 12.10.10.1 Status: 180 Ringing
192.10.10.1 12.10.10.1 Status: 180 Ringing
192.10.10.1 12.10.10.1 Status: 180 Ringing
192.10.10.1 12.10.10.1 Status: 200 OK, with SDP
12.10.10.1 192.10.10.1 Request: ACK sip:8665551212*mydomain.net=69.25.25.1+61897@68.100.100.1:5067
12.10.10.1 11.10.10.2 Status: 200 OK, with SDP
12.10.10.1 192.10.10.1 Request: INVITE sip:8665551212*mydomain.net=69.25.25.1+61897@68.100.100.1:5067, with SDP
192.10.10.1 12.10.10.1 Status: 100 Trying
11.10.10.2 12.10.10.1 Request: ACK sip:+18885551212@12.10.10.1
12.10.10.1 11.10.10.2 Request: INVITE sip:11.10.10.2:5060, with SDP
11.10.10.2 12.10.10.1 Status: 100 Trying
11.10.10.2 12.10.10.1 Status: 200 OK, with SDP
12.10.10.1 11.10.10.2 Request: ACK sip:11.10.10.2:5060
192.10.10.1 12.10.10.1 Status: 200 OK, with SDP
12.10.10.1 192.10.10.1 Request: ACK sip:8665551212*mydomain.net=69.25.25.1+61897@68.100.100.1:5067
11.10.10.2 12.10.10.1 Request: BYE sip:+18885551212@12.10.10.1
11.10.10.2 12.10.10.1 Request: BYE sip:+18885551212@12.10.10.1
11.10.10.2 12.10.10.1 Request: BYE sip:+18885551212@12.10.10.1
11.10.10.2 12.10.10.1 Request: BYE sip:+18885551212@12.10.10.1
11.10.10.2 12.10.10.1 Request: BYE sip:+18885551212@12.10.10.1
11.10.10.2 12.10.10.1 Request: BYE sip:+18885551212@12.10.10.1
11.10.10.2 12.10.10.1 Request: BYE sip:+18885551212@12.10.10.1
11.10.10.2 12.10.10.1 Request: BYE sip:+18885551212@12.10.10.1
192.10.10.1 12.10.10.1 Request: BYE sip:+19729877171@12.10.10.1
12.10.10.1 192.10.10.1 Status: 200 OK
12.10.10.1 11.10.10.2 Request: INVITE sip:11.10.10.2:5060, with SDP
11.10.10.2 12.10.10.1 Status: 100 Trying
11.10.10.2 12.10.10.1 Status: 487 Request Terminated
12.10.10.1 11.10.10.2 Request: ACK sip:11.10.10.2:5060
11.10.10.2 12.10.10.1 Request: BYE sip:+18885551212@12.10.10.1
12.10.10.1 11.10.10.2 Status: 200 OK
Comments:By: Mark Spencer (markster) 2004-09-27 18:18:59

You're not testing with latest code or even latest 1.0 Release code.
By: tschroer (tschroer) 2004-09-27 18:36:03

OK, please close out report.
By: Mark Spencer (markster) 2004-09-27 18:36:38

Can you try the latest release to confirm?
By: Mark Spencer (markster) 2004-09-28 16:53:13

Assuming this has been long ago fixed in CVS.