Dial plan explanation

Started by QBZappy, December 02, 2010, 10:25:46 PM

Previous topic - Next topic

RonR

I'm pretty sure it's just as I thought [feared?  :)].

When you dial 12345678901 or 2345678, your PrimaryLine setting of SP2 causes the ITSPB DigitMap [(011xx.|*xxx.|xxx.)] to be evaluated via the (Mpli) rule in your PHONE Port DigitMap.  The only way your ITSPA DigitMap [(1xxxxxxxxxx|<1aaa>[2-9]xxxxxx)] will be evaluated is if you dial **1 + 12345678901 or **1 + 2345678, which will use the **1(Msp1) rule.  Without **1 or a PrimaryLine setting of SP1, there's no path to ITSPA's DigitMap and it's never evaluated.

murzik

If I remove DigitMap (1xxxxxxxxxx|<1aaa>[2-9]xxxxxx) from ITSPA, then I cannot make a call.


RonR

You mean you can't make any kind of call under any scenario?  Please be a little more detailed with symptoms.

RonR

#23
With an ITSPA DigitMap of (1xxxxxxxxxx|<1aaa>[2-9]xxxxxx), did you try testing with **1 + 12345678901 and **1 + 2345678, with and without the S0's in place, with and without a trailing '#'?  My guess is the S0's and '#'s won't make any difference when **1 is used.

RonR

Quote from: murzik on March 19, 2011, 05:41:58 PMI am simply dialing numbers without **. Because I have rule set on Phone port { (1xxxxxxxxxx|<1aaa>[2-9]xxxxxx):sp2}
I failed to comment on this.

Having a route of {(1xxxxxxxxxx|<1aaa>[2-9]xxxxxx):sp2} in the OutboundCallRoute isn't interesting when it comes to evaluating DigitMap's.  Once the DMP has evaluated all the applicable DigitMap's as previously described, then the value selected by the DMP is compared to routes in the OutboundCallRoute to determine where to send the call.

In your case, your dialed numbers of 12345678901 and 2345678 are being processed by the ITSPB DigitMap 'xxx.' rule and are remaining unchanged until they hit the OutboundCallRoute, where 1aaa is added in the case of a 7-digit number.

What you've created is rather messy.  It appears you're wanting to use the ITSPA DigitMap with SP2 which is using ITSPB.  While that may be possible with enough alterations, it's a whole lot simpler and cleaner to keep SP1 using ITSPA's DigitMap and SP2 using ITSPB's DigitMap.

murzik

RonR
Thanks!
You helped me to understand better  how Digitmap works .

Saltine

I am very confused.  I have Google Voice set up on sp1 and a SIP provider on sp2.  Right now GV is set as my primary.  I want to be able to set GV to dial everything except 911 and toll free numbers.  I want my SIP provider to dial those.  How can I do it with without having to press **2.  Is there a way to do this?

jimates


OZOi

Simple question - what does (Mipd) stay for?

It's in default DigitMap rules in both ITSP profiles.
OBi100, firmware - v.1.2.1.

RonR

Mipd is a User Defined DigitMap and stands for IP Dialing.  It allows entry of a SIP URI from the keypad:

18005551212@tf.callwithus.com

can be dialed as:

18005551212*204*74*220*162

Cruize

I have GV on SP1 and my VOIP on SP2. I have set SP2 as my default line, but I want to pick SP1 for all calls to US  numbers.

I currently have the following OutboundCallRoute:
{([1-9]x?*(Mpli)):pp},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**9:>(Mpp)):pp},{(Mpli):pli}

How should I change this to accomplish what I want?

RonR

Why did you make the changes you did to your PHONE Port OutboundCallRoute?  Normally, no changes are required to it.

With SP2 set as your PrimaryLine, you can cause US/Canada calls to go out SP1 with the following change to your ITSPB DigitMap:

(<**1>1xxxxxxxxxx|<**11>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*]@@.)

TomTN

Hi everybody,
    I need help to create the dial plan following this (Obi 110 box):
Obi 110 firmware version: 1.2.1 (just updated tonite)
All calls local, long distance, and toll free are 10 and 11 digits only.

Primary line: --> PSTN
911            --> PSTN
407, 321 area code :  10 digits            --> PSTN
toll free 800,888,877,866,855: 11 digits --> PSTN
international:                                    --> PSTN ( occasionally calling)
other area codes: (long distance) 11 digits         --> Google voice (SP 1)
For long distance, I am not sure 10 digits will work or not,
but to make it consistent, I follow 11 digits like calling those toll free numbers.

Extra question:
when dial long distance, can home phone number (PSTN line)  be shown instead of Google voice number?
Thanks
TomTN.

RonR

#33
TomTN,

I haven't tested this, so there could be a surprise or two somewhere:


Physical Interfaces -> LINE Port -> DigitMap:

(321xxxxxxx|407xxxxxxx|1800xxxxxxx|1888xxxxxxx|1877xxxxxxx|1866xxxxxxx|1855xxxxxxx|011xx.|
<**1>1xxxxxxxxxx|<**11>xxxxxxxxxx)

On long distance calls through Google Voice, 10- or 11-digits may be dialed.

Google Voice does not permit the CallerID to be changed.

TomTN

Thanks for your quick help, RonR.
As you said, there are some surprise.

911: not tested, but add "|911|" to the digital map anyway
611, 511, 411: working (add "|611|511|411|" to the digital map)
long distance: 11 digits or 10 digits : working
toll free:     11 digits or 10 digits : working

Here are some problems:
calls to 407 local area code: sometimes recieving error msg
"We are sorry your call did not go through". But, If I try to dial it again the 2nd, the 3rd, or the 4th time, the call will eventually go thru.
calls to 321 area code numbers: if 321 exchanges are local, then the call go thru.
if 321 exchanges are local toll or long distance, then need to dial them as long distance call; otherwise recieving msg "we are sorry. when placing local call, it's neccessary to dial 1 plus area code plus seven digits number to complete this call."

Are there anything we can improve?
Thanks
TomTN

RonR

#35
Quote from: TomTN on May 13, 2011, 01:45:40 PM911: not tested, but add "|911|" to the digital map anyway

No change is needed for 911.  911 is already handled at the top-most level of PHONE Port DigitMap and sent to the LINE Port automatically.  |911| should not be added to the LINE Port DigitMap.

Quote from: TomTN on May 13, 2011, 01:45:40 PM611, 511, 411: working (add "|611|511|411|" to the digital map)

Your very explicit list didn't include these.   :)

Quote from: TomTN on May 13, 2011, 01:45:40 PMtoll free:     11 digits or 10 digits : working

Just for info...

11-digit toll free numbers are going to Bell South.
10-digit toll free numbers are going to Google Voice

If you want 10-digit toll free numbers to also go to Bell South, that's doable.

Quote from: TomTN on May 13, 2011, 01:45:40 PMcalls to 407 local area code: sometimes recieving error msg
"We are sorry your call did not go through". But, If I try to dial it again the 2nd, the 3rd, or the 4th time, the call will eventually go thru.

I seriously doubt this is a DigitMap problem.  This sounds like a DTMF dialing problem between the OBi and Bell South.  When this error occurs, review the Call History and verify it shows the correct number was dialed.  If the correct number was dialed, it's probably a DTMF problem.

Quote from: TomTN on May 13, 2011, 01:45:40 PMcalls to 321 area code numbers: if 321 exchanges are local, then the call go thru.
if 321 exchanges are local toll or long distance, then need to dial them as long distance call; otherwise recieving msg "we are sorry. when placing local call, it's neccessary to dial 1 plus area code plus seven digits number to complete this call."

If you have a relatively small number of 321 local exchanges, it may be possible to do something, but this could get messy real fast if the list is long.


TomTN

Quote from: RonR on May 13, 2011, 03:05:45 PM
Quote from: TomTN on May 13, 2011, 01:45:40 PM911: not tested, but add "|911|" to the digital map anyway

No change is needed for 911.  911 is already handled at the top-most level of PHONE Port DigitMap and sent to the LINE Port automatically.  |911| should not be added to the LINE Port DigitMap.

Quoteok. "|911|" removed from the digital map.

Quote from: TomTN on May 13, 2011, 01:45:40 PM611, 511, 411: working (add "|611|511|411|" to the digital map)

Your very explicit list didn't include these.   :)

Quote from: TomTN on May 13, 2011, 01:45:40 PMtoll free:     11 digits or 10 digits : working

Just for info...

11-digit toll free numbers are going to Bell South.
10-digit toll free numbers are going to Google Voice

If you want 10-digit toll free numbers to also go to Bell South, that's doable.

QuoteI got this part.
Quote from: TomTN on May 13, 2011, 01:45:40 PMcalls to 407 local area code: sometimes recieving error msg
"We are sorry your call did not go through". But, If I try to dial it again the 2nd, the 3rd, or the 4th time, the call will eventually go thru.

I seriously doubt this is a DigitMap problem.  This sounds like a DTMF dialing problem between the OBi and Bell South.  When this error occurs, review the Call History and verify it shows the correct number was dialed.  If the correct number was dialed, it's probably a DTMF problem.

Quotecan you tell me how to troubleshoot DTMF if this prob. occur again?

Quote from: TomTN on May 13, 2011, 01:45:40 PMcalls to 321 area code numbers: if 321 exchanges are local, then the call go thru.
if 321 exchanges are local toll or long distance, then need to dial them as long distance call; otherwise recieving msg "we are sorry. when placing local call, it's neccessary to dial 1 plus area code plus seven digits number to complete this call."

If you have a relatively small number of 321 local exchanges, it may be possible to do something, but this could get messy real fast if the list is long.

Quoteif recieve error msg, then I dial it as long distance.


RonR

Here's an updated DigitMap so that all toll free calls go to Bell South:

(411|511|611|1800xxxxxxx|1888xxxxxxx|1877xxxxxxx|1866xxxxxxx|1855xxxxxxx|
<1>800xxxxxxx|<1>888xxxxxxx|<1>877xxxxxxx|<1>866xxxxxxx|<1>855xxxxxxx|011xx.|
321xxxxxxx|407xxxxxxx|<**1>1xxxxxxxxxx|<**11>xxxxxxxxxx)

Can you determine which 321 area code exchanges are local to you?  If so and the list isn't too big, we should be able to make everything work automatically.

There's supposed to be a new firmware update soon to correct some DTMF problems.  I'd wait for it before trying anything yourself.  If you get the error again, check the Call History to make sure the OBi had dialed the correct number.

TomTN

thanks for the newly updated digital map.
I just look up area codes exchanges that local to my number in yellow pages, and here it is:
407 ->= 300 exchanges
321 ->= 120
352 ->= 16
surprise.
not ALL of 407 area codes exchanges are local to me, but only of 300 listed in the yellow pages.
Wish that somehow Obi box can automatically route local exchange to my PSTN,
and the rest to Google voice
Waiting for the DTMF fix in the new firmware.
what you think?

RonR

Quote from: TomTN on May 13, 2011, 07:39:51 PM
thanks for the newly updated digital map.
I just look up area codes exchanges that local to my number in yellow pages, and here it is:
407 ->= 300 exchanges
321 ->= 120
352 ->= 16
surprise.
not ALL of 407 area codes exchanges are local to me, but only of 300 listed in the yellow pages.
Wish that somehow Obi box can automatically route local exchange to my PSTN,
and the rest to Google voice
Waiting for the DTMF fix in the new firmware.
what you think?


There's no way to configure 436 special cases.  Unless there's a short list of non-local exchanges (to go the other direction), I'm out of ideas.