Quote:
|
Originally Posted by wmp
Something is still off for me. It appears that calls do not go through if I prefix the ${EXTEN} in the replacement field of my dial plan. Here is a sample of my current dial plan:
Code:
1 _NXXXXXX 1910${EXTEN} Vbuzzer
2 _1NXXNXXXXXX ${EXTEN} Vbuzzer
3 _ NXXNXXXXXX 1${EXTEN} Vbuzzer
If I dial 1-910-555-5555 (2) then the call goes through without a problem. However, if I dial 555-5555 (1) or 910-555-5555 (3) then the call is not successful. Can anyone confirm this? Changing my provider to Voxee fixes the problem but I am perplexed as to why Vbuzzer can only use method 2. |
It is perplexing that Voxee works but Vbuzzer doesn't. At first glance, your dial plans look ok to me.
Like you, I also wanted to have seamless support for 7, 10, and 11 digit numbers. I chose to implement it in the PAP2 rather than on VoXaLot, however, as I've had as many as five providers set up and didn't want to have three dial plans for each one. My PAP2 dial plan is:
Code:
(<911:15629042363>S0 |#x<:1562>[2-9]xxxxxx|#x<:1>[2-9]xx[2-9]xxxxxxS0 |#x1[2-9]xx[2-9]xxxxxxS0 |<:1562>[2-9]xxxxxx|<:1>[2-9]xx[2-9]xxxxxxS0 |1[2-9]xx[2-9]xxxxxxS0 |[x*][x*].)
This allows me to dial 7, 10, and 11 digit numbers and have them arrive at VoXaLot consistantly as 11 digits. This also allows me to specify one of my alternate providers by simply prefixing the desired number with #n. Each provider requires only one dial plan using this approach. Arbitrary digit combinations are also supported to allow Sip Broker access.
Ron