Vestalink ringing both lines on Obi202
JohnH:
This problem has me baffled. I've been using GV/Callcentric for some time and I'm switching over to Vestalink. However, for some reason my only Vestalink line is ringing both lines on my Obi202. I'm using ObiTALK for the setup.
You may want to jump to 7 and 8 because I think that's where the problem is.
Here are the details:
1. Vestalink is one Phone 1 and SP1. Phone 2 is NOT selected.
2. GV is still on Phone 2 and SP3. (Waiting for GV number to port to Vesta before switching). Phone 1 is not selected.
3. In the advanced area, under Physical Interfaces, the PrimaryLine setting Phone 1 port is SP1 and the setting for Phone 2 port is SP3.
4. In advanced area, under SP1, the X_InboundCallRoute setting is {>(33XX):ph},{ph}. It was {ph} but I changed it for reasons I'll explain below.
5. In Vesta, call forwarding is turned off.
6. When you call line 2, only line 2 rings. This problem is only when you call line 1.
7. IMPORTANT: While I know I shouldn't do this if I'm using ObiTALK, I took a peek at the Obi web controller. There, in SP1 under X_InboundCallRoute is this setting: {>(33XX):ph,ph2} I'm assuming the ph2 is causing the problem but this setting cannot be changed! (BTW, 33XX is the obfuscated version of my Vesta username). I tried switching this and rebooting, but it just reboots again and goes back to the old setting. I also tried changing the setting in ObiTALK to the setting in detail 4 (and several other versions of this setting), but it has no effect.
8. IMPORTANT: When I first set up my Obi202 with Vesta, I tried using their autoconfiguration and had this same problem with both lines ringing. The support guy told me to use ObiTALK instead and delete the device first (I did). However, I did not do a factory reset (if that's possible).
It seems to me that the Vesta autoconfiguration still has control over my Obi202.
Any ideas? Thanks in advance.
giqcass:
This is pretty standard behavior.
Go to
System Management
>>>>>>>>>>>>>>>>>Auto Provisioning
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>ITSP Provisioninghelp
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>Method = Disabled
Make sure you submit it!
Then Go to
Voice Service
>>>>>>>>>>>>>Sp1 Service
>>>>>>>>>>>>>>>>>>>>>>X_InboundCallRoute
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>Change it to {>(33XX):ph}
Submit then reboot.
Let me know if that does it.
Lavarock7:
On an Obi202 the port for Phone 1 has 4 wires and the port for Phone 2 has 2 wires. This allows Phone 1 to be a 2 line phone. Check to see if you have a 2 wire telephone cord yto use for that phone and whether that solves the problem.
JohnH:
Thanks to both of you! Giqcass, your method worked, but I'm still a little puzzled. I tried it first on ObiTALK, but it didn't work. Next, I tried it on my local device controller (or whatever you call it) and it worked fine. It seems like ObiTALK has lost some, but not all, of its control over my device since I first used the Vesta autoconfiguration.
At least it's working. Thanks again. :D
giqcass:
There are four ways to control an Obi.
1)Log in to the Obi itself.
2)Through a phone connected directly to the Obi.
3)Using a provisioning file.
4)SIP I don't know much about this method but Obi can make at least some changes to your obit with special sip messages sent over the Obitalk network.
Option 3 is the primary way Obihai and Vestalink use to control your Obi. When you used the Vestalink auto setup Vestalink changed the server your obi looks at to find updated provisioning files. Since your Obi was no longer looking at Obihai servers it could no longer find changes you made via the Obihai web control panel. In addition because it was looking at the Vestalink servers for updated provisioning files it would overwrite any changes you made to your obi locally with settings that it found on the vestalink servers. The change I told you to make told the Obi to stop looking for provisioning files on the Vestalink server.
Navigation
[0] Message Index
[#] Next page