Issues with Obi-to-Obi dialing (**9+9-digit-Obi#)
Stewart:
Confirm that both ITSP Provisioning->Method and OBiTalk Provisioning->Method are set to Disabled. Save settings. Reboot the device, re-enter the OutboundCallRoute, save and reboot again.
RonR:
Quote from: robbie on October 23, 2011, 12:52:45 am
---
{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}
---
It appears there's a nasty bug in OBiTALK Web Portal and/or the OBi firmware that's generating a corrupted OutboundCallRoute. Another user is experencing the same problem:
http://www.obitalk.com/forum/index.php?topic=1747.msg11355#msg11355
If you disable Auto Provisioning and check the OutboundCallRoute Default box in the OBi, your problem will go away.
infin8loop:
Since this thread mentions Auto Provisioning more than once, I'm going to post this observation/question here.
Up until yesterday my OBi110 was configured locally with the following two settings:
System Management --> Auto Provisioning --> ITSP Provisioning --> Method : System Start (Default check box checked) (I don't recall ever specifically changing this setting)
System Management --> Auto Provisioning --> OBiTalk Provisioning --> Method : Disabled (Default check box not checked but Disabled appears to be the default when the check box is checked). I believe but am not certain this was Enabled before I manually Disabled it locally and did not check the unchecked Default check box because I was concerned that a subsequent release might not default to Disabled.
Perhaps the answer is in the Admin Guide and I'm just not seeing or understanding it. The bottom line is my local settings (done thorough the local IP address) were NOT being overlayed. Example: The OBiTalk portal isn't aware that I have voip.ms on SP2 since I added it locally AFTER I Disabled OBiTalk Provisioning mentioned above months ago. Yesterday I disabled the ITSP Provisioning as well just to be safe because I keep seeing mention of it as well. The OBi110 is registered on OBiTalk but I never used the OBiTalk Expert Configuration it provides. I did however initially configure Google Voice on SP1 using the OBiTalk portal basic configuration wizard before I Disabled the OBiTalk Provisioning. Again, until yesterday I had only OBiTalk Provisioning Disabled and local settings were not being overlayed (at least any settings that I've looked at). I've been "safe" for months or at least thought I was. Are these two settings controlling different things? Is it plausible the ITSP Provisioning applies settings from the OBiTalk Expert Configuration (refers to a tftp://$DHCPOPT66/$DM.xml) but since I never used it I was ok? Every time I think I have a handle on this OBi, the handle falls off for some reason (grin). Does the OBi have undocumented TFTP access? I know I'm over thinking all this, but I like to fully understand the technology.
RonR:
infin8loop,
OBi provisioning is another area that is virtually undocumented. Prior to firmware v1.3, there was only one flavor of provisioning, but now there's two (ITSP and OBiTALK). The OBiTALK Web Portal obviously uses the ITSP flavor and can be disabled.
As we've previously discussed, from my own experience, there's no way to stop the Obihai folks from peering into and/or making changes to the internals of your OBi if they have a mind to. Not registering an OBi, setting secret passwords, etc. does not make the OBi secure.
infin8loop:
Quote from: RonR on October 23, 2011, 01:58:11 pm
The OBiTALK Web Portal obviously uses the ITSP flavor and can be disabled.
RonR,
Thanks for the reply. As of yesterday, I have BOTH flavors Disabled. And, yes, I fully understand neither setting disables their ability to access the OBi if they want to. Let's just hope they don't want to.
Navigation
[0] Message Index
[#] Next page
[*] Previous page