Summary:ASTERISK-10554: i extention not all times work
Reporter:Badalian Vyacheslav (slavon)Labels:
Date Opened:2007-10-17 06:07:34Date Closed:2011-06-07 14:02:52
Versions:Frequency of
Description:Hello. I try to move some configs to AEL and found that "i" extention not always work (its work if i use Background or WaitExten, but don't work if try call to extention direct)

i think no need to debug because it's easy to reproduce...



context ivr-main {
       s =>{


       1 => Playback(some-sound);
       i => Playback(some-sound2); // ITS WORK

context office {
       1 => Playback(some-sound);
       i => Playback(some-sound2); // IT'S NOT WORK "Call from 'xxx' to extension '2' rejected because extension not found."
Comments:By: Dmitry Andrianov (dimas) 2007-10-17 08:23:00

Do you include 'office' into some other context or you are jumping there directly?

jump 2@office;

should work

context a {
 includes {

won't - because 'i' extension in _current_ context will be used. Jump/goto just changes current context so it works.

By: Badalian Vyacheslav (slavon) 2007-10-17 08:30:06

in sip.conf:


like this

By: Dmitry Andrianov (dimas) 2007-10-17 08:39:00

Ok, in the documentation "i" extension is called "invalid response extension" so I guess it is related to invalid user input (to WaitExten). You are talking about another SIP tying calling this extension which is not a user input.

anyway, I think you can emulate what you want by creating "wrapper" context which contains:

_X. => jump ${EXTEN}@office;
i => Playback(...)

and configuring users to use that context.

By: Badalian Vyacheslav (slavon) 2007-10-17 08:45:05

hm... i think that Invalid is INVALID in any response (jump, dial to LOCAL and other)... if i mistake - sorry for this.

Maybe we get answer from administration what real logic of invalid? =)

By: Jason Parker (jparker) 2007-10-17 10:12:23

dimas is correct.  This is working as intended.