Summary:ASTERISK-04820: Asterisk does not handle ringing on ISDN calls when PROGRESS sent before ALERT
Reporter:Matthew Simpson (matthewsimpson)Labels:
Date Opened:2005-08-12 00:28:35Date Closed:2011-06-07 14:10:21
Versions:Frequency of
Environment:Attachments:( 0) bad_call_201_248_7214.txt
( 1) good_call_201_573_0628.txt
Description:When an outgoing call is placed over a Zap ISDN PRI channel, Asterisk will not properly play ringing tones.  Ringing tones are not heard in 183 SDP to SIP device, nor a bridge from another Zap channel.

I have attached two call traces a "good" call trace that properly plays ringing in the 183 SDP and a "bad" call trace that has only silence in the SDP.  In these traces, I hang up before the other party answers, but if the other party does answer, then audio path proceeds normally.


* could be related to bug 4468

* primary difference is on bad call ISDN process is: SETUP --> PROCEEDING --> PROGRESS --> ALERTING --> DISCONNECT

on good call ISDN process is: SETUP --> PROCEEDING --> ALERTING --> DISCONNECT

* this is a 5ESS PRI connected to a Lucent switch

* a Cisco 5400 with same PRIs connected to same switch does not have this problem

* problem tested against CVS-STABLE and CVS-HEAD from 08-11-2005
Comments:By: Matthew Fredrickson (mattf) 2005-08-22 16:47:03

I've been beating my head on chan_zap.c on this one and don't see how the progress message could be messing up ringing.  Peter, any ideas?

By: Matthew Fredrickson (mattf) 2005-08-22 16:49:36

If you can get me login access to the machine and are able to standby for a bit while I poke around the system it might be fixed a lot faster.  You can get a hold of me on IRC during the day.  My nick is Cresl1n

By: Matthew Fredrickson (mattf) 2005-08-29 21:22:25

no feedback