Vitelity Provider Setup

[joshabts]

Hello all,

I am new to 3CX (been using Asterisk forever) and am looking to setup a test server to play with. I am having trouble however getting inbound calls working using Vitelity as a VoIP provider.

I have set everything up and it is reporting as registered in Line Status, but when I try to make a call to the number of the line, it is failing with CHANUNAVAIL. I have contacted Vitelity and they are reporting that I am not actually registered to their servers at all.

I have a sneaking suspicion my ISP is blocking port 5060 traffic (seeing as they offer their own VoIP service) and I am wondering what settings I need to set in order to run inbound calls/register through a different port. My outbound and inbound register and proxy are set to vitelity's servers on port 5060 as that is what tehy are expecting but they said I should be able to receive calls on any port I choose.

Anyone able to get Vitelity working, or any provider working on another port? I tried changing my SIP port in the general settings and restarting but that didn't work.

Any help would be greatly appreciated!

 

[archie]

Wonderful!! Asterisk managed to break all basic rules of SIP protocol!!

Briefly: they have Asterisk as SIP server. In response to REGISTER it replies first 100 Trying which (sic!)
(1) HAS A CONTACT!
(2) this Contact doesn't match one you're trying to register (!!),
THAN it replies with 200 OK WITHOUT Contact!!!

We will never support such "interpretation" of standards. See RFC 3261, 10.3, Step 8 of processing registration request.

(Aside) Halea, where're your laughing engineers? I have good piece of artwork to laugh at for them.

 

[joshabts]

Ok, I am assuming that means Vitelity with this is essentially a no-go then.

For those of you have got Vitelity working, is there anything special you changed or tweaked, or which servers are you using to register?

Would appreciate the help! Thanks!

 

[timandjulz]

Correct Vitelity configuration

I started playing with 3cx over the weekend and battled the configuration for Vitelity. I was getting the same error: CHANUNAVAIL

Vitelity has a configuration to email you when an inbound call fails. The notification said CHANUNAVAIL and noted this is normally caused by the connection to the inbound server not working. (Usually because the PBX hasn't registered for inbound calls with Vitelity.)

I finally got it figured out... The specification for inbound/outbound server is opposite of what I thought would make sense. See attached image. 3cx doesn't register when configured for Vitelity the way you would think it should work. The key is that Outbound Proxy Hostname should be inbound2.vitelity.net

I hope this helps someone else.

Cheers,
Tim

 

[N_G]

Thanks for the tips, Tim

You'd not expect the name of an outbound proxy server to be called inbound.

We do recommend that users stick to the tested VoIP providers as we have prepared the templates such that all you have to do is fill in the details.

In any case glad that it is working for you now

 

[twscottiii]

This problem actually doesn't have anything to do with the addresses used for the SIP server or Outbound proxy. Vitelity will let you use the single sip address for both fields or you can use the seperate inbound and outbound addresses for more flexability. No matter which configuration you use you will need to go to the Advanced tab of the VOIP proivder configuration and modify the registration settings. Change the "Require registration for:" field to "In and Outgoing Calls".

This setting will cause the phone system to send your registration information to Vitelity for both incoming and outgoing calls. This is required per the instructions on Vitelity's support site.

As for the names of the Vitelity addresses...they make sense if you think of them from Vitelity's perspective

 

[Brett Coleman]

Would you believe this post helped me fix my inbound problem in 2017?