[asterisk-bugs] [Asterisk 0010444]: billsec value changes depending on dialing method

noreply at bugs.digium.com noreply at bugs.digium.com
Tue Aug 14 00:46:11 CDT 2007


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10444 
====================================================================== 
Reported By:                krtorio
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   10444
Category:                   CDR/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:            1.4.9  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             08-13-2007 20:06 CDT
Last Modified:              08-14-2007 00:46 CDT
====================================================================== 
Summary:                    billsec value changes depending on dialing method
Description: 
Billsec value when dialing manually is accurate.

However, if we use the manager action Originate, it gives a different
billsec value.

I think this can be easily reproducible.

Here's the sample dialplan:

[sample]
exten => _6XX,1,Dial(SIP/${EXTEN},60,t)

And here's the sample manager input:

Action: Originate
Channel: SIP/601
Exten: 602
Context: sample
Priority: 1


====================================================================== 

---------------------------------------------------------------------- 
 jamesgolovich - 08-14-07 00:46  
---------------------------------------------------------------------- 
I tried to duplicate this in my setup but couldn't.  A manual call to a
remote extension that played a soundfile resulted with billsec 19.  Using
manager originate to generate a call to the same extension also resulted
with a billsec of 19.  I did this using 1.4.10 and I don't believe anything
has changed relating to manager originate since 1.4.9. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
08-14-07 00:46  jamesgolovich  Note Added: 0068807                          
======================================================================




More information about the asterisk-bugs mailing list