[asterisk-bugs] [Asterisk 0014865]: 183 Session Progress Stops Ringback

Asterisk Bug Tracker noreply at bugs.digium.com
Wed Apr 8 16:17:52 CDT 2009


The following issue has been SUBMITTED. 
====================================================================== 
http://bugs.digium.com/view.php?id=14865 
====================================================================== 
Reported By:                flmike
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14865
Category:                   Sounds
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.24 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-04-08 16:17 CDT
Last Modified:              2009-04-08 16:17 CDT
====================================================================== 
Summary:                    183 Session Progress Stops Ringback
Description: 
Greetings,

These are the platforms.......

FreeBSD 6.3-RELEASE-p3 (GENERIC) http://bugs.digium.com/view.php?id=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?

Thanks,
Mike


====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-04-08 16:17 flmike         Asterisk Version          => 1.4.24          
2009-04-08 16:17 flmike         Regression                => No              
2009-04-08 16:17 flmike         SVN Branch (only for SVN checkouts, not tarball
releases) =>  1.4            
======================================================================




More information about the asterisk-bugs mailing list