[asterisk-users] AEL2 and Callbacks

[Douglas Garstang]

I am originating a command via the AMI with this...

Action: Login
Username: xxx
Secret: yyy

ACTION: Originate
Async: yes
Timeout: 60000
Exten: callback
Channel: Local/6505551212 at LegA
Callerid: 849120
Context: default
ActionID: 849120

My LegA context:
-----------------------
context LegA {
    _X. => {
        Dial(SIP/${EXTEN}@Provider); 
    }

}

And my default context:
------------------------------
context default {
    callback => {
        NoCDR();
        Wait(1);
        Dial(${destination},60,oL(${timeout}:${timeout_warning}:${timeout_warning_repeat}));
    }

}

The A leg is established, and once Asterisk goes to dial the B leg...

    -- Executing [16505551212 at LegA:1] Dial("Local/16505551212 at LegA-f707,2", "SIP/16505551212 at Provider") in new stack
    -- Called 16505551212 at Provider
    -- SIP/Provider-09a8cff8 is making progress passing it to Local/16505551212 at LegA-f707,2
    -- SIP/Provider-09a8cff8 answered Local/16505551212 at LegA-f707,2
  == Starting Local/16505551212 at LegA-f707,1 at default,callback,1 failed so falling back to exten 's'
  == Starting Local/16505551212 at LegA-f707,1 at default,s,1 still failed so falling back to context 'default'
[Oct 31 01:57:07] WARNING[29795]: pbx.c:2450 __ast_pbx_run: Channel 'Local/16505551212 at LegA-f707,1' sent into invalid extension 's' in context 'default', but no invalid handler

Uhm, why? I have a default context with a callback extension. Of course I have no explicit priority 1 though... this is AEL2.... 
What's it complaining for?

Doug.








__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20071031/23762d43/attachment.htm