[asterisk-bugs] [Asterisk 0015812]: In CDR Disposition save NO ANSWER instead BUSY or FAILED

Asterisk Bug Tracker noreply at bugs.digium.com
Wed Sep 2 09:43:55 CDT 2009


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15812 
====================================================================== 
Reported By:                Maximfs79
Assigned To:                mnicholson
====================================================================== 
Project:                    Asterisk
Issue ID:                   15812
Category:                   CDR/cdr_csv
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.1.5 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-09-02 02:45 CDT
Last Modified:              2009-09-02 09:43 CDT
====================================================================== 
Summary:                    In CDR Disposition save NO ANSWER instead BUSY or
FAILED
Description: 
I have used Asterisk 1.6.0.9, all will be ok. After update to asterisk
1.6.1.5 I have problem with cdr. Same effect on asterisk 1.6.0.14.
====================================================================== 

---------------------------------------------------------------------- 
 (0110028) Maximfs79 (reporter) - 2009-09-02 09:43
 https://issues.asterisk.org/view.php?id=15812#c110028 
---------------------------------------------------------------------- 
Configuration:
There are three accounting records:
3000, 3001, 3002
extensions 3XXX

I call with 3000 to 3001
Then with 3002 to 3001

In console the answer such:

chan_sip.c:4959 update_call_counter: Call to peer ' 3001 ' rejected due to
usage limit of 1
Or
Got SIP response 486 "Busy Here" back from 10.102.38.104

Then:
Everyone is busy/congested at this time

cause code return 17

I think problem in cdr.c. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-02 09:43 Maximfs79      Note Added: 0110028                          
======================================================================




More information about the asterisk-bugs mailing list