OBiTALK Community

I recently purchased an OBi110 and would like to configure it so that when I dial a long distance number, the call is routed out through my Google Voice Number. When I make a local call (local to my calling area and telecom service provider), the call goes out through my local carrier (ie. Telus Communications).

I had a friend help me out and he suggested the following:

Log into Obitalk.
Click on Obi Endpoint.
Click Obi Expert Config.
Click Yes.
Click Enter Obi Expert.
On left side menu under Physical Interfaces, click on Line.
Second setting from the top is called DigitMap.
Uncheck "Obitalk settings" at far right.
Enter this: (<403>xxxxxxx|403xxxxxxx|<**1>1xxxxxxxxxx|<**1>011xx.)
That's it... 911 and local 403 calls will always go Telus Communications, long distance will go over your Google Voice account.

I followed the instructions but when I call my cell phone or a friends land line from my phone connected to my OBi110, the CallerID number that shows up is my Google Voice number.

Is there a way that when I am calling a local number (so that the call routes through my local carrier - Telus) that the CallerID that displays on the phone I am calling will be my local number (ie. 403-xxx-xxxx) instead of my Google Voice Number, and conversely, when I make a long distance call, the CallerID number that is displayed is my Google Voice Number?

And... my local calling area now has 2 different area codes but they are both local calls, so how would I account for that? The area codes are: 403 and 587.

Thank you in advance.
Scott Turner.

Quote from: ssturner66 on April 24, 2012, 01:18:18 PM
I followed the instructions but when I call my cell phone or a friends land line from my phone connected to my OBi110, the CallerID number that shows up is my Google Voice number.

Is there a way that when I am calling a local number (so that the call routes through my local carrier - Telus) that the CallerID that displays on the phone I am calling will be my local number (ie. 403-xxx-xxxx) instead of my Google Voice Number, and conversely, when I make a long distance call, the CallerID number that is displayed is my Google Voice Number?

Calls made through your PSTN carrier (Telus) should show your Telus number for CallerID.  The OBi has no control over that.

Calls made through your Google Voice account will show your Google Voice number for CallerID.  Google Voice does not allow changing it.

Quote from: ssturner66 on April 24, 2012, 01:18:18 PM
my local calling area now has 2 different area codes but they are both local calls, so how would I account for that? The area codes are: 403 and 587.

(<aaa>[2-9]xxxxxx|403xxxxxxx|587xxxxxxx|<**1>1xxxxxxxxxx|<**1>011xx.)

where aaa is the area code (403 or 587) you wish to be assumed when 7-digit numbers are dialed.

RonR, It would appear that my OBi110 is not sending calls out my local carrier as all the CallerID's keep showing my Google Voice number.

I have made the changes you suggested by adding the |587xxxxxxx| into the DigiMap configuration under the Line setting. Just to make sure, I rebooted the OBi110 as well.

From the phone attached to my OBi110 (local 587-xxx-xxxx number), I dial my cell phone (which is a local 403-xxx-xxxx number).

My cell phone shows my Google Voice number 435-xxx-xxxx as the CallerID even though I made the call from my desk phone connected to my OBi110 and the call should have been a local call and should have routed out the PSTN port on the OBi110 and showed my 587-xxx-xxxx number as the CallerID.

I also tried calling my work which is a local 587-xxx-xxxx number but the CallerID still showed as my 435-xxx-xxxx Google Voice number.

Am I missing a configuration somewhere else to make the local PSTN CallerID show when calls route out the PSTN port for local calls?

Thank you.

Scott Turner

I suspect you have your PrimaryLine set to SP1 Service.  Verify you have all the following settings:


Physical Interfaces -> PHONE Port -> PrimaryLine : PSTN Line.

Physical Interfaces -> LINE Port -> DigitMap:

([2-9]11S0|<aaa>[2-9]xxxxxx|403xxxxxxx|587xxxxxxx|<**1>1xxxxxxxxxx|<**1>011xx.)

Service Providers -> ITSP Profile A -> General -> DigitMap:

(<1aaa>[2-9]xxxxxx|<1>[2-9]xxxxxxxxx|1xxxxxxxxxx|011xx.)

where aaa is the area code (403 or 587) you wish to be assumed when 7-digit numbers are dialed.


[2-9]11  ->  PSTN Line
  7 digits  ->  PSTN Line (with 403 or 587 added)
10 digits  ->  PSTN Line (that start with 403 or 587)
11 digits  ->  SP1 Service (that start with 1)
    011+  ->  SP1 Service

Hi RonR,

Sorry, but I'm a newbie here and you've lost me.

I got as far as the Physical Interfaces -> Phone Port -> PrimaryLine : PSTN Line.

The rest has me confused... do I enter it exactly as you have listed it ie. the ([2-9]11SO|<aaa>[2-9]xxxxxx|403xxxxxxx|587xxxxxxx|<**1>1xxxxxxxxxx|<**1>011xx.)

or am I supposed to be substituting numbers (of various lengths) for the [2-9] etc.

Not completely understanding your lines at the bottom of your message (the [2-9]11 -> PSTN Line etc.)

Thanks.

Scott Turner.

Simply copy/paste the values I listed into those settings.  They are the complete values.

Replace aaa with your area code (403 or 587).

The list at the bottom was just to show you what will go out where for the different dialing formats.

Scott -
just noticed that Ron's post has [2-9]11S0 - zero. For some reason your line looks like [2-9]11SO - letter oh. It should be zero...

Thanks RonR and Felix, I have my OBi110 up and running!
I appreciate your help in getting it working properly.

Scott Turner.

Sorry to revive this topic, but it almost exactly provides the information I'm looking for :)
I am such a newbie yet, that I don't know how to adapt the code above into this simple rule:

If we dial a 1 or 011 in the front, use Google Voice,
Everything else, use our landline (I think that sums it up?)
Oh wait, 1800 and other free numbers should use our landline too...

Thanks so much in advance  ;D

Edit, would this do?

([2-9]11S0|<250>[2-9]xxxxxx|250xxxxxxx|<**1>1xxxxxxxxxx|<**1>011xx.)

Ok... I studied the tutorial, but it is still rather difficult... would the following code be correct?

([2-9]11S0 | <250>xxx xxxx | <**1>1xxxxxxxxxx  !180x xxx xxxx !188x xxx xxxx | <**2>011xx. )


- [2-9]11S0 : (sorry, I don't understand this, what does it do?) - PSTN
- <250>xxx xxxx : anything with 7 digits will add 250 in front - PSTN
- <**1>1xxxxxxxxxx : anything that starts with 1 will use - SP1
- !180x xxx xxxx : except numbers that start with 180 ... - PSTN
- !188x xxx xxxx : except numbers that start with 188 ... - PSTN
- <**2>011xx. : international calls - SP2
- I think 911 is still missing? - PSTN

Please correct me if that was wrong, I think I am getting the hang if it by now :)

I thought ianobi would be by last night to give you the answers. I sent him a pm, he will be here later.

Aww thanks  :-* But really I am in no great hurry and it's good that I am forced to use my own rusty brain too  ;D

Sophia,

I'm assuming that you have PSTN on your Line Port, Google Voice on sp1, something on sp2? Also, Phone Port Primary Line is set:

Physical Interfaces -> PHONE Port -> PrimaryLine : PSTN Line

Leave the ITSP A and B DigitMaps at default.

To route the calls to the correct trunks (line, sp1 etc), use the Mpli (Map Primary Line). In your case this is the Line Port DigitMap:

Physical Interfaces -> LINE Port -> DigitMap:

([2-9]11S0|<250>[2-9]xxxxxx|250xxxxxxx|180xxxxxxxx|188xxxxxxxx|<**1>1[2-79]xxxxxxxxx|<**1>011xx.)

If you do have a service provider on sp2 through which you wish to send international calls, then:

Physical Interfaces -> LINE Port -> DigitMap:

([2-9]11S0|<250>[2-9]xxxxxx|250xxxxxxx|180xxxxxxxx|188xxxxxxxx|<**1>1[2-79]xxxxxxxxx|<**2>011xx.)

Calls will route as follows:

[2-9]11  ->  three digit numbers starting with 2 to 9 > PSTN Line
 7 digits  ->  Obi adds 250 > PSTN Line
10 digits  ->  that start with 250 > PSTN Line
11 digits -> that start with 180 > PSTN Line
11 digits -> that start with 188 > PSTN Line
11 digits  -> that start with 1 but not 18 > SP1 Service
   011+  ->  SP1 Service or SP2 if you use the **2 version

911 calls are a special case due to this rule in your Phone Port OutboundCallRoute:
{(<#:>|911):li}
This means that 911 calls will be sent direct to the Line Port regardless of anything in any DigitMap.

The above DigitMaps mean that you do not need to dial codes (**1 etc) to route the calls, the DigitMaps do it for you. However, if you wish to override the DigitMaps, then you can still dial **1 etc.

Feel free to ask questions – we are all learning here  :)
Sometimes my answers are a bit slow in coming as I am here when most of OBiLAND is asleep!

Edit: Refined 1xxxxxxxxxx to 1[2-79]xxxxxxxxx

Hello ianobi & sophia,

If I remember the user manual correctly, the exclamation mark "!" in the Digit Map in Sophia's Post#9 means preventing or blocking the calls following it:

!188x xxx xxxx (spaces for readability only, no spaces in reality)

I submit this post because I have had to block toll-free (18xx) calls from telemarketers to my GoogleVoice number, since the recipient is charged a toll.

Ianobi, please confirm if I am correct about the use of exclamation mark in DigitMaps.

Thanks

:)

tavie888,

Your general point is correct "!" is used to denote a barring rule. I assumed that in this context they must be typos ! used instead of | to separate one rule from another.

"!" can be useful in some contexts such as InboundCallRoutes, although there are other ways to create barring rules. DigitMaps mostly deal with outgoing calls. If you wanted to bar an outgoing route it seems simpler just to not include that route in the DigitMap.

Hello ianobi,

Thanks for your reply.  I also appreciate your explanation on the difference in purposes between that of DigitMap and InboundCallRoute. 

I wish Obihai improve their user manual accordingly and also add more practical examples on the use of "configuration rules", for lack of a better term.

Cheers!

  :)

Thanks so much for the replies! Actually I did not erroneously put the exclamation mark there, I thought I had to because I was under the impression that the overlapping 1 xxx xxx xxxx and 1 8xx xxxx would rule each other out... as they say "never assume" lesson learned  ;D

As for testing, I have a funny story to share, might as well do it here... This morning, our landline was out, we picked up the phone, got a Busy tone. So I plugged back the original setup, line to phone, same thing! Busy tone.

My husband FURIOUS, that is what happens when you monkey with things, why do you have to be such a geek, leave things alone, NOW you have done it....................... actually he didn't say any of those things (he is sweet) but I'm sure he thought all that  ;D
Anyway, he tested all the wires as far as he could, tried different setups, NOTHING! Still no dial tone, just the busy signal.

So I FINALLY started a chat session with Telus, our provider... what was the case? They are having a major outage! :o It wasn't my fault at all   ::) Anyway, I can't test things right now, we are waiting for things to get back to normal, and have our phone plugged in directly for the time being.

I'll let you know when I have been able to test things, in the meantime, thanks again for your help!  :-*

PS Yes we do have a second SP which is FreePhoneLine, I am not sure yet what to use it for but probably not for international calls. I just added that as an example :)

Keep on geeking - your husband will appreciate the cost savings  ;)

One thing to watch out for: If you cut and paste DigitMaps from here, then watch out for spaces creeping in; OBi really does not like spaces in its DigitMaps.

Quote from: ianobi on November 04, 2012, 01:29:37 AM
Keep on geeking - your husband will appreciate the cost savings  ;)

One thing to watch out for: If you cut and paste DigitMaps from here, then watch out for spaces creeping in; OBi really does not like spaces in its DigitMaps.

And sometimes when the digit map is on multiple lines it will only paste the first line. You may have to do it one line at a time to get it all in there. And as ianobi said, watch out for spaces or in call routes make sure the commas at in there.

Thanks so much for all your help! This is up and running now  ;D
I'm sure I will have more questions  :D

Ok............. blush.................. :-[

We're so happy with our OBi device, that we actually decided to drop our landline. We're going to port that to a prepaid phone line so we can take our time informing everybody to dial our VOIP number.

So now I have to figure out how to make all calls via Google Voice and FreePhoneLine  ;D Let's say all domestic calls over FreePhoneLine (SP1), and all international calls over Google Voice (SP2), that can't be that hard to set up, can it?

Quote from: Sophia on November 26, 2012, 05:53:53 PM
Ok............. blush.................. :-[

We're so happy with our OBi device, that we actually decided to drop our landline. We're going to port that to a prepaid phone line so we can take our time informing everybody to dial our VOIP number.

So now I have to figure out how to make all calls via Google Voice and FreePhoneLine  ;D Let's say all domestic calls over FreePhoneLine (SP1), and all international calls over Google Voice (SP2), that can't be that hard to set up, can it?

Simply port your landline to prepaid, then GV to keep the number...

Sophia,

With FPL on sp1 and GV on sp2. Set:

Physical Interfaces -> PHONE Port -> PrimaryLine : SP1 Service

Service Providers -> ITSP Profile A -> General -> DigitMap:

([2-9]11S4|<250>[2-9]xxxxxxS4|[2-9]xxxxxxxxxS0|1xxxxxxxxxxS0|<**2>011xx.)

Service Providers -> ITSP Profile B -> General -> DigitMap:

(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.)


Calls will route as follows:

[2-9]11  ->  three digit numbers starting with 2 to 9 > sp1
 7 digits  ->  Obi adds 250 > sp1
10 digits  ->  that start with 2-9 > sp1
11 digits  -> that start with 1 > sp1
   011+  ->  sp2

With regard to 911 calls, I would take a "belt and braces" approach. Although the above DigitMaps should route it correctly to FPL, I would makes changes in your Phone Port OutboundCallRoute:

Delete {(<#:>|911):li}

Insert {911:sp1},{(<#:>):li}

This will send 911 direct to sp1 with no delay.

I have guessed a little with Service Providers -> ITSP Profile A -> General -> DigitMap, as I'm not fully aware of what number formats FPL accept or need. You may need to get back to me about that.

I wish!!! But we are out in Canada, no way we can port our number to GV at the moment. In fact I don't think we can do it ever, because right now there is no VOIP provider who will accept numbers from our small town...  :(

Oh I see you posted while I was typing this, thanks for the information, ianobi!!

Hi everyone!
Sorry to hijack this thread but i actually have the same problem/setup as Sophie here.

I don't have a landline
My sp1 is google voice
My sp2 is Freephoneline.

I want the long distance calls to go out through GV and all the local calls to go use FPL.
I tried what was suggested in this post but so fare no luck..
Now when i try to do a call, it says there is no route for the call.

Any help with ITSPA, ITSPB and Physical phone digimaps would be greatly appreciated.

thanks,

Ok now i can make local phone calls, but not long distance call.

Here's my setup

SP1: GV
SP2: FPL

ITSP A (Googlevoice) digimap : (<1819>[2-9]xxxxxx|<1>[2-9]xxxxxxxxx|1xxxxxxxxxx|011xx.)
ITSP B (FPL) digimap : ([2-9]11S4|<819>[2-9]xxxxxxS4|[2-9]xxxxxxxxxS0|<**2>011xx.)

Physical phone digimap : ([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|**0|***|#|**1(Msp1)|**2(Msp2)|**9(Mpp)|(Mpli))

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

Like i said, i want to use FPL for local calls and googlevoice for longdistance.
Right now i can make local calls but when i do a long distance, i hear the noise of a busy line.

thanks,

Ok, everything works now, i was able to fix mon long distance call by adding this to my ITSPB

(<**1>1xxxxxxxxxx)

Just one question though, what is 011xx. for?

That one I can answer  ;D
011 is the code for international dialing from North America (in Europe, this is 00).

Quote from: ianobi on November 03, 2012, 04:11:05 AM
Sophia,

I'm assuming that you have PSTN on your Line Port, Google Voice on sp1, something on sp2? Also, Phone Port Primary Line is set:

Physical Interfaces -> PHONE Port -> PrimaryLine : PSTN Line

Leave the ITSP A and B DigitMaps at default.

To route the calls to the correct trunks (line, sp1 etc), use the Mpli (Map Primary Line). In your case this is the Line Port DigitMap:

Physical Interfaces -> LINE Port -> DigitMap:

([2-9]11S0|<250>[2-9]xxxxxx|250xxxxxxx|180xxxxxxxx|188xxxxxxxx|<**1>1[2-79]xxxxxxxxx|<**1>011xx.)

If you do have a service provider on sp2 through which you wish to send international calls, then:

Physical Interfaces -> LINE Port -> DigitMap:

([2-9]11S0|<250>[2-9]xxxxxx|250xxxxxxx|180xxxxxxxx|188xxxxxxxx|<**1>1[2-79]xxxxxxxxx|<**2>011xx.)

Calls will route as follows:

[2-9]11  ->  three digit numbers starting with 2 to 9 > PSTN Line
  7 digits  ->  Obi adds 250 > PSTN Line
10 digits  ->  that start with 250 > PSTN Line
11 digits -> that start with 180 > PSTN Line
11 digits -> that start with 188 > PSTN Line
11 digits  -> that start with 1 but not 18 > SP1 Service
    011+  ->  SP1 Service or SP2 if you use the **2 version

911 calls are a special case due to this rule in your Phone Port OutboundCallRoute:
{(<#:>|911):li}
This means that 911 calls will be sent direct to the Line Port regardless of anything in any DigitMap.

The above DigitMaps mean that you do not need to dial codes (**1 etc) to route the calls, the DigitMaps do it for you. However, if you wish to override the DigitMaps, then you can still dial **1 etc.

Feel free to ask questions – we are all learning here  :)
Sometimes my answers are a bit slow in coming as I am here when most of OBiLAND is asleep!

Edit: Refined 1xxxxxxxxxx to 1[2-79]xxxxxxxxx

Hello,

I've replaced the default "Physical Interfaces->LINE Port->DigitMap" with:

([2-9]11S0|0|[2-9]xxxxxx|<530:>530xxxxxxx|18[06-8][06-8]xxxxxxx|<**1>1[2-79]xxxxxxxxx|<**1>011xx.)

The results are as follows:

Test1: 911 to reach emergency services: Have not tested
Test2: 0 to reach the PSTN operator: Call routed properly through PSTN
Test3: Seven digit 530 area code number: Call routed properly through PSTN
Test4: Ten digit 530 area code number: Does not funciton - Single ring, delay, and then "Call did not go through. Please try your call again" error message
Test5: Ten digit 800,866,877, or 888 area code number: Does not funciton - Single ring, delay, then busy signal
Test6: Eleven digit 530 area code number: Call routed properly through GV
Test7: Eleven digit 800,866,877, or 888 area code number: Call routed properly through PSTN
Test8: Eleven digit long distance number: Have not tested
Test9: **8 + seven digit local number: Call routed properly through PSTN
Test10: **8 + eleven digit long distance number: Does not funciton - "No call route available to complete call"

I don't understand why Test4, Test5, or Test10 are failing.

Looking at the "Status->Call History" after a Test4 call it appears that the last three characters are removed insteat of the first three: "5309021". Same on Test5: "8004444".

No clue why Test10 is failing - maybe I have to change the "PHONE->OutboundCallRoute"?

Any assitance would be much appreciated.

Thanks!

Busthead,

Your original Line Port DigitMap:

([2-9]11S0|0|[2-9]xxxxxx|<530:>530xxxxxxx|18[06-8][06-8]xxxxxxx|<**1>1[2-79]xxxxxxxxx|<**1>011xx.)

Test1: 911 to reach emergency services: Have not tested
This should be no problem - 911 calls are a special case due to this rule in your Phone Port OutboundCallRoute:
{(<#:>|911):li}
This means that 911 calls will be sent direct to the Line Port regardless of anything in any DigitMap.

Test4: Ten digit 530 area code number: Does not funciton - Single ring, delay, and then "Call did not go through. Please try your call again" error message.
I suspect this rule [2-9]xxxxxx is matching the first seven of the ten digits dialled and sending out to line after the seventh digit. I will add a S4 delay in the proposed DigitMap.

Test5: Ten digit 800,866,877, or 888 area code number: Does not funciton - Single ring, delay, then busy signal.
Same problem as Test4, plus there is no route for ten digit numbers starting with 8.

Test8: Eleven digit long distance number: Have not tested
This should work fine through GV on sp1.

Test10: **8 + eleven digit long distance number: Does not funciton - "No call route available to complete call".
OBi is telling you the truth! Your digit map is designed to send long distance eleven digit numbers to GV. If you want the ability to use both, then you will need to change <**1>1[2-79]xxxxxxxxx to 1[2-79]xxxxxxxxx then long distance will go through PSTN unless you manually dial **1 followed by eleven digits. Or you make GV on sp1 your PrimaryLine, then we redirect all the PSTN numbers from there. I'll assume leave PrimaryLine as PSTN for now. No need to change Phone Port OutboundCallRoute.

Proposed Line Port DigitMap:

([2-9]11S0|0|[2-9]xxxxxxS4|<530:>530xxxxxxx|8[06-8][06-8]xxxxxxx|18[06-8][06-8]xxxxxxx|<**1>1[2-79]xxxxxxxxx|<**1>011xx.)

Try this DigitMap and come back if needed for fine tuning or a complete rewrite  :)

Quote from: ianobi on November 30, 2012, 01:43:36 AM
Busthead,

Your original Line Port DigitMap:

([2-9]11S0|0|[2-9]xxxxxx|<530:>530xxxxxxx|18[06-8][06-8]xxxxxxx|<**1>1[2-79]xxxxxxxxx|<**1>011xx.)

Test1: 911 to reach emergency services: Have not tested
This should be no problem - 911 calls are a special case due to this rule in your Phone Port OutboundCallRoute:
{(<#:>|911):li}
This means that 911 calls will be sent direct to the Line Port regardless of anything in any DigitMap.

Test4: Ten digit 530 area code number: Does not funciton - Single ring, delay, and then "Call did not go through. Please try your call again" error message.
I suspect this rule [2-9]xxxxxx is matching the first seven of the ten digits dialled and sending out to line after the seventh digit. I will add a S4 delay in the proposed DigitMap.

Test5: Ten digit 800,866,877, or 888 area code number: Does not funciton - Single ring, delay, then busy signal.
Same problem as Test4, plus there is no route for ten digit numbers starting with 8.

Test8: Eleven digit long distance number: Have not tested
This should work fine through GV on sp1.

Test10: **8 + eleven digit long distance number: Does not funciton - "No call route available to complete call".
OBi is telling you the truth! Your digit map is designed to send long distance eleven digit numbers to GV. If you want the ability to use both, then you will need to change <**1>1[2-79]xxxxxxxxx to 1[2-79]xxxxxxxxx then long distance will go through PSTN unless you manually dial **1 followed by eleven digits. Or you make GV on sp1 your PrimaryLine, then we redirect all the PSTN numbers from there. I'll assume leave PrimaryLine as PSTN for now. No need to change Phone Port OutboundCallRoute.

Proposed Line Port DigitMap:

([2-9]11S0|0|[2-9]xxxxxxS4|<530:>530xxxxxxx|8[06-8][06-8]xxxxxxx|18[06-8][06-8]xxxxxxx|<**1>1[2-79]xxxxxxxxx|<**1>011xx.)

Try this DigitMap and come back if needed for fine tuning or a complete rewrite  :)

Very much appreciate the prompt reply and assistance.

I'm satisfied with just removing the <530:>530xxxxxxx digit map for now and not supporting the ten digit dial functionality.

I would however like to know how I can maintain PSTN as the PrimaryLine and GV for long distance but occasionally route long distance calls over PSTN (for outbound faxing). I though prepending **8 to the dialed number would do the trick.

Thanks

There are two answers. First, rewrite the DigitMaps to make sp1 the PrimaryLine, then you can redirect eleven digit numbers to PSTN using **8. All other numbers would route automatically. Second, if it is only very occassional use for faxes, then simply press # before dialling the number. This will connect you direct to the PSTN line with no OBi DigitMaps involved.

Let me know if you want to go with the first suggestion and I will suggest suitable DigitMaps.

Quote from: ianobi on December 01, 2012, 04:38:06 AM
There are two answers. First, rewrite the DigitMaps to make sp1 the PrimaryLine, then you can redirect eleven digit numbers to PSTN using **8. All other numbers would route automatically. Second, if it is only very occassional use for faxes, then simply press # before dialling the number. This will connect you direct to the PSTN line with no OBi DigitMaps involved.

Let me know if you want to go with the first suggestion and I will suggest suitable DigitMaps.

Pressing # before faxing is an easy enough solution. Here is the digit map I ended up with:

([2-9]11S0|0|[2-9]xxxxxx|18[06-8][06-8]xxxxxxx|<**1>1[2-79]xxxxxxxxx|<**1>011xx.)

Much thanks.

1  Not sure if I can port my # to GV, Bandwith.com does is not listed in my Central office.  But it is in my local calling area.  
2  If the internet went down, my wife would not be happy if we relied on GV
3  My wife does not want the phone to function any differently than it does now

Currently I have a bundle with Cox. Thinking about ditching CATV for OTA TV, & ditching cox phone, and getting a "Baby Bell" phn, because I am a "Baby Bell" retiree and can get local service cheap (+ discounts on features, nothing on LD)

I see on this thread, you can set up LD calling to be done thru GV, and local calling thru your PSTN line.

One problem I see, is if my wife is on our PSTN line right now, I know I can always use a phn connected to my OBI and use GV to dial out.
If she was using our cordless system connected to the Obi 110, I would not know which line she is using.

When you add a PSTN line to your Obi, are you not giving up a way to have two concurrent phone calls?

and the other problem is outgoing caller id on LD, would be different

Quote from: dircom on March 04, 2013, 06:51:28 PM
One problem I see, is if my wife is on our PSTN line right now, I know I can always use a phn connected to my OBI and use GV to dial out.
A) If she was using our cordless system connected to the Obi 110, I would not know which line she is using.

B) When you add a PSTN line to your Obi, are you not giving up a way to have two concurrent phone calls?

C) and the other problem is outgoing caller id on LD, would be different

A) No, not true. An Obi110 has only one phone line (one jack) for an analog phone handset. The second jack is for the PSTN line, therefore if wife is on phone she is using the one and only phone line for her analog phone handset.  Her call may be going out VoIP/GV or PSTN, that you do not know unless you look at lights on the device or call status in the device web page.

B) No. For an Obi110 there are two ports/jacks on an Obi110, one for an analog handset, and one for a PSTN line. These are not interchangeable. See this: http://www.obihai.com/matrix.html.

One possible solution for your case is to use an Obi110 and an Obi202, in which you would configure a means for a phone handset on the Obi202 to make a call terminating on the PSTN line on the Obi110. If the PSTN line is in use you'd get a fast busy ringback or whatever you configure.

C) True.

I meant to say, leaving my existing PSTN line alone (not connected thru the obi), hooking up a separate phn to the OBI 110, I now have two phone numbers, that can function separately from each other.

I know some people use a PSTN # hooked up to a 110 for 911 purposes, or for overseas calling schemes.
In my case I was thinking about hooking up the PSTN line to the 110 for free LD

While you can look at the lights as you mentioned or look at the call status, its not a practical way to know what line was being used

If I connected the PSTN line to the obi, (and programmed the obi to use GV for LD) and plugged my cordless system into the OBI  calls into either # (PSTN or GV) would ring on the cordless, which is convenient.

But would I not be giving up the ability to make and receive 2 calls at the same time?
I don't see a practical solution, other than keeping the two lines separate (not connected thru the obi), and using a two line cordless system which is expensive .

If you have a PSTN now, and you get an OBi, and you hookup the PSTN to the OBi, then YES, you've eliminated the ability to use both lines at the same time.  Pretty straightforward.

If you MUST use two lines at once, you can buy an OBi 202.  However, that doesn't let you use your PSTN, which is why it was suggested below to use both a 110 and a 202.

One issue you're going to have, based on your questions, is that this seems to be somewhat confusing for you.  You say you were thinking of hooking up the PST to the 110 for free LD, what you meant to say was that you were thinking of getting a 110 to hookup to your phones so that when you want to call LD you use GV instead of the PSTN line, i.e. you have that choice.

I'd suggest, based on your questions, that you consider another option.  Keep your PSTN line hooked up like it is.  Buy an OBi 100.  Hookup a new wireless phone to it.  That's your Long Distance phone system.  Use the existing PSTN line for 911 and to receive calls.  Then you have both your two line requirement met and the ability to receive calls and use 911.

Or, don't do anything.  Get a GV number, use Google Talk on the computer with a headset to make free outgoing calls.  Or, if the PSTN is not being used, simply have Google Talk ring the house phone when making the call.  Info on how to do all that is on the Google Voice forums.

Quote from: Rick on March 05, 2013, 05:12:18 AM
If you have a PSTN now, and you get an OBi, and you hookup the PSTN to the OBi, then YES, you've eliminated the ability to use both lines at the same time.  Pretty straightforward.

I installed a 110 - It is straightforward, especially since I installed phones for a living, and did tech support for FIOS.  Just wanted to make sure I was not missing anything :)

If you MUST use two lines at once, you can buy an OBi 202.  However, that doesn't let you use your PSTN, which is why it was suggested below to use both a 110 and a 202.

One issue you're going to have, based on your questions, is that this seems to be somewhat confusing for you.  You say you were thinking of hooking up the PST to the 110 for free LD, what you meant to say was that you were thinking of getting a 110 to hookup to your phones so that when you want to call LD you use GV instead of the PSTN line, i.e. you have that choice.

Of course, for free LD, using GV

I'd suggest, based on your questions, that you consider another option.  Keep your PSTN line hooked up like it is.  Buy an OBi 100.  Hookup a new wireless phone to it.  That's your Long Distance phone system.  Use the existing PSTN line for 911 and to receive calls.  Then you have both your two line requirement met and the ability to receive calls and use 911.

Using my 110 in that manner as we speak

Or, don't do anything.  Get a GV number, use Google Talk on the computer with a headset to make free outgoing calls.  Or, if the PSTN is not being used, simply have Google Talk ring the house phone when making the call.  Info on how to do all that is on the Google Voice forums.

GV, OBI etc works great, I have no problem installing or using so far.
My only problem is to make the system transparent to my wife.
No way to do that as GV doesn't support name caller iD
and she doesn't want to use one phone to receive calls, and another to make calls,
and I don't want to tie them both together because I lose concurrent calling/receiving

Again, just checking to see if I missed anything, thanks for all the responses (and sorry for going off topic on this thread)

It appears I could port my phone# to a voip provider that has caller id with name
& then set up my obi to use GV for outbound

That way it would be transparent to my wife, it the phone would operate pretty much the same as our PSTN line
except that the outbound caller id would be different

Is that correct?   
If so any recommendations for free or inexpensive (but high quality) voip service for incoming calls with Caller id w/name?

Sorry to revive this super old topic, but I too am running into a problem now. We have a friend in Florida whose number starts with 863, but we can't get through to him.

Our current LINE DigitMap says:

([2-9]11S0|<250>[2-9]xxxxxx|250xxxxxxx|<1:>250xxxxxxx|1800xxxxxxx|188xxxxxxxx|1877xxxxxxx|1866xxxxxxx|1855xxxxxxx|
1844xxxxxxx|1833xxxxxxx|1822xxxxxxx|<**1>1[2-79]xxxxxxxxx|<**1>011xx.)

I'm thinking the error is in the <**1>1[2-79]xxxxxxxxx bit, but unclear how to change it.

What we're after is that all numbers starting with 1-xxx including 1-8xx (EXCEPT the toll free numbers starting with 800, 88x, 877, 866, 855, 844, 833 and 822) are routed through Google Voice. The exceptions should go through the landline. Is it possible to set it up that way? :)

Quote from: Sophia on January 11, 2014, 03:47:37 PM
Sorry to revive this super old topic, but I too am running into a problem now. We have a friend in Florida whose number starts with 863, but we can't get through to him.

Our current LINE DigitMap says:

([2-9]11S0|<250>[2-9]xxxxxx|250xxxxxxx|<1:>250xxxxxxx|1800xxxxxxx|188xxxxxxxx|1877xxxxxxx|1866xxxxxxx|1855xxxxxxx|
1844xxxxxxx|1833xxxxxxx|1822xxxxxxx|<**1>1[2-79]xxxxxxxxx|<**1>011xx.)

I'm thinking the error is in the <**1>1[2-79]xxxxxxxxx bit, but unclear how to change it.

What we're after is that all numbers starting with 1-xxx including 1-8xx (EXCEPT the toll free numbers starting with 800, 88x, 877, 866, 855, 844, 833 and 822) are routed through Google Voice. The exceptions should go through the landline. Is it possible to set it up that way? :)

I puzzled that you say the digit map you show is your LINE Port Digit Map.  Are you sure it isn't the PHONE port digit map?

Try adding |<**1>1863xxxxxxx| into the map.  It can go anywhere but perhaps the "nicest" place would be just after the bit you think the error is in.

I'm only following instructions :D I am quite happy to put it anywhere but initially I was told to put it in the LINE digit map... and it seems to work :)

Somebody just kindly sent me a PM with this information:

([2-9]11S0|<1250>[2-9]xxxxxx|<1>250xxxxxxx|1250xxxxxxx|(18(00|88|77|66|55|44|33|22)xxxxxxx|<1>8(00|88|77|66|55|44|33|22)xxxxxxx)|<**1>(1xxxxxxxxxx|011xx.))

It looks really nice to me so I guess I'll try that  ;D Will keep you posted!

Unfortunately that code doesn't seem to work at all  ???

But I changed it into

([2-9]11S0|<250>[2-9]xxxxxx|250xxxxxxx|<1:>250xxxxxxx|1800xxxxxxx|188xxxxxxxx|1877xxxxxxx|
1866xxxxxxx|1855xxxxxxx|1844xxxxxxx|1833xxxxxxx|1822xxxxxxx|<**1>1xxxxxxxxxx|<**1>011xx.)

Which is probably not as clean but it seems to work  ;D

Hi Sophia, good to see you're using the Obi again. I don't know how many 800 numbers there are for your location, but a trick that RonR posted way back when is great for them. Create a "User Defined map" that looks something like this (18(00|55|66|77|88)xxxxxxx) and name it TFree. Then any place you need to specify 800 numbers simply use (MTfree). Be sure and include the M and the parenthesis. If your 800 numbers are different, simply change the User defined map. Works like a charm and greatly simplifies things if 8xx numbers would happen to change. You only need to change one place!

Hi ProfTech, thanks  ;D I couldn't stay away anyway, I like Obi too much :D

I got the list of 800 numbers from http://en.wikipedia.org/wiki/Toll-free_telephone_number#North_America "Toll-free numbers in the North American Numbering Plan (NANP) are commonly called "800 numbers" after the original area code which was used to dial them. They include the area code 800 since 1967, 888 (since 1996), 877 (since 1998), 866 (since 2000), 855 (since 2010), and 844 (December 7, 2013).[18] Area codes reserved for future expansion include 833, 822, 880 through 887, and 889.[19]"

I thought I might as well include them all now :D

Got another PM from the anonymous benefactor that the code they provided

([2-9]11S0|<1250>[2-9]xxxxxx|<1>250xxxxxxx|1250xxxxxxx|(18(00|88|77|66|55|44|33|22)xxxxxxx|<1>8(00|88|77|66|55|44|33|22)xxxxxxx)|<**1>(1xxxxxxxxxx|011xx.))

should work (I probably copied it wrong) so I'll be giving that a second try :)

Edit: while I'm typing this, I actually think I know what might be wrong with that code... this is what the explanation was:

Quotex11 -> LINE Port
7-digits -> LINE Port (with 1250 prepended)
250xxxxxxx -> LINE Port (with 1 prepended)
1250xxxxxxx -> LINE Port
Toll Free -> LINE Port (with 1 prepended if not present)
All other 1xxxxxxxxxx -> SP1
011+ (international) -> SP1

But the 7 digits should actually not add 1250, just 250.
Likewise, 250xxxxxx should not prepend a 1
and 1250 should be treated like all other numbers, meaning using SP1.

So I think this is what it should read:

Quotex11 -> LINE Port
7-digits -> LINE Port (with 250 prepended)
250xxxxxxx -> LINE Port (with 1 prepended)
1250xxxxxxx -> LINE Port
Toll Free -> LINE Port (with 1 prepended if not present)
All other 1xxxxxxxxxx -> SP1
011+ (international) -> SP1

Another edit, I got a reply back already!!!

QuoteIn that case:

Physical Interfaces -> LINE Port -> DigitMap:

([2-9]11S0|<250>[2-9]xxxxxx|[2-9]xxxxxxxxx|18(00|88|77|66|55|44|33|22)xxxxxxx|<1>8(00|88|77|66|55|44|33|22)xxxxxxx|<**1>(1xxxxxxxxxx|011xx.))

x11 -> LINE Port
7-digits -> LINE Port (with 250 prepended)
10-digits -> LINE Port
Toll Free -> LINE Port (with 1 prepended if not present)
All other 1xxxxxxxxxx -> SP1
011+ (international) -> SP1

Hmmm - anonymous benefactor and a digit map style that looks familiar - I reckon I could take a guess who that might be! Of course, I'm too much of a gentleman to mention a name   :)

You just gotta love all the intrigue  ;D ;D ;D

Quote from: ianobi on January 17, 2014, 12:11:01 PM
Hmmm - anonymous benefactor and a digit map style that looks familiar - I reckon I could take a guess who that might be! Of course, I'm too much of a gentleman to mention a name   :)

never mention an unperson. ;D

Hi Everyone,

My OBI110 has been working fine until I updated it the other day. Now my call routing that was set up no longer works. When I call from the local phone line connected to my OBI110 to my cell phone, the caller ID that shows up is my Google Voice Number whereas it used to be my local number as the call was a local call, not a long distance call.
I looked through the thread and found the posts by RonR about configuring my Primary Line and DigitMap. I looked at my OBI110 and the lines that used to be there are definitely different. I have tried on several occasions to replace the new lines with the ones that were in RonR's post but after I make the change, click submit at the bottom of the configuration page and reboot the OBI110, when it comes back on line, the line I entered is gone and replaced by what used to be there.
I need to change the PrimaryLine from SP1 Service to PSTN Line but nomatter what I do, it always reverts back to SP1 Service. Same thing for the DigitMap under the Physical Interfaces -> LINE Port -> DigitMap:.

Any suggestions?

Thanks.

Scott Turner

Quote from: ianobi on November 27, 2012, 09:47:04 AM
Sophia,

With FPL on sp1 and GV on sp2. Set:

Physical Interfaces -> PHONE Port -> PrimaryLine : SP1 Service

Service Providers -> ITSP Profile A -> General -> DigitMap:

([2-9]11S4|<250>[2-9]xxxxxxS4|[2-9]xxxxxxxxxS0|1xxxxxxxxxxS0|<**2>011xx.)

Service Providers -> ITSP Profile B -> General -> DigitMap:

(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.)


Calls will route as follows:

[2-9]11  ->  three digit numbers starting with 2 to 9 > sp1
 7 digits  ->  Obi adds 250 > sp1
10 digits  ->  that start with 2-9 > sp1
11 digits  -> that start with 1 > sp1
   011+  ->  sp2

How do you change the DigitMap to route certain Canadian calls (11 digits) with specific area codes to SP1, and all other Canadian and US calls (11 digits) to SP2?

e.g.
10 digits -> 250, 530 > SP1
11 digits -> 1-234-xxxx, 1-567-xxxx > SP1 (the dashes are for reading purpose only)
all other 11 digits -> SP2

Physical Interfaces -> Phone Port -> Primary Line: SP2 Service.

Physical Interfaces -> Phone Port -> DigitMap
Add AFTER the beginning parenthesis:
(Msp1)|

Physical Interfaces -> Phone Port -> OutboundCallRoute
Add to the beginning:
{(Msp1):sp1},

Service Providers -> ITSP Profile A -> General -> DigitMap:
((250|530)xxxxxxx|1(234|567)xxxxxxx)

Service Providers -> ITSP Profile B -> General -> DigitMap:
(1xxxxxxxxxx)

10 digit numbers other than 250 and 530 will fail.
Did you want international numbers?

Quote from: azrobert on January 06, 2015, 02:02:30 PM
Physical Interfaces -> Phone Port -> Primary Line: SP2 Service.

Physical Interfaces -> Phone Port -> DigitMap
Add AFTER the beginning parenthesis:
(Msp1)|

Physical Interfaces -> Phone Port -> OutboundCallRoute
Add to the beginning:
{(Msp1):sp1},
[/quote]

I want the SP1 to be my primary line, are these settings still valid?

Quote from: azrobert on January 06, 2015, 02:02:30 PM
Service Providers -> ITSP Profile A -> General -> DigitMap:
((250|530)xxxxxxx|1(234|567)xxxxxxx)

Service Providers -> ITSP Profile B -> General -> DigitMap:
(1xxxxxxxxxx)

10 digit numbers other than 250 and 530 will fail.
Did you want international numbers?

This is a little tricky. Let me explain my usage. I'm using freephoneline as my SP1, it covers most of Canadian area codes for free. However, I'm not sure if there is a reliable way to determine if an area code is Canadian or US. 250 and 530 are "examples" local area codes. 234 and 567 are "examples" of covered Canadian area codes. All other area codes, I'll have to consider them as non-covered Canadian/US area codes, which is why it will require users to explicitely dialing "1".

I have modified profile A to:
(911|<1>(250|530)xxxxxxx|1(234|567)xxxxxxx|*98|[6-7]x*xxxxxxxxxxx.)
Is this correct?
Also I left the default [6-7]x*xxxxxxxxxxx. there. What is it?

Thanks!

I'm not sure what [6-7]x*xxxxxxxxxxx. is used for.
It might be used for routing calls over the OBiTalk network to a 2nd OBi.

What you are doing will not work without additional code.

You said "These are examples".
That means there are additional area codes. Correct?
Are you going to code all the Canadian area codes into the configuration?
It looks like all the numbers will be sent to the providers as 11 digits.
Will the users know what all the local Canadian numbers are?
If yes, you can route all 10 digit numbers to FPL.
Will the users know what all the covered Canadian numbers are?
If yes, they can dial those as 10 digit numbers.
Then 11 digit numbers can be routed to SP2.
I have a feeling you won't like the above.

This is how an OBi works.
First, the ITSP DigitMaps do NOTHING on their own.
After a number is dialed the Phone Port (PP) DigitMap gets control.
The PP DigitMap validates the dialed number.
The last rule (Mpli) points to the Primary Lines's (PL) DigitMap.
So if the PL is SP1, the ITSP A DigitMap is included with the PP DigitMap.
If you add a prefix, the dialed number is changed now.

If the number is validated by the PP DigitMap, it is passed the PP OutboundCallRoute.
Rule {(Mpli):pli} points to the PL DigitMap and the PL.
If the PL is SP1 and the dialed number matches a rule in the ITSP A DigitMap the call is routed out SP1.

If PL is SP1:
If you dial a 10 digit 250 number it is changed to 11 digits in the PP DigitMap.
Now it won't match rule <1>(250|530)xxxxxxx in the OutboundCallRoute and fail.
That rule is looking for a 10 digit number and will prefix it with "1".

If you make the PL SP2 you won't have this problem, but you might have other problems.

The PL is normally used to route un-prefixed calls to a specific trunk.
You would use a **n prefix to route calls to other trunks.
You are trying to eliminate the **n prefix, so which trunk is the PL is basically irrelevant.

Anyway, try this:
Physical Interfaces -> Phone Port -> Primary Line: SP2 Service.

Physical Interfaces -> Phone Port -> DigitMap
Add anywhere
(250|530)xxxxxxx|*98|

Physical Interfaces -> Phone Port -> OutboundCallRoute
Add to the beginning:
{(Msp1):sp1},

Service Providers -> ITSP Profile A -> General -> DigitMap:
(911|<1>(250|530)xxxxxxx|1(234|567)xxxxxxx|*98)

Service Providers -> ITSP Profile B -> General -> DigitMap:
(1xxxxxxxxxx)

You are verifying 10 digit numbers in the PP DigitMap without adding a prefix.
Now it will match the OutboundCallRoute.

By placing {(Msp1):sp1} at the beginning of the OutboundCallRoute, you are actually making SP1 the PL.
SP1 will have priority over SP2.

Thank you for the very detailed information. I'll try this out tonight.

Do I still need to do this:
Physical Interfaces -> Phone Port -> DigitMap
Add AFTER the beginning parenthesis:
(Msp1)|


When I said "These are examples", you are correct that I mean there may be additional area codes. But I'm not going to code all the area codes to the configuration. I am only coding the current local area codes with my old local carrier. I'm in the process of porting out and dumping the local carrier, but don't want to change the family's habit in dialing.

Quote from: BB88 on January 07, 2015, 07:59:23 AM
Do I still need to do this:
Physical Interfaces -> Phone Port -> DigitMap
Add AFTER the beginning parenthesis:
(Msp1)|

No, you should not add (Msp1) to the PP DigitMap.
I replaced this by adding "(250|530)xxxxxxx"

Previously (Msp1) did not add a "1" prefix.
Now with adding "1" it would screw up routing in the OutboundCallRoute.
You want to pass the dialed number unchanged to the OutboundCallRoute.

I tried your settings and it appears to be working. However, I still want to tinker things myself to keep SP1 as primary line, and I came up with the following, while keeping many settings as default:

Physical Interfaces -> PHONE Port -> DigitMap:
([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|**0|***|#|##|**70(Mli)|**8(Mbt)|**81(Mbt)|**82(Mbt2)|**1(Msp1)|**2(Msp2)|**3(Msp3)|**4(Msp4)|**9(Mpp)|*98|(Mpli))
this is the device default setting

Physical Interfaces -> PHONE Port -> OutboundCallRoute:
{([1-9]x?*(Mpli)):pp},{911:sp1},{(<##:>):li},{(<**70:>(Mli)):li},{(<**82:>(Mbt2)):bt2},{(<**81:>(Mbt)):bt},{(<**8:>(Mbt)):bt},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Msp3)):sp3},{(<**4:>(Msp4)):sp4},{(<**9:>(Mpp)):pp},{((00|011)xx.):sp1},{(1(250|530)[2-9]xxxxxx|(250|530|234|567)[2-9]xxxxxx):sp1},{(18(00|88|77|66|55)[2-9]xxxxxx|8(00|88|77|66|55)[2-9]xxxxxx):sp1},{(1[2-9]xx[2-9]xxxxxx):sp2},{([2-9]xx[2-9]xxxxxx):sp1},{([2-9]xxxxxx):sp1},{(Mpli):pli}
this is where I set up all the routing rules, inspired by RonR's OBi Configuration Utility

Physical Interfaces -> PHONE Port -> PrimaryLine: SP1 Service

Service Providers -> ITSP Profile A -> General -> DigitMap:
(911|[2-9]xxxxxx|[2-9]xx[2-9]xxxxxx|1[2-9]xx[2-9]xxxxxx|(00|011)xx.|*98|[6-7]x*xxxxxxxxxxx.)
this is the default setting when I set it up through OBiTalk Compatible Service Provider freephoneline.ca)

Service Providers -> ITSP Profile B -> General -> DigitMap:
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*#]@@.)
this is the default setting when I set it up through OBiTalk Approved Service Provider Google Voice)

Star Codes -> Star Code Profile A -> Code28 -> *95, Blind Transfer, coll($Bbxrn)

These settings also seem to do what I want.
I have a couple questions:
1. In the ITSP Profile B (Google Voice) DigitMap, I believe the <1>[2-9]xxxxxxxxx|011xx. are redundant, since they will be routed to SP1.
What does (Mipd)|[^*#]@@. do?  Again, they are the default settings from the automatic setup process.
2. Star Codes
In the PP DigitMap, there is a ***. Does it already cover the *98 in the later part of the PP DigitMap?
Also, Star Code28 has been changed to *95. Is *98 still valid?  Which one is needed in which DigitMap (PP and/or ITSP profile)?  I copied these setting from other's.

Physical Interfaces -> PHONE Port -> OutboundCallRoute:
{([1-9]x?*(Mpli)):pp},{911:sp1},{(<##:>):li},{(<**70:>(Mli)):li},{(<**82:>(Mbt2)):bt2},{(<**81:>(Mbt)):bt},{(<**8:>(Mbt)):bt},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Msp3)):sp3},{(<**4:>(Msp4)):sp4},{(<**9:>(Mpp)):pp},{((00|011)xx.):sp1},{(<1>(250|530)[2-9]xxxxxx|1(234|567)[2-9]xxxxxx):sp1},{(18(00|88|77|66|55)[2-9]xxxxxx):sp1},{(1[2-9]xx[2-9]xxxxxx):sp2}

{(Mpli):pli} The primary line is redundant since all the checks are hard coded previously. Removed.
{([2-9]xxxxxx):sp1} 7 digit dialing not required. Removed.
{([2-9]xx[2-9]xxxxxx):sp1} Any 10 number not required. removed.
8(00|88|77|66|55)[2-9]xxxxxx 10 digit 800 numbers not required. Removed.
{(18(00|88|77|66|55)[2-9]xxxxxx):sp1} 800 numbers to SP1?
250 and 530 11 digits not required. Removed.
International calls to SP1?

{(1(250|530)[2-9]xxxxxx|(250|530|234|567)[2-9]xxxxxx):sp1}
This is invalid. Allows 11 digit 250 and 530. Allows all 10 digit area codes. Does not prefix 10 digits with "1". It was modified.

The whole SP2 DigitMap is not used and redundant. Unless you want to force a call out SP2 by dialing a **2 prefix.

(Mipd) is a User Defined Digit Map and is checking for an IP address dialed like xx*xx*xx*xx and changes it to xx.xx.xx.xx
[^*#]@@. is checking for a character string Not beginning with * or # usually a URI.
Both are usually not needed and should be deleted.

*** is used to access the Auto Attendant 2 for config commands.

There are two types of Star Codes. The codes in the Star Code profile are commands for the OBi to perform. The codes in the PP DigitMap are Star Codes sent to a provider. The Star Codes in the PP DigitMap get priority and will disable a matching code in the Star Code Profile. That is why a different number was assigned.

{([2-9]xx[2-9]xxxxxx):sp1} Any 10 number not required. removed. Can I keep it for 10 digit dialing, or your <1> prefix take care of it?
8(00|88|77|66|55)[2-9]xxxxxx 10 digit 800 numbers not required. Removed. Can I keep it in case anyone want to call a 10-digit toll free, or is it invalid? I want to call from SP1, because many of these service numbers have Caller ID to verify I am calling from my primary number.
{(18(00|88|77|66|55)[2-9]xxxxxx):sp1} 800 numbers to SP1? Yes, I want to have 800 numbers to SP1 because many of these service numbers have Caller ID to verify I am calling from my primary number.
250 and 530 11 digits not required. Removed. Please see explanation below
International calls to SP1? Yes, I want to use the SP1 carrier to handle international call, because of called id.

{(1(250|530)[2-9]xxxxxx|(250|530|234|567)[2-9]xxxxxx):sp1}
This is invalid. Allows 11 digit 250 and 530. Allows all 10 digit area codes. Does not prefix 10 digits with "1". It was modified.
Sorry, I meant to have this:
{((250|530)[2-9]xxxxxx|1(250|530|234|567)[2-9]xxxxxx):sp1}
which allows 10 digit dialing on 250 and 530, and at the same time 11-digit on 250, 530, and a couple other area codes. The reason is even with the same area code, some are local calling and some are long distance for my previous PSTN carrier. I assume the new VOIP carrier will have the same rule.

Thanks again!

Some providers allow 10 digits, others don't.
It can't hurt to add the prefix like this:
{(<1>[2-9]xx[2-9]xxxxxx):sp1}

The 800, 250, 530, 234 and 567 10 digit tests are redundant and can be removed.
The above generic 10 digit test will include these.
If you keep them, add the "1" prefix.

If you want 7 digits to default to an area code do this:
{(<1250>[2-9]xxxxxx):sp1}

Quote from: azrobert on January 09, 2015, 08:35:20 AM
Some providers allow 10 digits, others don't.
It can't hurt to add the prefix like this:
{(<1>[2-9]xx[2-9]xxxxxx):sp1}

The 800, 250, 530, 234 and 567 10 digit tests are redundant and can be removed.
The above generic 10 digit test will include these.
If you keep them, add the "1" prefix.

If you want 7 digits to default to an area code do this:
{(<1250>[2-9]xxxxxx):sp1}

If I have this: {(<1>8(00|88|77|66|55)[2-9]xxxxxx):sp1},{(1[2-9]xx[2-9]xxxxxx):sp2}
Will both 10 and 11-digit 800 numbers got routed to SP1?

No. It's only comparing for a 10 digit 800 number. If it matches a dialed number it will add the prefix.