Speed Dials not synchronized (OBI200) - no call route available

[Thomas1]

Just got my OBi200 connected with GV - aside from the rather time consuming 'Add Device' workflow (I lost count how many times I had to enter the **5 numbers , device is added and connected to GV. I will share details in a separate topic for others to benefit.

My current issue is with the speed dials. I have read a lot of topics on the topic and believe I'm adding it correctly.

I add a 3rd Speed Dial (ID#=3, Number=12223334444) using the ObiTalk -> Speed Dials page. Page seems to Save correctly. I'm assuming (since admin password is entered correctly on device information page), ObiTalk would push config to device.

Dialing the entire number (i.e. 122233344444) works - call is routed properly. However, dialing via Speed Dial - "3#" - yields a "there is no call route available".

Checking the local config on Obi device's webserver (i.e. http://<local ip>) - I only see 2 speed dials (default ones) and not the 3rd one I added from ObiTalk.

What am I missing? Any/all help is appreciated.

[SteveInWA]

I did some experimenting, and at least on the two devices I tried (a 202 and a VVX450), it seems that the portal isn't reliably communicating with the devices tonight.  I can't pull up the device status page on the portal, but I can display some, but not all, other pages.  I entered a speed dial number on the portal, and it won't push to the devices.  I entered the speed dial on the device's local interface and rebooted it. Of course, the portal then overwrote the speed dial with nothing.

I also tried changing the device's admin password from the portal, and that doesn't work either.

So, it is completely FUBAR.  I suggest you open a ticket with Poly on Monday.

[drgeoff]

A workaround is to disable Obitalk Provisioning and make configuration changes by logging in to the OBi's onboard web server. Except for configuring GV, everything you can do via the portal can also be done locally. An existing GV configuration is not disturbed by disabling Obitalk Provisioning.

[Thomas1]

Thanks for the suggestions Steve/drgeoff. I went ahead and opened a support ticket.

In the mean time, I went into the device and tried to add a Speed Dial (User Settings -> Speed Dials) manually:

• 1. Unchecked 'Default' checkbox (Parameter name = 3)
• 2. Added the number (12223334444) to line #3
• 3. Hit Submit (message indicating a reboot is needed)
• 4. Clicked Reboot button (top right)

When device rebooted, the new SD was gone. Assuming this was because auto provisioning was enabled so I disabled it by going to (System Management -> Auto Provisioning -> OBiTalk Provisioning):

• 1. Unchecked 'Default' checkbox next to Parameter name = "Method"
• 2. Change from 'Periodically' to 'Disabled'
• 3. Hit Submit (message indicating a reboot is needed)
• 4. Clicked Reboot button (top right)

Speed dial worked upon reboot! Happy now!

Would prefer to use ObiTalk, but does not seem too reliable. Is the portal not sync'ing a common occurrence? If I have to log into device each time just to verify it sync'ed, may as well just disable auto-provisioning. Thoughts, use auto-provisioning or not? I'm guessing for basic config (i.e. SDs), it should be ok; for anything more advanced, I guess to disable.

[drgeoff]

I have an OBi within arm's reach that I configure locally.  I have another OBi so far away that its time zone is 9 hours ahead and I configure it using Expert mode on the portal.

[alivoiper]

I tried this for my SP line keys but it didn't work. Can't figure out why... they still are displaying the wrong thing, even though I turned off Auto provisioning

[Byrd154]

Just got my OBi200 connected with GV - aside from the rather time consuming 'Add Device' workflow (I lost count how many times I had to enter the **5 numbers , device is added and connected to GV. I will share details in a separate topic for others to benefit.

My current issue is with the speed dials. I have read a lot of topics on the topic and believe I'm adding it correctly.

I add a 3rd Speed Dial (ID#=3, Number=12223334444) using the ObiTalk -> Speed Dials page. Page seems to Save correctly. I'm assuming (since admin password is entered correctly on device information page), ObiTalk would push config to device.

Dialing the entire number (i.e. 122233344444) works - call is routed properly. However, dialing via Speed Dial - "3#" - yields a "there is no call route available".

Checking the local config on Obi device's webserver (i.e. http://<local ip>) - I only see 2 speed dials (default ones) and not the 3rd one I added from ObiTalk.

What am I missing? Any/all help is appreciated.

Discover the best accessories for your TomTom product in the car, motorcycle, camper, Chargers and Cables. See all 17. sat nav high speed dual charger.

mysainsburys

[drgeoff]

^^ Goodness know why the SPAMMER thought a portal for employees and agents of a UK supermarket chain would be of the slightest interest to anyone on this forum.

[Lavarock7]

The spammers do this because the forum is in Google searches. It is a free way to get their URL and name out there. It used to be that the more websites that list a link to their site, the higher they are in Google.