Voxalot launches iNum Connectivity

[martin]

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

[Ron]

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

[martin]

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

[emoci]

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)

[martin]

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"

[emoci]

Well not sure...I'm still getting a busy tone...

Testing with:
883510000000091
883510074022302

[affinity]

Originally Posted by martin

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"

So.... you cannot have a catchall.

How do you code all other numbers, except those starting with 883 ?

[krbonne]

Hi,

Originally Posted by martin

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.
Thanks

What is the enum-root for inum? I run a asterisk at home.


Cheerio! Kr. Bonne.

[blanu]

Originally Posted by krbonne

What is the enum-root for inum?

If the ENUM root is not public available, then perhaps it'd be an idea for voxalot to put its entire iNum range in, say, e164.org (or even e164.arpa)?

Cheers,
Blanu

--
חג אורים שמח

[Ron]

Originally Posted by martin

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

Still not working, Martin. Still getting "We're sorry, the number you have called could not be connected".

883510000000091 is being routed to Voxalot as the privider by an explicit Dial Plan rule that looks for a prefix of '6'. A Dial Plan Test returns "A call to:6883510000000091 will get forwarded to 883510000000091 via Voxalot".