Summary:ASTERISK-09119: Asterisk (chan_sip) hangs up call immediately after remote party picks up.
Reporter:wmis.net (wmis)Labels:
Date Opened:2007-03-27 16:16:50Date Closed:2011-06-07 14:02:55
Versions:Frequency of
Environment:Attachments:( 0) allworx-debug.txt
( 1) asterisk-allwork.txt
( 2) asterisk-debug.txt
( 3) tcpdump.txt
( 4) verbosedebug.txt
Description:Asterisk occasionally hangs up an outbound call initiated from an Allworx (http://www.allworx.com) IAD as soon as the call is picked up.  If the call is retried immediately, the call completes successfully.

We have dozens of customers on Sipura and Adtran IADs that have never had this problem, so I am wondering if it is an Allworx issue.

I have attached SIP debug output.



Comments:By: Serge Vecher (serge-v) 2007-03-27 16:20:13

We need a console SIP debug trace illustrating the problem. Please do the following:
1) Prepare test environment (reduce the amount of unrelated traffic on the server);
2) Make sure your logger.conf has the following line:
  console => notice,warning,error,debug
3) restart Asterisk with the following command:
  'asterisk -Tvvvvvdddddngc | tee /tmp/verbosedebug.txt'
4) Enable SIP transaction logging with the following CLI commands (1.4/trunk commands in parenthesis):
set debug 4 (core set debug 4)
set verbose 4 (core set verbose 4)
sip debug (sip set debug)
5) Reproduce the problem
6) Trim startup information and attach verbosedebug.txt to the issue.

By: wmis.net (wmis) 2007-03-27 16:23:23

Allwork <-SIP-> Asterisk <-SIP-> Cisco AS5300 <-PRI->

By: wmis.net (wmis) 2007-03-28 13:59:59

I uploaded debugging from both Asterisk and Allworx for the same call.  It looks like Allworx is ACK'ing the INVITE, and Asterisk is receiving it, but ignoring it?

By: Serge Vecher (serge-v) 2007-03-28 14:25:59

can you please do the log exactly as per my instructions?

By: wmis.net (wmis) 2007-04-09 10:26:29

No, I cannot set it up how you are asking.  This is a production environment and the customer does not have an extra Allworx box.

By: Serge Vecher (serge-v) 2007-04-09 12:18:18

all you have to do to get the right output is to capture the console. This could be done, for example, by connecting to the running session with -r option.

By: wmis.net (wmis) 2007-04-10 09:15:37


I have debug recording to syslog, which dumps it to /var/log/asterisk.log.  I trimmed it up and put it in asterisk-allwork.txt attachment.  Is this not the same?  Are you wanting to see the Dial() and such as well?

By: Serge Vecher (serge-v) 2007-04-10 10:29:20

alright, take a look at the following log http://bugs.digium.com/file_download.php?file_id=12800&type=bug. The amount of information logged is quite different.

By: wmis.net (wmis) 2007-04-12 08:43:45

debug uploaded.  I hope this is what you needed.

By: wmis.net (wmis) 2007-04-12 08:52:21

^G[Apr 12 09:26:32] WARNING[26247]: chan_sip.c:1228 retrans_pkt: Maximum retries exceeded on transmission a11ce-10262-461e3382-1cff-216.109
.205.115 for seqno 7771 (Critical Response)

is where the call hangs up.

By: wmis.net (wmis) 2007-04-16 11:25:54

Allworx developers looked at the log and said:

  Without knowing what all the Asterisk logging means, we can see                                                                                                                              
  the Asterisk is receiving the ACK for setting up the call, but is then                                                                                                                        
  retransmitting the 200 OK instead of starting audio. The ACK message                                                                                                                          
  looks OK, so not sure what the Asterisk is doing.

By: wmis.net (wmis) 2007-04-19 13:01:13


By: wmis.net (wmis) 2007-05-03 15:13:43

anyone have any ideas?

By: Joshua C. Colp (jcolp) 2007-09-06 13:28:49

1.2 is no longer being worked on, if this can be reproduced on 1.4 feel free to reopen with the info.