Re: Age Of The Ring Delay Fix

2 views
Skip to first unread message
Message has been deleted

Macabeo Eastman

unread,
Jul 12, 2024, 8:38:44 AM7/12/24
to ininzeoclus

When someone calls into that ring group, all extensions will begin ringing right away as expected, but once someone answers the call, the other extensions will continue ringing for a couple of seconds each. While the other extensions are still ringing, there is not audio transmitting to the person who answered. Once all the extensions in the ring group stopped ringing the audio begins working.

age of the ring delay fix


Descargar archivo https://lpoms.com/2yOCV6



Hello, all. I had the same issue after an update with 5 users in a ring group. Worked good with one user in the group and with 3 users the connection was delayed about 5 seconds. When all 5 users were in the group it was aroiund 15 seconds.

I speculate that this is due to the AGI file that runs when the ringing channel terminates, so several ringing channels in a ring group all run the AGI file simultaneously when the call is answered. There may be efficiencies to be made in the AGI, but may have to add a random delay on the channel before the AGI to prevent them all launching at once.

I recently upgraded from FreePBX 15 to 16 and ran a slew of updates at the same time. This symptom presented after all of those updates were complete. I disabled the Missed Call Notification module and it immediately resolved the problem.

We just moved over to Teams and have an issue where there is a delay in the desk phone ringing. For example, when we transfer a call, it rings three times for the person on hold but only once on the phone. The same thing is going for the initial call as well, the caller waits much longer on the phone than the time we hear the phone ringing in the office.

How do your calls get to Teams? Is it a Microsoft Calling Plan, Direct Routing, some other call forwarding etc. When you say 'ringing in the office' do you mean on a pc, mac, mobile, Teams phone etc. ?

@Steven Collier It is a Microsoft calling plan, Teams phone. Ex: Call comes in from outside, call is transferred from one user to another, the transferrer hears 2-3 rings before the person who is receiving the transfer rings once.

@xppDev Have you found any solution for this? We've noticed that it does take a couple rings before it starts ringing to anyone in our call queues. Sure it doesn't seem like a lot, but if it takes a couple more rings before someone answers, certain callers might be impatient. We are going straight through Microsoft for everything, so no direct routing/SBC.

Recently replaced my Ring doorbell with the new nest doorbell battery, as I'm running a "google household" so it made sense to do so. Currently massively regretting my decision and hoping someone could help.

Since installation there has been a consistent 7-8 second delay between the doorbell being pressed and my smart speakers/screens chiming/ringing to alert me it's been pressed. I get a phone notification at exactly the same time that the speakers chime.

I'm not bothered about slow phone notifications, but a slow chime is proving a total nuisance. I've missed every single parcel delivery since I've fitted it as the delivery people have left long before I've managed to get to the door. 7-8 seconds doesn't sound long, but if you sit and count it like you're waiting at a door it's more than long enough for someone to give up and walk away before I even know they're there.

I have had the same complaint. I purchased the new nest Doorbell (battery) to replace my olderI Nest HELLO doorbell and noticed the long delay as well. For me I would say it was more like 4 seconds. Because of that and a number of other issues I had with the new doorbell I returned it and went back to my Nest HELLO doorbell.

I apologize for my late response and thank you for all of your patience while waiting for a reply. I can definitely understand how frustrating your situation must be, but I wanted to make sure that your issue was addressed. Do you still need help with this issue? I know that there's been a delay in response since you posted.

I decided to buy into the Google Home network. I just bought 2 Google Battery Nest doorbells and i can't get them to alert my phone that someone is there. Any ideas? This is subpar to the Ring system. I feel like I have downgraded. Any help would be much appreciated. Thanks

This is still a problem. Today I have answered the door twice, the delivery guys knocked and rang the doorbell at the same time. I was able to answer the door, collect my package and the guy leave before my google nest speakers chimed!!! This is beyond a joke for a piece of equipment this expensive! It can't do it's primary job, it is by definition "unfit for purpose", surely there is a fix for this??

I am sorry that there is no update on this issue at this time. It is still being looked into, I just cannot provide you with a solution just quite yet. We as Community Specialists are primarily here to moderate these Community Forums. Part of that role requires us to close and lock threads if there is limited, to no activity. The previous threads were locked within proper procedure.

It is not required for the issue to be resolved for the thread to be locked and closed. I understand that this process may be frustrating, but Community Specialists are still required via our title, to manage our communities this way.

Hey there,
Just wanted to hop in here to see if we still needed help on this. Please let us know if you have any other questions or concerns as I will be locking this in 24 hours.

Have a great day.
Garrett DS

Yes it stays open. This is a widely known issue with Google Nest Doorbell. The software programmers need to start earning their money. The first electronic doorbell was Ring and it still runs circles around this Google Doorbell. We are bought in on Google with Gmail, Drive, Google Mesh, Google nest thermostat, 2 Google Hubs and 2 Google doorbells. So, you would think that Google runs the world but Ring still beats the Google Doorbell. Please keep this open in hopes that Google will see and respond.

I contacted Google 4 weeks ago to report a dead doorbell. The Google doorbell was on my Google wifi mesh for about 30 days then will not connect now. I contacted Google again about a week ago to followup on where my replacement was. The tech support could not find my return after being on hold for about 25 minutes. Google's service is just plain pitiful.

Unfortunately, no. This as well as the delay in app notifications seem to be a common problem that quite a few people have complained about. All the threads that I have come across regarding these issues have been closed for inactivity by community specialists without any proper solution.

Does anyone else with this issue have the same WiFi SSID on 2.4 and 5Ghz? I do, and also have four access points (all on different frequencies). I wonder if it's a WiFi wake-up delay due to the doorbell being brain dead on how it selects a network to connect to?

I'm working fine with the same SSID. I'm on a mesh router and all is working great with my Nest cams (First generation). You might try opening a support ticket and getting an actual google tech involved and see were it goes. Here is the link:

I HAVE EXACT SAME ISSUE - 10-20 second delay, rings when I have answered the door and said goodbye to delivery driver. Can you explain how you can sell a doorbell that does not function as a doorbell???

Same problem here. Even camera notifications are several seconds late. I have tried every solution i have found on the internet, but it is still slower than my father's cheap Chinese model. Come on Google!!

I wanted to utilise my nest speakers as chimes and get the video feed on my displays. All of which is pretty useless with such a long delay!
I've WiFi 6 network with the router practically next to the doorbell.
No chance will I be paying for nest aware subscription to get the expected functions of a video doorbell with a delay like this.


Thank you for bringing up the concern you're experiencing, I would love to look into this further for you. The first troubleshooting step that I'd recommend would be to restart your device. This process should keep all your settings, and reconnect it to the same Wi-Fi network. This is helpful if it ever freezes, has connection problems, or isn't working normally.

Thank you for trying the suggested troubleshooting steps. If you're still experiencing this, please fill out this form, and a higher tier of support will reach out to you with next steps. Thank you for your patience.

Just checking in to see if everyone has filled out the support form. If you have, thank you! And please continue your troubleshooting over email with support. Please let us know if you have any further questions or concerns. We'll leave this thread open for a little longer for follow-up questions and concerns.

I have the same issue here. Google Nest Mini in combination with the Nest Doorbell (battery). It takes about 5-10 seconds before the chime on the Google Nest Mini sounds. This is way too long. It should be 1-2 seconds maximum. I tried turning it off and on (both doorbell and Nest Mini), but that doesn't solve the issue.

I just got the keypad in and have been working on getting it setup properly with HSM. I have what i think is to strange thing that i would like clarification on or just validation if i am correct in this setup.

It looks like the driver for the Ring Keypad has options for both Arming Delay's and Entry/Exit delay. What are each of those values suppose to do in relation to HSM. HSM only has the delay value for arming and intrusion, and from what I can tell doesn't have anything explicitly for Entry/Exit delays or atleast labled that way.

What I have setup is a delay of 30 seconds. When i trigger the arming from the Ring keypad it seems to use the 30 seconds twice. Once for Arming Delay and then again for a exit delay. Key though is the second exit delay occurs after HSM is ARMED. They keypad refers to both as a exit delay. Simply put i am confused as to why the keypad is doing this.

Another strange thing that is occurring is i am getting a error in logging. It is below. The keypad still appears to work mostly as i can arm and disarm. Just something seems a little off with this since it seems to be going through the exit delay twice.

d3342ee215
Reply all
Reply to author
Forward
0 new messages