Dial Tone prompts for each outgoing account

<< < (3/3)

RonR:
Yes, you can redesign the entire dialing syntax, but what you're proposing is a considerable amount of change to the PHONE Port DigitMap and OutboundCallRoute to effect a new dialing methodology.  I may be wrong, but I doubt that's what the OP is looking to do at this stage.  It also seems to me to be overkill just to avoid dialing the occasional **n prefix.

jimates:
Quote from: RonR on April 23, 2011, 10:58:05 pm

Yes, you can redesign the entire dialing syntax, but what you're proposing is a considerable amount of change to the PHONE Port DigitMap and OutboundCallRoute to effect a new dialing methodology.  I may be wrong, but I doubt that's what the OP is looking to do at this stage.  It also seems to me to be overkill just to avoid dialing the occasional **n prefix.


I agree with the last sentence. As far as the first sentence, there are only 2 changes to make in each place.

There is no telling what the OP wants to do if they desire to eliminate pressing 2 digits from the default dialing sequence.


On the Obi100 # can be assigned in place of **9 because there is no line port & **2 can be shortened to *2 which does no conflict with star codes in any way.

default digit map
([1-9]x?*(Mpli)|[1-9]|[1-9][0-9]|911|**0|***|#|**1(Msp1)|**2(Msp2)|**9(Mpp)|(Mpli))

edit to
([1-9]x?*(Mpli)|[1-9]|[1-9][0-9]|911|**0|***|#|**1(Msp1)|*2(Msp2)|#(Mpp)|(Mpli))


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

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

Or switch them up, *9 does not conflict with star codes either

Navigation

[0] Message Index

[*] Previous page