Displaying 2 results from an estimated 2 matches for "dodialstd".
2010 Dec 22
8
Possible Bug (Include ${HANGUPCAUSE} in CDR)
Ok I can't get my CDR values to set from the h extension in either 1.6.2 or
1.8 What is wrong? Here is what I found in the cdr.conf
; Normally, CDR's are not closed out until after all extensions are
finished
; executing. By enabling this option, the CDR will be ended before
executing
; the "h" extension so that CDR values such as "end" and "billsec" may
2010 Dec 22
0
Include ${HANGUPCAUSE} in CDR
...tion of the
code. How might I get this info into the CDR. I need this info for Quality
of Service as well as route checking. Any ideas would be apperciated.
Here is my dial line and my h lines. I also use the g option so if the
other party hangs up and that is not working either.
exten =>
doDialStd,n,Dial(${siteDefaultOutboundTrunk}/${c_DialArg}${c_DialExten},120,
ge)
exten => h,n,Set(CDR(cause_code)=${HANGUPCAUSE})
Bryant exten => h,n,Set(CDR(cause_code)=${HANGUPCAUSE})Bryant
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com...