Douglas Garstang wrote: > 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/[EMAIL PROTECTED] > Callerid: 849120 > Context: default > ActionID: 849120 > > My LegA context: > ----------------------- > context LegA { > _X. => { > Dial(SIP/[EMAIL PROTECTED]); > } > > } > > 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 [EMAIL PROTECTED]:1] Dial("Local/[EMAIL PROTECTED],2", > "SIP/[EMAIL PROTECTED]") in new stack > -- Called [EMAIL PROTECTED] > -- SIP/Provider-09a8cff8 is making progress passing it to Local/[EMAIL > PROTECTED],2 > -- SIP/Provider-09a8cff8 answered Local/[EMAIL PROTECTED],2 > == Starting Local/[EMAIL PROTECTED],1 at default,callback,1 failed so > falling back to exten 's' > == Starting Local/[EMAIL PROTECTED],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/[EMAIL PROTECTED],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. > > > originates have always had an issue where it falls back to an 's' extension. and since you do not have one, nor an 'i' for invalid extension... it bombs out.
_______________________________________________ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users