News:

The OBiTALK service has reached it's End of Life period and will be decommissioned as of October 31st, 2024. More information can be found at this link https://support.hp.com/us-en/document/ish_10969583-11049883-16

Main Menu

Long delays to intercom another obi2182, sometimes to dial. How to speed up?

Started by jccpa, May 11, 2021, 05:47:33 PM

Previous topic - Next topic

jccpa

Sometimes it takes up to 30 secs to PresenceMonitor to Linked number (ie Ext 40), between "Trying" and "Peer Ringing"

Other times it is about immediate.

Why? Is it hitting the obitalk. com server first? Is there a way to "cache" the obitalk 'routes' locally?

How can we speed this up?

I am using Obi2182 to 2182 on the same subnet. I *could* probably switch to IPAddresses, but that could be very complicated and UN-feature-rich.

Thanks.

jccpa

Okay, so I manually switched DNS1 and DNS2 on the phone from google (8.8.8.8) to Comcast and connections are just about instant.

Brings me to some questions:

1. Are the Obi devices hitting Obitalk cloud servers EVERY time?

2. What happens if the internet is down, do the phones stop ability to intercom?

3. If I want to be able to intercom internally during internet outages, would setting up a LAN DNS server be enough?

4. Any way to cache the Obi data locally?

EDIT: The "instant" part was short lived. Now about 5 seconds, which is still much faster, but the questions remain.