OBiTALK Community

We need an explanation of the dial plan rules. Can someone please post explanation with samples.
Thanks
...

This is a follow up. I was in touch with a tech support person. He was helpful in troubleshooting my setup. We did not figure out why the unit did not register to the Grandstream GXE 5024 PBX, however it registered immediately to an Asterisk PBX as an extension. We spoke on the phone  Obi to Obi. The quality of conversation was very good. He was calling from California (I think), I was in Montreal. He emailed me the following I think others might find useful, as I'm sure this is the only info out there related to the Obi dial plan until they issue more documentation.

"Now, explanation on the dialplan that we have.

"M" stands for DigitMap, if you look at the configuration, there are unique configuration For DigitMap on calls via SP1 (Msp1), DigitMap on calls via sp2 (Msp2), Digitmap on obi to obi calls / (Mpp) DigitMap for your PrimaryLine (Mpli) - this one will be applied to whatever setting Your PrimaryLine currently points to.

i.e:
for Msp1, click on left column "ITSP Profile A" -> General see DigitMap on right column for Msp2, click on left column "ITSP Profile B" -> General see DigitMap on right column

CallReturnDigitMaps
Mean how you set the dialplan for a call back to the number that you see from Incoming callerID.

Our "admin guide" will be available soon, and it will also cover dial plan.
- Obihai Support Team"

DigitMap as indicated earlier, is specific to the SP or outgoing trunk interface.
For example in SP1 (ITSP Profile A -> General), Also referred to as Msp1 - default setting is:

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

1xxxxxxxxxx = 1 followed by 10 digits. This is good for typical (US-style) domestic calling.
<1>[2-9]xxxxxxxxx = 1 is optional followed by 10 digits that start with any digit from 2 to 9.
011xx. = US-style international dialing. Dial 011 followed by any numbe.r
xx. = Is any number, any length.

Now you might ask if "xx." is the wildcard, then why not use it only?
Because the best user experience will occur if the OBi can match the number sooner and then send
to the service than having to wait for the timeout (10 seconds) to expire.

DigitMap names associated to the various OBi interfaces are as follows:
Msp1 = DigitMap for SP1
Msp2 = DigitMap for SP2
Mpli = DigitMap for Primary Line
Mpp  = DigitMap for PP (OBiTALK)

Any of the above can be "included" in any DigitMap.
For example, in your DigitMap for SP2, you can include Msp1 to include the SP1's settings for DigitMap to apply to SP2.

More examples:
xxxxxxxS4 = Dial the entered 7 digit string after 4 seconds.
<S4:1234> = Call 1234 if no digits entered for 4 seconds.
obxxxxxxxxx = "ob" followed by 9 digits is an OBiTALK call.

- Obihai Support Team

Is [x*]. valid to mean 'zero or more occurrences of the set' as it is in the PAP2?

x means 0-9
x. means zero or more occurrences of 0-9

yet x can't be inside the square bracket

instead of [x*].  please do [0-9*].

Quote from: OBi-Guru on February 14, 2011, 02:09:28 PMinstead of [x*].  please do [0-9*].

As long as that means zero or more occurrences of a digit or an asterisk, that'll do.   :)

Thanks!

Quote from: RonR on February 14, 2011, 02:26:42 PM

Quote from: OBi-Guru on February 14, 2011, 02:09:28 PMinstead of [x*].  please do [0-9*].

As long as that means zero or more occurrences of a digit or an asterisk, that'll do.   :)

Thanks!

OBi-Guru,

[0-9*]. is not working:


Phone Port Primary Line : SP1 Service

Phone Port DigitMap : (911|**0|***|(Mpli)|**1(Msp1)|**2(Msp2)|**8(Mli)|**9(Mpp))

Phone Port OutboundCallRoute : {911:li},{**0:aa},{***:aa2},{(Mpli):pli},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp}

ITSPA DigitMap : (x[0-9*].)

SP1 X_ServProvProfile : A


As soon as the second digit is dialed, the number is immediately sent to the service provider.  Adding S4 to the ITSPA DigitMap has no effect.

The problem is the same with just:

(x[0-9].)


The DigitMap I really want is one which I use in a PAP2:

(*xxx[0-9*].|<#:>xx[0-9*].|<:0>x[0-9*].)

RonR,

We have verified that [x*] and x[0-9*]. do not work as expected in current firmware.
We will be posting a fix for these soon.

Unfortunately I cannot think of a good work around, other than just repeating
the pattern for as many times as necessary, such as, ...

  (x|x[0-9*]|x[0-9*][0-9*]|x[0-9*][0-9*][0-9*]|x[0-9*][0-9*][0-9*][0-9*]|...)

You can also contact support@obihai.com if you are interested in trying out a test
load with the fix.

Thanks -
Obihai Support Team

Email sent.

Thank you!

Correct me if I am wrong,
(1xxxxxxxxxS0) - 11 digits US number,
Or
(<1xxx> [2-9]xxxxxxS0) – 7 digits US number
Will be dialed immediately after criteria are met?


For some reason this is not working for me.

Quote from: murzik on March 18, 2011, 07:27:43 PM
(1xxxxxxxxxS0) - 11 digits US number

You only have space for 9 digits and you need 10:

(1xxxxxxxxxxS0)

Quote from: murzik on March 18, 2011, 07:27:43 PM
(<1xxx> [2-9]xxxxxxS0) – 7 digits US number

You have a space that doesn't belong there (I haven't tested to see what problems, if any, that cause).  '<1xxx>' needs to be '<1aaa>' where aaa is your local area code (I can't tell if that's what you meant or you had actually put 'xxx' there).

If you're using only these two rules together in the same DigitMap, it should work:

(1xxxxxxxxxxS0|<1aaa>[2-9]xxxxxxS0)

If you have additional rules in the same DigitMap, the S0 in the second rule may be problematic.

S0 is broken in non-beta versions of firmware (I don't know what the earliest beta version is that fixes this problem).

Thanks RonR

Quote from: RonR on March 18, 2011, 08:10:15 PM
If you're using only these two rules together in the same DigitMap, it should work:

(1xxxxxxxxxxS0|<1aaa>[2-9]xxxxxxS0)

This is exactly what I have and I am running latest beta.  But for some reason S0 have no effect.

murzik,

I was told that S0 was fixed in build 2081.  I'll try your case in a little while and report what I experience.

murzik,

When I was about to start testing your DigitMap, it dawned on me that in this particular case, S0 won't have any effect because both rules are effectively S0 already.  When either rule goes into the Exactly Matched state the other will be in the Mismatch state, so the DMP returns the matched rule's value immediately.

RonR

If S0 is matched already, or S0 is working, then 11 or 7 digits US number should be dialed immediately after I press last digit.  It should be as fast as I would have pressed # after last digit. But it is not.

Quote from: murzik on March 19, 2011, 11:50:01 AMIt should be as fast as I would have pressed # after last digit. But it is not.

There's no difference here.  Is this your complete DigitMap (with or without any S0's)?:

(1xxxxxxxxxx|<1aaa>[2-9]xxxxxx)

Is your PrimaryLine pointing to this DigitMap (or you're explicity utilizing it using **?)?  Please elaborate on the total picture.

I've tried both  with S0 and without, makes no difference, but using # at the end always make number to be dialed much faster.
(1xxxxxxxxxx|<1aaa>[2-9]xxxxxx) is my complete digimap for GV, this is my secondary lane, but I have outbound rule set to be {(1xxxxxxxxxx|<1aaa>[2-9]xxxxxx):sp2}, so I do not have to use **.

The routes in your PHONE Port OutboundCallRoute do not come into play here (other than routing the call out the desired port).

I'm assuming the '(1xxxxxxxxxx|<1aaa>[2-9]xxxxxx)' DigitMap is in ITSPA, ITSPB, or LINE.  Unless your PrimaryLine points to the one that has this DigitMap, it will never be evaluated unless you use **1, **2, or **8 to access it.  My guess is that S0 has no effect because the DigitMap you're modifying is never being used.

Quote from: RonR on March 19, 2011, 04:48:35 PM
I'm assuming the '(1xxxxxxxxxx|<1aaa>[2-9]xxxxxx)' DigitMap is in ITSPA, ITSPB, or LINE.  Unless your PrimaryLine points to the one that has this DigitMap, it will never be evaluated unless you use **1, **2, or **8 to access it.  My guess is that S0 has no effect because the DigitMap you're modifying is never being used.

Digimap is always in use.
for example I have Digimap '(1xxxxxxxxxx|<1aaa>[2-9]xxxxxx)' for ITSPB and (011xx.|*xxx) for ITSPA, if I will remove '(1xxxxxxxxxx|<1aaa>[2-9]xxxxxx)' and just leave Digimap emty, then I am not able to make calls to US.

Is your PHONE Port DigitMap at the default value?

Where is your PrimaryLine set to?

What is the DigitMap on your PrimaryLine?

Which SPx uses with ISPB?

Are you simply dialing test numbers without any **? (such as 12345678901 and 2345678)?

Yes. Phone Port Digit Map at the default value.

Primary line is set to SP2.

DigitMap for the primary line is (011xx.|*xxx.|xxx.)

SP2 is in use with ITSPB. SP2 is my sip provider.

SP1 with ITSPA  set to Google voice.

DigitMap for ITSPA  (1xxxxxxxxxx|<1aaa>[2-9]xxxxxx)

I am simply dialing numbers without **. Because I have rule set on Phone port { (1xxxxxxxxxx|<1aaa>[2-9]xxxxxx):sp2}

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.

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

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

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.

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.

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

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?

As for the 911, see configuration A in my guide
http://www.obitalk.com/forum/index.php?topic=339.msg1766#msg1766

Simple question - what does (Mipd) stay for?

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

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

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?

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)|[^*]@@.)

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.

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.

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

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.

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.

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.

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?

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.

Hi all,

I'm trying to change DigitMap for ITSPB which is configured for SIP to make international calls.
I'd like to have following phone number transformation:
Dialed phone number: **201123334445566
Phone to send to SP2 : 23334445566

SP2 is configured with ITSPB
Primary line is set to to SP1 which is GV

I have default OutboundCallRoute on PHONE port "...,{(<**2:>(Msp2)):sp2},..." and changed ITSPB DigitMap to: (<011:>2333xxxxxxx)

When I try to place a call, I get an error that there is no route. Am I doing something wrong here?

andrewp,

Is this your whole ITSPB DigitMap value? : (<011:>2333xxxxxxx)

If so:

When the PHONE Port DigitMap is processed, your dialed number of **201123334445566 will be transformed to **223334445566 by the ITSPB DigitMap rule (<011:>2333xxxxxxx).  When **223334445566 is then processed by the PHONE Port OutboundCallRoute, the **2 will be removed but the remaining number (23334445566) will not match your ITSPB DigitMap rule (<011:>2333xxxxxxx) because the 011 has already been removed.  Consequently, the {(<**2:>(Msp2)):sp2} rule cannot be executed.

Thanks a lot RonR,

I was suspecting something like that, but was not sure if PHONE port DigitMap is applied automatically or only when referenced from the Call Route.

When I was placing a call, the Call Status page of OBi110 was showing phone number as **223334445566 i.e already processed by PHONE -> ITSPB DigitMap transfromation.

I guess that the correct digit map for ITSPB will be: (<011:>2333xxxxxxx|2333xxxxxxx)

It would be less confusing if DMP would apply phone number transformation only when DigitMap is referenced from the Call Route rule.

Thanks again for your quick help.

Quote from: andrewp on June 02, 2011, 01:30:38 PM
I guess that the correct digit map for ITSPB will be: (<011:>2333xxxxxxx|2333xxxxxxx)

That should work.

Want to implement a fix number dialing, when one pick up home phone, directly call to my mobile number thru Line phone.

Can i set as following, where 9999999 is my mobile number? so when someone pick up my home codeless phone, obi will dial out 999999 for me?
OutboundCallRoute (:99999999)

yiucsw,

You want to leave the OutboundCallRoute configured normally and set:

Physical Interfaces -> PHONE Port -> DigitMap : (<S0:12341234567>)

where 12341234567 is your mobile number.

Hi guys,
I've recently purchased a couple of Obi110's which I am setting up for use within Australia (replacing SPA3000's) but I'm having problems getting my head around the DigitMaps etc. At present, the Phone Port DigitMap and Phone Port OutboundCallRoute are still set to their default values.

As the bulk of all my calls are made via my VoIP provider (I only use one), I have their details set under ITSP Profile A and also have set:
Physical Interfaces -> PHONE Port -> PrimaryLine : SP1 Service

My current SPA3000 dial plan (which I would like to replicate) is as follows:
(000S0<:@gw0>|1100S0<:@gw0>|1800xxxxxxS0<:@gw0>|13[19]xxxS0|1300xxxxxxS0|1900xxxxxx!
|77[1578]S0|0011xx.|[45689]xxxxxxxS0|0[23478]xxxxxxxxS0|xx.)

This translates to:
   
000 (the Australian equivalent of 911), 1100 and 1800xxxxxx via PSTN
13[1-9]xxx, 1300xxxxxx, 77[1578], 0011xx. , [45689]xxxxxxx and 0[23478]xxxxxx via SP1
1900xxxxxx barred
xx. (anything else via SP1)

Can you advise what I need to achieve this. Thanks.

Physical Interfaces -> PHONE Port -> DigitMap:

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


Physical Interfaces -> PHONE Port -> OutboundCallRoute:

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


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

(<**8>1100|<**8>1800xxxxxx|!1900xxxxxx|13[1-9]xxx|1300xxxxxx|77[1578]|
0011xx.|[45689]xxxxxxx|0[23478]xxxxxx|xx.|(Mipd)|[^*]@@.)


Physical Interfaces -> LINE Port -> DigitMap:

(xxxxxxS4|1xxxxxxxxx|xx.)


Note: The rules in boldface can be omitted as they'll be caught by the xx. rules.


                 000  ->  PSTN
               1100  ->  PSTN
1800 + 6 digits  ->  PSTN

1900 + 6 digits  ->  Barred

Everything else  ->  SP1

Hi RonR,

Thanks for the response. All seems to be working OK, but obviously I can't test 000.

Prior to making these changes, I could press # on the phone and it would immediately swap to the PSTN line with the PSTN line dial tone so I could make calls manually. Now when I press #, there is a pause of about 10 secs, then the OBi110 seems to reset; the OBi phone and line lights start blinking, they go off and the power light turns red; then all the lights come back green. At the point the power light goes red, the PSTN dial tone is heard but when the lights come back green then the OBi generated dial tone returns.

Is another entry required to re-enable the # connecting immediately to the PSTN line?

Pressing only a # should not have changed.  It still should bridge you immediately to the LINE Port.

The OBi should not be rebooting.  Recheck your DigitMaps and OutboundCallRoute for a typo.

There is no error checking in the OBi, so incorrect entries can cause the OBi to simply reboot.

Hi RonR,

I checked all the changes I made (including the config settings for use in Australia) but couldn't see any error. So I deleted the device from ObiTalk and re-added it then made the changes again, checking after each change. The end result is it is now working correctly so there must have been a mistake that I didn't see.

Thanks for your help.

thanks for all the explanation:
Can i have a more direct approach:
I have four OBI110 in four different location:china(Beijing), China(Guangzhou),Hong Kong and Macau
what i want is call forward all mobile call from China(Beijing) and China(Guanghzhou) to both Hong Kong and Macau Mobile number.

So the 1st thing i do is call forward my China(beijing) mobile to a fixiine in China(beijing) and China(guangzhou) mobile to a fixline (Guangzhou) which each connect to an individual OBI110.

The 1st concept to to put what i type in the InboundCallRoute? which 6356XXXX is my macau mobile phone number and 9643XXXX is my hong kong phone number.

{S0:3*6356XXXX};{S0:2*9643XXXX}

Is it possible, or i am in a wrong direction

Quote from: yiucsw on June 27, 2011, 02:20:55 AM
{S0:3*6356XXXX};{S0:2*9643XXXX}

This is not valid anywhere in an OBi, so that's a bad start.

I've read your post a number of times, but I'm still not sure I fully understand what you're trying to accomplish.

I understand you have four OBi110 devices, each in a different locaion: Beijing, Guangzhou, Hong Kong, and Macau.

I understand there are at least two PSTN lines involved, each connected to an OBi (Beijing and Guangzhou).

I understand there are two mobile phone numbers involved (Hong Kong: 9643XXXX and Macau: 6356XXXX).

Is this the physical layout?:

OBi #1 -> Beijing PSTN

OBi #2 -> Guangzhou PSTN

OBi #3 -> Hong Kong PSTN

OBi #4 -> Macau PSTN

Are you wanting all incoming PSTN calls to OBi #1 to cause OBi #3 to call 9643XXXX using PSTN as well as OBi #4 to call 6356XXXX using PSTN, bridging the first one that answers?

Are you wanting all incoming PSTN calls to OBi #2 to cause OBi #3 to call 9643XXXX using PSTN as well as OBi #4 to call 6356XXXX using PSTN, bridging the first one that answers?

If so, this may be problematic, as OBi #3 and OBi #4 will report the call completed as soon as it's initiated because they're not able to tell if/when the called party actually answers.

This is not valid anywhere in an OBi, so that's a bad start.

The purpose of this arrangement is to avoid roaming charge for my mobile phone and reduce customer's concern to call my mobile phone when i am in hk or macau. So i need to bridge all my mobile phone together.

Yes, four OBi110 devices, in a different location: Beijing, Guangzhou, Hong Kong, and Macau.
Each location has one PSTN line, BJ, GZ, HK, Macau

I understand there are four mobile phone numbers involved
(BJ:139XXXXXXXX, GZ:133XXXXXXXX Hong Kong: 9643XXXX and Macau: 6356XXXX).


OBi #1 -> Beijing PSTN
OBi #2 -> Hong Kong PSTN
OBi #3 -> Macau PSTN
OBi #6 -> Guangzhou PSTN

want obi#1(PSTN)->obi#2(9643XXXX) + obi#3(6356XXXX) and bridge the first one that first answers.
want obi#6(PSTN)->obi#2(9643XXXX) + obi#3(6356XXXX) and bridge the first one that first answers.

If multiple call forward is not possible or problematic, is there any easy way that i can switch call forward when i travel to different location?
i.e. when i am in macau, i can answer switch all call forward in Macau, and when i hk, i can switch all call forward to HK. when i am in GZ, i can turn all call forward off?

yiucsw,

You might consider using a forking "simultaneous call approach". Have a look here for an idea.
http://www.obitalk.com/forum/index.php?topic=1072.msg6737#msg6737

You can avoid messing around with call forwarding settings using this method, as several phones can ring at the same time.

I am trying to wrap my head around this... unsuccesfully ;-)

I have two Service Providers. My local SIP provider on #1, and Google Voice on #2.

How do I create a Dial plan (Digit Map), that all 10 and 11 digit numbers, go through Google Voice (US Numbers), and everything else through my local SIP Provider (3, 4 and 8 digit numbers).

Thanks for any help.

Quote from: Dogzipp on September 08, 2011, 03:26:04 PM
I have two Service Providers. My local SIP provider on #1, and Google Voice on #2.

How do I create a Dial plan (Digit Map), that all 10 and 11 digit numbers, go through Google Voice (US Numbers), and everything else through my local SIP Provider (3, 4 and 8 digit numbers).

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


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

(xxx|xxxx|xxxxxxxx|<**2>1xxxxxxxxxx|<**21>[2-9]xxxxxxxxx|(Mipd)|[^*]@@.'@'@@.)


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

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


3/4/8 digits  ->  SP1 Service
10/11 digits  ->  SP2 Service

It seemed to work for a while. I changed the DigitMap, rebooted the unit. But after a while, the default settings are being used again...

Am I getting updated with other settings from the mothership? Do I have to turn off Obitalk provisioning?

Quote from: Dogzipp on September 08, 2011, 07:22:25 PM
It seemed to work for a while. I changed the DigitMap, rebooted the unit. But after a while, the default settings are being used again...

Am I getting updated with other settings from the mothership? Do I have to turn off Obitalk provisioning?

To configure the OBi directly, you must disable Auto Provisioning or the OBiTALK Web Portal will overwrite your settings with its.

We suggest you use the OBi Expert configuration (http://www.obitalk.com/forum/index.php?topic=458.0) pages to make modifications such as this -- No need to disable provisioning.

This is especially useful when you have OBi devices dispersed throughout a country or the world. From your single OBiTALK web portal log-in you may control your OBi devices with a great deal of granularity and control.

What does [^*]@@.'@'@@. stand for? For URI calling?

Quote from: Dogzipp on September 08, 2011, 10:38:54 PM
What does [^*]@@.'@'@@. stand for? For URI calling?

Yes.  You can store SIP URI's in Speed Dials.

The [^*] part is a workaround for a bug in the OBi firmware.

Hello,

Unfortunately dial plan configuration isn't really sinking in to my brain, I would really appreciate some help with my (hopefully) basic requirements.  I'm a UK user.

I would like.
- any number beginning 00, 01, 02, 03, 07 to be sent to SP1
- any number beginning **2 to go to SP2
- any number beginning 118 to be rejected
- any number beginning 09 to be rejected
- everything else to be sent to PSTN

Really appreciate any help you can give me here, many thanks,

Ben.



I'd like to avoid having to dial **x for

Service Providers -> ITSP Profile A -> General -> DigitMap : (xx.|(Mipd)|[^*]@@.'@'@@.)

Service Providers -> ITSP Profile B -> General -> DigitMap : (xx.|(Mipd)|[^*]@@.'@'@@.)

Physical Interfaces -> LINE Port -> DigitMap : (xx.)

Physical Interfaces -> PHONE Port -> DigitMap:

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

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

Label : rtr
DigitMap : (!(09|118)xx.|<**1>0[01237]xx.|<**8>xx.)


             09/118+  ->  Barred
00/01/02/03/07+  ->  SP1
   Everything else  ->  PSTN Line


Note 1: Any number can be directed to SP1, SP2, or the PSTN LINE using **1, **2, and **8 respectively.  If you wish to restrict SP1 calls to 00/01/02/03/07+ in all cases, replaxe xx. with 0[01237]xx. in the ITSP Profile A DigitMap.  If you wish to bar 00/01/02/03/07+ calls from the PSTN Line in all cases, add !0[01237]xx.| to the beginning of the LINE Port DigitMap.

Note 2: 09/118+ calls are not barred if **1, **2, or **8 is used to direct calls to SP1, SP2, or the PSTN LINE respectively.  If you wish to bar those calls also, add !(09|118)xx.| to the beginning of the ITSP Profile A, ITSP Profile B, and/or LINE Port DigitMap(s) as desired.

Thanks Ron, I'll implement these tomorrow!

So I'm doing OK so far with an Obi110 and I'm comfortable with the SIP and provider config but still getting my head around the digitmaps. I think I've read this thread enough and right above about UK dialing to use what Ron suggested but just looking to validate I haven't over looked something.  :)

My setup:

SP1 - GV
SP2 - Sipgate UK
Line - Sipgate USA for E911

I left everything as is/was from the web site site other than the customizations for Sipgate UK setup. I'm using SP1/GV as the default service and have defined 636 as the local area code for 7 digit dialing.

Using what Ron defined above for mrbenjaminjo I created a user defined digitmap with a label of gbr with this data:
(!(09)xx.|<**2>0[0123578]xx.)
This seems to work so I don't have to dial **2 to make UK calls via SP2. I've only tested 0800 and 0500 numbers right now but those both worked.

My phone port digitmap now reads:
([1-9]x?*(Mpli)|[1-9]|[1-9][0-9]|911|**0|***|#|**1(Msp1)|**2(Msp2)|**8(Mli)|**9(Mpp)|(Mpli)|(Mgbr))
with the Mgbr added at the end

The phone port OutboundCallRoute is unaltered but reads:
{([1-9]x?*(Mpli)):pp},{(<#:>|911):li},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}

Could someone please take a look at this and confirm this doesn't look like it will cause any side effects?

Would it be more efficient to replace the digitmap under ITSP Profile B General to accomplish this? Should I change the digitmap for ITSP B to (!(09)xx.|<**2>0[0123578]xx.|(Mipd)|[^*]@@.'@'@@.) and then not need the user digitmap with the gbr label?

Thanks in advance

SimonD,

If your PrimaryLine is SP1/ITSPA and you're trying to block numbers starting with 09 from SP2 and redirect numbers starting with 0[0123578] to SP2, I would suggest:

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

(<**2>0[0123578]xx.|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1636>[2-9]xxxxxx|011xx.|(Mipd)|[^*#]@@.'@'@@.)

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

(!09xx.|0[0123578]xx.|(Mipd)|[^*#]@@.'@'@@.)

Leave the PHONE Port DigitMap and OutboundCallRoute unaltered.  No User Defined DigitMap is needed.

Ron,

Thanks for the feedback. As I read more and see the examples you're providing this is beginning to start to make some sense.  :)

I also went back and read the beginning of this thread which noted the faster the Obi can get an exact match the better it is hence why xx. isn't used alone.

So I looked in more detail at the UK calling plan (thanks Wikipedia http://en.wikipedia.org/wiki/Telephone_numbers_in_the_United_Kingdom ) and figured with a little more work I could make the matching for the UK numbers I want to call much more specific to mimic the US defaults that are defined.

While this doesn't account for a couple of the anomalies (10 digit beginning 01 or 8 digit beginning 08) it should work for everything else (11 and 10 digit numbers) and I based it on what you suggested for the ITSP A and ITSP B previously but also added 00xx. for UK based international calls and kept the block for numbers beginning 09.

ITSP A (Default Call out via Google Voice)
(<**2>0[123578]xxxxxxxxx|<**2>0[58]xxxxxxxx|<**2>00xx.|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1636>[2-9]xxxxxx|011xx.|(Mipd)|[^*#]@@.'@'@@.)

ITSP B (Sipgate UK)
(!09xx.|0[123578]xxxxxxxxx|0[58]xxxxxxxx|00xx.|(Mipd)|[^*#]@@.'@'@@.)

I'm gonna try this out tomorrow but just thought I'd post in case there's something I've missed and if nothing is wrong then in case it's useful for others wanting a UK digitmap with faster matching.

Thanks

Simon

SimonD,

Looks like you're on a good path to me.  Let us know how it turns out.

Ron

Ron/All

Seems to be working as expected - both US and UK dial patterns are recognized and it is definitely faster when using UK pattern numbers than the earlier option I originally started with above.

Following the pattern for allowing 7 digit dialing in the US I guess you can also do the same for UK dialing as well. In the updated example below I have UK area code 01444 defined such that you can 6 digit dial what are local numbers for the 01444 area code. Probably only useful if you're in UK and using it there all the time for UK calling.

ITSP A (Default Call out via Google Voice) General Digitmap
(<**2>0[123578]xxxxxxxxx|<**2><01444>[234568]xxxxx|<**2>0[58]xxxxxxxx|<**2>00xx.|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1636>[2-  9]xxxxxx|011xx.|(Mipd)|[^*#]@@.'@'@@.)

ITSP B (Sipgate UK) General Digitmap
(!09xx.|0[123578]xxxxxxxxx|<01444>[234568]xxxxx|0[58]xxxxxxxx|00xx.|(Mipd)|[^*#]@@.'@'@@.)

Thanks for all the info that's posted here - it's very useful as I explore the options the Obi gives. Hopefully my land line will complete it's first hope to T-Mobile on Monday before quickly moving it again to GV :)

I'm new to this so please bear with me.  I'm trying to set up my new OBi110 to have all my calls to go through SP1 (google voice, primary line) and only 911 calls to go through the line port.  Can someone give me some hints on what I need to change?  Thanks.

Quote from: sequoia2006 on January 09, 2012, 11:58:42 AM
I'm new to this so please bear with me.  I'm trying to set up my new OBi110 to have all my calls to go through SP1 (google voice, primary line) and only 911 calls to go through the line port.  Can someone give me some hints on what I need to change?  Thanks.

911 calls always use the LINE Port by default.

To set up Google Voice on SP1 and use it as your primary line, you can use the OBiTALK Web Portal or set up the OBi manually (which will give you more control and more accurate status):


System Management -> Auto Provisioning -> ITSP Provisioning -> Method : Disabled
System Management -> Auto Provisioning -> OBiTALK Provisioning -> Method : Disabled

Google Voice on SP1:

Service Providers -> ITSP Profile A -> General -> Name : Google Voice
Service Providers -> ITSP Profile A -> General -> SignalingProtocol : Google Voice
Voice Services -> SP1 Service -> AuthUserName : (Google Voice username)
Voice Services -> SP1 Service -> AuthPassword : (Google Voice password)
Voice Services -> SP1 Service -> X_SkipCallScreening : (checked)
Physical Interfaces -> PHONE Port -> PrimaryLine : SP1 Service

Quote from: RonR on January 09, 2012, 12:43:02 PM

Quote from: sequoia2006 on January 09, 2012, 11:58:42 AM
I'm new to this so please bear with me.  I'm trying to set up my new OBi110 to have all my calls to go through SP1 (google voice, primary line) and only 911 calls to go through the line port.  Can someone give me some hints on what I need to change?  Thanks.

911 calls always use the LINE Port by default.

To set up Google Voice on SP1 and use it as your primary line, you can use the OBiTALK Web Portal or set up the OBi manually (which will give you more control and more accurate status):


System Management -> Auto Provisioning -> ITSP Provisioning -> Method : Disabled
System Management -> Auto Provisioning -> OBiTALK Provisioning -> Method : Disabled

Google Voice on SP1:

Service Providers -> ITSP Profile A -> General -> Name : Google Voice
Service Providers -> ITSP Profile A -> General -> SignalingProtocol : Google Voice
Voice Services -> SP1 Service -> AuthUserName : (Google Voice username)
Voice Services -> SP1 Service -> AuthPassword : (Google Voice password)
Voice Services -> SP1 Service -> X_SkipCallScreening : (checked)
Physical Interfaces -> PHONE Port -> PrimaryLine : SP1 Service

Thanks Ron,
I did the setup through the web portal and it seemed to work as exptected but I can't test the 911 call.  Do I need to change anything in the DigitMap for the Phone interface or ITSP?

This is my current Phone DigitMap:
([1-9]x?*(Mpli)|[1-9]|[1-9][0-9]|911|**0|***|#|**1(Msp1)|**2(Msp2)|**8(Mli)|**9(Mpp)|(Mpli))

You shouldn't need to change anything for 911 calls to be sent to the LINE Port.

I do recommend testing 911.  There's two approaches, the first being the best:

1.  Call your local police or fire non-emergency number and explain that you have a new telephone system and would like to make a test 911 call.  They will usually tell you to go ahead and do so, making it clear when you call 911 to inform the disapatcher there is no emergency.

or

2.  Temporarily change 911 in the PHONE Port DigitMap and OutboundCallRoute to something like 611 (Repair Service) and then dial 611.  If the call goes through as expected, you know it works.  Don't forget to change 611 back to 911 in both the PHONE Port DigitMap and OutboundCallRoute.

I will do that.  Thanks Ron.

Last ATA was a Zoom and it let users configure the dialplan so no **1, **2, etc, was required when using different accounts.  Set it up to recognize if the first digit was a 1 then use SIP and if not use PSTN.  Can the same be set up with Obihai (wife factor and having to dial **1 for Long Distance)?

Line = PSTN with no long distance
SP1 = Google Voice
SP2 = CallCentric for E911 when I eventually ditch the PSTN

Thanks in advance.

Physical Interfaces -> PHONE Port -> OutboundCallRoute:

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

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

Physical Interfaces -> LINE Port -> DigitMap : ([2-9]11|[2-9]xxxxxx|[2-9]xxxxxxxxx|1xxxxxxxxxx)

Voice Services -> ITSP Profile A -> General -> DigitMap:

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


          911  ->  SP2
    [2-8]11  ->  LINE Port
7/10 digits  ->  LINE Port
   11 digits  ->  SP1 Service
        011+  ->  SP1 Service

RonR,

Thanks.  Seems to be transparently working like a regular phone.  Didn't change 911 to sp2, yet.  Still working towards canceling the PSTN. :)

Quote from: roundaway on January 21, 2012, 06:40:52 PM
RonR,

Thanks.  Seems to be transparently working like a regular phone.  Didn't change 911 to sp2, yet.  Still working towards canceling the PSTN. :)

Make sure you get 911 working BEFORE you cancel your POTS service.

Dear RonR
I recently purchased a Obi110 for a friend (she is living outside USA). I configured my Google Voice phone number and everything was ok.!!
I need your help for configure it.
1st
Incoming call to Obi's PSTN port have to be transferred to my US cell_phone1, without pause or PIN access just blind transfer to my cellphone
2nd
Call from same US cell_phone1 to my Google Voice phone number have to be blind forward to PSTN line. PIN access have to be required for any others caller
I will appreciated your help.
Thanks
Albert

Physical Interfaces -> LINE Port -> InboundCallRoute : {SP1(12341234567)}

Voice Services -> SP1 Service -> X_InboundCallRoute : {12341234567:li},{aa}

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

Voice Services -> Auto Attendant -> PIN1 : (numeric PIN)

where 12341234567 is US cell_phone1.

Quote from: Albert on February 02, 2012, 07:59:30 PMIncoming call to Obi's PSTN port have to be transferred to my US cell_phone1, without pause or PIN access just blind transfer to my cellphone ...

Though RonR's solution will do exactly what you asked for, it seems like a very unusual request, because your friend would be unable to receive calls at home!  Is this an "extra" line that she doesn't presently use, e.g. it's bundled with her Internet and TV service, but she takes all calls on her cell phone?  Otherwise, please post details, as there may be a better way to accomplish your goals.

Dear.
I used config from RonR and everything Great.!!.
Only inbound call from PSTN to SP1 no blind forward.
I used:
Physical Interfaces> LINE> InboundCallRoute> SP1(US cell_phone1)
After 7 ring call inbound throw PSTN finaly bridge to US cell_phone1 but call hang-hook continued a unknown number ring and hang-hook again
What could be wrong?

Quote from: Albert on February 04, 2012, 09:33:23 AM
After 7 ring call inbound throw PSTN finaly bridge to US cell_phone1 but call hang-hook continued a unknown number ring and hang-hook again

I don't know what this means.  I'm not familiar with the term 'hang-hook'.


In my previous example, I did leave out the curly-braces that should be around the rule:

Physical Interfaces -> LINE Port -> InboundCallRoute : {SP1(12341234567)}

should work.  I use that here to forward incoming landline calls to my cell phone.

-----

Upon further review, either should work equally well:


Physical Interfaces -> LINE Port -> InboundCallRoute : SP1(12341234567)

or

Physical Interfaces -> LINE Port -> InboundCallRoute : {SP1(12341234567)}


Curly-braces are not required when there is only a single rule.

Dear
I can't forward Incomng PSTN call to Google Voice
I've configured OBI for Google Voice (SP1), and make outgoing calls, blind forward from GV to Line port with no problem. Everything is great.!!
SP1 Services> X_InboundCallRoute> {cell_phone:li},{aa}
When Inbound call is connected throw PSTN port, it can't forward to Google Voice (SP1). The phone (PSTN) continues to ring and not forward to GV
Line Port> InboundCallRoute> SP1(cell_phone)
Somebody have any idea why not forward?
Regards
Albert

What, if anything, shows in Call History after a failing call?

If you have one or more phones connected directly to the PSTN line (as opposed to being connected to the OBi's PHONE port), it's normal for them to ring while the forward is being set up, and until the cell phone is answered.

Dear Stewart
Yes, the call history after failing call show the caller number. I dont have any phone connected directly to PSTN line. When somebody call me throw my PSTN line port, it can't forward to Google Voice (SP1). The caller's phone continue ring and not forward to GV
Line Port> InboundCallRoute> SP1(my_cell_phone)
Regards
Albert

If you manually dial your cell phone number from the phone connected to the OBi (using GV), does the call work as expected?  If not, troubleshoot that first.

If the manual call works ok, try another forwarded call.  Allow at least 15 seconds (after the PSTN caller hears ringing) for your cell phone to ring.  Then, log into the OBi and go to Status -> Call History.  You should see several lines of information for the call in question.  Confirm that the Peer Number for the Outbound side is correct.  Then, post everything in the History for that call (mask the actual phone numbers).

What country / city is the OBi in?

Can anyone help a little. I am overwhelmed with the amount of options the Obi has, and I am not sure as to where exactly put things..

I want to use my LINE mainly for all calls, except:

Calls that start with 4 (8 digits) to go through SP1
Calls that start with 1 (11 digits) to go through SP2 (Google Voice).
Everything else through the PSTN (911, 1xxx and 8 digit calls that start with 2-3 and 5-8)

I was thinking about this:

Physical Interfaces -> Phone Port -> Primary Line : PSTN Line
Physical Interfaces -> Line Port -> Digitmap : (<**1>4xxxxxxxS0|<**2>1xxxxxxxxxxS0|xx.)

But I am not 100% sure.. I see some people do the digits maps directly on ITSP Profile A, but I guess that's when your main line is SP1?

I would appreciate any configuration help, on how to make things work.

I would suggest:

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

Physical Interfaces -> LINE Port -> DigitMap : (<**1>4xxxxxxx|<**2>1xxxxxxxxxx|911|1xxx|[2-35-8]xxxxxxx)

Each of these rules is an exact match, therefore no S0 is needed anywhere.

Quote from: RonR on February 07, 2012, 06:31:38 PM
Each of these rule is an exact match, therefore no S0 is needed anywhere

What does the S0 do exactly?

Quote from: Dogzipp on February 07, 2012, 06:56:35 PM
What does the S0 do exactly?

Sn overrides the default interdigit timer.  S0 would force an immediate exit of the Digit Map Processor if the asociated rule mates but there is sill an indefinite match rule possible.

Wouldn't <**2>1xxxxxxxxxx and 1xxx conflict then?

You're right.  Unless there's something unique between those two that you can use to qualify them, you'll have to add an Sn (1xxxS2) to allow possibly dialing a fifth digit after 1xxx.

Quote from: RonR on February 07, 2012, 08:11:16 PM
You're right.  Unless there's something unique between those two that you can use to qualify them, you'll have to add an Sn (1xxxS2) to allow possibly dialing a fifth digit after 1xxx.

So (<**1>4xxxxxxx|<**2>1xxxxxxxxxx|911|1xxxS2|[2-35-8]xxxxxxx) should be allright?

Looks good, but the real test is to plug it in and try the various patterns to make sure they do what you want.

The Call History will show you the outcome of each test.

I'm using the OBI on Callcentric (port 2, the default port) and it's working great.  Port 1 is Google voice and it's working great, too.

But I'm a cheapskate and the idea of paying Callcentric for 800- number calls just doesn't sit well, so I'd like to modify the digit map to peer to SIP Broker (**275) before sending out the toll-free digit strings.  When I was using a regular old SIP, I used the dial plan below, but I have to admit to having a hard time understanding the multi-layer digit maps the OBI's use.  Anyone know how to convert this to a digit map to accomplish that?

(*xx.|*xxx|*75xx|[3469]11|0|00|<:**275*>1800x.|<:**275*>1866x.|<:**275*>1877x.|<:**275*>1888x.|[2-9]xxxxxx|1xxx[2-9]xxxxxxS0|xxxxxxxxxxxx.|**275*x.)

This will send your toll free calls though SP2 (Callcentric) via Sip Broker instead.

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

(*123|**275*xx.|[2-9]11|<**275*>(18(00|88|77|66|55)xxxxxxx|<1>8(00|88|77|66|55)xxxxxxx)|
1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1aaa>[2-9]xxxxxx|011xx.|(Mipd)|[^*#]@@.'@'@@.)

where aaa is your local area code.

I have PSTN line in Canada and my VOIP provider located in Ukraine and mapped to SP2.  I'm trying to setup the rule: prefix 8044 going to SP2 and 8044 substracted from #. Here is my settings:
Phone Port ->OutboundCallRoute:
{([1-9]x?*(Mpli)):pp},{(<#:>|911):li},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<8044:>(Msp2)):sp2},{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}
ITSP Profile B -> DigitMap:
(<8044:>xxxxxxx|xxxxxxx)
LINE Port-> DigitMap:
(xxxxxxxS4|1xxxxxxxxxx|xx.)
Works Ok, but it's a long delay before phone start ringing. I was following Ron's suggestions and changed Line Digimap to
[2-9]11|416xxxxxxx|905xxxxxxx|647xxxxxxx|289xxxxxxx|1xxxxxxxxxx|3xxxxxx|011xxxxxxxxxxxx)
After this change all calls started with 8044 are not going to SP2 at all. Any help?

Leave the PHONE Port DigitMap and OutboundCallRoute, and the ITSP Profile B DigitMap at Default.

Assuming your PrimaryLine is PSTN Line, set:

Physical Interfaces -> LINE Port -> DigitMap:

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

Thanks Ron. Works Ok. Could you please explain me sequence of events, other words, what OBI analyzed first (Phone DigitMap, Line Digitmap, CallRoute.., etc....)???? Thanks in advance.

Quote from: Gennady on February 20, 2012, 04:27:54 PM
Could you please explain me sequence of events, other words, what OBI analyzed first (Phone DigitMap, Line Digitmap, CallRoute.., etc....)?

When a number is dialed from the PHONE Port, the OBi DigitMap Processor evaluates it digit-by-digit using the PHONE Port DigitMap:

Physical Interfaces -> PHONE Port -> DigitMap:

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

With your Primary Line set to PSTN Line, pli gets replaced by li, making the actual PHONE Port -> DigitMap:

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

Mli is a reference to the LINE Port Digit:

Physical Interfaces -> LINE Port -> DigitMap:

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

Each of these rules matches as follows:

[2-9]11S0 matches 211/311/.../811/911.  The S0 forces the interdigit timer to 0 if any of these are matched.
[2-9]xxxxxxx matches any 7-digit number starting with 2 through 9.
1xxxxxxxxxx matches any 11-digit number starting with 1.
011xx. matches any number starting with 011.
<8044:**2>xxxxxxx matches any 7-digit number starting with 8044 and replaces the 8044 with **2.

Once a match is found, the resulting number is evaluated using the PHONE Port OutboundCallRoute:

Physical Interfaces -> PHONE Port -> OutboundCallRoute:

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

With your Primary Line set to PSTN Line, pli gets replaced by li, making the actual PHONE Port -> OutboundCallRoute:

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

As before, Mli is a reference to the LINE Port Digit.  Msp2 is a reference to the SP2 Service DigitMap.

In all the cases except where 8044 was replaced by **2, the number will again match one of the rules in the LINE Port DigitMap, resulting in the call being placed through the LINE Port.

In the case where 8044 was replaced by **2, the number will match one of rules in the SP2 Service DigitMap, resulting in the call being placed through the SP2 Service after first removing **2.

Thanks Ron, now it's clear.

Ron, after implementing your changes suddenly I lost ability to switch lines on my PSTN line by phone flash button. HookFlashHandling is set to "Handle Hook Flash Localy" (default) and Flash time on the phone is 700ms. Any idea?

Quote from: Gennady on February 22, 2012, 04:57:21 PM
Ron, after implementing your changes suddenly I lost ability to switch lines on my PSTN line by phone flash button. HookFlashHandling is set to "Handle Hook Flash Localy" (default) and Flash time on the phone is 700ms. Any idea?

DigitMap and OutboundCallroute settings should not affect Hook Flash handling.

From the OBi Device Administration Guide (http://www.obihai.com/docs/OBiDeviceAdminGuide.pdf):

Handle Hook Flash Locally

This is the normal setting, where the device intercepts all the hook flash events detected on the PHONE port, and acts on them accordingly, such as:
- Hold current call and start second dial tone for 3-way calls
- Start a 3-way conference
- End call with 2nd conferencee in a 3-way conference
- Swap between two calls in a call-waiting situation

Send Hook Flash Signal to PSTN

Device does not act on hook flash events detected on the PHONE port. It either ignores hook flash events OR regenerates similar hook flash events on the PSTN line if the phone user is currently in a call using the PSTN line service when the hook flash event happens. This option may be useful in cases where the user has traditional call-waiting or 3-way calling services on his PSTN line service; hence he can control those PSTN supplementary services using hook flash signals. However, the OBi in this case would automatically disables its own call-waiting function on the PHONE port, and the user would have no means to tell OBi to make 3-way calls.

Note that an alternative way to let OBi generate a hook flash signal to the PSTN line is to use a double hook flash event by hook flashing twice within 700 ms. See the description of the parameter EnableDoubleHookFlash in this table. With this enabled, you can still let the device handle normal hook flash event locally and preserve the call-waiting and 3-way calling functionalities.

Thanks Ron, I reset OBI to factory default and manually type everything back, and now flash working.  I suspect that during my "experiments" I setup a wrong value somewhere.  Now my settings for Physical Interfaces -> LINE Port -> DigitMap:  ([2-9]11S0|[2-9]xxxxxxxxx|3xxxxxx|<8044:**2>xxxxxxx).
Could you please tell me of how I should direct all international calls started with 011 to SP1? 

Quote from: Gennady on February 24, 2012, 01:59:51 PM
Now my settings for
Physical Interfaces -> LINE Port -> DigitMap:  ([2-9]11S0|[2-9]xxxxxxxxx|3xxxxxx|<8044:**2>xxxxxxx).
Could you please tell me of how I should direct all international calls started with 011 to SP1? 

Physical Interfaces -> LINE Port -> DigitMap:

([2-9]11S0|[2-9]xxxxxxxxx|3xxxxxx|<8044:**2>xxxxxxx|<**1>011xx.)

what does this part of the dialplan do? is it for speedials?

{([1-9]x?*(Mpli)):pp}

like it takes 1 or 2 digits with a star after and sends it to primary line..but for what?

thanks!

Quote from: brav on February 27, 2012, 01:22:38 AM
{([1-9]x?*(Mpli)):pp}

One or two digits followed by an asterisk followed by a number that matches the PrimaryLine DigitMap rules is sent to the OBiTALK Service trunk.  This is for single-stage dialing from OBi's and OBiON Apps (limited to using the PrimaryLine).

RonR,

I am doing some clean up and simplification in one of my Obi's.
What can I do to clean these up some, and what is  Msp1. It is present in some default settings but removed in some custom settings.

ITSP Profile
Digit Map - (1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1814>[2-9]xxxxxx|011xx.)

SP1 - X_InboundCallRoute - {ph,pp(290xxxxxx|290xxxxxx|290xxxxxx)}

Obitalk Service
Digit Map
(<ob>xxxxxxxxx|obxxxxxxxxx)

InboundCallRoute – (3 Obion softphone numbers with this Obi set as the default gateway and direct dialing, same as from the phone port)
{(290xxxxxx|290xxxxxx|290xxxxxx)>(xx.):SP1},{(290xxxxxx|290xxxxxx|290xxxxxx)>(<**2:>xx.):SP2},{(290xxxxxx|290xxxxxx|290xxxxxx)>(<**8:>xx.):LI},{(290xxxxxx|290xxxxxx|290xxxxxx):aa},{ph}

Phone Port -  (I know I should move the 411 to the digit map and out of the call route. This was done long long ago when we first got Obi's, and since it worked I didn't worry about it.)
Digit Map
([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|411|**0|***|#|**1{t=di2}(Msp1)|**2{t=di2}(Msp2)|**8{t=od}(Mli)|**9{t=di2}(Mpp)|(Mpli))

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

Quote from: jimates on March 25, 2012, 08:14:44 PM
ITSP Profile
Digit Map - (1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1814>[2-9]xxxxxx|011xx.)

This is an optimzed DigitMap for most service providers with US/Canada calling (11/10/7 digits and 011+).

Since this DigitMap is typically needed in multiple places, a good idea is to place it in a User Defined DigitMap where it can be shared instead of replicated:

User Defined Digit MapX
Label: ste
DigitMap : (1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1814>[2-9]xxxxxx|011xx.)

Then it can be used in multiple places:

Services Providers -> ITSP Profile A -> General -> DigitMap : (<411:18002464411>|(Mste))

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

Adding 411 number substitution support to SP1 is shown in the example above.

Quote from: jimates on March 25, 2012, 08:14:44 PM
SP1 - X_InboundCallRoute - {ph,pp(290xxxxxx|290xxxxxx|290xxxxxx)}

This is not valid syntax and should be:

Voice Services -> SP1 Service -> X_InboundCallRoute : {ph,pp(ob290xxxxxx),pp(ob290xxxxxx),pp(ob290xxxxxx)}

Quote from: jimates on March 25, 2012, 08:14:44 PM
Obitalk Service
Digit Map
(<ob>xxxxxxxxx|obxxxxxxxxx)

This is correct.

Quote from: jimates on March 25, 2012, 08:14:44 PM
InboundCallRoute – (3 Obion softphone numbers with this Obi set as the default gateway and direct dialing, same as from the phone port)
{(290xxxxxx|290xxxxxx|290xxxxxx)>(xx.):SP1},{(290xxxxxx|290xxxxxx|290xxxxxx)>(<**2:>xx.):SP2},{(290xxxxxx|290xxxxxx|290xxxxxx)>(<**8:>xx.):LI},{(290xxxxxx|290xxxxxx|290xxxxxx):aa},{ph}

This should be:

Voice Services -> OBiTALK Service -> InboundCallRoute:

{(290xxxxxx|290xxxxxx|290xxxxxx)>(Msp1):sp1},{(290xxxxxx|290xxxxxx|290xxxxxx)>(<**2:>(Msp2)):sp2},
{(290xxxxxx|290xxxxxx|290xxxxxx)>(<**8:>(Mli)):li},{(290xxxxxx|290xxxxxx|290xxxxxx):aa},{ph}

For a more elegant approach, you might consider Single-Stage Dialing Through Any OBi Trunk (http://www.obitalk.com/forum/index.php?topic=1103.0).  The result is more consistent with PHONE Port dialing and much easier to maintain.  If you don't need to call out through other OBi's, the only change required is:

Voice Services -> OBiTALK Service -> InboundCallRoute:

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

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

Label : cot
DigitMap : (290123002|290123003|290123004)

Quote from: jimates on March 25, 2012, 08:14:44 PM
Phone Port -  (I know I should move the 411 to the digit map and out of the call route. This was done long long ago when we first got Obi's, and since it worked I didn't worry about it.)
Digit Map
([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|411|**0|***|#|**1{t=di2}(Msp1)|**2{t=di2}(Msp2)|**8{t=od}(Mli)|**9{t=di2}(Mpp)|(Mpli))

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

With 411 moved to the SP1 DigitMap, these would become:

Physical Interfaces -> PHONE Port -> DigitMap:

([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|**0|***|#|**1{t=di2}(Msp1)|**2{t=di2}(Msp2)|
**8{t=od}(Mli)|**9{t=di2}(Mpp)|(Mpli))

Physical Interfaces -> PHONE Port -> OutboundCallRoute : Default

Thanks so much. I made the changes for a much cleaner config.

even with the invalid syntax the call forking was working before.

but the "single stage dialing" isn't really single stage dialing, is it?

since I have a single Obi set as the default gateway for all 3 of my Obion numbers I can dial from the app just like from the phone port. True single stage dialing, nothing extra like speed dials to direct the calls through a certain Obi.

With the elaborate single stage dialing setup don't you have to direct the call to the Obi using extra digit inputs?

What I proposed (since you don't use more than one OBi):

Voice Services -> OBiTALK Service -> InboundCallRoute:

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

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

Label : cot
DigitMap : (290123002|290123003|290123004)

adds support for **1 that you didn't have (I reaslize it isn't necessary since SP1 is your PrimaryLine).

The main improvement is a more streamlined approach, with all the trusted callers in a single DigitMap once instead of being repeated four or five times in the InboundCallRoute.

No extra dialing is required.  The extra digits are only needed to address other OBi's (this is stipped out of the example above).

OK, if I didn't have them assigned to the gateway (or if I were going to use more than the one Obi, I would need the slight extra dialing just to direct the call to an Obi. Right?

I will make the changes to that also.

An OBiON App always needs to be assigned to a gateway OBi.  Default dialing (normal single-stage dialing with no extra digits) will go to the gateway OBi and use its service providers.

If you also want the capability to place calls though an alternate OBi's providers, you need to use the full blown 'Single-Stage Dialing Through Any OBi Trunk' configuration and dial the extra digits to address that alternate OBi.  In that case, the OBiON App call is routed to the alternate OBi to use the alternate OBi's providers.

Although DigitMap for the primary line is much more reliable and it's precedence is lasting for the secondary one.
The legitimate value of dial up connection is totally depends on it's basic configurations.

Hi newbie here, don't know if this is right topic but i need some help to setup the dial plan for obi110.

i just have a cordless phone connected to phone port, no line in cause have to POTS line.

i have GV as sp1 and as primary line, and voip as sp2.
currently every time i dial out from sp2 for international calling i have to use **20049<10 digits> while calling in US through GV is direct. Also pressing # give me no dial tone, because i don't have anything connected to line in port (and not planning to in near future). So i was wondering if i could use # instead on **20049 so that every time i have to call internationally then i can simply use #<ten digit> number? is it doable?

Thanks in advance.
Regards.

littleboy,

One option is to have international calling (00+) automatically redirected to SP2:

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

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

where aaa is your local area code.

Quote from: RonR on May 11, 2012, 05:43:36 PM
littleboy,
One option is to have international calling (00+) automatically redirected to SP2:
Service Providers -> ITSP Profile A -> General -> DigitMap:
(<1aaa>[2-9]xxxxxx|<1>[2-9]xxxxxxxxx|1xxxxxxxxxx|<**2>00xx.)
where aaa is your local area code.

Hi RonR, that was quick reply, thanks for the information, I will try it.

Also it still means i need to type in 00<country code><phone no> for international calls, i was think of reducing everything to single digit prefix's instead of 00<country code>, is it possible?

I was trying this: {(<#:>)(<0049>xxxxxxxxxx):sp2}

where 0049 is country code for germany.

Regards.

Quote from: littleboy on May 11, 2012, 06:23:30 PM
I was trying this: {(<#:>)(<0049>xxxxxxxxxx):sp2}

where 0049 is country code for germany.

Personally, I don't like replacing a 'normal/standard' feature of the OBi such as '#' meaning 'bridge to the LINE Port'.  But it's all a matter of what you prefer, so as long as it works for you, that's what counts.

Instead of the above, I think you would need the following changes:

DigitMap : ...|#xxxxxxxxxx|...

OutboundCallRoute : ...{(<#:0049>xxxxxxxxxx):sp2}...

Hi RonR, I am really grateful, will try this immediately.

btw yes, I know it is not good to replace a standard feature, but as i said i am never going to touch the line-in port and need to make international calls multiple times in a day, so really helps in this case.

Thanks once again, will get back here as to how it works.
Regards.

Hey Thank you very much RonR, it works like a charm.
Regards.

Ron, your explanation of the "sequence of events" you gave on Feb 20 is the best explanation of how it all works I have seen anywhere and I now see how you arrived at your take on leaving the Phone port digit map at it's default. However in the case of slightly more complex setups it isn't particularly intuitive. I won't expound on it here but I could not get it to work in the case where a trunk group was involved either.

Quote from: ProfTech on May 12, 2012, 09:56:57 AM
Ron, your explanation of the "sequence of events" you gave on Feb 20 is the best explanation of how it all works I have seen anywhere and I now see how you arrived at your take on leaving the Phone port digit map at it's default. However in the case of slightly more complex setups it isn't particularly intuitive. I won't expound on it here but I could not get it to work in the case where a trunk group was involved either.

I use some very complex DigitMap schemes here, as well as multiple Trunk Groups, and haven't run into any serious problems that I recall at the moment.  If you want to post some scenarios that fail, I'll see if I can spot the reason for their failure.

Thanks Ron,
I don't want to waste your time but thought I would post this just for fun. A Few notes;

Local area code is 217 but not all 217 calls are local / free. ATT here allows but does not require dialing 11 digits for a local call but my wife requires that 7 digits work. :-)
Callcentric on the other hand, requires 11 digits for all calls. I don't make international calls.
Local [7 digit] calls and Toll free calls should go to the PSTN if it is available and automatically to Callcentric if the PSTN is in use. All 1+ [except Toll Free] calls should be sent to Callcentric even if they are in AC 217 [tricky part].

This is what I have that works.

ITSP Profile A -> DigitMap -> ((MLdist)|*7[89]|411)
Line Port -> DigitMap ->      ((1217[2-9]xxxxxx)|(MTfree))

User defined Maps:
Ldist -> (1[2-9]xx[2-9]xxxxxx)
TFree -> (18(00|55|66|77|88)xxxxxxx)
ObiM  -> ([49]11|*7[89]|<1217>[2-9]xxxxxx|<**1>1217[2-9]xxxxxx)

Phone Port:
DigitMap -> ([1-9]S9|1[0-9]S9|#|(MObiM)|(MLdist)|**2(Msp2)|**9(Mpp)|***)
OutboundCallRoute -> {(<#:>|911):li},{(Mpli):pli},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**9:>(Mpp)):pp},{***:aa2}
PrimaryLine -> Trunk Group 1

Trunk Group 1:
TrunkList -> li,sp1
DigitMap  -> ((Mli)|(Msp1))

ProfTech,

You requirements present a bit of a challenge given the unusual and undocumented way that Trunk Groups process DigitMaps.  Here's a configuration that works (I tested it) with an unmodified PHONE Port DigitMap and OutboundCallRoute.  I think it's considerably simpler than yours (but I'm biased).


Physical Interfaces -> PHONE Port -> PrimaryLine : Trunk Group 1

Service Providers -> ITSP Profile A -> General -> DigitMap : (*7[89]|411|1xxxxxxxxxx|1<LCL2:217>[2-9]xxxxxx)

Physical Interfaces -> LINE Port -> DigitMap:
(<1LCL1>[2-9]xxxxxx|1<LCL1:LCL2>[2-9]xxxxxx|1<LCL2:217>[2-9]xxxxxx|18(00|55|66|77|88)xxxxxxx)

Trunk Group1
TrunkList : li,sp1
DigitMap : ((Mli)|<**1>(Msp1))


                 911  ->  LINE
            7 digits  ->  LINE + SP1 (1217 + 7 digits in both cases)
          Toll Free  ->  LINE + SP1
*7[89]/411/1+  ->  SP1

Looks cool. Are the LCL etc pre-built internal pieces?

Quote from: ProfTech on May 13, 2012, 04:55:45 PM
Are the LCL etc pre-built internal pieces?

No, they're simply arbitrary literal strings I used to help steer the processing.  I used 'LCL' to designate 'local'.

Ron,
I plugged it in and everything worked fine [didn't have any doubt  ;)] but I was still a little mystified about the LCL nomenclature. After I slept on it, it dawned on me what you were doing. I could tell there was some tricky stuff going on when a trunk group was involved but wasn't sure what it was. I can see from your code it is making multiple passes through the interpreter but I hadn't thought about "Pasting up" letters or replacing letters with numbers, either. Then I realized The Obitalk service pastes in "ob" by default.

Thanks

Quote from: ProfTech on May 14, 2012, 07:36:45 AM
I could tell there was some tricky stuff going on when a trunk group was involved but wasn't sure what it was.

Unfortunately, there's quite a bit in the OBi that's undocumented and not obvious at first glance.  Often times, you have to spend a great deal of time doing trial and error, relying on empirical data to figure out how things actually work.

My voip provider does strange things when caller id is blocked.

my concern is if call id block is active when calling 911.

my provider uses a northern 911 service which will not see my location if call id is blocked.

how do I disable it for 911 calls?

I have been trying to do a replacement string with no success.

Codes for unblock are *82 and *68(one time)

<911:*68S1911> which does not work
i have been using my cell number to test with and replacing the second 911 with my cell number.

How do I actually accomplish this?

I wonder if one of the Guru's can help me with complicated dial plan:

Obi202 (500 333 ***)

Line 1
GV
   •   outgoing calls beginning with "1" following 10 digits (xxxxxxxxxx)
   •   7 digit number will have automatically added 1(212) or (212) US area code
   •   
Line 2
Callcentric
   •   direct incoming calls and forwarded from GV, call out to callcentric 1777
   •   
Line 3 primary line
SIP Telphin (acct # 1, no incoming sip number)
   •   outgoing calls beginning with "8" following 10 digits (xxxxxxxxxx) "8" retained
   •   "011" dialed, it replaced with "810" (its equivalent of "+") and then any nuber of digits international number
   •   6 digit number will have automatically added 84862 before (xxxxxx)
   •   
Line 4
Direct connection to Obi110 (200 222 ***)
   •   Incoming and outgoing calls direct connection to POTS line of Obi110 (200 222 ***) (outgoing calls can begin for example with "9" dial tone).
   •   Incoming calls special ring.

Obi100 (300 314 ***)

Line 1
GV primary line
   •   outgoing US calls (with or without  "1")
   •   7 digit number will have automatically added 1(212) or (212) US area code
Line 2
Callcentric
   •   direct incoming calls and forwarded from GV
Additional:
when "011" dialed, call being routed via Obi202  (500 333 ***) Line 3 - SIP Telphin with "011" replaced with "810" following any number of digits international number

Obi110 (200 222 ***)

Line 1 primary line
SIP Telphin (acct # 2, no incoming sip number)
   •   outgoing calls beginning with "8" following 10 digits (xxxxxxxxxx)  "8" retained, no modification
   •   calls beginning with "810" following any number of digits dialed without modification
   •   6 digit number will have automatically added 84862 before (xxxxxx)
   •   outgoing calls beginning with "1" following 10 digits (xxxxxxxxxx) have "810" added before "1" (8101xxxxxxxxxx) - US number

Line 2
Callcentric
   •   direct incoming calls and forwarded from GV, call out to callcentric 1777
POTS line
direct connection to/from Obi202 (500 333 ***) Line 4 to/from POTS line

Any assistance is greatly appreciated!

Since RonR was evicted from forums not much hel with complex issues

Hi,

You may also check this video on what dial plan is. It is based on Ozeki Phone System XE and it fairly explains dial plan and VoIP:
http://www.ozekiphone.com/product-information-340.html

BR

Quote from: JSmith on October 12, 2012, 06:19:12 AM
Hi,

You may also check this video on what dial plan is. It is based on Ozeki Phone System XE and it fairly explains dial plan and VoIP:
http://www.ozekiphone.com/product-information-340.html

BR

Well "what is a dial plan" is pretty easy. It's when one gets to the nuts and bolts level is things get more complicated.

I need help with a simple question: using Outside Dial tone.
Present configuration:
Line - for 3 and 7D special service calls, with direct # access.
SP1 - for GV
SP2 - (default) for all 10D, 11D and 011 calls.

I would like to dial an access code other than **1, such as '48' (GV), get
Outside Dial tone, then continue. Where would I put {t=od}?

You would put it in the Phone Port DigitMap such as:

**1{t=od}(Msp1)

I would be careful about replacing **1 with 48. It may conflict with other numbers. If you do replace **1 with 48 in the Phone Port DigitMap, then remember in the Phone Port OutboundCallRoute to change **1 to 48 in this rule:

{(<**1:>(Msp1)):sp1}

Great. Did exactly as advertised!
I realize modifying default codes is rarely a good idea, but I really wanted to add my '48'.

Finally made this work:
|<48{t=od}S9:**1>|**1{t=od}(Msp1)|
48 & **1 go to my default SP2 of course, so further routed from there to SP1 (GV) successfully.

This code will work until this area has a '48x' local area code!
Strangely it was necessary to add the S9, as default timeing was 2 seconds in the substitution format.

Hopefully, this is simple, one line in/out, no Google Voice, nothing fancy - I just want to verify this, as I'm new to dial plans:

I have set up my In-Laws with an Obi100 and CallCenctric VOIP. I'm trying to keep things as simple as possible for my In-Laws, they are elderly with declining sight and hearing, and don't deal with change well.

I've tested the system, setting up the Obi100 manually per the CallCentric directions here:

http://www.callcentric.com/support/device/obihai/obi100

The port of their number is in process, so I want to tweak the dial plan when I go over there to disconnect their phone wires from the POTS and connect them to their Obi100.

Their Area Code and Exchange are 847-478-xxxx (great for dyslexics, right?) ;)

To goof-proof their dialing, and accommodate any combination they might do, I'd like the following input/responses:

I'll use AAA for Area Code, and EEE for Exchange -


They dial 11 digits -  1AAAEEExxxx - should go through as dialed
They dial 10 digits -   AAAEEExxxx - Obi100 should add the 1 and dial 1AAAEEExxxx

They dial  7 digits -      EEExxxx - Obi100 should add the 1847 and dial 1847EEExxxx
They dial  4 digits -         xxxx - Obi100 should add the 1847478 and dial 1847478xxxx

This should allow them to just dial 4 digits to their local friends in the same exchange.


The default Callcentric Dial Map is (under Service Providers > ITSP Profile > General):

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

so I'm planning on (changes in BOLD):

(*xx.|**275*x.|[3469]11|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1847>[2-9]xxxxxx|<1847478>xxxx|011xx.|xx.|(Mipd)|[^*#]@@.)


I'm not sure what the default timeout is, four seconds? Should I use Sx codes with this, they are pretty slow and I don't want the 4 digits to trigger a dial sequence if they are still dialing a different exchange or area code.

TIA for any help - KenC

PS - secondarily, is there a guide to these codes somewhere? I've read through most of this thread, and I've reverse engineered most of it, but it sure would be nice to see a syntax spelled out somewhere - thanks again.

Admin manual has everything.
http://www.obihai.com/OBiAdminGuide.htm#_Toc333506161
Default timeout is 9 or 10 seconds, which is why it is a good idea to specifically code 10 or 11 digit dialing with an S0   (capital S Zero) at the end. Otherwise, S2 works for most other codes.
Consider using the RonR configuration utility, although the 4-digit dialing is a bit unusual.

Try changing:  |<1847>[2-9]xxxxxx|<1847478>xxxx|011xx.|xx.|(Mipd)|[^*#]@@.)

to
|<1847>[2-9]xxxxxxS0|<1847478>xxxxS0|011xx.S2|xx.|(Mipd)|[^*#]@@.)

There are two interdigit timers 10 seconds and 2 seconds. In your digit map most of the dialled numbers will automatically be using the 2 second interdigit timer.

Be very careful of using S0 to force the interdigit timer to 0 seconds. A rule such as <1847478>xxxxS0 will match any number as soon as the first four digits have been dialled and no other rules can be used.

We can all be a bit slow dialling from the phone. I know I sometimes stop to re-read a number halfway through dialling! I suggest a 4 second interdigit timer where duplication of the first few digits is possible. You know them, so you might want to make that longer. I suggest for your In-Laws:

Service Providers > ITSP Profile A > General > DigitMap:
(*xx.|**275*x.|[3469]11|1xxxxxxxxxxS0|<1>[2-9]xxxxxxxxxS0|<1847>[2-9]xxxxxxS4|<1847478>xxxxS4|011xx.|xx.)

I've dropped |(Mipd)|[^*#]@@. From the digit map as these are for ip address and sip uri address calling, which I guess will not be needed here.

The four digit dialling is unusual. Is there a chance any of the four digit numbers starts 311x, 411x, 611x or 911x ? If so, there are obvious problems!

Quote from: zapattack on April 27, 2013, 01:15:12 AM
Admin manual has everything.
http://www.obihai.com/OBiAdminGuide.htm#_Toc333506161

Thank you - that does seem to have what I need, will study up a bit later.

Quote
Try changing:  |<1847>[2-9]xxxxxx|<1847478>xxxx|011xx.|xx.|(Mipd)|[^*#]@@.)

to
|<1847>[2-9]xxxxxxS0|<1847478>xxxxS0|011xx.S2|xx.|(Mipd)|[^*#]@@.)

Quote from: ianobi on April 27, 2013, 02:43:55 AM
There are two interdigit timers 10 seconds and 2 seconds. In your digit map most of the dialled numbers will automatically be using the 2 second interdigit timer.

Be very careful of using S0 to force the interdigit timer to 0 seconds. A rule such as <1847478>xxxxS0 will match any number as soon as the first four digits have been dialled and no other rules can be used.

Yes, when I read the suggestion above to use S0, it did seem that would trigger a dial as soon as 4 digits were dialed and that would be a problem when dialing a full area code or exchange. I'll follow your examples below.

Quote
We can all be a bit slow dialling from the phone. I know I sometimes stop to re-read a number halfway through dialling! I suggest a 4 second interdigit timer where duplication of the first few digits is possible. You know them, so you might want to make that longer. I suggest for your In-Laws:

Service Providers > ITSP Profile A > General > DigitMap:
(*xx.|**275*x.|[3469]11|1xxxxxxxxxxS0|<1>[2-9]xxxxxxxxxS0|<1847>[2-9]xxxxxxS4|<1847478>xxxxS4|011xx.|xx.)

I've dropped |(Mipd)|[^*#]@@. From the digit map as these are for ip address and sip uri address calling, which I guess will not be needed here.

The four digit dialling is unusual. Is there a chance any of the four digit numbers starts 311x, 411x, 611x or 911x ? If so, there are obvious problems!

Thanks, I will drop the |(Mipd)|[^*#]@@ since it is not needed and just confuses things. I assume this isn't needed for direct no-charge CallCentric-to-CallCentric calls (177xxxxxx #'s)? One often-called relative has CallCentric, so the free calling would be a plus.  

Good point on the 4 digits and 311x, 411x, 611x or 911x conflict - I missed that possibility. So a call to someone with a 4 digit # like 6113 would match to 611 and go to cust service. I suppose a delay on the x11 would help, but probably best for that to be immediate. OTOH, their calling list is not large, I doubt there are any 311x, 411x, 611x or 911x numbers that they use, and I can check that. I suppose I could do "*" for four digit dialing?  I'm not sure how to code that so the * isn't dialed, I'll check that admin guide for that.

update: "*" is already used by CallCentric for features, so I will try with "#" instead - see follow-up post


Thanks so much for the fast feedback, this really helps.

KenC

The Callcentric to Callcentric calls should be processed by the 1xxxxxxxxxxS0 rule.

You may wish to consider setting up speed dials for often used numbers. An OBi has 99 speed dials using single and double digits from 1 to 99. Speed dial 1 is reserved for a softphone.

Quote from: ianobi on April 27, 2013, 10:08:30 AM
The Callcentric to Callcentric calls should be processed by the 1xxxxxxxxxxS0 rule.

You may wish to consider setting up speed dials for often used numbers. An OBi has 99 speed dials using single and double digits from 1 to 99. Speed dial 1 is reserved for a softphone.

Thanks for that validation. I have set up a few of the Obi100 speed dials, these are helpful. I'll see about setting up more for their other friends/family.

So I read up, and if I decide to go this route, it seems this could do the # plus 4 digit number to short-cut dial in the 847-478 exchange:

|<#:>1847478xxxx|

So dialing #xxxx will match, and the # will be removed and the 1847478 pre-pended, so 1847478xxxx will be dialed. Is that right? Since we are using the # as a 'trigger' no timeout should be required, it should be unique.

-KenC

I see how you are thinking. The rule you would need is:
|<#:1847478>xxxx|

Let's try to keep it simple. Using the digit map as I proposed, if you dial four digits followed by # then the rule |<1847478>xxxxS4| would be processed instantly.

Dialling # after any number of digits forces the interdigit timer to 0 and instantly executes the rule. So if your In-Laws are ok with that, then it's simple and can be applied to any number - four digits, seven digits etc. I suggest leaving the S4 in place in case they forget to dial the # at the end of the number.

Quote from: ianobi on April 27, 2013, 11:43:42 AM
I see how you are thinking. The rule you would need is:
|<#:1847478>xxxx|

Let's try to keep it simple. Using the digit map as I proposed, if you dial four digits followed by # then the rule |<1847478>xxxxS4| would be processed instantly.

Dialling # after any number of digits forces the interdigit timer to 0 and instantly executes the rule. So if your In-Laws are ok with that, then it's simple and can be applied to any number - four digits, seven digits etc. I suggest leaving the S4 in place in case they forget to dial the # at the end of the number.

I gotcha, thanks - I see now I had the 1847478 in the wrong place.

I think I'll go with the # plus four digit rule for in the exchange calls. |<#:1847478>xxxx|

It seems the other one would still have the 311, 411, 611, 911 conflict? That's what I figured hitting # first would do - just in case someone has a number like 478-6113 it can't match 611 as they dial since it would be dialed as #6113.

They live in a retirement community, so lots of acquaintances are in the same exchange. This will make it similar to calling another room in the same hotel - I think they'll like that.  We will also get them some phones with the BIG keypads on them, that helps with the sight and dexterity problems.

I think I have a handle on this, will try it out next week when I go over there to rewire them after their number is ported. Thanks so much for the help!

-KenC

The number was ported, so I went over today to re-wire and set these dial maps. Here's an update:

Recall I wanted to allow for "1" plus 10 digit dialing, 10 digit dialing, 7 digit dialing in the Area Code, and 4 digit dialing in the exchange.

Based on input here, and a few other things I saw from other sources ( like [2-9] for both Area Codes and Exchanges where applicable), I tried the following map:

(*xx.|**275*x.|[3469]11|1[2-9]xx[2-9]xxxxxxS0|<1>[2-9]xx[2-9]xxxxxxS0|<1847>[2-9]xxxxxxS4|<#:1847478>xxxx|011xx.|xx.)


"1" plus 10 digit dialing, and 7 digit dialing worked, but 10 digit dialing did not. I almost went blind looking for an extra space, a missing "|" or ":" something - couldn't find anything. So I tried the # plus 4 digit dialing, and I got kicked out as soon as I hit the #. So I decided to delete that for now (low priority anyway), in case that rule was interfering somehow (but I don't see how). So now:

(*xx.|**275*x.|[3469]11|1[2-9]xx[2-9]xxxxxxS0|<1>[2-9]xx[2-9]xxxxxxS0|<1847>[2-9]xxxxxxS4|011xx.|xx.)

Then 1 plus 10, 10, and 7 digit dialing worked. So I decided to just drop the 4 digit idea for now (though it would be nice).

I tried one more thing - I saw the example of a "warm" line in the guide, a number that would be dialed automatically after the specified wait with no digits entered. They've been known to knock the phone off the hook and not notice, so this would be set to call us if that happened. So I added a 27 second wait to try (planned to make it 90 seconds if it worked) - |<S9S9S9:our-11-digit-number-here>| , but it timed out back to dial tone (or fast busy? Off-Hook tone?) right at 20 seconds. Maybe it would work with a 19 second delay, but I didn't want it calling us for that - and my wife agreed ;) .

So that get's us there for the key stuff, thanks to all for your help. I just realized I forget to check CallCentric's * codes, they should be OK with the *xx. rule (and I did check them before), so I'm sure they work - and they don't use them anyhow, so no big deal. And we've got one more 'BIG BUTTON" phone to help with the eye-sight and dexterity issues, plus I'll add some more speed dials for them when they are ready.

-KenC

KenC,

I'm glad you have all the basics working. I had another look at the four-digit dialling idea and I can see why it does not work.

This rule should work:
Service Providers > ITSP Profile A > General > DigitMap:
(*xx.|**275*x.|[3469]11|1[2-9]xx[2-9]xxxxxxS0|<1>[2-9]xx[2-9]xxxxxxS0|<1847>[2-9]xxxxxxS4|<#:1847478>xxxx|011xx.|xx.)

The problem is the "#" is matched here before it can be used as you want:
Physical Interfaces > PHONE Port > DigitMap:
([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|**0|***|#|**1(Msp1)|**2(Msp2)|**3(Mvg1)|**9(Mpp)|(Mpli))

To make your rule work you would have to remove "#" from the Phone Port DigitMap. This should solve your problem, but would remove the ability to use "#" at the end of dialling any number to tell the OBi to send the number out with no delay. This may or may not matter to your In-Laws.

There's just not enough buttons on an average phone!

Quote from: ianobi on May 03, 2013, 03:50:20 AM
KenC,

I'm glad you have all the basics working. I had another look at the four-digit dialling idea and I can see why it does not work.

...

To make your rule work you would have to remove "#" from the Phone Port DigitMap. This should solve your problem, but would remove the ability to use "#" at the end of dialling any number to tell the OBi to send the number out with no delay. This may or may not matter to your In-Laws.

There's just not enough buttons on an average phone!

Ahh - that explains it. I could play with some other combinations, but it doesn't really seem worth it to eliminate dialing a 3 digit exchange, so I think I'll leave it as is.

I'm still somewhat curious why 10 digit dialing didn't work, but it's academic now as I have what I need.


Hmmm, I guess you can do partial dials with speed dial? So I could set up speed dial 9 as "1847478" then they dial 4 digits - that seems simple enough?

-KenC

Quote from: KenC_OB on May 03, 2013, 09:03:42 AM
Ahh - that explains it. I could play with some other combinations, but it doesn't really seem worth it to eliminate dialing a 3 digit exchange, so I think I'll leave it as is.

Does the as-it-is include the suggestion in Reply #143? You could increase the S4 to S8 if you  expect to normally use the # after the 4 digits. That would make the possibility of accidental dialing less if the number entry of bigger numbers was slow.

Combine that with specific quick dials, and you should be good. If the users have letters on their keypad, you can make meaningful speed dials that would be thought of as KC#, for example, to dial speed dial slot 52. I thought that was very useful when somebody posted that suggestion.

Quote from: Shale on May 03, 2013, 09:32:37 AM

Does the as-it-is include the suggestion in Reply #143? You could increase the S4 to S8 if you  expect to normally use the # after the 4 digits. That would make the possibility of accidental dialing less if the number entry of bigger numbers was slow.

Combine that with specific quick dials, and you should be good. If the users have letters on their keypad, you can make meaningful speed dials that would be thought of as KC#, for example, to dial speed dial slot 52. I thought that was very useful when somebody posted that suggestion.

Sorry, I should have been clearer - my 'as is' is currently:

(*xx.|**275*x.|[3469]11|1[2-9]xx[2-9]xxxxxxS0|<1>[2-9]xx[2-9]xxxxxxS0|<1847>[2-9]xxxxxxS4|011xx.|xx.)

I did not include the suggestion from post #143:

QuoteLet's try to keep it simple. Using the digit map as I proposed, if you dial four digits followed by # then the rule |<1847478>xxxxS4| would be processed instantly.

my concern there was (rare as it would likely be), that was pointed out earlier - if one of those 4 digit numbers was 311x, 411x, 611x or 911x, the |[3469]11| rule would gobble it up.

I guess my next step is, when I have some time, since I am on PhonePower and they are on CallCentric, I guess we can call straight thru the internet and avoid per minute charges, using SIP Broker? I'll google a bit. and that sounds like a new thread if I need help.

-KenC

Quote from: KenC_OB on May 03, 2013, 09:45:47 AM

my concern there was (rare as it would likely be), that was pointed out earlier - if one of those 4 digit numbers was 311x, 411x, 611x or 911x, the |[3469]11| rule would gobble it up.

|[3469]11S4| would introduce a 4 second delay. It may or may not be worth doing.

On the other hand, if there were no 911x numbers that they would ever dial (encompassing a maximum of 10 phone numbers total), then you could have a special rule for 911 and |[346]11S4| for the less critical ones.

Quote from: Shale on May 03, 2013, 09:54:10 AM

Quote from: KenC_OB on May 03, 2013, 09:45:47 AM

my concern there was (rare as it would likely be), that was pointed out earlier - if one of those 4 digit numbers was 311x, 411x, 611x or 911x, the |[3469]11| rule would gobble it up.

|[3469]11S4| would introduce a 4 second delay. It may or may not be worth doing.

On the other hand, if there were no 911x numbers that they would ever dial (encompassing a maximum of 10 phone numbers total), then you could have a special rule for 911 and |[346]11S4| for the less critical ones.

Something like that did cross my mind, though it didn't occur to me to break out 911 separate and immediate - seems like a reasonable approach. I think I'll give that a try. Thanks.

-KenC

I've got a question about automatically injecting a Star Code into a dialed number and have the commands in the corresponding Star Code apply to that call.  Is it possible using DigitMap in the Phone port or DigitMap in the ITSP profile?

my original post is here: http://www.obitalk.com/forum/index.php?topic=6625.0

Thanks in advance.

Just purchased obi200 but the configuration is so different from Sipura I would need some help.
I like to have one main provider that will be used by default when I pick up the phone, and by dialing #1 (#2 #3) it would route the call to provider 2 3 4. On any choice of provider I like to be able to dial any digit/*/# combination.

Can someone please give me hand with that  ???

Thanks!

Quote from: lifeisfun on October 25, 2013, 02:53:43 AM
Just purchased obi200 but the configuration is so different from Sipura I would need some help.
I like to have one main provider that will be used by default when I pick up the phone, and by dialing #1 (#2 #3) it would route the call to provider 2 3 4. On any choice of provider I like to be able to dial any digit/*/# combination.

Already built in is that to call 9876543210 on provider 2, you can dial **29876543210. If you dial just 9876543210, it goes via the provider you had set as the default.

Quote from: lifeisfun on October 25, 2013, 02:53:43 AM
I like to have one main provider that will be used by default when I pick up the phone, and by dialing #1 (#2 #3) it would route the call to provider 2 3 4. On any choice of provider I like to be able to dial any digit/*/# combination.

# is an OBi reserved character and has a special function. It indicates end of string and any digits dialed BEFORE the # will be immediately processed by the OBi. However the OBi will allow the 1st character dialed to be a #, so you can accomplish most of what you want.

x on a DigitMap indicates a single digit. Upper case X indicates a digit or asterisk. Placing a period after the x indicates zero or more occurrences.

You did not specify any requirement on length of the dialed string, so this example is crude.

In the Phone Port DigitMap place the following AFTER the beginning parenthesis:
#[123]XX.|

Place the following at the beginning of the Phone Port OutboundCallRoute:
{(<#1:>XX.:sp2},{(<#2:>XX.:sp3},{(<#3:>XX.:sp4},

The above will allow 1 or more digits/asterisks to be routed out your trunks.
You are specifying an unlimited length string when using XX., so the OBi will wait up to 10 seconds after you stop dialing for additional digits. You can dial a # after the last digit to eliminate the pause.

If you want to send the string with a trailing # do this:

{(<#1:>XX.<#>:sp2}

Quote from: affled on September 13, 2013, 09:17:10 PM
I've got a question about automatically injecting a Star Code into a dialed number and have the commands in the corresponding Star Code apply to that call.  Is it possible using DigitMap in the Phone port or DigitMap in the ITSP profile?

my original post is here: http://www.obitalk.com/forum/index.php?topic=6625.0

Thanks in advance.

I got it to work by adding a Star Code entry like this:

1623(<1623>xxxxxxx), Modem Call, set($Noji1,200),set($Noec1,1),set($Cdm1,3), call($Code)

Then I dialed 16231234567

There is a disagreement on this forum on the sequence of events after dialing a Star Code.

I believe the Phone Port DigitMap gets control first. If the DigitMap gets a match it passes control directly to the OutboundCallRoute, bypassing the Star Code profile. The dialed string must FAIL in the Phone Port DigitMap before the Star Code profile gets control, therefore you MUST REMOVE any rule in the DigitMap that will match the dialed string.

Quote from: azrobert on October 25, 2013, 04:08:11 PM

Quote from: lifeisfun on October 25, 2013, 02:53:43 AM
I like to have one main provider that will be used by default when I pick up the phone, and by dialing #1 (#2 #3) it would route the call to provider 2 3 4. On any choice of provider I like to be able to dial any digit/*/# combination.

# is an OBi reserved character and has a special function. It indicates end of string and any digits dialed BEFORE the # will be immediately processed by the OBi. However the OBi will allow the 1st character dialed to be a #, so you can accomplish most of what you want.

x on a DigitMap indicates a single digit. Upper case X indicates a digit or asterisk. Placing a period after the x indicates zero or more occurrences.

You did not specify any requirement on length of the dialed string, so this example is crude.

In the Phone Port DigitMap place the following AFTER the beginning parenthesis:
#[123]XX.|

Place the following at the beginning of the Phone Port OutboundCallRoute:
{(<#1:>XX.:sp2},{(<#2:>XX.:sp3},{(<#3:>XX.:sp4},

The above will allow 1 or more digits/asterisks to be routed out your trunks.
You are specifying an unlimited length string when using XX., so the OBi will wait up to 10 seconds after you stop dialing for additional digits. You can dial a # after the last digit to eliminate the pause.

If you want to send the string with a trailing # do this:

{(<#1:>XX.<#>:sp2}

Thanks for the detailed explanation and help!
I'll try that, and most likely will ask for help if I'm in trouble again :)

Quote from: Shale on October 25, 2013, 07:14:48 AM

Quote from: lifeisfun on October 25, 2013, 02:53:43 AM
Just purchased obi200 but the configuration is so different from Sipura I would need some help.
I like to have one main provider that will be used by default when I pick up the phone, and by dialing #1 (#2 #3) it would route the call to provider 2 3 4. On any choice of provider I like to be able to dial any digit/*/# combination.

Already built in is that to call 9876543210 on provider 2, you can dial **29876543210. If you dial just 9876543210, it goes via the provider you had set as the default.

Thanks

Quote from: lifeisfun on October 26, 2013, 04:53:42 AM

I presume that sp1 is set as default line, just out of curiosity where do you change that? I didn't find that option.

If using OBiTalk, in the setup for SP1, there is a box to tick: Primary Line for Outgoing Calls. With my OBi202, each SP has 2 boxes to tick or not, because there are two phone ports.

Quote from: azrobert on October 25, 2013, 05:58:53 PM

Quote from: affled on September 13, 2013, 09:17:10 PM
I've got a question about automatically injecting a Star Code into a dialed number and have the commands in the corresponding Star Code apply to that call.  Is it possible using DigitMap in the Phone port or DigitMap in the ITSP profile?

my original post is here: http://www.obitalk.com/forum/index.php?topic=6625.0

Thanks in advance.

I got it to work by adding a Star Code entry like this:
Thank you, I hope to give that a try
1623(<1623>xxxxxxx), Modem Call, set($Noji1,200),set($Noec1,1),set($Cdm1,3), call($Code)

Then I dialed 16231234567

There is a disagreement on this forum on the sequence of events after dialing a Star Code.

I believe the Phone Port DigitMap gets control first. If the DigitMap gets a match it passes control directly to the OutboundCallRoute, bypassing the Star Code profile. The dialed string must FAIL in the Phone Port DigitMap before the Star Code profile gets control, therefore you MUST REMOVE any rule in the DigitMap that will match the dialed string.

QuoteIs there any way to eliminate the 10sec after dialing number without dialing# to eliminate the pause before it gets sent out??

Don't use the X. in the DigitMap. For example if you always dial 10 digits use XXXXXXXXXX in the DigitMap and after you dial the 10th digit the OBi will immediately process the string.

Use xxxxxxxxx|xxxxxxxxxx if you dial 9 or 10 digits. 10 digits will be processed immediately. Dialing 9 digits will have a 4 second delay because the OBi doesn't know if you will dial the 10th digit.

You can also specify a 3 second pause like this: XX.S3
Don't set the pause too low. If you pause will dialing the OBi might start processing the call before you are finished.

QuoteI'm not sure what you mean by this since English is not my first language  

If you want to send the string with a trailing # do this:

{(<#1:>XX.<#>:sp2}

Use the above rule if you dial 1234567 but want 1234567# sent to your provider.

QuoteI presume that sp1 is set as default line, just out of curiosity where do you change that? I didn't find that option.

Shale already answered this if you use OBitalk to update the OBi.
If you update the OBi directly over the Web the Primary Line setting is just below the Phone Port OutboundCallRoute.

In the  Phone Port DigitMap (Mpli) points to the primary line's DigitMap, so if you change the primary line setting the Phone Port DigitMap is automatically updated.

Same for the OutboundCallRoute: {(Mpli):pli}

Quote from: affled on October 26, 2013, 07:48:19 AM

Thank you, I hope to give that a try

I have a suggestion on testing this. Before adding the Star Code make sure the dialed number fails in the DigitMap. You will get a busy signal. Then add the Star Code. This way you will be confident the Star Code is processing the dialed number.

Quote from: Shale on October 26, 2013, 07:29:37 AM

Quote from: lifeisfun on October 26, 2013, 04:53:42 AM

I presume that sp1 is set as default line, just out of curiosity where do you change that? I didn't find that option.

If using OBiTalk, in the setup for SP1, there is a box to tick: Primary Line for Outgoing Calls. With my OBi202, each SP has 2 boxes to tick or not, because there are two phone ports.

Got it, all working - THANKS folks!
Now last problem my outgoing CID doesn't work but I'll post in general section :)

I recently upgraded from a OBi100 to a OBi200.

I am currently reading through the OBi device administration guide trying to figure out the call routing and digit map section.

I'm set up currently with voip.ms on SP1, Google Voice on SP2 and Callcentric on SP3. I used the OBi Configuration(OBicfg.exe) utility to help me with the dial plans.

I have a quick question, which I hope someone can explain to me.

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

1) OBicfg.exe gave me the following with which I am not able to dial 933
([2-9]xxxxxx|[2-9]xx[2-9]xxxxxx|1[2-9]xx[2-9]xxxxxx|(00|011)xx.|<8835100>xxxxxxxx|8835100xxxxxxxx)

2) However, when I revert to the default I can dial 933.
(*75xx|*xx|1xxxxxxxxxx|<1212>[2-9]xxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*]@@.) 

Note: 933 is the number that Callcentric provides to test 911

Both 1) and 2) seem to follow all my other dial plans I have put in place. Can someone help explain what I am missing?

Thanks.

bonita,

911 and 933 are normally dealt with by the Phone Port DigitMap and the Phone Port OutboundCallRoute. Assuming that 911 and 933 should route to sp3, then you should see something like this:

Physical Interfaces > PHONE Port 1&2 > DigitMap:
(... other rules ...|911|933| ... other rules ...)

Physical Interfaces > PHONE Port 1/2 > OutboundCallRoute:
{ ... other rules ... },{(911|933):sp3},{ ... other rules ...}

This means that calls to 911 or 933 get dealt with directly with no reference to any other digit maps and no chance of delays or misrouting.


The Phone Port DigitMap defines which numbers to allow; the Phone Port OutboundCallRoute routes the numbers to the intended spX. For the puposes of this post:

Service Providers > ITSP Profile A > General > DigitMap = Msp1

I'm also guessing that sp1 is your Primary Line. Therefore:

Msp1 = Mpli

Mpli is "DigitMap Primary Line" – the service that does not require ** codes.

You will notice that Mpli occurs in both the Phone Port DigitMap and the Phone Port OutboundCallRoute. Therefore anything within Mpli is also in The Phone Port DigitMap and the Phone Port OutboundCallRoute.

Now here is your answer (sorry for the delay!):

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

This contains the rule "xx." This rule means one of any digit followed by none or any number of any digits. In effect it's a "catch-all" that allows any number of any length to be matched. With this in Mpli any number, including 933, is matched in the Phone Port DigitMap and Phone Port OutboundCallRoute.

The downside of the "xx." rule, and some others, is that your OBi has no idea when you have finished dialling, so it waits for ten seconds before deciding that you have finished before it processes the number.

Quick question - slow answer   :)

Quote from: ianobi on November 19, 2013, 08:28:50 AM
bonita,

911 and 933 are normally dealt with by the Phone Port DigitMap and the Phone Port OutboundCallRoute. Assuming that 911 and 933 should route to sp3, then you should see something like this:

Physical Interfaces > PHONE Port 1&2 > DigitMap:
(... other rules ...|911|933| ... other rules ...)

Physical Interfaces > PHONE Port 1/2 > OutboundCallRoute:
{ ... other rules ... },{(911|933):sp3},{ ... other rules ...}

This means that calls to 911 or 933 get dealt with directly with no reference to any other digit maps and no chance of delays or misrouting.

Thanks for the response. I appreciate your taking time to explain in detail.

Last night another user sent me a PM with a similar response and I found out that I had inadvertantly missed adding 933 in the DigitMap section. All my dial plans are working fine now.

I have the following in the same OutboundCallRoute
{(1[2-9]xx[2-9]xxxxxx):sp2}
{(1555555xxxx):sp1}

I want to confirm if the order in which they are in the OutboundCallRoute plays an important role.

If I have these two in my OutboundCallRoute as follows:
(.....{(1[2-9]xx[2-9]xxxxxx):sp2}....{(1555555xxxx):sp1}.....) then all numbers seem to be dialed using SP2

However, if I reverse the order of these two in my OutboundCallRoute as such:
(.....{(1555555xxxx):sp1}.....{(1[2-9]xx[2-9]xxxxxx):sp2}....) then 1555555xxxx numbers go through SP1 and the rest of the numbers use SP2.

Thanks.

NOTE: Edited message above, after ianobi's response: corrected DigitMap to OutboundCallRoute

We need to be accurate about terminology here. In a digit map it's the best match that wins and gets matched. In an OutboundCallRoute or InboundCallRoute a complete number is compared with each rule from left to right and the first rule to match is used.

Your observation concerns OutboundCallRoutes and the order does matter. First rule from the left to match will be used.

Hi everyone,

I am new to Obihai and have been trying to set up my dialing plan for days now. I Was wondering if anyone could help me with a small issue.

My setup:

SP1: GV (used for my business with a separate number)
SP2: Anveo with E911 (Primary provider)
SP3: VoipJumper (cheaper than Anveo for international calls)

Using ObiCfg utility (thank you RonR), I was able to get almost everything working:

1. 911 and all North American calls routed to SP2
2. 011 routed to SP3
3. **1, **2, **3 route to SP1, SP2, SP3 respectively

However, I would like to be able to make calls using SP1 GV without dialing **1. Ideally, I would like to be able to dial 0 followed by area code and 7 digit number.

I tried using suggestion from http://www.toao.net/500-mangos-guide-to-configuring-an-obi100-obi110-and-obi202-ata (http://www.toao.net/500-mangos-guide-to-configuring-an-obi100-obi110-and-obi202-ata)

DigitMap: (<0:001>[2-9]xx[2-9]xxxxxx|001[2-9]xx[2-9]xxxxxx)

but that didn't work. I think GV does not actually accept 001-aaa-xxx-xxxx calls. Could someone point me in the right direction? I tried modifying Physical Interfaces -> Phone Line 1 Digit Map and Outbound Call Route, and ITSP Profile A and B.

This is the relevant part of the ObiCfg text output:
Physical Interfaces -> PHONE Port 1 -> DigitMap: (911|#|***|**1(Msp1)|**2(Msp2)|**3(Msp3)|**4(Msp4)|**9(Mpp)|(Mpli))
Physical Interfaces -> PHONE Port 1 -> OutboundCallRoute: {911:sp2},{(<#:>):ph2},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Msp3)):sp3},{(<**4:>(Msp4)):sp4},{(<**9:>(Mpp)):pp},{((00|011)xx.):sp3},{(Mpli):pli}
Physical Interfaces -> PHONE Port 1 -> PrimaryLine: SP2 Service

Service Providers -> ITSP Profile A -> General -> DigitMap: (<1408>[2-9]xxxxxx|<1>[2-9]xx[2-9]xxxxxx|1[2-9]xx[2-9]xxxxxx)
Voice Services -> SP1 Service -> X_ServProvProfile: A
Voice Services -> SP1 Service -> X_InboundCallRoute: {ph1,ph2}

Service Providers -> ITSP Profile B -> General -> DigitMap: ([2-9]11S0|<1408>[2-9]xxxxxx|<1>[2-9]xx[2-9]xxxxxx|1[2-9]xx[2-9]xxxxxx|(00|011)xx.)
Voice Services -> SP2 Service -> X_ServProvProfile: B
Voice Services -> SP2 Service -> X_InboundCallRoute: {ph1,ph2}

Service Providers -> ITSP Profile C -> General -> DigitMap: ((00|011)xx.)
Voice Services -> SP3 Service -> X_ServProvProfile: C
Voice Services -> SP3 Service -> X_InboundCallRoute: {ph1,ph2}


Thank you!

um30 - welcome to the forum.

The mango version looks very odd. Your request is slightly unusual, but I think the following should work:

Physical Interfaces -> PHONE Port 1 -> OutboundCallRoute: {911:sp2},{(<#:>):ph2},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Msp3)):sp3},{(<**4:>(Msp4)):sp4},{(<**9:>(Mpp)):pp},{(<0:1>[2-9]xx[2-9]xxxxxx):sp1},{((00|011)xx.):sp3},{(Mpli):pli}

Service Providers -> ITSP Profile B -> General -> DigitMap: ([2-9]11S0|<1408>[2-9]xxxxxx|<1>[2-9]xx[2-9]xxxxxx|1[2-9]xx[2-9]xxxxxx|0[2-9]xx[2-9]xxxxxx|(00|011)xx.)

Thank you ianobi! Your suggestion worked! :)

I think I made a mistake when I put the <0:1> replacement code in ITSP Profile A rather than Phone 1 OutboundCallRoute.

It is still not entirely clear to me why we need to handle the 0[2-9]xx[2-9]xxxxxx sequence in ITSP Profile B when the replacement from 0 to 1 has already been made in the OutboundCallRoute. But I'm here to learn... :)

I really appreciate your help!

In your case Primary Line = SP2 Service. Therefore:

ITSP Profile B DigitMap = (Msp2) = (Mpli)

So whatever we put in ITSP Profile B DigitMap is also in (Mpli). All numbers to be dialled need to be "allowed" in the Phone Port DigitMap which contains (Mpli). (Mpli) is the only DigitMap that require no ** codes, so it is a convenient way of getting 0[2-9]xx[2-9]xxxxxx into the Phone Port DigitMap.

Now 0[2-9]xx[2-9]xxxxxx is allowed we need to route it. This is done in the Phone Port OutboundCallRoute using rule {(<0:1>[2-9]xx[2-9]xxxxxx):sp1}. I have done the transformation here of replacing the 0 with 1 so the rule only picks numbers starting with 0[2-9]. Had I done the transformation in ITSP Profile B DigitMap, then the number would have started with "1" when it was processed by the OutboundCallRoute and so we lose the choice of sending to either sp1 or sp2.

If you look at the RonR config, it does something similar by placing (00|011)xx. in the ITSP Profile B DigitMap, even though the rule will be needed for sp3.

I hope that helped  :)

Thank you ianobi! That's a great explanation! :)

I need to dial 123 for my voicemail & I'm trying to figure out how to add that to my dial plan so it dials it immediately. I tried adding |<S0:123> to the end of the DigitMap, but that didn't work.

tawd1992,

The format you are looking for is "other rules|123S0|other rules". However if you put that in a digit map, then any number you dial starting "123" will never get any further and will be sent to your provider as "123".

I believe that azrobert gave you the best answer in your other thread. If you put it in a speed dial in the format spX(123) then no digit maps are involved.

Yes, azrobert's speed dial suggestion turned out to be the best option. That's good to know about the other rules option as that may come in handy for another situation. Thanks.

Hello,

Could someone help me out on the following: I have a call plan that allows me to make really cheap calls to certain countries (in Europe, USA, Canada, etc.) while pretty expensive in others countries and to mobile numbers (also in Europe).
Could someone show how to allow certain calls, i.e. to landlines in Europe, and blocking all the cell phone calls? Obviously I have the country codes that I am willing to allow and to block.

Thank you in advance,

Sid

Sid - welcome to the forum.

Please give more details:
Which model OBi do you have?
How many sp's are in use - sp1, sp2 etc.
Which is the Primary Line? That is the one that does not require ** codes to use.
The codes you wish to allow and the ones to block.
Is the same sp used for your national calls and international calls?

That should be enough to get us started!

Hi
I have an OBI202 and I setup my mail ITSP on phone1 (atlasvoice, toronto based)
and I have a second ITSP as B.
The second ITSP is used only for outgoing calls since I dont have a number.
Also I have to mention the second ITSP is a european company and it accepts 00 for
international calls
I have all digitmap and call routes with their defaults values.
I have read quite few pages but I am not sure I have understood all the rules for
dial plans so if someone knows these rules well maybe can help me here

I want to do the following
a) How can I add #1 just before the number in order to make the call from ITSPB
   I used to be doing that in SPA3102.
   For example if I call UK I can type #10044xxxxxx and the call will be dialed from ITSPB
   More if I setup a third ITSP I would like to have #2 for the third

Thanks

Quote from: prince72 on March 23, 2014, 08:54:02 AM
Hi
I have an OBI202 and I setup my mail ITSP on phone1 (atlasvoice, toronto based)
and I have a second ITSP as B.
The second ITSP is used only for outgoing calls since I dont have a number.
Also I have to mention the second ITSP is a european company and it accepts 00 for
international calls
I have all digitmap and call routes with their defaults values.
I have read quite few pages but I am not sure I have understood all the rules for
dial plans so if someone knows these rules well maybe can help me here

I want to do the following
a) How can I add #1 just before the number in order to make the call from ITSPB
   I used to be doing that in SPA3102.
   For example if I call UK I can type #10044xxxxxx and the call will be dialed from ITSPB
   More if I setup a third ITSP I would like to have #2 for the third

Thanks

With the default settings, dialling **2 as a prefix will use SP2 for the call.  Is that really more arduous than #1?

You can do this without any prefixes.

Service Providers -> ITSP Profile B -> General -> DigitMap:
(0044xxxxxx.)

Service Providers -> ITSP Profile C -> General -> DigitMap:
(0061xxxxxx.)

Physical Interfaces -> Phone Port
DigitMap:
((Msp2),(Msp3)................current rules...........)
OutboundCallRoute:
{(Msp2):sp2},{(Msp3):sp3},..........current rules..............

Can you explain a bit your suggestion azrobert
If I add the ((Msp2),(Msp3).. as digitmap and
{(Msp2):sp2},{(Msp3):sp3} as outboutcallRoute
how can obi202 understand that numbers starting from 00
will be dialed out from SP2 or SP3?

Service Providers -> ITSP Profile B -> General -> DigitMap:
(0044xxxxxx.)

Service Providers -> ITSP Profile C -> General -> DigitMap:
((0061|0062)xxxxxx.)

Physical Interfaces -> Phone Port
DigitMap:
((Msp2)|(Msp3)|................current rules...........)
OutboundCallRoute:
{(Msp2):sp2},{(Msp3):sp3},..........current rules..............

First, I made a couple mistakes in the DigitMap. I forgot the vertical bar after (Msp3) and the comma should be a vertical bar.
I also want to make clear what I want done.
Add (Msp2)|(Msp3)| after the beginning parenthesis.

The Phone Port DigitMap validates the dialed number.
(Msp2) and (Msp3) point to the ITSP B and C DigitMaps.
So adding these to the Phone Port DigitMap will allow you to dial numbers beginning with 0044, 0061 and 0062, followed by 6 or more digits.
{(Msp2):sp2} in the Phone Port OutboundCallRoute will check for dialed numbers beginning with 0044 and on a match will route the call out SP2.
{(Msp3):sp3} in the Phone Port OutboundCallRoute will check for dialed numbers beginning with 0061 or 0062 and on a match will route the call out SP3.

If this doesn't meet your requirements tell me exactly what you need.

One of our OBi users in Australia has written an excellent tutorial on digit maps - "OBi Digitmaps Unravelled" - that I have attached to this post.

Thunderbird1 has been a regular contributor on the Australian Whirlpool forum in the discussion thread on the OBi202, found here:

http://forums.whirlpool.net.au/forum-replies.cfm?t=2215053

"S0" at the end of a string like |1xxxxxxxxxxS0| will cause it to dial immediately after the last digit instead of using the interdigit timer. This will allow u to redial numbers that u had to enter extra digits for a VRU like "press 1 for sales, 2 for technical support", etc
just be careful u don't add it to the wrong sequence
here is my sequence the allow 7,10, or 11 digit dialing and redials extra digit added numbers since it just cuts them off. Change the 919 to ur area code

(*xx|1xxxxxxxxxxS0|<1919>[2-9]xxxxxx|<1>[2-9]xxxxxxxxxS0|011xx.|xx.|(Mipd)|  [^*]@@.)


A major PITA with Nettalk since it can't be changed on the DUO

Quote from: MarkObihai on April 29, 2014, 07:56:41 AM
One of our OBi users in Australia has written an excellent tutorial on digit maps - "OBi Digitmaps Unravelled" - that I have attached to this post.

Thunderbird1 has been a regular contributor on the Australian Whirlpool forum in the discussion thread on the OBi202, found here:

http://forums.whirlpool.net.au/forum-replies.cfm?t=2215053

Hi Mark:

So, I looked at your link.  It's a 29-page and growing thread.  I gave up after reading a few of those 29 pages.  The "tutorial" is a 17-page textbook.  This is a good example of how incredibly complex the dial plan rules can be...endless, endless threads here, on DSLReports, and now on Whirlpool.  I think there are probably less than 3-5 human beings outside of Obihai that really understand (and can explain!) how to make a simple, efficient dial plan.  Having two different places in the configuration for dial plan rules that interact with each other (Phone port and Service Provider) makes it much worse.

Here is another (10-page) thread, going on for years, that just makes my head hurt.

http://www.obitalk.com/forum/index.php?topic=34.0

The "programming language" knowledge needed is just too steep.  I understand that it offers powerful configuration options, but less than 10% of users need that.

Relying on the ITSPs to create optimized dial plans for their services is also a bad idea, since most of them have no clue, either.

What is really needed, is a GUI, check-the-boxes tool integrated right into the Obitalk portal, to optimize dial plans.  Something similar to what RonR created and posted over on DSL reports, but built into the portal, not standalone.

Ah, it's the kind of knowledge we'll need if we are ever going to conquer FTL. ;D

Adding to my comment "Relying on the ITSPs to create optimized dial plans for their services is also a bad idea, since most of them have no clue, either."

Ideally, if Obihai is going to be successful with their authorized service provider program, they should consult with each authorized SP to design an optimized dial plan for that provider as a starting point (e.g. which string reaches that SP's voicemail box, and how to handle international calls), then provide the user with the GUI check-box interface to tweak it (for example, if a user wants outbound calls or inbound calls to route to some other SP or VG, or if they want to use some other route for E911, and on and on). 

No mere mortal should have to figure this out when signing up with an ITSP.  Can you imagine if Comcast required you to know C++ and Ruby on Rails to set up your channel list?

I have a question regarding numbering plan for international dialing and 911:

Current setup:
line 1: with GoogleVoice, used for all inbound and US domestic (including Canada) outbound calls
line 2: VoiP provider, used for outbound only for international calls.

For example, if I need to dial UK, I dial **2-011-44-xxx-yyyyyyy where **2 - second line prefix, 011 - international dialing prefix, 44 - UK country code.

I need to create numbering plan such as every dialing sequence that starts 011 will be replaced by **2011  and
if 911 dialed from Line 1, I want the call to be forwarded to predefined number (provided by gv911.com), for example, 1-222-333-4444 on line 1.

Assuming that sp1 is your Primary Line, then:

Service Providers > ITSP Profile A > General > DigitMap:
(<**2>011xx.S3|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*#]@@.)

If your voip provider fails, then you should still be able to force 011 calls via GV by dialling **1 before the number.


911 is best routed at a higher level, that is in the Phone Port OutboundCallRoute, then it will not be affected by any future digit map changes.

Replace any existing rule containing "911" in the Phone Port OutboundCallRoute with:

Physical Interfaces > PHONE Port > OutboundCallRoute:
... existing rules here ... ,{(<911:12223334444>):sp1}, ... existing rules here ...

Quote from: ianobi on December 16, 2015, 03:57:21 AM
Assuming that sp1 is your Primary Line, then:

Service Providers > ITSP Profile A > General > DigitMap:
(<**2>011xx.S3|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*#]@@.)
...

Thank you.

I did it and discovered another problem: I forgot that provider on line 2 requires prefix 00 instead of 011 for international dialing. So, 011 shall be replaced by 00 on line 2. Another option: to strip 011 completely while dialing via line 2: provider 2 supports two options: 00 or without prefix. For example, both sequences will work:

00-44-xxx-yyyyyyy and 44-xxx-yyyyyyy

No "00" prefix:
Service Providers > ITSP Profile A > General > DigitMap:
(<011:**2>xx.S3|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*#]@@.)

With "00" prefix:
Service Providers > ITSP Profile A > General > DigitMap:
(<011:**200>xx.S3|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*#]@@.)

I am using Obi200 and my config is as below.

SP1: Google Voice with dedicated Google Voice Number
SP2: Freephoneline.ca

My primary line is SP2.

I am using raza.com for my long distance needs. You need to dial access number and then dial destination number in order to place call successfully.
Can anyone please give me the Digit Map settings which can prepend Raza.com access number when I dial long distance number? Please note that there is a 4-5 sec pause required after dialing Access Number in order for Raza.com to verify account details

I have tried following under Service Providers > ITSP Profile B > General > DigitMap
<14164776885> 91xx.
Where, 14164776885 is Raza.com access number and 91xx. is number starting with 91

Above setting is not working for me. Any help will be appreciated. Thanks in advance.

Okay, I'm basically trying to define the following, how do I get it to do the ObiTalk defaults which has the following DigitMap string:
(*xx|1xxxxxxxxxx|<1415>[2-9]xxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*]@@.)

What I want to do is:
When I dial,  I want it to call
211             1-800-273-6222
311             1-415-701-2311
411             1-800-373-3411
511             1-888-500-4636
811             1-800-227-2600

I got it working so others can use this for reference:
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*#]@@.|<211:8002736222>|<311:4157012311>|<411:8003733411>|<511:8885004636>|<811:8002272600>)

Thanks!

Quote from: CaliBoy on January 29, 2016, 11:15:50 AM
Can anyone please give me the Digit Map settings which can prepend Raza.com access number when I dial long distance number? Please note that there is a 4-5 sec pause required after dialing Access Number in order for Raza.com to verify account details

There's no way for the Obi to add the needed pause. Unless you can send a desitnation string to Freephoneline.ca that does what you want it won't work.

Quote from: ianobi on April 27, 2013, 11:43:42 AM
I see how you are thinking. Lucky Patcher (https://luckypatcher.pro/) Kodi (https://kodi.software/)  The rule you would need is:
|<#:1847478>xxxx|

Let's try to keep it simple. Using the digit map as I proposed, if you dial four digits followed by # then the rule |<1847478>xxxxS4| would be processed instantly.

Dialling # after any number of digits forces the interdigit timer to 0 and instantly executes the rule. So if your In-Laws are ok with that, then it's simple and can be applied to any number - four digits, seven digits etc. I suggest leaving the S4 in place in case they forget to dial the # at the end of the number.

Thank you - that does seem to have what I need, will study up a bit later.

Email sent.

Thanks RonR

Want to implement a fix number dialing, when one pick up home phone, directly call to my mobile number thru Line phone.

Quote from: Black1Star on May 19, 2020, 06:10:26 AM
Want to implement a fix number dialing, when one pick up home phone, directly call to my mobile number thru Line phone.

(<:your cell number>| as first rule in Line DigitMap

When I was about to start testing your DigitMap, it dawned on me that in this particular case, S0 won't have any effect because both rules are effectively S0 already.  When either rule goes into the Exactly Matched state the other will be in the Mismatch state, so the DMP returns the matched rule's value immediately.



shazam for pc windows (https://sites.google.com/view/shazamforpcwindows/home)