Summary:ASTERISK-11511: pri stops receiving answering calls
Reporter:Daniel Morgan (danm)Labels:
Date Opened:2008-02-26 03:41:13.000-0600Date Closed:2011-06-07 14:08:21
Versions:Frequency of
Environment:Attachments:( 0) failed.txt
( 1) failing_call_1.4.18.txt
( 2) failing_call_1.4.18_different.txt
( 3) successful.txt
Description:Randomly inbound all calls start failing from pri span 1.
We are able to make outbound calls throughspan 1.


There are two traces
1, failing call this is an incoming call from span 1 to 331002
2, successful call out going to span 1 to 07973222228
Comments:By: Daniel Morgan (danm) 2008-02-26 04:05:28.000-0600

Sometime this happens everyday some weekly.

By: jmls (jmls) 2008-02-26 04:53:41.000-0600

have you tried using asterisk 1.4.18 ?

By: Daniel Morgan (danm) 2008-02-26 04:56:00.000-0600

not yet we will upgrade now and test.

By: Daniel Morgan (danm) 2008-02-28 08:46:30.000-0600

we have upgraded to Asterisk 1.4.18 the problem has not re-occured yet but can sometime work for a week before it happens.

By: Daniel Morgan (danm) 2008-03-04 03:47:03.000-0600

The problem has re-occurred again i have uploaded "failing call 1.4.18.txt"

Also since upgrading to 1.4.18 we now see

Sending Set Asynchronous Balanced Mode Extended

This appears on the console about every 1 second.

By: Daniel Morgan (danm) 2008-03-04 11:19:05.000-0600


I have just uploaded "failing call 1.4.18 different.txt"

this has a lot more information in it.

By: Daniel Morgan (danm) 2008-03-20 12:25:30

We are using a have swapped cards to a Digium Te4sxxp card and the problem is still occuring.

Please advise.

By: snuffy (snuffy) 2008-08-22 09:57:06

Are you still having this problem in latest or even 1.4 svn?

By: Leif Madsen (lmadsen) 2008-12-05 11:16:24.000-0600

I hate to suspend this issue on you, but since it appears there is currently no activity from the original poster, I'm going to close this. However, please feel free to find a bug marshall in #asterisk-bugs on the IRC network irc.freenode.net to have this issue re-opened. Thanks!