[Asterisk-Users] Re: Pattern matching problem

[kevin ling]

Hi Andrew,

Sorry for my english first. 

My configuration and hardware: AAH2.7 & 2.8, Digium TE100P, welltech 4fxo
voice gateway

SIP Phone
|
|
Asterisk Server ------------- TE100P ------------- Telcom1
|
+----  Welltech 4FXO voicegateway -------- Telcom2
                                                       
Actually no matter on the digital interface (TE110P) or analog channels
(4FXO). Bellowing is my outbound routing config. I try to dial 6137451576
number. The asterisk doesn't match this dial pattern. And when I dail
"6137451". It's work. 

So you mean the "analogue channels" is analog phone attach on a fxs port?

[outrt-001-outside]
include => outrt-001-outside-custom
exten => _NXXXXXX,1,Macro(dialout-trunk,1,${EXTEN},,)
exten => _NXXXXXX,n,Macro(outisbusy,)
 
Kevin

-----Original Message-----
From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Andrew
Kohlsmith
Sent: Thursday, April 27, 2006 9:10 AM
To: asterisk-users at lists.digium.com
Subject: Re: [Asterisk-Users] Re: Pattern matching problem

On Wednesday 26 April 2006 20:54, kevin ling wrote:
> Same dial pattern on my extension.conf, But it's work great. The 
> Asterisk only match 7 digits number. My * version is 2.1.6.

>From an analogue Zap channel?  Bullshit.

Analogue channels do not present the extension "in one shot" -- they present
the digits one at a time, in sequence.  When the dialplan matches, it
matches.  Why do you think the telco needs you to enter "1" for long
distance?  And why do you think they're moving to ten-digit dialing for so
many areas?

This is very very basic, standard pattern matching.  Analogue channels are
very different from digital ones in how the desired extension or telephone
number is presented to the switch.

-A.
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --

Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

On Wednesday 26 April 2006 20:34, hugolivude wrote:
> Thanks, but the problem's with the first extension:
>
> exten => _NXXXXXX,1,NoOp(Number dialed ${EXTEN}) exten => 
> _NXXXXXX,n,Dial(Zap/1/${EXTEN})
>
> The problem is I _do_ get a match as you can see by the CLI output, 
> but it shouldn't match IMO - 6137451576 shouldn't match _NXXXXXX but 
> that line gets executed.

When you dial "six one three seven four five one" Asterisk says "hey!  That
matches _NXXXXXX!" -- the fact that you have "five seven six" left means
nothing, just as you can dial 1-800-PROGRESSIVE as Eric stated earlier.

On analog Zap interfaces, Asterisk (just like the telco) simply listens
until the digits match.  If you don't want a ten digit number to match, then
adjust your dialplan accordingly.  This is not a strange error in Asterisk,
it is a mismatch between what you want the system to do and how the system
operates.

Digital Zap channels and VOIP channels do not work this way because the
entire number is sent in one "go" -- when you dial from a SIP phone,
Asterisk does not see a stream of digits, it sees one "message" or "packet"
of information with the entire phone number in it.  That is why it doesn't
match with SIP or IAX or PRI channels.  (overlap dial excepted.)

-A.