Limited Length of DigitMap??
quanttrom:
The string itself does NOT get truncated. The OBi 110 will save it and display it just fine.
When you try dialing it will just fail to interpret it and won't dial anything for you.
I like your idea of splitting it into multiple user DigitMaps :) very nice !
You are right about the area codes and the majority of my traffic. I just did it for completeness sake.
RonR:
Quote from: quanttrom on October 18, 2011, 04:09:24 pm
The string itself does NOT get truncated. The OBi 110 will save it and display it just fine.
You're right. Prior to v1.3, they used to get truncated. Now they don't get trunctated but the OBi obviously gets badly corrupted internally. In my case, after setting the LINE Port DigitMap to 530 characters, providers on SP1 and SP2 won't even register.
Sloppy programming.
quanttrom:
The map string was only 151 chars anyways. Maybe it's the large number of OR operators..
RonR:
Quote from: quanttrom on October 18, 2011, 08:17:42 am
([69]11 <:#> | 519 [2-9]xx xxxx <:#> |...)
What's with the '<:#>' additions to your DigitMap? That will append a '#' to the number sent to the service provider. I know of no service providers that want that (certainly not Google Voice).
Stewart:
Quote from: RonR on October 18, 2011, 06:08:34 pm
What's with the '<:#>' additions to your DigitMap? That will append a '#' to the number sent to the service provider. I know of no service providers that want that (certainly not Google Voice).
I'm reasonably certain that's correct for the OP's case. See http://www.myxlink.com/xlink_bttn.aspx .
Navigation
[0] Message Index
[#] Next page
[*] Previous page