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

[Asterisk Bug Tracker]

The following issue has been CLOSED 
====================================================================== 
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:                     closed
Asterisk Version:           1.6.1.5 
JIRA:                        
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 open
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-09-02 02:45 CDT
Last Modified:              2009-09-22 09:01 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0111167) lmadsen (administrator) - 2009-09-22 09:01
 https://issues.asterisk.org/view.php?id=15812#c111167 
---------------------------------------------------------------------- 
This is not a bug -- it is a configuration issue. Per your console output:

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


You called from 3000 to 3001. That is 1 call.

You called from 3002 to 3001.  That is another call -- counter is now 2.

Your console shows that you've got call-limit set to 1 -- thus the 2nd
call is rejected.

Closing this issue due to a configuration problem. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-22 09:01 lmadsen        Note Added: 0111167                          
2009-09-22 09:01 lmadsen        Status                   feedback => closed  
======================================================================