Dial Plan for forcing international calls via SP2

<< < (2/4) > >>

soccerfan:
Thank you RonR and jimates. I got it to work by accessing the device web portal ;D
I also disabled auto-provisioning as RonR suggested. Now for two quick questions:

1. What should I add to the dial plan to also make the 044 prefix place calls via SP2
    (both 011 and 044 are prefixes for international numbers for voip.ms).
2. With auto-provisioning disabled, can I still make changes via the 'Expert Settings'
   of the obitalk portal (and will they stick)?
Thanks again for all your help.

RonR:
Quote from: jimates on March 23, 2011, 01:56:11 pm

As of today, you can do that with the Expert Settings from the Obitalk Portal. Prior to the Expert Settings you could only do it from the web interface. This makes remote configuration possible and a very nice feature.
Unless I'm mistaken, the OBi Expert Configuration facility is also an all or nothing proposition.  If you make any changes to the OBi locally (manually) without remembering to manually make the same changes in the OBi Expert Configuration facility, your local changes will be wiped out the next time you reboot.

I can see some value to the OBi Expert Configuration facility if you have an OBi in a remote location with no other way to access it since the OBi doesn't support remote login's.  But for local (manual) configuration, I still fail to see why one wouldn't simply maintain it locally and be done with it.

RonR:
soccerfan,

If you want 044 + number to also go out SP2 like 011 + number does:

Code:

ITSPA DigitMap:
(1xxxxxxxxxxS0|<1>[2-9]xxxxxxxxxS0|<1aaa>xxxxxxxS4|<**2>011xx.|<**2>044xx.|xx.)

ITSPB DigitMap:
(1xxxxxxxxxxS0|<1>[2-9]xxxxxxxxxS0|<1aaa>xxxxxxxS4|011xx.|044xx.|xx.)


soccerfan:
Thanks RonR, I'm a happy camper now. Applied your suggested configs locally.
I'll try to play with the Expert Settings some other time. Regards. 

oleg:
Hi RonR,
My understanding of DigitMap must be slightly different… I thought each ISTP DigitMap should be responsible only for own patterns… I believe such approach may be a bit easier to understand and maintain. See below... criticism very welcome!

I was solving similar task: GV on sp1 for US calls and voipstunt on sp2 for international calls.
I have the following setup:

ITSP A DigitMap
Code:

(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx)
This allows dialing US phone number in form 1-234-345-4567 or 234-345-4567. 10 digits number will be automatically prefixed with 1.

ITSP B DigitMap
Code:

(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<011:>xx.|xx.)
This allows dialing US phone number, 011 prefixed international number or international number starting from country code (with theoretical risk of calling similar US number instead if digits match one of first two patterns, practically it does not happen - all international numbers I dial are longer than 10 digits). This rule removes 011 since provider takes this way.

PHONE Port DigitMap includes following rules (I show only relevant part of the map)
Code:

…|(Msp1)|(Msp2)|…
This allows dialing a number matching any of two maps above

PHONE Port OutboundCallRoute includes (again, only relevant part)
Code:

…,{(Msp1):sp1},{(Msp2):sp2},…
This routes call matching any of two maps above to the corresponding service.

---oleg

Navigation

[0] Message Index

[#] Next page

[*] Previous page