Vitelity IAX Setup

[parker]

Title says it all -- their response to a simple query about being unable to register with IAX:

We are sorry but we do not recommend the use of IAX nor provide technical assistance/support for its use. If you wish to continue using it, you must be able to configure your system properly on your own.

Perhaps someone on this forum can help? Outbound works fine, either IAX or SIP. Inbound SIP works fine (both registration and calls). Inbound IAX doesn't register ("Request Sent" status) with inbound22.vitelity.net (the inbound server vitelity assigned). Out of curiosity, I tried IAX registration with inbound2 (and inbound1), and registration completed (instantly), although there is stil no inbound IAX (calls from the real world to the (toll-free) DID go to BUSY, with a failed-call e-mail). (At the moment, registration is in session for both SIP/inbound22 and IAX/inbound2, with the settings on the DID routed via IAX ("not recommended").)
Static IP here, and we fully control our border routers; other than the registration (to a "non-assigned"(?) inbound server), there are no packets at all (save for a steady stream of ICMPs) incoming from *.vitelity.net for incoming calls. If anyone can hand me a clue, or pass me a method to get vitelity on the case, or lart me for mistakes I've made that I don't see, I'd be grateful.

P.S. the reason I'd like to stick with vitelity is that they've got the cheapest toll-free monthly charge (these numbers are fairly low-usage, so any reasonable per-minute/PAYG rate structure is fine). Otherwise, I'd stick with teliax... As for IAX preference over SIP, it seems to me that IAX is vastly superior for server-to-server (ITSP and PiaF).

 

[jehowe]

I have inbound over IAX working with Vitelity. Since you've got it working over SIP, it would seem Vitelity has assigned the DID to your account and that you have the inbound route setup properly on your end. This is what I recommend that you try.

First disable the inbound SIP trunk so it won't interfere. Then go to the inbound IAX trunk and check or place these settings under the Peer Details (this is what I have):

username=yourusername
type=friend
secret=yoursecret
host=inbound22.vitelity.net <- the server they assigned to you
disallow=all
context=from-trunk
allow=ulaw

Last, make sure you have "Route to my Asterisk PBX server via IAX" and "Assign DID's to the account: youruseraccount" set under account settings on Vitelity's management page.

If this doesn't work, I'm stumped, but would think that it would point to an issue on their end.

 

[parker]

Thanks for the suggestions. I was already confident that it's an issue on their end as there are NO IAX PACKETS arriving, so the IAX registration never completes ("Request Sent" status). I nevertheless tried your suggestion (to the letter), and the symptoms and observations were exactly as before; the IAX2 registration never gets an acknowledgement from inbound22. They did have one final suggestion, of substituting the IP address of inbound22 for the name. Again, as everything points to a problem on their end (specifically, inbound22), this suggestion was also of no use. Really, the failed-call e-mail says:

A call to your DID has failed. We received 'CHANUNAVAIL' when attempting to route the call to your server or device. This error usually means your server or device is not currently registered to our servers. Please make sure you are registered to the correct inbound server for your account as per the configuration samples found on the support page within the user portal and that you have selected the correct routing method for your DID(s) on the DIDs page.

Of course, that's what I'm trying to get solved, which is the Registration! The problem is likely as simple as inbound22 not accepting registration, and they should look into just that, as per their own e-mail. Per-call is NOT the problem here; I'm not even getting to first base. I'll try one last time with the support ticket, but if I don't at least get acknowledgement of the Registration problem, then I'd have no hesitation in warning all readers to stay away from vitelity if you expect them to do anything with IAX except know how to spell it...

 

[parker]

I have looked into the steady stream of ICMP's that we've been receiving, which reinforces the theory that there's a problem with inbound22 (or, at least refusal to IAX register, which vitelity doesn't acknowledge is a problem). Packet trace shows they all look like:

19:16:57.869126 IP 64.2.142.15.GIGe-net.vitel.net > my.server: ICMP 64.2.142.15.GIGe-net.vitel.net udp port iax unreachable, length 66

In the absence of some other explanation, that's clearly the cause of inbound22 ignoring my registration request -- it's unreachable (the port is firewalled or IAX is not "turned on" on inbound22). I really really hope that someone from vitelity reads this...

 

[parker]

Final (I think) update. After sending them the packet trace showing the IAX port on inbound22 was shut off on their end, they "reprovisioned" my account to inbound2. Three seconds to change on my end, and registration completed. Inbound calls work fine, too. I guess whatever was broken on their network and/or on inbound22 was not easy or desirable to fix...

 

[dghundt]

I was assigned inbound18 and using their default configuration example, could not get my inbound regsitered. (outbound trunks work fine). Guess I'll ask them to put me on inbound2.

Silly newbie question, but I am not opening any ports on my router as I am registering with them. This is correct?

 

[dghundt]

Recently my vitelity settings are not working. If I leave the registration out, can't make calls (this is new). If I put registration in, I can make calls, but the IAX2 channels remain active and start to stack up until I have problems.

Does anyone have a current Vitelity IAX configuration for pbxiaf?

 

[tomsyr]

I have 2 trunks set up for my one account- one for inbound, and one for outbound. In the Inbound settings, I have the registration entry. This is not needed in the outbound settings:

vitel-inbound

type=friend
username=myusername
secret=mypassword
context=from-trunk
host=inbound18.vitelity.net
disallow=all
allow=ulaw

Registration
myusername:[email protected]

vitel-outbound

type=friend
username=myusername
secret=mypassword
context=from-trunk
host=inbound18.vitelity.net
disallow=all
allow=ulaw

 

[dghundt]

Thanks it worked! I did change the host to the outbound server assigned to me in the support tab since I have no inbound DIDs. Don't know why my old settings stopped working.