![]() |
|
Voxalot Support Support for the Voxalot service. |
![]() |
Thread Tools | Display Modes |
![]() |
#1 |
![]() ![]() Join Date: Feb 2006
Posts: 2,930
Thanks: 528 Thanked 646 Times in 340 Posts ![]() ![]() ![]() ![]() ![]() ![]() |
![]() Please see http://forum.voxalot.com/voxalot-sup...uncements.html
Feedback welcome. Edit: Adding info to this post... VoXalot has a range within the +883 country code (INUM): +883 510 004 XXXXXX Where XXXXXX is the Voxalot account number. This setup is now live in production (both Voxalot and Voxbone). NOTE: You can not call Voxalot <-> Voxalot using the 883510004 prefix as this does not make much sense. You can however, use the 883510004 from any of the other iNum providers (Gizmo etc) and some PSTN carriers. iNum echo test: 883510000000091 For locations where the local PSTN carrier is not yet supporting the +883 country code, access numbers are provided: iNum - One number for the world - iNum Partners
__________________
Martin Please post support questions on the forum. Do not send PMs unless requested. Last edited by emoci; 05-10-2009 at 03:55 PM. |
![]() |
![]() |
![]() |
#2 |
![]() ![]() Join Date: Feb 2006
Posts: 447
Thanks: 4 Thanked 8 Times in 8 Posts ![]() |
![]() Martin,
How does Voxalot determine that an outgoing call is to be routed via iNum? I don't find a Sip Broker *Code for iNum. Does Voxalot assume that any dialed number starting with 883 is an iNum number and pick it off? If I simply dial the iNum echo test (883510000000091), I get a fast busy. I've tried various Dial Plan entries to ensure that any number starting with 883 was routed to Voxalot as the provider, but that also gets a fast busy or "Your call could not be connected". Would you please elaborate on how iNum numbers are detected and handled, and what, if anything, we have to have in our Dial Plans to support them? Inbound calls to my Voxalot number from an iNum PSTN access number or Sip Broker PSTN access number work fine. Thanks, Ron |
![]() |
![]() |
![]() |
#3 |
![]() ![]() Join Date: Feb 2006
Posts: 2,930
Thanks: 528 Thanked 646 Times in 340 Posts ![]() ![]() ![]() ![]() ![]() ![]() |
![]() Sorry Ron we were trialing a new ENUM root that was intercepting the calls. You should not need to change anything as iNum calls should be seamless. You just need to make sure that none of your dial plan entries are kicking in.
Please try again and let me know if it is OK? Thanks
__________________
Martin Please post support questions on the forum. Do not send PMs unless requested. |
![]() |
![]() |
![]() |
#4 |
![]() ![]() Join Date: Jul 2007
Location: Toronto, Canada
Posts: 1,422
Thanks: 123 Thanked 369 Times in 282 Posts ![]() ![]() ![]() ![]() |
![]() Hmm,
Still not working yet...I actually managed to see it route to an 8x.xx. IP once while running a test via the Dial Plan test line... (I assume that was the eNum root) |
![]() |
![]() |
![]() |
#5 |
![]() ![]() Join Date: Feb 2006
Posts: 2,930
Thanks: 528 Thanked 646 Times in 340 Posts ![]() ![]() ![]() ![]() ![]() ![]() |
![]() Yes that was the ENUM root.
The dial plan test facility on the web site does not yet support iNum so for now what you are looking for is the following message when you click "Test Call": "A call to:883510000000091 will not get forwarded"
__________________
Martin Please post support questions on the forum. Do not send PMs unless requested. |
![]() |
![]() |
![]() |
#6 |
![]() ![]() Join Date: Jul 2007
Location: Toronto, Canada
Posts: 1,422
Thanks: 123 Thanked 369 Times in 282 Posts ![]() ![]() ![]() ![]() |
![]() Well not sure...I'm still getting a busy tone...
Testing with: 883510000000091 883510074022302 |
![]() |
![]() |
![]() |
#7 | |
![]() ![]() Join Date: Feb 2006
Posts: 2,930
Thanks: 528 Thanked 646 Times in 340 Posts ![]() ![]() ![]() ![]() ![]() ![]() |
![]() Quote:
Which proxy are you connected to?
__________________
Martin Please post support questions on the forum. Do not send PMs unless requested. |
|
![]() |
![]() |
![]() |
#8 |
![]() ![]() Join Date: Jul 2007
Location: Toronto, Canada
Posts: 1,422
Thanks: 123 Thanked 369 Times in 282 Posts ![]() ![]() ![]() ![]() |
![]() |
![]() |
![]() |
![]() |
#9 |
![]() ![]() Join Date: Feb 2006
Posts: 2,930
Thanks: 528 Thanked 646 Times in 340 Posts ![]() ![]() ![]() ![]() ![]() ![]() |
![]() I just grepped the logs on both the US1 and US2 proxies for "883510074022302" and got nothing.
Is there a chance that the call to 883510074022302 did not get to Voxalot?
__________________
Martin Please post support questions on the forum. Do not send PMs unless requested. |
![]() |
![]() |
![]() |
#10 |
![]() ![]() Join Date: Jul 2007
Location: Toronto, Canada
Posts: 1,422
Thanks: 123 Thanked 369 Times in 282 Posts ![]() ![]() ![]() ![]() |
![]() It's possible...grab records once more and see if anything shows up now if you can... maybe willhave to do some testing internally make sure it's not an ATA dialplan issue
|
![]() |
![]() |
![]() |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Voxalot and Sipura/ATA Tutorial: A Comprehensive Walkthrough | ctylor | Voxalot General | 5 | 04-28-2010 12:52 AM |
New user problems with Call Connection Rules | bdlhome | Voxalot Support | 12 | 09-10-2008 02:19 AM |
VoXaLot Launches European Server | Tony | Voxalot Support | 28 | 02-07-2007 07:15 AM |
Newbie - but please be nice | Mallycat | Voxalot Support | 21 | 04-15-2006 07:50 AM |