Auto Attendant Stopped Answering Trusted Callers - Suspect Firmware Update

<< < (4/4)

drgeoff:
Quote from: Jeff47 on November 09, 2018, 04:59:14 am

Hi,

I tried changing "x." to "+", and rebooted Obi200, but AA still didn't work for me. I emailed the support; they told me to try "@" instead of "+", but that didn't work for me either. Is there any new information on how to solve this problem? Will there be a new firmware update coming that could solve this problem?

thanks,

Rather short on details.  What do you mean by "AA still didn't work"? What ITSP are you using?  Where are you trying those x., + and @ characters?  What is the format of the string you have there now?

Hoeveer:
I've attempted to perform this change of x. to + on my Obihai 200, and after reboot it seems that OBiTALK re-asserts itself and changes the string back to x. on reboot.

I discovered that I needed to read the instructions above a little closer, and figure out how to get to obiexpert instead of trying to make the changes directly on the Obihai 200 device.

It pays to read the directions a few times for comprehension!

drgeoff:
Quote from: Hoeveer on December 19, 2018, 10:53:16 am

I've attempted to perform this change of x. to + on my Obihai 200, and after reboot it seems that OBiTALK re-asserts itself and changes the string back to x. on reboot.

Seems that Polycom really doesn't want us using this functionality any more.


Without more info I'd guess that you are changing this via your OBi200's onboard web server management interface.  Unless you have disabled Obitalk provisioning, changes made that way will be almost immediately overwritten by the settings on the Obitalk portal.  Make the change using Expert mode on the portal.  At the end of the relevant line are two tick boxes.  You must clear both of those before you can edit the setting.

Navigation

[0] Message Index

[*] Previous page