Callcentric and GV, having trouble with **2 with GV.
RonR:
Is OBiTALK Provisioning also Disabled? It's normally ITSP Provisioning that's in control.
Other than that, it sounds like you're doing everything correctly but the OBiTALK Web Portal is forcing itself on you anyway.
RonR:
If all else fails, delete your device from the OBiTALK Web Portal. That will surely get it out of the picture.
JamesD:
That's what it was, ObiTalk. Once I set that to disabled it kept from reverting back. Just to be in the safe side I left ITSP and Auto Firmware Update to disabled. Now I can use **2 with no problem.
One concern tho, I have setup Callcentric with 911 via the obi web portal. How can I make sure that dialing 911 will be routed correctly? (without actually calling 911 of course) :)
This is how it is suppose to be setup:
Callcentric > SP1 > All outbound calls and 911
Google Voice > SP2 > as back up for other calls, not 911.
Thanks again Ron!
RonR:
Quote from: JamesD on October 23, 2011, 04:53:55 pm
That's what it was, ObiTalk. Once I set that to disabled it kept from reverting back.
It appears that in addition to the OutboundCallRoute configuration getting screwed up, Obihai has reversed the ITSP and OBiTALK Provisioning Methods. OBiTALK has always been disabled by default and ITSP was the one that controlled provisioning from the OBiTALK Web Portal up until the last day or so.
Quote from: JamesD on October 23, 2011, 04:53:55 pm
How can I make sure that dialing 911 will be routed correctly? (without actually calling 911 of course) :)
This is how it is suppose to be setup:
Callcentric > SP1 > All outbound calls and 911
Google Voice > SP2 > as back up for other calls, not 911.
Make the following change:
Physical Interfaces -> PHONE Port -> OutboundCallRoute:
{([1-9]x?*(Mpli)):pp},{(<#:>):li},{911:sp1},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},
{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}
It's probably a good idea to actually dial 911 and make sure the call goes through. Immediately inform the dispatcher that this is not an emergency and then verify your address and other information. There has been at least one incorrect 911 configuration reported at the Callcentric end recently.
JamesD:
Good thing I asked. What was on my obi device was totally different. I'm a noob at this but according to the old callroute that I pasted below does it mean that it was going to pipe 911 calls to li which is the line port aka landline?
{([1-9]x?*(Mpli)):pp},{(<#:>|911):li},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}
Also I figured out how to enable "New Message" indicator for Callcentric voicemail for those interested.
Assuming Callcentric is setup on SP1:
SP1 Service > Calling Features >
And under the following settings listed below, I unchecked the Default box, all three of them and then under Value check all three boxes.
MWIEnable
X_VMWIEnable
MessageWaiting
That's it, now it will notify when you have a new message waiting for you. This is my first day using the Obi110 so please correct me if anyone see's a mistake. Probably most of you already new this. :)
Thanks Ron! and everyone..
Navigation
[0] Message Index
[#] Next page
[*] Previous page