Quote from: RonR on January 21, 2012, 11:37:15 AM
The following will prepend 0011101 to all calls sent using SP2:
Service Providers -> ITSP Profile B -> General -> DigitMap:
(<0011101>(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1aaa>[2-9]xxxxxx|<011:>xx.)|(Mipd)|[^*#]@@.'@'@@.)
where aaa is your local (US) area code.
I'm getting strange digit formations that are sent out to the selected service (SP2) with above syntax.
The exact digitmap I'm using for SP2 is shown below. In addition to substituting 011 with the Voxbeam prefix,
I'm also adding/replacing numbers that start with "00" with Voxbeam prefix as well:
(<0011101>(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<011:>xx.|<00:>xx.|xx.)|(Mipd)|[^*#]@@.)
Below is representative behavior I see at the call records.
Example:
I dialed: **2301234567890
digits shown at PHONE1 terminal: **20011101301234567890
digits shown at SP2 terminal: 001110111101301234567890
It seems that for some reason the 0011101 prefix was added to the phone terminal digits before the SP2 digitmap was applied. And when the SP2 digitmap was applied, the "011" pattern was removed and
a second 0011101 prefix was attached.
The digit map and outbound call route info for PHONE are the defaults.
I can't seem to figure out why Obi shows that the PHONE terminal added the first
instance of the 0011101 prefix.
L.
PS: I tested also with an SP2 digitmap where I removed all the 00 and 011 handling part.
I see again that the 0011101 prefix is shown in the PHONE1 terminal digits.