search for: destinationcontext

For those of you who saw my gargantuan post the other day I'd just like to say thanks for listening and sorry for the lengthy post! It turns out that my key issue was with the WaitExten app. I saw this on the wiki which really helped out: http://www.voip-info.org/wiki/view/Asterisk+cmd+Dial (See example 2: Dial macro) I replaced WaitExten with Read, did a little shuffling of

...o match with the recording, which we labeled with {UNIQUEID} in MixMonitor. For some reason, the uniqueid is not correct in the CDR. Here is the manager event for a call: Event: Cdr Privilege: call,all AccountCode: 6384106:MMI-Y:200705081051010077 Source: 0000000000 Destination: 6398714109927773 DestinationContext: outbound CallerID: 0000000000 Channel: Zap/15-1 DestinationChannel: SIP/teliax-081ed5b0 LastApplication: NoOp LastData: StartTime: 2007-05-08 10:51:04 AnswerTime: 2007-05-08 10:51:05 EndTime: 2007-05-08 11:01:56 Duration: 652 BillableSeconds: 651 Disposition: ANSWERED AMAFlags: DOCUMENTATION Uniqu...

Hello, My question is.. How does cdr_manager work? Does it suppose to populate cdr-csv/Master.csv? What about the cdr table on the database? What is the event some people talk about? I have changed (and reloaded) my configuration of cdr_manager.conf to ; ; Asterisk Call Management CDR ; [general] enabled = yes and it doesn't seem to make any difference. After originate a call from the

When recording inbound agent calls, if the queues use agent members (Agent/6000), we can get the calls recorded as agent-xxxx.yyyy.zzzz.gsm where xxxx is the agent number. However, if the queues use phone members (SIP/6000), the recorded filename is simply yyyy.zzzz.gsm. Is there any way of making the recorded file either agent-xxxx or even sip-xxxx where xxxx is the extension number. I had