Dialplan problems

[Dale]

I have a couple of issues with configuring a dialplan on a Snom ONE Mini running version 4.5.1.1107.

 

The dialplan does not block calls as expected.

 

The dial plan is simple:

200;-;;^1[2-9][0-9][0-9]976*;;;false

300;Vitelity Gateway;;*;;;false

 

 

The test area shows that rule 250 matches to block calls to numbers such as 12319761234, but the calls are actually permitted to go through the Gateway when dialed on the PBX. There is no other dialplan assigned. Also, if I run a test number in the test area of the web page for 12319771234 the test results show that the number matches the 250 pattern when, in fact, it does not.

 

1) Why does my Pattern not block 1xxx976xxxx numbers in the real pbx

2) Why does the test area show that 1xxx977xxxx numbers will be blocked when they don't match the pattern?

3) Is there a different pattern that will actually work to block 1xxx976xxxx numbers?

[Vodia PBX]

If you are using complex pattern, you must try to match also the domain part. For example, 6173998147@domain.com. Your pattern does not match the @ character. This this: ^1[2-9][0-9][0-9]976.* (note the dot)

Or try this "simple" pattern: 1[2-9][0-9][0-9]976xxxx

[Dale]

When I try ^1[2-9][0-9][0-9]334.* the test area for the dial plan works as expected, but the call goes through the PBX.

 

This is also true when I try 1[2-9][0-9][0-9]334xxxx

 

(Note I'm using 334 here instead of 976 so I can test with a non toll number, the real goal is to use 976 instead of 334.)

 

What is see in the log in either of these cases is:

 

Dialplan "test": Match 2313347380@pbx.XXXXX.com to sip:2313347380@sip29.vitelity.net;user=phone on trunk Vitelity Gateway

 

I also want to be able to block 411 calls. I'm testing with 611 instead. If I have a rule that says

 

150;-;;1611;;;false

 

and I dial 1611 even though the dial plan test show that rule 150 is matched, the log shows that the call goes through:

 

Dialplan "test": Match 1611@pbx.XXXXX.com to sip:1611@sip29.vitelity.net;user=phone on trunk Vitelity Gateway

 

Why won't the PBX block the above calls?

 

I have the PBX configured with

 

North America 2 digit extensions [2-7]x

Country Code: 1

Area Code: 231

[Vodia PBX]

Oh. One more thing. If you are using country code 1, then all numbers are fed in a normalized form into the dial plan. Domestic calls are always presented in 10 digit format (no leading 1), all other number are presented with 011.... That means that [2-9][0-9][0-9]976xxxx should work for you.

[Dale]

I understand what you are saying, but it does not work.

 

Here are some simple examples.

 

Dialplan

200;-;;[2-9][0-9][0-9]334xxxx;;;false

300;Vitelity Gateway;;*;;;false

 

If I dial on the phone 12313347300 the call goes through. The logfile shows:

 

Dialplan "test": Match 2313347300@pbx.XXXXX.com to sip:2313347300@sip29.vitelity.net;user=phone on trunk Vitelity Gateway

 

Call also goes through if I set the first (#200) dialplan rule to be

^[2-9][0-9][0-9]334.*

 

The call even completes if I set the first (#200) dialplan rule to be

2313347300

 

As I test more I realize that it even completes if I set the #200 rule to be

*

 

This should block all calls, so I must not be understanding something.

 

I have the domain dialplan set to "test" which is the one I'm testing. The extension I'm dialing from has the dialplan set to "Domain Default"

 

Rewrite global numbers is set to "Check domain country code" for the Vitelity Gateway.

 

Why doesn't this work?

[Vodia PBX]

Okay, finally tried this on my own. Seems like you are right, there is something wrong with the "Not Allowed" entry! Try putting in a replacement, for example *. We'll fix this in the next release.

[Dale]

Great! So there will be another point release for version 4.5 for the snom one mini? Any idea how often a bug fix release is produced?

[Vodia PBX]

For the version 4 releases, it is easier to just do the workaround. It is very difficult for us to make version 4 builds as the build environment is not available to us any more. Those servers are not accessible to us any more.

[Dale]

And what is the workaround that I'm supposed to use? It appears that I can block no numbers. I need to block 1xxx976xxxx numbers and 411 and 1900 numbers as well as 1xxx555xxxx. How do I do it?

[Vodia PBX]

Put a star character into the replacement in the dial plan where you want to reject the further processing of the dial plan.

[Dale]

Thanks. I misunderstood the workaround from your earlier reply. Putting a * in the replacement field does work as an acceptable workaround.