Voxalot / SIP Broker Support Forums - View Single Post

ataboy · 02-14-2009, 10:03 AM

Thanks for testing for me, kurun. I have made some changes and the results are intriguing.

1. I moved the line to Priority 1 to avoid any conflicts.
2. I changed the access code from 88 to 44 (PBXes uses digit 8 for conference calls).
3. I also changed the code slightly from _44. to _44x, as I see you had.

I had already done a Dial Plan Test, but I did another and saw "A call to:447 will get forwarded to **7 via Voxalot"

Then I tested it on a live call from a telephone directly registered with Voxalot. The call failed, with the message "Sorry, the number you have called could not be connected."

Next I tested it on a callthrough via PBXes. Again it failed, this time with the message "We're sorry, the speed dial number you dialled does not exist."

Curiouser and curiouser. . .

02-14-2009, 10:03 AM	#3
ataboy Senior Member Join Date: May 2006 Location: Greater London, UK Posts: 198 Thanks: 36 Thanked 23 Times in 23 Posts	Thanks for testing for me, kurun. I have made some changes and the results are intriguing. 1. I moved the line to Priority 1 to avoid any conflicts. 2. I changed the access code from 88 to 44 (PBXes uses digit 8 for conference calls). 3. I also changed the code slightly from _44. to _44x, as I see you had. I had already done a Dial Plan Test, but I did another and saw "A call to:447 will get forwarded to **7 via Voxalot" Then I tested it on a live call from a telephone directly registered with Voxalot. The call failed, with the message "Sorry, the number you have called could not be connected." Next I tested it on a callthrough via PBXes. Again it failed, this time with the message "We're sorry, the speed dial number you dialled does not exist." Curiouser and curiouser. . .