Summary:ASTERISK-06215: When hitting # for next channel, the # is passed on to the channel listened on
Reporter:Morten Tryfoss (mtryfoss)Labels:
Date Opened:2006-01-29 13:48:50.000-0600Date Closed:2011-06-07 14:09:59
Versions:Frequency of
Description:This is what I get on the pbx cli.

Jan 29 21:38:32 WARNING[13489]: pbx.c:2392 __ast_pbx_run: Invalid extension '#', but no rule 'i' in context 'masterferries_hoved'

Comments:By: Clod Patry (junky) 2006-01-29 20:44:07.000-0600

Is that for a specific channel or for group?

i cant reproduce it on current trunk (8874).
   -- Executing ZapScan("SIP/15-ac43", "") in new stack
   -- Zap channel Zap/1-1 is in-use, monitoring...
   -- Playing 'digits/1' (language 'en')
   -- Zap channel Zap/1-1 is in-use, monitoring...
   -- Playing 'digits/1' (language 'en')
   -- Zap channel Zap/1-1 is in-use, monitoring...
   -- Playing 'digits/1' (language 'en')
   -- Zap channel Zap/1-1 is in-use, monitoring...

By: Morten Tryfoss (mtryfoss) 2006-01-29 23:01:44.000-0600

I use only Zapscan(). It's a Sangoma 104d card with 2 E1's active.

By: Morten Tryfoss (mtryfoss) 2006-01-29 23:04:19.000-0600

The channel I'm listening on is currently on a Waitexten() or Background() when it fails. When it's not, it seems to work fine.

By: Clod Patry (junky) 2006-04-23 14:36:08

Do you stil have this issue with latest trunk?

By: Morten Tryfoss (mtryfoss) 2006-04-24 00:58:13

Yes, the problem is still there.

The call listening on is as follows:

Cell phone <Zap> ServerA <IAX2> ServerB (The Waitexten and Background is executed at ServerB).

The call which runs the zapscan is as follows:

Grandstream GXP-2000 <SIP> ServerC <IAX2> ServerA

By: Serge Vecher (serge-v) 2006-05-09 09:47:49

mtryfoss: can you reproduce this issue with a Digium card?

By: Morten Tryfoss (mtryfoss) 2006-05-09 14:43:38

No, sorry. We don't have any cards from digium, so I'm not able to test it.

By: Serge Vecher (serge-v) 2006-05-09 14:47:36

ok, since nobody else has this problem with a Digium card, we have to presume it's an issue with Sangoma hardware. To best address this problem, please contact Sangoma directly for support. If they are able to produce apatches that needs inclusion into an Asterisk tree, please feel free to reopen this bug report with those patches attached. Thanks.