Voice Gateway Account Setup

[Diana]

Spent the weekend setting my New OBi110 as follows:

Setup Google Voice on SP1 as my primary outgoing/incoming.  
Ported my T-Mobile@home Number to Google Voice.  This was done in 24-hours (exactly).  Since the number was already with T-Mobile, was NOT my mobile number, I was able to avoid having to transfer the number to a Pre-Paid Cell service.  They treated the number as if it was a Mobile Number!

Setup VOIP.ms on SP2 and will be using this line solely for e911:

Setup Voice Gateway1 for CallWithUs.  This is where I have some setup issues and need some assistance.  This Line will only be used to call a specify country, 876 and I need to be able to pickup the phone attached to the phone port and dial 1876XXXXXXX and these calls route through the gateway account 1 via CallWithUS.  How do I setup:

A) Phone Port DigitMap: (?)

|**1(Msp1)|**2(Msp2)|**3(Mvg3)|**4(Mvg4)|**6(Mvg6)|**7(Mvg7)|**8(Mli)|**9(Mpp)|


and

B) PHONE Port OutboundCallRoute:(?)

{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Mvg3)):vg3},{(<**4:>(Mvg4)):vg4},
{(<**6:>(Mvg6)):vg6},{(<**7:>(Mvg7)):vg7},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}


per RonR's setup approach to achieve my objective?  Being a non-techie, A step by step outline would be very helpful.

Also, although I have VOIP.ms setup on SP2 and it shows it as Registered on the device status page when I'm connected to the device, the OBiTalk Dashboard shows it as "Not Configured" for Service Provider 2 and for Service Provider 1, it shows "Connected"?  I did all setup via the OBi110 directly and nothing was done from the OBitalk Portal.  

[RonR]

Diana,

The bolded portions of the PHONE Port DigitMap and OutboundCallRoute are additions to the default values:


PHONE Port DigitMap:

|**1(Msp1)|**2(Msp2)|**3(Mvg3)|**4(Mvg4)|**6(Mvg6)|**7(Mvg7)|**8(Mli)|**9(Mpp)|


PHONE Port OutboundCallRoute:

{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Mvg3)):vg3},{(<**4:>(Mvg4)):vg4},
{(<**6:>(Mvg6)):vg6},{(<**7:>(Mvg7)):vg7},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}


These additions establish the following dialing associations:

**3  ->  Voice Gateway3 (vg3)
**4  ->  Voice Gateway4 (vg4)
**6  ->  Voice Gateway6 (vg6)
**7  ->  Voice Gateway7 (vg7)


Assuming CallWithUs is configured on Voice Gateway3, you'd dial **3 + number to use CallWithUs.

If you'd like dialing 1876XXXXXXX to automatically go out Voice Gateway3, change:

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

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

[Diana]

Diana,

The bolded portions of the PHONE Port DigitMap and OutboundCallRoute are additions to the default values:


PHONE Port DigitMap:

|**1(Msp1)|**2(Msp2)|**3(Mvg3)|**4(Mvg4)|**6(Mvg6)|**7(Mvg7)|**8(Mli)|**9(Mpp)|


PHONE Port OutboundCallRoute:

{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Mvg3)):vg3},{(<**4:>(Mvg4)):vg4},
{(<**6:>(Mvg6)):vg6},{(<**7:>(Mvg7)):vg7},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}


These additions establish the following dialing associations:

**3  ->  Voice Gateway3 (vg3)
**4  ->  Voice Gateway4 (vg4)
**6  ->  Voice Gateway6 (vg6)
**7  ->  Voice Gateway7 (vg7)


Assuming CallWithUs is configured on Voice Gateway3, you'd dial **3 + number to use CallWithUs.

If you'd like dialing 1876XXXXXXX to automatically go out Voice Gateway3, change:

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

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

Thank you RonR.  I went ahead a use Voice Gateway 3 for CallWithUs.  The sections I'm having problems with now are the sections shown in bold bold:

Voice Gateway3 will be used with Callwithus:

Name : Callwithus
AccessNumber : SPx(sip.Callwithus.com)  (Is this exactly how it should be specify?)
DigitMap : (Mste)                                   (What should go here?)
AuthUserID : your_callwithus_user_id
AuthPassword : callwithus_password



And finally, let's configure the User Defined DigitMap referenced in Voice Gateway3:

Label : ste
DigitMap : (1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1aaa>xxxxxxx|011xx.|(Mipd)|[^*]@@.'@'@@.)


Apparently we do not need a "User Defined DigitMap" in my case with a single Voice Gateway?  How do we reference the SP1 DigitMap above?  The Voice Gate setup is a bit confusing.  Thanks again for your help.

[RonR]

AccessNumber : SPx(sip.Callwithus.com)  (Is this exactly how it should be specify?)

Since your SIP provider (VOIP.ms) is on SP2, you would need to use : SP2(sip.Callwithus.com)

DigitMap : (Mste)                                   (What should go here?)

And finally, let's configure the User Defined DigitMap referenced in Voice Gateway3:

Label : ste
DigitMap : (1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1aaa>xxxxxxx|011xx.|(Mipd)|[^*]@@.'@'@@.)

Apparently we do not need a "User Defined DigitMap" in my case with a single Voice Gateway?  How do we reference the SP1 DigitMap above?

You could use:

VG3 DigitMap : (1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1aaa>xxxxxxx|011xx.|(Mipd)|[^*]@@.'@'@@.)

instead of having it in a User Defined DigitMap and referencing it indirectly as (Mste), but you'll probably want to use it again elsewhere in the future so I'd keep it as described.

The SP1 DigitMap gets referenced from the PHONE Port DigitMap by **1(Msp1) and (Mpli).  (Mpli) refers to (Msp1) because you have the PHONE Port PrimaryLine set to SP1 Service.

[Diana]

Thanks again RonR.  Everything is working great now.  The correct Digimap is:

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

We were missing the ":" after the "**3", which sent the call out the CallWithUs Voice Gateway 3, but it was pre-appending the number 3 to 1876xxxxxxx.

One last issue I am having with VOIP.ms setup on SP2, is I am getting incoming calls to the Phone, but I having problems making ongoing calls.  I get a "486 Busy Here" when I dial 911 or a message saying "no call route available" when I dial **2+10-digit number.  Do you know what could be causing this issue?  Also, what should the port number for SP2 be...5060 or 5061?  I will do a search in the meantime to see if I can figure out what is calling the outgoing problem.  Thx!!!

[RonR]

The correct Digimap is:

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

We were missing the ":" after the "**3", which sent the call out the CallWithUs Voice Gateway 3, but it was pre-appending the number 3 to 1876xxxxxxx.

You need the **3 prepended so that the call goes out VG3.  The **3 will be removed by the {(<**3:>(Mvg3)):vg3} OutboundCallRoute rule before it's actually sent to CallWithUS.  The SP1 DigitMap I suggested is correct and you should be able to simply dial 18761234567 and have it go out VG3 automatically and unchanged.

One last issue I am having with VOIP.ms setup on SP2, is I am getting incoming calls to the Phone, but I having problems making ongoing calls.  I get a "486 Busy Here" when I dial 911 or a message saying "no call route available" when I dial **2+10-digit number.  Do you know what could be causing this issue?  Also, what should the port number for SP2 be...5060 or 5061?  I will do a search in the meantime to see if I can figure out what is calling the outgoing problem.  Thx!!!

If you want 911 to be sent to SP2 instead of the LINE Port, you need to change {(<#:>|911):li} to {(<#:>):li},{911:sp2} in the PHONE Port OutboundCallRoute.

**2 + 10-digit number should go out SP2 with a leading 1 automatically added because of the bolded rule in the ITSPB DigitMap:

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

[Diana]

Diana,

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

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

UPDATE

RonR:

The place that was missing the ":" is shown above, where "<**3>" should be "<**3:>".  Without the ":", the outgoing calls would appear as 31876xxxxxxx, instead of 1876xxxxxxx.  Are you saying that the ":" is not required?

BTW, I have everything working per your suggestions/guidance. 

1) I have GV working for incoming and outgoing on SP1
2) I have VOIP.ms working for e911 on SP2.  I had to purchase a DID from VOIP.ms before they would allow me to setup e911, so I end paying $2.49 ($0.99 for DID + $1.50 for e911) per month for e911.  I'm curious:  Are their any SIP provider that allow e911 to be sent out using the GV Number associated with SP1?  VOIP.ms allows you to set the outgoing DID to the GV number, but it breaks e911, as the emergency center will not see your address.
3) On gateway 3, I have Callwithus setup for international calls to 1876.

Thanks again for all your help RonR!!

[RonR]

Diana,

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

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

UPDATE

RonR:

The place that was missing the ":" is shown above, where "<**3>" should be "<**3:>".  Without the ":", the outgoing calls would appear as 31876xxxxxxx, instead of 1876xxxxxxx.  Are you saying that the ":" is not required?

This doesn't compute.  If the colon was required and it was left out, the outgoing call would appear as **31876xxxxxxx and not 31876xxxxxxx.

The purpose of <**3> is to intentionally add **3 to the beginning on any 1876xxxxxxx number dialed so that it matches the {(<**3:>(Mvg3)):vg3} rule in the OutboundCallRoute, sending the call to vg3.  The <**3:> in the OutboundCallRoute rule will remove the **3 before it gets to vg3, leaving just 1876xxxxxxx.

Feel free to post all the DigitMaps and the OutboundCallRoute if you can't find the problem.

[Diana]

RonR:

This is what I have for:

Phone Port

DigitMap: ([1-9]x?*(Mpli)|[1-9]|[1-9][0-9]|911|411|**0|***|#|**1(Msp1)|**2(Msp2)|**3(Mvg3)|**8(Mli)|**9(Mpp)|(Mpli))

OutboundCallRoute:  {(<#:>):li},{911:sp2},{(<123:1aaa7111181>):sp1},{(<411:18003733411>):sp1},{([1-9]x?*(Mpli)):pp},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Mvg3)):vg3},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}

1aaa7111181 = GV Number setup on SP1 (dial 123 to access Voicemail)

911 goes out through SP2 (VOIP.ms)

ITSP Profile A:

General

DigitMap:  (<**3>1876xxxxxxx|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|*xx|*xx.|(Mipd)|[^*#]@@.)


Gateways and Trunk Groups

Voice Gateway3

Enable                    Yes         
Name                        Callwithus      
AccessNumber        SP2(sip.callwithus.com)      
DigitMap           (<**3:>1876xxxxxxx|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1954>xxxxxxx|011xx.|(Mipd)|[^*]@@.'@'@@.)
AuthUserID               XXXXXXXXX      
AuthPassword       ******   


If I use "<**3>" in the Voice gateway DigitMap, then it append a 3 to the number: 31876xxxxxx.

If I use <**3:>, the the call goes through as: 1876xxxxxxx.

I still do not understand what the access number means and what is accomplish with it!

So it appears I'm not using the DigitMap of ITSP Profile A.  So, the current setup does work, but since I trying to understand the proper way to setup the OBi110, maybe you can suggest the appropriate changes to have this done correctly.  I'm familiar with the Linksys SPA3102, where all changes are done with the Dialplan and Gateway accounts 1-4.

[RonR]

Diana,

Try replacing your values with these.


Physical Interfaces -> PHONE Port -> DigitMap:

([1-9]x?*(Mpli)|[1-9]|[1-9][0-9]|911|**0|***|#|**1(Msp1)|**2(Msp2)|**3(Mvg3)|**8(Mli)|**9(Mpp)|(Mpli))


Physical Interfaces -> PHONE Port -> OutboundCallRoute:

{([1-9]x?*(Mpli)):pp},{(<#:>):li},{911:sp2},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},
{(<**2:>(Msp2)):sp2},{(<**3:>(Mvg3)):vg3},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}


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

(<123:12341234567>|<411:18003733411>|<**3>1876xxxxxxx|(Mste))

Replace 12341234567 above with your Google Voice number.


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


Voice Services -> Gateways and Trunk Groups -> Voice Gateway3 -> DigitMap : (Mste)


User Settings -> User Defined Digit Maps -> User Defined Digit Map2:

Label : ste
DigitMap : (1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1aaa>xxxxxxx|011xx.|(Mipd)|[^*]@@.'@'@@.)

Replace aaa above with your local area code.


123  ->  SP1 : 12341234567 (Google Voice number)
411  ->  SP1 : 18003733411

  7 digits  ->  SP1 : 1 + Area Code + 7 digits
10 digits  ->  SP1 : 1 + 10 digits
11 digits  ->  SP1 : 11 digits

911  ->  SP2 : 911

1876 + 7 digits  ->  VG3 : 1876 + 7 digits

[Diana]

Great!!!  Followed your very detail procedure above and everything is working the way it should.  I'm going to spend some time trying to understand how these multiple DigitMap, Call Routes, etc fits together.  It is a lot more complicated that the Linksys SPA3102 device.  THanks RonR.

[Diana]

I need to make a small change to the DigitMap for Profile A, so that when a number is dialed from the Phone attached to the PHONE Port, 011-44-XXXXXXXXXX, it goes out through VG3 [which is setup for CallWithUs (CWU)], as 44-XXXXXXXXXX (CWU acceptable UK-dialed number format).  In other words, it would strip the 011 before sending the outbound call through Voice Gateway 3.  I could simply add <**3>44xxxxxxxxxx to the DigitMap below, but US calls to area codes 440-443 would be routed thru CWU and we are use to dialing 011 when calling the UK.

(<123:12341234567>|!(2341234567|12341234567)|<411:18003733411>|<**3>1876xxxxxxxS0|<**3>011xx.|(Mste))

So, what is the correct syntax to strip the 011 from the dialed number?

EDIT:  I saw in another thread about dialing Belgium Numbers, where this is used:  |<011:+>xx.|<+:>xx.|;  Is this correct for stripping 011?

Diana,

Try replacing your values with these.


Physical Interfaces -> PHONE Port -> DigitMap:

([1-9]x?*(Mpli)|[1-9]|[1-9][0-9]|911|**0|***|#|**1(Msp1)|**2(Msp2)|**3(Mvg3)|**8(Mli)|**9(Mpp)|(Mpli))


Physical Interfaces -> PHONE Port -> OutboundCallRoute:

{([1-9]x?*(Mpli)):pp},{(<#:>):li},{911:sp2},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},
{(<**2:>(Msp2)):sp2},{(<**3:>(Mvg3)):vg3},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}


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

(<123:12341234567>|<411:18003733411>|<**3>1876xxxxxxx|(Mste))

Replace 12341234567 above with your Google Voice number.


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


Voice Services -> Gateways and Trunk Groups -> Voice Gateway3 -> DigitMap : (Mste)


User Settings -> User Defined Digit Maps -> User Defined Digit Map2:

Label : ste
DigitMap : (1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1aaa>xxxxxxx|011xx.|(Mipd)|[^*]@@.'@'@@.)

Replace aaa above with your local area code.


123  ->  SP1 : 12341234567 (Google Voice number)
411  ->  SP1 : 18003733411

 7 digits  ->  SP1 : 1 + Area Code + 7 digits
10 digits  ->  SP1 : 1 + 10 digits
11 digits  ->  SP1 : 11 digits

911  ->  SP2 : 911

1876 + 7 digits  ->  VG3 : 1876 + 7 digits

[RonR]

See if this gets the job done:


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

(<123:12341234567>|<411:18003733411>|<**3>1876xxxxxxx|<**3>01144xxxxxxxxxx|(Mste))

Replace 12341234567 above with your Google Voice number.


Voice Services -> Gateways and Trunk Groups -> Voice Gateway3 -> DigitMap:

(<011:>44xxxxxxxxxx|(Mste))



There's a couple of places in the UK that use 9-digit numbers.  If you want to support calling those too:


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

(<123:12341234567>|<411:18003733411>|<**3>1876xxxxxxx|<**3>01144(xxxxxxxxx|xxxxxxxxxx)|(Mste))

Replace 12341234567 above with your Google Voice number.


Voice Services -> Gateways and Trunk Groups -> Voice Gateway3 -> DigitMap:

(<011:>44(xxxxxxxxx|xxxxxxxxxx)|(Mste))



If you were looking for a general way to strip 011 from all international calls (not just UK) going out VG3:



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

(<123:12341234567>|<411:18003733411>|<**3>1876xxxxxxx|<011:**3+>xx.|(Mste))

Replace 12341234567 above with your Google Voice number.


Voice Services -> Gateways and Trunk Groups -> Voice Gateway3 -> DigitMap:

(<+:>xx.|<011:+>xx.|(Mste))


User Settings -> User Defined Digit Maps -> User Defined Digit Map2:

Label : ste
DigitMap : (1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1aaa>xxxxxxx|(Mipd)|[^*]@@.'@'@@.)

[Diana]

RonR:

I just got around making the changes you suggested and is having issues making outgoing calls via single-stage dialing and through the Auto Attendant.  Could do a quick glance to see if all the changes you suggested is correct.  I try dialing from my OBiON App using Single-Stage dialing to 1876XXXXXXX and 011442076301000 ( Hyton hotel in London) and keep getting a single ring and then hang up.  If I call into the AA and enter 2, then PIN, followed by the outgoing number, I get "No Call Route Available".  Without the changes below, everything work as required (except the 011+44+XXXXXXXXXX!

I did check the username and password for CallWithUs and it is correct.  Their is no calls showing up on the CWU Logs for these calls.  I'm making these calls from my OBiON since I am away from home at the moment.  Will access the Web interface directly later to see the call logs and find out what is being dialed out.

I made the following changes shown below:

If you were looking for a general way to strip 011 from all international calls (not just UK) going out VG3:



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

(<123:12341234567>|<411:18003733411>|<**3>1876xxxxxxx|<011:**3+>xx.|(Mste))

Replace 12341234567 above with your Google Voice number.


Voice Services -> Gateways and Trunk Groups -> Voice Gateway3 -> DigitMap:

(<+:>xx.|<011:+>xx.|(Mste))


User Settings -> User Defined Digit Maps -> User Defined Digit Map2:

Label : ste
DigitMap : (1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1aaa>xxxxxxx|(Mipd)|[^*]@@.'@'@@.)

[RonR]

I need to make a small change to the DigitMap for Profile A, so that when a number is dialed from the Phone attached to the PHONE Port, ...

Diana,

You asked for changes for calls dialed from the OBi PHONE Port.

Calls from OBiON Apps do not go through the PHONE Port and are handled by rules in the OBiTALK Service InboundCallRoute.  You will need to make similar changes there.  I don't remember what you have there now, so if you need suggestions, I would need to see the current set of rules.

Calls through the Auto Attendant also do not go through the PHONE Port.  The Auto Attendant has it's own DigitMap and OutboundCallRoute that would need the same changes you made to the PHONE Port if you want it to behave similarly.

[Diana]

The data is pretty much what was suggested by you and shown in preceding posts.  Below is a overall summary of all the OBi110 settings as it stands today, including my Inbound Call Route for the OBiTALK Service.  I want to be able to make calls from both PHONE Port and OBiON APP (using Single-Stage Dialing Through the Obi Trunk).  Essentially, there should be no difference between the dialing sequence when using the PHONE or the OBiON APP (if possible).  Some of the data was what I pickup from other recommendation you made relating to Single-Stage Dialing:

General Settings:

SP1: GV (GV Number = 12341234567)

SP2: VOIP.ms (registered to a specific VOIP.ms Server); used primarily for e911 (could potentially use as a
Rollover Trunk in case of GV failure).

VG3: CallWithUS (CWU) – Voice Gateway 3 [ Not registered to CWU Server] used primarily for internationals calls ONLY to 1876 and UK (could potentially use as a Rollover Trunk in case of GV failure).

LINE Port is NOT used.

Primary Line: SP1
RegistrarServerPort:   -> 5064 (ITSP Profile A)
RegistrarServerPort:   -> 5080 (ITSP Profile B)
STUNServer:             -> stun.voxalot.com (ITSP Profile B) – Stun Enable only for Profile B
X_STUNServerPort:    -> 3478

OBiON End Point #1 (Android #1): 2903xxxxx
OBiON End Point Obi110 : 2007xxxxx (Default Voice Gateway for ALL OBiON Endpoints)
OBiON End Point #2 (Android #2): 2902xxxxx
OBiON End Point #3 (Android #3): 2906xxxxx

Speed Dial #1 : **92903xxxxx
Speed Dial #2 : PP(ob2007xxxxx)
Speed Dial #3 : **92902xxxxx
Speed Dial #4 : **92906xxxxx
--------------------------------------------------------------------------------------------
NOTE: The settings below will generally strip 011 from all international calls going out VG3 when calls are made from the PHONE port:

SP1 Service -> X_InboundCallRoute:  {asterisk:},{(xxx):},{'asterisk':},{('asterisk'):},{?:sp2(12341234568)},{ph}

Where 12341234568 is second GV number to re-direct "Anonymous" calls coming in on SP1 to.


Physical Interfaces -> PHONE Port -> DigitMap:

([1-9]x?*@@.|[1-9]|[1-9][0-9]|911|411|**0|***|#|**1(Msp1)|**2(Msp2)|**3(Mvg3)|**8(Mli)|**9(Mpp)|(Mpli))


Physical Interfaces -> PHONE Port -> OutboundCallRoute:

{([1-9]x?*@@.):pp},{(<#:>):li},{911:sp2},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Mvg3)):vg3},
{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}


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

(<123: 12341234567>|<411:18003733411>|<**3>1876xxxxxxxS0|<011:**3+>xx.|(Mste))

Replace 12341234567 above with your Google Voice number.

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


Voice Services -> Gateways and Trunk Groups -> Voice Gateway3 ->DigitMap : (<+:>xx.|<011:+>xx.|(Mste))


Voice Services -> OBiTALK Service -> InboundCallRoute:

{(Mcot)>(Msp1):sp1},{(Mcot)>(<*1:>(Msp1)):sp1},{(Mcot)>(<*2:>(Msp2)):sp2},
{(Mcot)>(<*3:>(Mvg3)):vg3},{(Mcot)>(<*8:>(Mli)):li},{(Mcot)>(<*9:>(Mpp)):pp},
{(Mcot)>(<**1:>(Msp1)):sp1},{(Mcot)>(<**2:>(Msp2)):sp2},
{(Mcot)>(<**3:>(Mvg3)):vg3},{(Mcot)>(<**8:>(Mli)):li},
{(Mcot)>(<**9:>(Mpp)):pp},{(Mcot):aa},{ph}


Voice Services -> Auto Attendant -> DigitMap:
([1-9]x?*@@.|[1-9]|[1-9][0-9]|<00:$1>|0|**1(Msp1)|**2(Msp2)|**8(Mli)|**9(Mpp)|(Mpli))

Voice Services -> Auto Attendant -> OutboundCallRoute:
{([1-9]x?*@@.):pp},{0:ph},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}


User Settings -> User Defined Digit Maps -> User Defined Digit Map1:

Label : ipd
DigitMap : (xx.<*:@>xx?x?<*:.>xx?x?<*:.>xx?x?<*:.>xx?x?|xx.<*:@>xx?x?<*:.>xx?x?<*:.>xx?x?<*:.>xx?x?<*::>xx?x?x?x?)


User Settings -> User Defined Digit Maps -> User Defined Digit Map2:

Label : ste
DigitMap : (1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|(Mipd)|[^*]@@.'@'@@.)

User Settings -> User Defined Digit Maps -> User Defined Digit Map3:

Label : cot
DigitMap :(2007xxxxx|2903xxxxx|2902xxxxx|2906xxxxx)

OBiON Number for Obi110 (2007xxxxx ) and 3 different Android devices (2903xxxxx; 2902xxxxx; 2906xxxxx)


123  ->  SP1 : 12341234567 (Google Voice number –Dial 123 to check GV Voice Mail)
411  ->  SP1 : 18003733411 (Free 411)
 7 digits  ->  7 digits Dialing not required or allowed!!!!
10 digits  ->  SP1 : 1 + 10 digits
11 digits  ->  SP1 : 11 digits
011 + xxxxxxxxx digits  ->   VG3 :   9 digits UK number – CWU Provider
011 + xxxxxxxxxx digits  ->  VG3 : 10 digits UK number - CWU
911  ->  SP2 : 911 (VOIP.ms Provider)
1876 + 7 digits  ->  VG3 : 1876 + 7 digits (International Dialing to a Specific Country -CWU)

[RonR]

Diana,

Single-stage dialing was an afterthought in the OBi and was implemented in a very limited and less than elegant manner.  The Single-Stage Dialing Through Any OBi Trunk that you're using attempts to overcome some of the design limitations but is still very constrained.  This is because the PHONE Port's two-step dialing mechanism (DigitMap + OutboundCallRoute) isn't used in single-stage dialing.  Consequently, the custom routing of 1876xxxxxxx and 011+ you want on the PHONE Port doesn't automatically get picked up with single-stage dialing and must be shoe-horned in separately using brute-force tactics.  I'm going to try to accomplish this with a few more changes, but since I have no easy way of testing all this, it may take a couple of iterations.


Voice Services -> OBiTALK Service -> InboundCallRoute:

{(Mcot)>1876xxxxxxx:vg3},{(Mcot)>(011xx.):vg3},{(Mcot)>(Msp1):sp1},{(Mcot)>(<*1:>(Msp1)):sp1},
{(Mcot)>(<*2:>(Msp2)):sp2},{(Mcot)>(<*3:>(Mvg3)):vg3},{(Mcot)>(<*8:>(Mli)):li},{(Mcot)>(<*9:>(Mpp)):pp},
{(Mcot)>(<**1:>(Msp1)):sp1},{(Mcot)>(<**2:>(Msp2)):sp2},{(Mcot)>(<**3:>(Mvg3)):vg3},
{(Mcot)>(<**8:>(Mli)):li},{(Mcot)>(<**9:>(Mpp)):pp},{(Mcot):aa},{ph}


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

(<123:12341234567>|<411:18003733411>|<**3>1876xxxxxxxS0|<**3>011xx.|(Mste))


Voice Services -> Gateways and Trunk Groups -> Voice Gateway3 ->DigitMap : (<011:>xx.|xx.|(Mste))


The |411| rule in the Physical Interfaces -> PHONE Port -> DigitMap should be removed.


If you need the Auto Attendant caught up with VG3 support and the custom routing, let's tackle that once everything else is working properly.

[Diana]

RonR:

Made the changes and test.  Calls to 011442078368080, went out to the UK and call answered by Hotel Front Desk.  The 011 was stripped from the number and showed up in CallWithUs call logs as 442078368080..Perfect!

Calls to 1876xxxxxxx results in the calls ending immediately.  If I dialed 0111876xxxxxxx, the calls went through as 1876xxxxxxx as desired.  I look at this syntax:

{(Mcot)>1876xxxxxxx:vg3} and notice that all the others appear as:( X ):vg3, i.e.,

{(Mcot)>(1876xxxxxxx):vg3} and edited the Inbound Call Route to reflect that and now all 1876xxxxxxx calls are being routed through VG3 as required.  So all is good!!!!

Also, went ahead and removed |411| rule in the Physical Interfaces -> PHONE Port -> DigitMap!

To to check:  Only the three OBiON Numbers (2903xxxxx; 2902xxxxx; 2906xxxxx) will be able to dial out?  I would now like some assistance with the Auto Attendant aspect, where I can do the same thing by calling into the AA and being able to dial out to 1876 and 011 after entering PIN!

Thanks again for you help here.

Diana,

Voice Services -> OBiTALK Service -> InboundCallRoute:

{(Mcot)>1876xxxxxxx:vg3},{(Mcot)>(011xx.):vg3},{(Mcot)>(Msp1):sp1},{(Mcot)>(<*1:>(Msp1)):sp1},
{(Mcot)>(<*2:>(Msp2)):sp2},{(Mcot)>(<*3:>(Mvg3)):vg3},{(Mcot)>(<*8:>(Mli)):li},{(Mcot)>(<*9:>(Mpp)):pp},
{(Mcot)>(<**1:>(Msp1)):sp1},{(Mcot)>(<**2:>(Msp2)):sp2},{(Mcot)>(<**3:>(Mvg3)):vg3},
{(Mcot)>(<**8:>(Mli)):li},{(Mcot)>(<**9:>(Mpp)):pp},{(Mcot):aa},{ph}


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

(<123:12341234567>|<411:18003733411>|<**3>1876xxxxxxxS0|<**3>011xx.|(Mste))


Voice Services -> Gateways and Trunk Groups -> Voice Gateway3 ->DigitMap : (<011:>xx.|xx.|(Mste))


The |411| rule in the Physical Interfaces -> PHONE Port -> DigitMap should be removed.


If you need the Auto Attendant caught up with VG3 support and the custom routing, let's tackle that once everything else is working properly.

[RonR]

{(Mcot)>(1876xxxxxxx):vg3} and edited the Inbound Call Route to reflect that and now all 1876xxxxxxx calls are being routed through VG3 as required.

Is 1876xxxxxxx the actual value?  I thought it was a complete number (i.e. 18761234567) in which case the parenthesis shouldn't be required according to the OBi Device Administration Guide.

[RonR]

Only the three OBiON Numbers (2903xxxxx; 2902xxxxx; 2906xxxxx) will be able to dial out?

Any OBi/OBiON App whose OBiTALK number is listed in the 'cot' User Defined DigitMap should be able to call out.

I would now like some assistance with the Auto Attendant aspect, where I can do the same thing by calling into the AA and being able to dial out to 1876 and 011 after enter PIN!

Give this a try and let me know if there's any problems:

Voice Services -> Auto Attendant -> DigitMap:

([1-9]x?*@@.|[1-9]|[1-9][0-9]|<00:$1>|0|**1(Msp1)|**2(Msp2)|**3(Mvg3)|**8(Mli)|**9(Mpp)|(Mpli))

Voice Services -> Auto Attendant -> OutboundCallRoute:

{([1-9]x?*@@.):pp},{0:ph},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Mvg3)):vg3},
{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}

Voice Services -> Auto Attendant -> UsePIN : (checked)

Voice Services -> Auto Attendant -> PIN1 : (must be all digits)