Vestalink: ~8 second delay before ring back heard
NickC:
I'm in the trial period for Vestalink. Call quality is as good or better than GV but I observe a longer than expected delay before the calling phone starts ringing.
When I place a call there will be a long period of silence before ring back tone is heard on the calling phone. Approximately 7-9 seconds before ringing is heard.
When calling from GV there's only a second delay before ring back is heard.
When comparing the overall latency of a GV call or Vestalink call and the called phone ringing, GV appears to be ~4-5 seconds faster.
Vestalink support mentioned that GV plays "fake" ring back tones before the call is actually initiated while Vestalink only plays the ring back tone when actually ringing out.
The long silence when placing a call makes it unclear if the phone is actually going to call or not. So far it always connects but I'm also concerned if needed in an emergency case.
Is this long delay of silence expected for non-GV providers?
I tried changing the DigitMap but that didn't have any impact.
NickC:
I tried callcentric and aveno - both operate more like GV where a ringback tone is played nearly immediately after entering the phone number to call.
I retested with Vestalink and confirmed that you don't hear a ringback tone for ~8 seconds.
However, the overall call latency from entering the phone number to the called phone ringing is the same for all providers. In my testing, it was ~12 seconds for the called phone to ring.
It would be nice if Vestalink started playing the ringback tone ASAP to make it obvious that the phone is working. This helps with the WAF and makes it more consistent with behavior observed with regular land lines (no long periods of silence).
Since the overall call latency is the same, I went with Vestalink.
intelafone:
The reason we don't send the ring back immediately is because that is incorrect, the ring back should only be heard when the other phone is actually ringing. When we started in 2010 we did the immediate ring similar to GV and Anveo. It becomes annoying for some users because the ring will change sound as it progresses to the other phone. I recommend you add this to our feedback forum, because we could implement an option that allows users to decide how they want this to work in their account settings.
CLTGreg:
Quote from: intelafone on April 06, 2014, 10:54:44 am
The reason we don't send the ring back immediately is because that is incorrect, the ring back should only be heard when the other phone is actually ringing. When we started in 2010 we did the immediate ring similar to GV and Anveo. It becomes annoying for some users because the ring will change sound as it progresses to the other phone. I recommend you add this to our feedback forum, because we could implement an option that allows users to decide how they want this to work in their account settings.
I appreciate you explaining this. I recommend you do the option if only to introduce the function in to our heads. I didn't notice this until I had some 404 errors so I thought things were getting worse. I would have had a better opinion if I would have known this. I think must people are going to think something is wrong or "just slow" because of the price or what not.
Doc_Glenn:
I find the dead time really distressing. Well, what about two signals? First is some tone to signify that the system is "working" (oh, the original Star Trek computer!). Then the ring back when it is real.
Navigation
[0] Message Index
[#] Next page