iNum problem?
 

Hi there,

I would like to know there is some problem in connecting calls from Voxalot users to iNum numbers. Since some days ago I have tried to call iNum numbers, including the echo test number (+883-510-000-000091), and the calls returned as unknown number.

Just to isolate the issue, I have tried calling iNum echo test directly from another Provider and it worked fine.

Thanks.

I can confirm the problem you are experiencing with iNum. Hopefully, Martin will take a look at this shortly and make the necessary correction.

iNum numbers unreachable from Voxalot
 

Hello Martin,

Is there any news about this matter?

Thanks in advance.

Calls to iNum numbers don't work yet...
 

Hello Voxalot support team,

Please help calls to iNum numbers from Voxalot numbers work again.

At least, give us just some information/explanation about this problem and the plan to solve it, please.

Thanks,

André

Voxalot's internal support for iNum calls is still not functioning.

If you happen to have a Gizmo5 account set up on Voxalot, you can route iNum calls through Gizmo5 using the following Dial Plan entry:


Pattern: _883XXXXXXXXXXXX

Replacement: +${EXTEN}

Provider: Gizmo5

If you do a test on the Dial Plan page, you will see that Voxalot is routing an 883xxxxxxxxxxxx number to a Voxbone IP address. So either the routing IP has changed or it is not working.

However, the suggestion by Ron should work perfectly, and any provider on the iNUM list can also be tested and used :
iNum - One number for the world - iNum Providers

Just be sure to match the replacement number in your Dial plan with the format expected by the provider you are using.

For example, if you are using Callcentric as the outbound provider, the number must be in the format [00883xxxxxxxxxxxx].

I've added my INUM number (provided by Voxalot) as a jabber contact (number@inum.net) in my messaging client, mainly for testing purposes.

It's offline for a few days now :(

Something wrong
 

I just wonder... if this a known problem why is there no answer or action on it?

The problem exists. Nothing is done. Nothing is said. Something is not going well with Voxalot.

iNum calls are working again through Voxalot. Unfortunately, they are being routed through a very annoying Voxbone server that requires you to listen to an obfuscated 5 digit pin and enter it before your call is connected. Consequently, the best solution is still to catch iNum calls in your dial plan and route them via a more friendly server such as Gizmo5 as described above.

So from the looks of it ...:

-Calls to INum via VoXalot are still not working
-VoXBone has submitted their numbers into 164.arpa ... which means the connection that's bein observed lately is due to ENUm lookup (and the server they've sumbitted is reported to require this 5 Digit pin).

See SIP Sorcery Community Forums • View topic - sys.ENUMLookup for iNum 883 numbers