Help with basic digit map

[SeanTek]

I am new to making digit maps.

First of all, are the terms "dial plan" and "digit map" basically synonymous?

I want to map a single short number (311) to a full telephone number (USA +1). So, it would be:
311 -> 12134733231. I want this to work regardless of which line I have chosen, with no change to the service choice.

I thought I would create the digit map in the Obi config page:
User Defined Digit Map2
Label: LA311
DigitMap: (<311:12134733231>)

But it does not seem to have the desired effect. What am I missing?

(As a bonus, what else do I put in the digit map to stop the waiting once 3 1 1 are pressed, so that the call is immediately connected?)

[drgeoff]

User defined digit maps have no effect unless they are 'called' from one of the usual places.

You can explicitly insert

<311:12134733231>|

immediately after the opening bracket of the Phone Port Digit Map. (Both Phone Ports if an OBi202.)

But that will not work if you are using **1 etc to select the outgoing SP.  I don't see why inserting

<311:12134733231>|<**1311:**112134733231>|<**2311:**212134733231|

wouldn't overcome that.

[SeanTek]

Add

<311:12134733231S0>|

immediately after the opening bracket of the Phone Port Digit Map.

To be clear: that is Physical Interfaces -> PHONE 1 -> PHONE Port -> DigitMap , right?

Mine is currently:

Code:

([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|**0|***|#|##|**70(Mli)|**8(Mbt)|**81(Mbt)|**82(Mbt2)|**1(Msp1)|**2(Msp2)|**3(Msp3)|**4(Msp4)|**9(Mpp)|(Mpli))

which I believe is the default. But there is no opening curly brace { .

You can delete your user defined map. User defined digit maps have no effect unless they are 'called' from one of the usual places.

What do you mean by "the usual places"? You mean, called from somewhere like the PHONE Port -> DigitMap you mentioned above?

[drgeoff]

I modified my reply.  See above

In UK English, 'bracket' can mean a ( .  Maybe that is not the case where you are.

I'm unsure about the S0 bit even after consulting the Admin Guide.    http://www.obihai.com/OBiDeviceAdminGuide#_Toc367543132

[azrobert]

I think the correct syntax is: <311S0:12134733231>

You need to match 311 first before transformation occurs, so you need to use S0 on the 311.

The phone digit map is always used, so drgeoff's suggestion for the **x prefixes will work. If you want to place the code in other digit maps you must explicitly point to them. The default phone digit map points to the primary line's digit map with rule (Mpli).  Rule "**2(Msp2)" is used when forcing a call to SP2.

Another coding option is to include the above rule in each of the ITSP digit maps.

If you create a user digit map and name it udd, you need to add rule (Mudd) to the phone digit map.

[SeanTek]

In UK English, 'bracket' can mean a ( .  Maybe that is not the case where you are.

I would call ( a 'parenthesis'. [ is a 'bracket'. { is a 'curly brace'. 

Anyway I will test these out shortly (after the oauth_disabled storm dies down).

[drgeoff]

In UK English, 'bracket' can mean a ( .  Maybe that is not the case where you are.

I would call ( a 'parenthesis'. [ is a 'bracket'. { is a 'curly brace'. 

See BODMAS and PEMDAS in the Mnemonics section at https://en.wikipedia.org/wiki/Order_of_operations

[SeanTek]

I tried these, and they worked! Specifically:

Code:

<311:12134733231>|

and

Code:

<311S0:12134733231>|

worked. The latter is my preferred approach, because once I enter 311 I want it to "go" immediately.