Summary:ASTERISK-04929: Call initiated with call file always redials
Reporter:Remco Barendse (linuxfreak)Labels:
Date Opened:2005-08-29 14:22:21Date Closed:2011-06-07 14:10:46
Versions:Frequency of
Description:I am using this as my call file:
Channel: SIP/228        (my phone)
MaxRetries: 0
Context: from-internal  (the context to dial from)
Extension: 003120531234 (the phone number)
Priority: 1
Callerid: Myfinecustomer <003120531234>                                                                                      
so the external number is connected to my sip phone. However after speaking for approx 5 minutes, Asterisk always does a retry and I see the same external number in my display coming in on the second line. It does this on every call. When I'm finished I also see 2 records in the log files.                                                                                                                                                                                                                                 Asterisk is trying to place the call again even though the first attempt was succesful and the call is still in progress/

I didn't specify a redial anywhere. I'm running the latest cvs stable (of this morning).

Upon redial the console shows this:
-- Attempting call on SIP/228 for 003120531234@from-internal:1 (Retry 1)
Comments:By: Kevin P. Fleming (kpfleming) 2005-08-29 15:08:40

We will need a complete call trace to look into this one.

By: Remco Barendse (linuxfreak) 2005-08-30 03:50:19

OK, I'm really embarrased to ask but I looked through the wiki and couldn't find the info. How can I make the call trace?

By: Russell Bryant (russell) 2005-08-30 13:28:23

Turn on 'sip debug' (and 'zap debug' if you're using zap to connect your SIP phone to the phone number).  Also, make sure verbose messages are on ('set verbose 5').  Include the 'sip debug' output as well as any other output from the CLI.

By: Matthew Simpson (matthewsimpson) 2005-09-02 19:30:14

btw, I can confirm the bug has been present since before CVS-STABLE 1.0.  It has affected an application of mine for at least a year.

By: Michael Jerris (mikej) 2005-09-02 20:02:53

Matthew, are you able to produce the requested debug\call traces, perferabally against current cvs head?

By: Michael Jerris (mikej) 2005-09-09 20:07:31

Suspended due to no response.  Please re-open this bug report when the requested information is available for upload.  Thanks.  If you need assistance, please see somone in #asterisk-bugs on irc for help.

By: Remco Barendse (linuxfreak) 2005-10-23 03:50:35

OK I'm trying to do some traces but can't get initial call setup request, the debug info is shooting at a fenomal pace across ths screen and i couldn't capture it. Even though I did start asterisk with -d it doesn't log to any files either??

The strange thnig is I just tested it on my home setup and this doesn't have this bug (1.09 stable).

By: Olle Johansson (oej) 2005-10-24 01:40:24

Try connecting to asterisk as

asterisk -rvvvvdddd | tee /tmp/calltrace.txt

to get the call trace captured to file.

By: BJ Weschke (bweschke) 2005-10-24 13:41:01

this sounds like something I should be able to lab up fairly easily here. Will try and do so in the next day or two and then get back with what I've found.

By: BJ Weschke (bweschke) 2005-10-26 20:26:52

i couldn't reproduce this with cvs-head. I know it was originally mentioned as a stable bug, but I wanted to dbl check the problem didn't exist with head as well. I used the call file example above and left a call connected for 20 mins. It never re-attempted a 2nd call.

By: Remco Barendse (linuxfreak) 2005-10-27 00:27:46

I'm not sure what is causing it. I tried it at home on Asterisk stable 1.09 and it did not redial either. At the office however, I upgraded to the latest CVS stable, the problem is still there. This is what I'm running at the office:
Asterisk CVS-v1-0-10/23/05-11:30:26 built by root@gw on a i686 running Linux

The problem is that the office box is a production server and to get proper captures I need a time when nobody is on the system otherwise I just get lots and lots and lots of log output
I'll try to do it tonight

By: Mark Spencer (markster) 2005-10-30 02:17:33.000-0600

Since none of us can duplicate this, I'm going to close it out.  It sounds a little like a time of day issue on the machine that it's failing on.