but I didn't succed to get the wanted information this way (e.g. dialedpeernumber and dialedpeername not set).
short answer on one one of Andrews questions:
ResetCDR resets time and callstatus. It's something you use if you have a callingcard (or other application) that which
needs to 'Answer()' the line in order to get the dtmf for calling cardnumber. If you dont issue the ResetCDR before calling
out then you wouldn't know if the called party answers since the cdr status 'answered' would come from your application
answering the call and not from the called party, billable time would be wrong to.
This is at least how it used to be, you do now have the 'C' option in the Dial() command which I think obsoletes the ResetCDR
but it's probably keept so it does'n't break peoples dialplans/agi scripts.
After writing this response I realized that we should move over to -user with the remaining answers to keep noise down on -dev
Freddi
Date: Mon, 20 Dec 2004 19:22:53 -0500 From: Andrew Kohlsmith <[EMAIL PROTECTED]> Subject: Re: [Asterisk-Dev] Call-forking and cdr-patch To: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="iso-8859-1"
On December 20, 2004 07:14 pm, Brian West wrote:
app_forkcdr not what you want?
As someone who doesn't understand what forking the CDR will get you, can you provide an example? There are several applications * has which I have trouble making heads or tails of.
ForkCDR ResetCDR ICES NBScat SetAMAFlags (how to use them really) TestClient/Server
-A.
_______________________________________________ Asterisk-Dev mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
