[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:13:34 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:13 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0118993) fa_bian (reporter) - 2010-03-04 19:13
 https://issues.asterisk.org/view.php?id=16959#c118993 
---------------------------------------------------------------------- 
#################################
### normal call (sip-history) ###
#################################

### provider 1, WITH ringing ###
1. Rx              INVITE / 101 INVITE /
sip:01712345678 at 123.123.123.123;user=
2. AuthChal        Auth challenge sent for  - nc 0
3. TxRespRel       SIP/2.0 / 101 INVITE - 401 Unauthorized
4. SchedDestroy    32000 ms
5. Rx              ACK / 101 ACK /
sip:01712345678 at 123.123.123.123;user=phone
6. Rx              INVITE / 102 INVITE /
sip:01712345678 at 123.123.123.123;user=
7. CancelDestroy
8. Invite          New call:
0006283e-03f60058-0f9a4154-3a12d06e at 192.168.0.100
9. AuthOK          Auth challenge succesful for 1234
10. NewChan         Channel SIP/1234-00000300 - from
0006283e-03f60058-0f9
11. TxResp          SIP/2.0 / 102 INVITE - 100 Trying
12. TxResp          SIP/2.0 / 102 INVITE - 183 Session Progress
13. TxResp          SIP/2.0 / 102 INVITE - 180 Ringing
14. TxRespRel       SIP/2.0 / 102 INVITE - 200 OK
15. Rx              ACK / 102 ACK / sip:01712345678 at 123.123.123.123

### provider 2, WITHOUT ringing ###
1. Rx              INVITE / 101 INVITE /
sip:01712345678 at 123.123.123.123;user=
2. AuthChal        Auth challenge sent for  - nc 0
3. TxRespRel       SIP/2.0 / 101 INVITE - 401 Unauthorized
4. SchedDestroy    18496 ms
5. Rx              ACK / 101 ACK /
sip:01712345678 at 123.123.123.123;user=phone
6. Rx              INVITE / 102 INVITE /
sip:01712345678 at 123.123.123.123;user=
7. CancelDestroy
8. Invite          New call:
0006283e-03f60057-0d0b087c-5b73c322 at 192.168.0.100
9. AuthOK          Auth challenge succesful for 1234
10. NewChan         Channel SIP/1234-000002fe - from
0006283e-03f60057-0d0b
11. TxResp          SIP/2.0 / 102 INVITE - 100 Trying
12. TxResp          SIP/2.0 / 102 INVITE - 183 Session Progress
13. TxRespRel       SIP/2.0 / 102 INVITE - 200 OK
14. Rx              ACK / 102 ACK / sip:01712345678 at 123.123.123.123 

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




More information about the asterisk-bugs mailing list