Digimap and outgoing porting for Obi202

<< < (2/2)

Shale:
While we are discussing obscure, I wonder how <x?>xx. would do to replace xx. as the catch-all with lower precedence.  Much less obscure might be xx.S2 or xx.S4  as alternatives.

These are not suggestions to hueofheather or others, but just throwing them out as for food for thought.

Longer but clearer strings are better for real use.

hueofheather:
Well, thank you guys!

I used Service Providers > ITSP Profile A > General > DigitMap:

(<**21>613xxxxxxx|<**21>815xxxxxxx|<**2>1613xxxxxxx|<**2>1815xxxxxxx|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*#]@@.)

Now however when I dial **2 to select the line, I get a busy signal. IE, to check voicemail.    If there is an easy fix, what would that be?

Again, thanks for your help!


 I had the right idea but used the wrong Digimap.  I was in the Phone Port .



Thanks for your help!

Shale:
Quote from: hueofheather on September 11, 2013, 05:25:41 pm


Now however when I dial **2 to select the line, I get a busy signal. IE, to check voicemail.    If there is an easy fix, what would that be?


You are dialing **2 and then waiting? You need to keep dialing the digits before stopping. So you might dial **21202551234 to dial 1202551234 on SP2.

ianobi:
Shale,

Quote

Much less obscure might be xx.S2 or xx.S4  as alternatives.

There's definitely merit in using xx.S4 instead of xx.

The problem here is that having xx. or [^*#]@@. in any digitmap means that whatever you dial those two rules are always in the "Indefinitely Matched" state. This means that even if you have a rule in the "Exactly Matched" state, there will still be a two second delay.

My personal preference is to delete xx.|(Mipd)|[^*#]@@. from my digitmaps and find other less general ways of matching numbers/characters.

Navigation

[0] Message Index

[*] Previous page