There is too much good stuff on this site to find out if someone already posted similar, so here is my solution:
If you can't figure out what to do with your OBI 100:
If you have a functioning OBI 200:
If you want a remote phone or an extension:
If you know someone who has an OBI 100 can't afford to buy a 200 - like your parents: there is a solution.
OBITALK.............
DISCLAIMER: I AM NOT AN OBI EXPERT. MY OBI 100 IS FULLY FUNCTIONAL AT MY VACATION HOME VIA MY 200 AT HOME.
Bill Ruggirello
These instructions will resurrect an OBI100 by letting it function on the new GV network via OBITALK and an OBI200. Yes, you still need a 200 or 202.
You can set it up as an extension or not. The 100 can be on a local or remote network with internet access.
I believe, but have not tried, that you can setup 1, 2, 3, or 4 OBI100s to run thru 1 OBI200. OR you can setup 2 SPs on 2 OBI100s to run on 1 OBI200. OR any combination of OBI100 SPs to an OBI200 SPs. As the prof says, the exercise is left to the student.
Bottom line, the OBI100 is not totally dead. Of course, you can also still use it as a regular SIP with other providers. I have ALMOST gotten ANVEO E911 and GV to coexist on my 100. If anyone has a solution to that, please seem my other post.
There are some assumptions here. If you don't understand what they are, get someone who does to help you. This process may not work on the weekend because OBI's network seems to have weekends off. BE SURE YOU CLICK "SUBMIT" AFTER ANY CHANGE BEFORE YOU LEAVE THAT PAGE.
Go to OBITALK dashboard and delete then add your 100. It will tell you it is no longer supported.
Open up expert mode. Under System Management/Auto Provisioning, set METHOD to Disabled for Auto Firmware Update and ITSP Provisioning. SUBMIT
You can allow ITSP provisioning if you do not want to or cannot provision it locally.
Note: The OBI100 must be set to provision remotely, which I think is default after a factory reset.
Do a factory reset on the OBI100 = ***8 on the attached handset or paperclip. Wait........
If the OBI is remote and none accessible to you, you will need an assistant.
The following settings apply to either remote or local provisioning. For remote provisioning on OBITALK, use the expert mode.
For local provisioning, log onto the 100 using its IP address. The easiest way to get the OBi's IP address is to dial *** for the IVR. After the prompt enter 1 for Basic Network status. It will announce the OBi's IP address.
Note: it is not working for me now. It might work BEFORE you configure it. Let me know if it does, as I can't remember if it did.
Default local login = admin/admin
Under System Management/Auto Provisioning, set METHOD to Disabled for Auto Firmware Update and ITSP Provisioning. SUBMIT & REBOOT.
This sets inbound calls to go to the attached handset on the 100 and outbound calls to route thru the OBI200.
On the OBI100 under:
Voice Services/SP1 Service/X_InboundCallRoute = ph
SUBMIT
Voice Services/OBITALK Service/InboundCallRoute = ph
SUBMIT
Physical Interfaces/PHONE Port/OutboundCallRoute = {((Mpli)):pp}
SUBMIT
510555555 = your OBI200 OBITALK #
On the OBi200
configure your number on your OBI200 via OBITALK == You can set it on any SP.
Test that it works. If you do it on the weekend and it doesn't configure wait till Monday PM. I find adding never works the first time. The 2nd time is usually a charm.
Set these on the OBI200*
Voice Services/SPx Service/X_InboundCallRoute: pp(300111111)
SUBMIT
Voice Services/OBiTalk Service/InboundCallRoute: {300111111:spx}
SUBMIT
300111111 = your OBI100 OBITALK #
"x" is the SP# for the GV# you are using on the 200. Mine is sp4
The above sets inbound calls on the 200 SPx to route to the 100.
Outbound calls from the 100 route to the network with SPx callerID.
Reboot both devices and verify everything is still as you set them above.
AMEN!
*If you want to use the 100 as an EXTENSION, modify this:
Voice Services/SPx Service/X_InboundCallRoute: pp(300111111:ph)
This will cause both the 100 & 200 handset to ring.
NOTE: NOTE: Another thing I just discovered.
This digimap currently (meaning I might find a need to change it) works for me on both 100 & 200.
(*xx|1xxxxxxxxxxS0|[2-9]xxxxxx|[2-9]xxxxxxxxxS0)
The default seems to have changed because when I first reset the OBI it had 7 digit dialing. OBITALK appears to have removed it requiring me to add it back in.
It allows 11 digit, 10 digit or 7 digit dialing and also speed dialing. You just have to make sure the right AC is specified. 919 may not work for you.
HOWEVER, if you want the 7 digit dialing to go thru from the 100 you need to change this on the 200:
Voice Services/OBITALK Service/Digimap = (xx.|obxxxxxxxxx)
The default is (xxxxxxxxx|obxxxxxxxxx) which does not let 7 digit dialing thru.
I do not yet know what the 2nd part of that is for.
Bill
↧