Vitelity keeps unregistering on me

[dghundt]

Vitelity iax trunk keeps unregistering on me. Other iax and sip trunks are fine. Any reload fixes this, for a while.
Anyone else with this issue?

trunk name vitel-outbound
conifg-

disallow=all
allow=gsm
type=friend
username=username
secret=secret
fromuser=secret
trustrpid=yes
sendrpid=yes
canreinvite=no
host=outbound.vitelity.net
qualify=yes

 

[jeffmac]

I don't think the Vitelity outbound trunks need to be registered. Mine isn't, but the inbound is. Did your example for Vitelity include a register string for the outbound trunk?
Jeff

 

[dghundt]

The registration string is blank, but if I use the qualify option, it will tell me if it is 'registered' or not. When iax2 peers says vitelity is registered, it works. If peers says vitelity is not registered, it does not work.

I changed back to sip trunk with vitelity, and it seemed to stay registered. I recall having the same problem a couple years ago. I should write this down somewhere.
Thanks.

 

[marv]

I monitor my trunks for failure and have noticed that Vitelity loses its registration with me a maybe twice a day. Not sure exactly why, but it generally has been reconnecting within 15-30 seconds. On a few occasions I noticed I lost connectivity for an hour or so in the wee hours of the morning.
I have tweaked my registration times to be more aggressive to help compensate.
If you find any solutions, do let us know!

 

[cjkeeme]

With Vitelity I would say I get between 1-10 failed inbound calls per week. This is not so bad considering we have near 2000 incoming calls in a week.

For whatever reason, Vitelity doesn't support the IAX service they offer. The claim IAX isn't stable as SIP, but in my experience I see the other way around.

 

[jades]

Vitelity is a piece of garbage. Don't waist your money on them. I've been through terrible experience with them, as well as many many others

 

[mruge]

I have been with Vitelity for over a year now and have had very few problems.

 

[jades]

"and have had very few problems"

You should not have ANY problems at all with a reliable Voice Over IP provider. I have been with Voice Pulse for 4+ years and my company makes over 30,000 minutes a month of calls and we NEVER had one problem.

 

[jehowe]

VoicePulse is definitely one of the best run voip businesses out there, which certainly shows in their product and costs. I use them for outbound and they've been exceptional. But I wouldn't say Vitelity is a piece of garbage. I use them for inbound and they've been great.

Frankly, unless it's T1 based PRI for voice, using unmanaged public IP networks is going to be a problem with *any* provider.

 

[Bart]

We run several thousand calls a day both toll free and local DID's using Viltelity - We rarely have a problem and we don't register. Routes are built only using outbound context but with correct host - Inbound and registration are empty

Bart

 

[dghundt]

We run several thousand calls a day both toll free and local DID's using Viltelity - We rarely have a problem and we don't register. Routes are built only using outbound context but with correct host - Inbound and registration are empty

Bart

sip or iax?
our vitelity sip trunk stays 'registered', but we prefer IAX.

 

[Bart]

Oh, we use SIP exclusively

Bart

 

[rolfbeethoven]

Would you mind posting what you do to monitor your trunks for failure and how you are tweaking your registration times? I lose registration to Vitelity and it doesn't reconnect on its own. I have to reboot the server sometimes to reregister. I would like to ensure that I'm trouble shooting the problem appropriately. I would appreciate some guidance and what to check or a link to another post that explains this.

Thanks.

 

[Bart]

My understanding is viltelity does not recommend using registration method (yeah, I know they show it on their support web site). When we first started using them we also had problems. The solution was not to register and use IP routing. They also highly recommend SIP.

I use what works

Bart

 

[dghundt]

I made sure to make qualify=no and now my iax2 outbound trunk continues to work.

 

[kieranmullen]

Are you geting any help with IAX from vitelity? They told me it was unsupported so they were not willing to work with me to get it going.

 

[dghundt]

It just works for me.

I have never had any great help with sip or iax in the past; they have always told me their end was working fine and they don't support asterisk.

 

[wa4zlw]

Hi Folks!

SInce I moved the pbx to our synagogue which is on Comcastic versus Service Electric here, I've noticed my Vitelity outbound trunk keeps going away. I've had QUALIFY=YES and that's what seems to be the problem. If I set it NO then it seems to work but I prefer to have QUALIFY=YES to see if there's any lag. I'm using SIP. INBOUND always stays registered as does the OUTBOUND trunk for TOLLFREEGATEWAY which works all the time.


Host Username Refresh State Reg.Time
inbound18.vitelity.net:5060 xxxx 45 Registered Tue, 18 Aug 2009 19:33:42
Sip Peers


Name/username Host Dyn Nat ACL Port Status
vitel-sip-out/clbc 64.2.142.214 N 5060 Unmonitored
TollFreeGateway 204.8.45.222 N 5060 OK (208 ms) Here's my trunk:

type=peer
username=xxxx
secret=yyyyyy
fromuser=xxxx
trustrpid=yes
sendrpid=yes
context=from-trunk ; (this could be ext-did or from-pstn as well)
canreinvite=no
host=outbound.vitelity.net
disallow=all
progressinband=yes
allow=ulaw
nat=yes
qualify=no ; this seems to be vitelity's problem =yes

Also, FWIW, the COmcastic modem/router is junk IMHO as it doesn't seem to do auto-NAT and you have to configure each one manually?

I'm eventually going to put a Mikrotik router there as I have here at home but that's extra $$$ right now.

Any thoughts this has got me stumped and I don't need calls all the time from the Rabbi

THanks leon

 

[jades]

Vitelity once mentioned to me that they have issues (and possibly special settings) with a certain ISP, and I THINK it was Comcast. Call them up and find out.

 

[kevinfvc]

I use Vitelity and switched to Comcast a couple of months ago with no issues. Plain, residential service from Comcast.