Dialing **8 to call on POTS line yields invalid message
MichiganTelephone:
To test that theory, you could try going to System Management, Auto Provisioning and change the Auto Provisioning method to disabled, submit the change, then go back to DigitMap and try enabling the default settings and see if you get the **8 code rule. I'm starting to suspect they are working on the OBiTALK portal and something got messed up. I was told that the plan was to upgrade the portal so that you could configure ALL OBi device settings using an Advanced tab on the portal, and it wouldn't surprise me if in preparing to implement that, something got messed up. Disabling Auto Provisioning for a day or two might be the workaround. Don't do that, see OBi-Guru's message below (any time my advice conflicts with his, follow his advice, not mine!) ;)
OBi-Guru:
While working to push out 1-stage dialing capability yesterday, there was an error on the DigitMap for the Phone and AA, causing **8 and option #1 not to work.
We are putting on a fix at this time, and are pushing out a new DigitMap profile. Please wait a few moment and don't remove your autoprovisioning.
AndyA:
Mich's suggestion worked but seeing Obi-Gurus instruction I quickly returned Provisioning. So do we wait and get confirmation that the fix is pushed?
AndyA:
By the way does pushing a fix work even if we're signed on to OBiTalk and the web port or do we have to be completely signed off?
OBi-Guru:
The fixed profile is being pushed out now and devices under auto-provisioning will resync to the fixed profile within 1 hour time period.
Sorry for the trouble.
Signing on/off OBiTALK portal does not affect the profile push.
Navigation
[0] Message Index
[#] Next page
[*] Previous page