Long delay before ringing- Vestalink?

[fuzzyeddie]

I tried to switch over to that new VOIP service Vestalink. Calls sound great.

But for incoming calls, they will hear 5-10 rings before I even hear one. What happened?

Thank you

[gderf]

The caller is being played rings as soon as the call is dialed, well before the call is connected and the phone on the other end begins to ring.

The other way to do it is for the caller to hear silence until the phone on the far end begins to ring.

[fuzzyeddie]

Thank you for the reply. It is actually being connected through Google Voice though, so it rings for the caller until it goes to Google Voice voicemail. No actual rings on the physical phone will be heard.

[gderf]

Then either the call never gets to GV, or GV is not forwarding the call.

[fuzzyeddie]

Thank you- Both of those things happen. There is always record of the forwarded call on Vestalink' end.

[MikeHObi]

Thank you- Both of those things happen. There is always record of the forwarded call on Vestalink' end.

This is a problem that Google Voice has been having for 6 months or so now.  It was noticed first with Callcentric DID's since Callcentric Free NY DID's are a popular option for Obi users to get E911.  But I've experienced the issues on Anveo as well.

Google Voice uses companies to complete calls for them.  One or more of these companies has a problem when connecting to some DID's.  This results in calls taking too long to complete such that by the time your phone rings, google voice mail is already picking the call up and sometimes your phone doesn't even ring.  Other times the issue shows up as incorrect CID, typically showing PRIVATE or Anonymous.

The problem occurs randomly in some cases and repeatedly in others.  The problem seems to be related to the where the origin of the call comes from as well as the destination of the call.

To date, google has not officially recognized this as a problem and to my knowledge they are doing nothing to resolve this problem.  One of the many benefits of "free" services.

[fuzzyeddie]

Thank you- That is useful to know. It is probably adding to my problem.

However, when I call the Vestalink hosted number directly, without Google Voice involved at all, there is still a delay. Is there a setting in the Obi that could correct that?

[MikeHObi]

Thank you- That is useful to know. It is probably adding to my problem.

However, when I call the Vestalink hosted number directly, without Google Voice involved at all, there is still a delay. Is there a setting in the Obi that could correct that?

Is the delay the same or different?  The point is that with IP phones and Cell phones the ringing you hear when you dial a number is generated by either your phone or your phone provider.  It has nothing to do with the phone you are trying to contact ringing.  So if you hear 3 rings before your phone even rings once.  That means there is time between your call connecting to Vestalink, and Vestalink routing to your SIP device, and then your SIP device ringing.

Using my cell phone calling a DID directly I can usually get one or two rings before my phone actually rings.  When I have GV forwarding to Callcentric and it worked I usually got 2 or 3 rings before my home phone rings.

How many are you seeing when you call directly?  Should be 6 seconds per ring.  So if your handset rings 3 times before your phone rings that would be 18 seconds to complete the call.