[SOLVED] Can't Call OBiTALK Test Number

<< < (4/4)

Everton:
Quote from: RonR on October 23, 2011, 09:24:38 am

As can clearly be seen, there is a nasty bug in OBiTALK Web Protal and/or OBi firmware that's resulting in a highly corrupted OutboundCallRoute containing HTML escape sequences (</>) when Auto Provisioning is used to configure this setting. This leaves all **1/**2/**8/**9 prefixes unusable.

I use the OBiTALK Web Portal with the current and previous version of the OBi Firmware and never got those corrupted OutboundCallRoute data. Why is it happening to some users and not others? Could it be associated with an incompatible Browser (I use Chrome exclusively)?

RonR:
Quote from: Everton on October 23, 2011, 10:10:35 am

I use the OBiTALK Web Portal with the current and previous version of the OBi Firmware and never got those corrupted OutboundCallRoute data.

Is the OBiTALK Web Portal configuring your OutboundCallRoute? Try unchecking the OutboundCallRoute Default box in the OBiTALK Web Portal and see if you get a corrupted OutboundCallRoute in your OBi.

Everton:
It is unchecked for the "OutboundCallRoute Default box" As I said, I do not used the direct web portal, even though I have direct direct assess to the OBi110 remotely. I manage the Network and OBi110 for a friend and ALL changes/enhancements (including changes to "OutboundCallRoute") have been done via the OBiTALK Web Portal. Have you been able to reproduce this behavior recently?

Quote from: RonR on October 23, 2011, 10:17:58 am

Quote from: Everton on October 23, 2011, 10:10:35 am

I use the OBiTALK Web Portal with the current and previous version of the OBi Firmware and never got those corrupted OutboundCallRoute data.

Is the OBiTALK Web Portal configuring your OutboundCallRoute? Try unchecking the OutboundCallRoute Default box in the OBiTALK Web Portal and see if you get a corrupted OutboundCallRoute in your OBi.

RonR:
Quote from: Everton on October 23, 2011, 10:27:33 am

Have you been able to reproduce this behavior recently?

I never use the OBiTALK Web Portal, in order to avoid this sort of problem.

Neither of the two users experiencing this problem should have had an OutboundCallRoute that was other than Default. Both had an extra/unwanted/unrequested {911:sp1} rule forced onto the beginning of their OutboundCallRoute (overriding the normal 911 call processing). Checking the Default box in the OBi corrected the problem. It's pretty clear the OutboundCallRoute was incorrect as generated by the OBiTALK Web Portal. There's never been a case before where an OutboundCallRoute value that was copy/pasted from an OBi to a forum message resulted in < and > being shown with HTML escaping. Based on all this, it certainly appears something is awry.

RonR:
Quote from: Everton on October 23, 2011, 10:27:33 am

Have you been able to reproduce this behavior recently?

I pulled a new OBi from the shelf and used the OBiTALK Web Portal to configure it. The bug is reproducible:

Physical Interfaces -> PHONE Port -> OutboundCallRoute:

{911:sp1},{([1-9]x?*(Mpli)):pp},{(<#:>|911):li},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},
{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}

Navigation

[0] Message Index

[*] Previous page