[asterisk-bugs] [Asterisk 0016959]: SIP-Provider without "SIP/2.0 180 Ringing" makes trouble with call file

Asterisk Bug Tracker noreply at bugs.digium.com
Thu Mar 4 19:05:40 CST 2010


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16959 
====================================================================== 
Reported By:                fa_bian
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16959
Category:                   General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.2.2 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-03-04 06:15 CST
Last Modified:              2010-03-04 19:05 CST
====================================================================== 
Summary:                    SIP-Provider without "SIP/2.0 180 Ringing" makes
trouble with call file
Description: 
I make a auto dial via call file.

If I use a SIP-Provider who sends a "SIP/2.0 180 Ringing" all is fine!

If I use a SIP-Provider who DOESN'T send a "SIP/2.0 180 Ringing" Asterisk
DOESN'T proceed in context.
====================================================================== 

---------------------------------------------------------------------- 
 (0118988) fa_bian (reporter) - 2010-03-04 19:05
 https://issues.asterisk.org/view.php?id=16959#c118988 
---------------------------------------------------------------------- 
#############
### call file ###
#############

### provider 1, WITH ringing ###
1. NewChan         Channel SIP/provider1_out-000002f9 - from
62e013a51855090d
2. TxReqRel        INVITE / 102 INVITE - INVITE
3. Rx              SIP/2.0 / 102 INVITE / 407 Proxy Authentication
Required
4. TxReq           ACK / 102 ACK - ACK
5. AuthResp        Auth response sent for 112233 in realm
sip.provider1.tld - nc 1
6. TxReqRel        INVITE / 103 INVITE - INVITE
7. Rx              SIP/2.0 / 103 INVITE / 100 Giving a try
8. Rx              SIP/2.0 / 103 INVITE / 183 Session Progress
9. Rx              SIP/2.0 / 103 INVITE / 200 OK
10. TxReq           ACK / 103 ACK - ACK
11. Masq            Old channel:
Local/00491712345678 at ext_all_out-b67c;1<ZOMBIE>
12. Masq (cont)     ...new owner: SIP/provider1_out-000002f9

### provider 2, WITHOUT ringing ###
1. NewChan         Channel SIP/provider2_out-000002fb - from
596bba4d26bba5f11
2. TxReqRel        INVITE / 102 INVITE - INVITE
3. Rx              SIP/2.0 / 102 INVITE / 401 Unauthorized
4. TxReq           ACK / 102 ACK - ACK
5. AuthResp        Auth response sent for 445566 in realm
sip.provider2.tld - nc 1
6. TxReqRel        INVITE / 103 INVITE - INVITE
7. Rx              SIP/2.0 / 103 INVITE / 100 Trying
8. Rx              SIP/2.0 / 103 INVITE / 183 Session progress
9. Rx              SIP/2.0 / 103 INVITE / 200 Ok
10. TxReq           ACK / 103 ACK - ACK 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-03-04 19:05 fa_bian        Note Added: 0118988                          
======================================================================




More information about the asterisk-bugs mailing list