[asterisk-users] Goto in Realtime extensions

[Yves Räber]

* Version: Asterisk 1.4.14

* Commas instead of pipes => already tried, this is not working at all

* Realtime switch for script_13_0 => No, should I ? This would be really
a shame, I want to use realtime BECAUSE I don't want to play with my
extensions.conf file. (I'm building a web interface that has to generate
the contexts).

* Using numbers instead of 's' => already tried, no changes

* Renaming contexts without underscores => tried it right now, no
changes

Thanks for all those ideas.

Yves.

On Thu, 2008-02-07 at 17:39 +0200, Atis Lezdins wrote:
> On 2/7/08, Yves Räber <yraber at mailup.net> wrote:
> > I would have been happy ... but it's not that. This query gives me the
> > right row (I double checked).
> >
> > On Thu, 2008-02-07 at 08:36 -0600, Tilghman Lesher wrote:
> > > On Thursday 07 February 2008 08:05:40 Yves Räber wrote:
> > > > Hello,
> > > >
> > > > I'm having troubles while using the "Goto" function in a realtime
> > > > extension. Here is the error message :
> > > >
> > > > -- Executing Goto("SIP/siemens1-081f56b0", "script_13_0|s|1")
> > > > -- Goto (script_13_0,s,1)
> > > > [Feb  7 13:24:21] WARNING[28666]: pbx.c:2455 __ast_pbx_run: Channel
> > > > 'SIP/siemens1-081f56b0' sent into invalid extension 's' in context
> > > > 'script_13_0', but no invalid handler
> > > >
> > > > And I definitively have a row in my extensions table with context
> > > > script_13_0, exten s and priority 1 !
> > > >
> > > > I also tried to goto in another context that is in my extensions.conf
> > > > file, and it works.
> > > >
> > > > Is this a restriction or a bug ? It seems that it's not possible to
> > > > "Goto" to another context within the realtime extensions.
> > >
> > > It's impossible to guess what might be wrong, because you haven't included
> > > a dump from your table.  Try a:
> > >
> > > SELECT * FROM extensions_table WHERE exten='s' AND context='script_13_0'
> > > AND priority='1'
> > >
> > > If that fails, you have your answer.
> > >
> 
> What version? You could try replacing pipes with commas. Do you have
> realtime switch statement for script_13_0? Can you try renaming
> context to not use underscores? Try using not "s" but any number (and
> create extension _X.)
> 
> Regards,
> Atis
>