search for: originatefailure

The Asterisk Manager Interface is driving me nuts. Whoever wrote it should be drawn and quartered. Sometimes the data comes back separated by \r\n, and sometimes it's separated by \n. The whole thing is completely inconsistent, and trying to write any kind of API for it is -GHASTLY- Doug.

...'Newexten', 'Channel': 'OutgoingSpoolFailed'} 2004-07-14 23:59:36,919 DEBUG Hangup, {'Cause': '0', 'Event': 'Hangup', 'Channel': 'OutgoingSpoolFailed', 'Uniqueid': '1089842434.76'} 2004-07-14 23:59:36,921 DEBUG OriginateFailure, {'Context': 'meetme', 'Exten': 'kolejka', 'Event': 'OriginateFailure', 'Channel':'IAX2/kamyk'} Maciej Kaminski

...well known that setting the ActionID when connecting to AMI has absolutely no effect? Is this fixed in Asterisk 1.4? If you add an ActionID to your Originate command for example, it looks like the only events that come back with an ActionID associated are the initial response, OriginateSuccess and OriginateFailure. That's it. No other events have an ActionID associated. This pretty much makes the AMI useless. What about all the other events? Newcallerid, Newstate, Link, Unlink and REALLY importantly the CDR events. Really... someone please tell me it's fixed in 1.4? Thanks, Doug. _____________...

...on a solution that I hope will give the best of > > both worlds. Im relying on the API events instead of local > channels. > > Ill post more information when Ive made more progress. However, > > Ive made 2500 test calls and I havent lost a single > > OriginateSuccess or OriginateFailure event. (Im keying on these, > > specifically the OriginateFailure event because it has a Reason > > value that gets populated: 0=Invalid, 3=No Ans, 5=Busy.) > > > > > > > > Hope to have more info posted this week. > > > > > > > >...

Skipped content of type multipart/alternative-------------- next part -------------- Reliably Transmitting (no NAT) to 111.111.111.50:16666: INVITE sip:111.111.111.50:16666 SIP/2.0 Via: SIP/2.0/UDP 111.111.111.8:5060;branch=z9hG4bK360502ae;rport From: "asterisk" <sip:asterisk@111.111.111.8>;tag=as348de10b To: <sip:111.111.111.50:16666> Contact:

i am creating call files, and catching successfully the ones that don't connect in a 'failed' extension. can anyone tell me how to find out the reason for the failure (ie busy, no answer). ${DIALSTATUS} doesn't appear to get set (presumably because Dial() isn't used) and channel_status doesn't seem to be any good. thanks in advance. -- - Rich Doughty

...y a no answer attempt. Is there a way to distinguish between a no answer and an invalid? For me, a 'failed' attempt is dialing an invalid number, and I'd like the CDRs to reflect that. I'd like a no answer to be as 'successful' as a busy. I'm familiar with the 'OriginateFailure' event and it's 'Reason' field, but I don't know how to get that reason into the CDR. Is that possible? Thanks, MC

hi, afaik, the action-id provided with the OriginateAction should only show up in the OriginateSuccess or OriginateFailure event. Intermediate events that are generated when the channels are create will NOT carry the action-id of the originate. The async flag tells asterisk to process originates in parallel, i.e. if you have two users originating calls and NO async flag set, the second originate will be processed AFTE...

Hello, all! I'm looking at the wiki page and info on the mailing list and I'm getting conflicting info... I am using the manager API from the telnet CLI and I am testing creating calls with it. I login with events: on and I can originate calls just fine. However, when I set ActionID on an Originate, I cannot see anywhere where that actionid carries into the Event output. But I found