Voxalot / SIP Broker Support Forums

Voxalot / SIP Broker Support Forums (http://forum.sipbroker.com/index.php)
-   Voxalot Support (http://forum.sipbroker.com/forumdisplay.php?f=4)
-   -   Voxalot launches iNum Connectivity (http://forum.sipbroker.com/showthread.php?t=3629)

klijnw 12-23-2008 08:36 PM

Hi, I also tried via voipbuster the 883510004xxxxxx number and got the same problem => rings 3 or 4 times and then says "unfortunedly it is not possible to ring this number at this moment". I also tried via PSTN the country INUM-accessnummer in Amsterdam 020-8080808 followed by the same 883510004xxxxxx and it worked FINE! My Voxalotphone ring including numberregonistion from the original line ... PERFECT! So I think it's a voipbuster problem.

rybshik 12-23-2008 08:54 PM

Quote:

Originally Posted by klijnw (Post 20593)
Hi, I also tried via voipbuster the 883510004xxxxxx number

How do you get the prefix "510004" for voipbuster? what is the rest "xxxxxx"? Voipbuster's username?

If my voipbuster username is 'dude1975', what should i dial?

How one gets the code/prefix for another Betamax server?

Thanks.

ataboy 12-23-2008 09:22 PM

I just tried three PSTN iNum access numbers at random (Paris, Chicago and Stockholm) and all 3 calls failed to connect.

I was calling from a GSM phone, not over VoIP.

Edit: I just called the London number from a BT line (i.e. as local as you can get) and got the message "The service cannot be connected".

carlosalbffgomes 12-23-2008 09:26 PM

As far as I know, only Voxeo, Gizmo and Voxalot has already issued iNum numbers to its customers. Voipbuster doesn't have done it yet, despite it's listed has one of the supporters of the iNum initiative. However, in their rates pages they says that dialling an iNum number has no cost. But as emoci said, maybe they haven't yet activated the route for calling iNum numbers, so the call to an iNum can not be connected.

thegreatfixer 12-24-2008 01:17 AM

good info i use Gizmo & Voxalot and look forward to this

kwag 12-24-2008 03:22 AM

iNum access number
 
Last night, and this morning, the access number for iNum in Puerto Rico (787) 395-7140 was working perfectly.

Since this afternoon, all I get is "The number you are calling is temporarily unavailable"

This makes me wonder who controls the quality of service of these DID lines :confused:

I'm sure it's not iNum's fault, but probably whoever they selected to provide the DID service on location. :mad:

rybshik 12-24-2008 04:25 AM

I do not see how iNum is better or more useful than SipBroker

kwag 12-24-2008 06:29 AM

Quote:

Originally Posted by rybshik (Post 20602)
I do not see how iNum is better or more useful than SipBroker

I agree with you!

g00fy 12-24-2008 06:52 AM

Yesterday I could call the echo test, but since this morning I get the 'not exsisting'-tone when dialing any iNum number.

krbonne 12-24-2008 12:05 PM

(un-)usefullness of iNum
 
Hi Rybshik,

Quote:

Originally Posted by rybshik (Post 20602)
I do not see how iNum is better or more useful than SipBroker

Well, I also have my question marks about this service.

At first sight, iNum looks very interesting as they provide ITU-assigned e164 numbers which -in theory- should also be accessable from the PSTN-network. (iff you read the ITU-document "at cost of a 'national' call").

However, then I ask myself why they set up a seperate enum-root, and not use the "official" e164.arpa tree like everybody else.


My guess is that -very simple- voxbone want to get incoming calls on their netwerk and -in fact- compete with sipbroker.
So, I agree with you- it would indeed be a good idea if e164.org would also register these inum-addresses so that they can also be used from the sipbroker dialin-network.

BTW. Has anybody see this:
http://www.itu.int/dms_pub/itu-t/oth...F30001MSWE.doc

"The initial +883*5100 dialling plan will consist of +883*5100 followed by five digits, i.e. +883*510*0XX*XXX.".
So does this mean that the numbers as assigned by voxalot at not ITU-complient?


Cheerio! Kr. Bonne.


All times are GMT. The time now is 06:42 AM.

Powered by vBulletin® Version 3.7.2
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.