This post is at: ForumFeatures Wanted
5 posts / 0 new
Last post
amagurie
amagurie's picture
Joined: 2008/04/02
Points: 0

Hi,

I posted this in the general questions and it did not seem to get noticed, I have noticed other issues posted in features wanted so thought I would try here?

I have a couple of inbound routes that have brackets for pattern matching eg:

_12123123[89]X

which TL creates a context such as:

/etc/asterisk/inbound_actions.include:[from-outside-_12123123[89]X-tl-allhours]

but because it contains the brackets, is invalid and asterisk shows it in the dialplan as:

from-outside-_12123123[89

Is there anyway to get TL to escape them for the context but use the expression for the extension?

Regards
Allister

sonoracomm
sonoracomm's picture
Joined: 2008/05/18
Points: 0

I have this same problem exactly.

Is there a tweak I can make to fix this?

Otherwise, I'll just have to manually put in a lot of inbound routes...

Thank in advance,

G

eeman
eeman's picture
Joined: 2007/11/06
Points: 260

no tweak since that part is in the perl module. The real fix is to use an X for the placeholder of expressions inside a brace.

12123123[89]X would become 12123123XX for the naming portion of the code, while the extension expression remains 12123123[89]X

what did alex say when you requested that amagurie?

Erik Smith
dCAP
Thirdlane/Asterisk Support available
esmith.bgnv@gmail.com

sonoracomm
sonoracomm's picture
Joined: 2008/05/18
Points: 0

That works perfectly.

I now realize that I don't have to be overly strict with the pattern since this pattern only affect incoming [from-outside] calls.

I was worried that other sequential DIDs on a connected PBX would be affected and they were not.

Thanks very much,

G

amagurie
amagurie's picture
Joined: 2008/04/02
Points: 0

I never heard from Alex.

I just manually alter the context part after the route has been created, no great as it can't be updated etc, but it is my only way around it at the moment as I need the stricter patterns.

Allister