Summary:ASTERISK-13928: 183 Session Progress Stops Ringback
Reporter:Michael Flynn (flmike)Labels:
Date Opened:2009-04-08 16:17:51Date Closed:2011-06-07 14:02:39
Versions:Frequency of
Environment:Attachments:( 0) extensions.conf
( 1) musiconhold.conf
( 2) ringing.txt
( 3) session.txt
( 4) sip.conf

These are the platforms.......

FreeBSD 6.3-RELEASE-p3 (GENERIC) #0: Wed Jul 16 08:44:40 UTC 2008
asterisk-1.4.10_33  An Open Source PBX and telephony toolkit

Asterisk is being used in our calling card application. The issue only occurs when calls are processed through Asterisk (calling card) and only after the final call has been started. Also, when the final call is to an IP phone on our network and we receive a 180 ringing, there is no issue. When the final call is through our termination partners and we receive a 183 session progress, the ringback stops. The ringback is a musiconhold ringtone and it does start but stops when 183 session progress is received.

We have traces showing both the 180 ringing and the 183 session progress.
It is clear in the traces that the musiconhold continues until the ACK after OK
in the 180 ringing trace but stops early when 183 session progress is received in the 183 session progress trace.

This a major problem for us, we can't introduce calling card products.

Any ideas on how we can work around this?



All of the traces are available along with the configuration files.
(Don't know how to attach them here)
Comments:By: Leif Madsen (lmadsen) 2009-04-21 21:35:26

Please reproduce this issue on a vanilla version of Asterisk that is recent. You have indicated you are getting this issue on 1.4.10, which is quite an old version.