When Calling Out, a few seconds delay

Posts: 4777 · Vonage Forum **MVM** Joined: Aug 30, 2005 Posts: 4777

[quote="blutarsky"]

Sim-X wrote:

almost seems like instead of the Vonage adapter (rtp300 in this case) dynamically generating the ring tone you hear on outgoing calls, it's playing a pre-recorded sound of ringing, which is why it can't cut it in half to play partial ring.

I'm not sure what you mean here, since it would be as easy to cut off a recording as it would be to cut off a dynamically generated signal. If you mean that there's no real connection between the ring tone that you hear and the ringing at the receiving end, I think that's absolutely correct (and normal). What seems to be happening here is that some signal that tells the RTP that the connection has been made is not being received immediately or is not being acted on immediately. Why it's happening to you and a few others and not to everyone is part of the mystery.

At least you're finally getting responses from others with the problem. If enough of them will complain, maybe Vonage will put the resources on it to get the problem fixed.

Posts: 11 · Vonage Forum Associate Joined: Sep 10, 2005 Posts: 11

so far it seems that people who have tried the test with the automated line all have the RTP300. Anyone else want to try it with another kind of adapter? You think they would have tested this stuff out before setting people up like this. Everything else seems to work pretty good. By *70 doesn't work by the way, and if I press in keys to fast, it won't pick them up. Like when calling the sprint voicemail number that was posted

612-207-6245 it will ask you for your vm number. I type it in, but if I press the buttons to quick it doesn't pick it up correctly and I have to re-enter it. Where with a landline with the same phone, no problems

Posts: 282 · Posted: Sun Sep 11, 2005 4:01 pm Post subject: Same Issue With PAP2

I posted a few replys ago, but just wanted to clarify that I'm seeing the same issue you describe using the PAP2 - so it doesn't seem to be hardware dependent.

Also, when I call the Sprint voicemail number, I get the cut off message as I noted ealier, but I've since done a number of test calls to other numbers (my cell phone, my work voicemail, etc) and there is no delay. I'm also able to get a "half-ring" when calling to my cell phone and waiting for the ring to just start before answering. It stops rining instantly and connects. I have no idea why it works perfectly for some numbers and not others, but it is certainly a problem that is easy to demonstrate.

Posts: 7 · New Forum Member Joined: Sep 11, 2005 Posts: 7

I get a full ring, then hear "to the Sprint..." Just sent the RT312P2 back the other day to our I woudl test it. Would be interesting to see if it is only related to the RTP300.

Posts: 12 · Vonage Forum Associate Joined: Sep 07, 2005 Posts: 12

I've had Vonage less than a week and am testing. I also get a full ring, then hear "to the Sprint..." From my landline, or mobile, I get the entire greeting complete with "Welcome..."

During the Sprint call I punched in a random number as quickly as I could, and it repeated the digits back stating it was an invalid number. I have also tested other touchtone enabled services with other places I do business with, and have not experienced any problems at all with tone being recognized.

I do, however, experience a slight latency with some, not all, Vonage-to-landline calls, and even a slightly longer delay with Vonage-to-mobile calls. The delay seems most noticeable on the Vonage end (had one case today where I heard "Lo..." instead of "Hello.")

My theory is some degree of latency is expected (this is the Internet after all, and codecs are involved.) Most of the time, there is enough natural pause between the time a phone is picked up until the person speaks into the phone, for the other person to hear the entire greeting, but some of the time there is not enough pause, such as with some automated systems that get every second they can out of their call time by reducing such natural pauses to a bare minimum. Believe it or not, those fractions of a second really add up when thousands of calls are made daily. For a good ex. of this, try our own Vonage voicemail menus! Speedy Gonzales...

Some receiving equipment (e.g. POTS) handle this issue quite well, while others (e.g. Voip) do not. In most casual speech between real people over Vonage, I have found there to be more than enough natural pause that the latency is either completely transparent, or at worst, a minor nuisance that is easily adapted to.

Posts: 9 · New Forum Member Joined: Sep 10, 2005 Posts: 9

Hey guys I did try this and I get the same thing, however try this automated messaging system. Its a furniture protection company, Guardsman. 1-877-584-GOLD. I do not get a ring with this one. Interesting.

Posts: 12 · Vonage Forum Associate Joined: Sep 07, 2005 Posts: 12

rdff41 wrote:

Hey guys I did try this and I get the same thing, however try this automated messaging system. Its a furniture protection company, Guardsman. 1-877-584-GOLD. I do not get a ring with this one. Interesting.

Same result, from all three of my phones (Vonage, landline, cellular) so this is not a Vonage only symptom.

"Automated attendant" feature of most PBX's, like apparently this one, allow for configuration of when to "answer" and it's not unusual for the admin to set it at the minimum setting, which may be "0 rings" or "immediately" or some such. Especially if its coming into the switch over a digital trunk, which if the company is any size at all it most probably will be (T1 or PRI or the like) then the end result is the user at the other end may not even hear any ringing at all. This is not that uncommon an occurrence. (BTW I used to admin a few PBX's and had to set these features up.)

Posts: 7 · New Forum Member Joined: Sep 11, 2005 Posts: 7

Darrell wrote:

"Automated attendant" feature of most PBX's, like apparently this one, allow for configuration of when to "answer" and it's not unusual for the admin to set it at the minimum setting, which may be "0 rings" or "immediately" or some such. Especially if its coming into the switch over a digital trunk, which if the company is any size at all it most probably will be (T1 or PRI or the like) then the end result is the user at the other end may not even hear any ringing at all. This is not that uncommon an occurrence. (BTW I used to admin a few PBX's and had to set these features up.)

Did you try to call the Sprint number from your Vonage account? Most people with the rtp300 seem to get a full ring, when cell phones, home lines receive no ring at all. The problem isn't that certain numbers may pick up properly with no rings, the problem is that the router seems to have a bad habit of completing rings and cutting off people. ie. hearing a ring then "to Sprint..." instead of no ring and "Welcome to Sprint..."

As a result if you have an over eager friend on the other side you may not hear their first Hello.

Posts: 75 · Vonage Forum Senior Joined: Sep 06, 2005 Posts: 75

Fugacity wrote:

... The problem isn't that certain numbers may pick up properly with no rings, the problem is that the router seems to have a bad habit of completing rings and cutting off people...

that is *precisely* the problem -- glad you summed it up so clearly. and it seems like there shouldn't be any reason (or excuse) for it to happen like that.

please Vonage -- fix this!

Posts: 12 · Vonage Forum Associate Joined: Sep 07, 2005 Posts: 12

Fugacity wrote:

Did you try to call the Sprint number from your Vonage account?

Yes, as summarized in an earlier post in this thread.

Fugacity wrote:

Most people with the rtp300 seem to get a full ring, when cell phones, home lines receive no ring at all. The problem isn't that certain numbers may pick up properly with no rings, the problem is that the router seems to have a bad habit of completing rings and cutting off people. ie. hearing a ring then "to Sprint..." instead of no ring and "Welcome to Sprint..."

No argument there....in my last post I wasn't referring to the Sprint issue specifically but rather responding--in a general fashion--to someone who found something "interesting" about another company (Guardsman, IIRC) when he called their system. BTW the Sprint issue, according to some in this thread, is not limited to the RTP300.

Fugacity wrote:

As a result if you have an over eager friend on the other side you may not hear their first Hello.

It doesn't necessarily take an "over eager" friend.