[asterisk-bugs] [Asterisk 0016594]: ISDN to SIP doesn't generate SIP 180 Ringing with Call Progress ISDN message

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16594 
====================================================================== 
Reported By:                denisgalvao
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16594
Category:                   Core/Channels
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.6.1.12 
JIRA:                       SWP-718 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-01-13 10:57 CST
Last Modified:              2010-01-14 12:07 CST
====================================================================== 
Summary:                    ISDN to SIP doesn't generate SIP 180 Ringing with
Call Progress ISDN message
Description: 
When I place a call trough a SIP UA and this call goes out through an ISDN
link, the Call Progress message from ISDN is not converted to a SIP 180
Ringing message to the UA.

P.S.: Im not sure about the category of this issue, BTW I believe it is a
channel related thing.
====================================================================== 

---------------------------------------------------------------------- 
 (0116688) wimpy (reporter) - 2010-01-14 12:07
 https://issues.asterisk.org/view.php?id=16594#c116688 
---------------------------------------------------------------------- 
I'm not a SIP expert. Does SIP require a Ringing message before a connect?
In that case the only solution I see is a state machine that sends a
ringing when the connect message is received and no Ringing was sent so
far.

Translating a proceeding message into ringing will surely cause strange
effects. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-01-14 12:07 wimpy          Note Added: 0116688                          
======================================================================