SIP phones no longer connected after 3.2.1 (Build: 5794EX) Saturday 1/21/18
azrobert:
I'm tired of saying "The trunk where you had X_Proxy checked", so I'm assuming it's SP4.
The routing rules will be in the SP4 X_InboundCallRoute.
It should look something like:
{userid>(Msp1):sp1}
The userid is optional and must match the phone's userid. This is really for security. The (Msp1) is to validate the outbound number and is also optional.
You could change the sp4 inbound route to ph or sp1
ph will send the call to the OBi200 phone port. You don't need to have a phone attached to determine if it's ringing, the phone LED will flash.
sp1 will route the call with the outbound number unchanged to sp1.
When you send the call to the phone port, a call history entry will be created and you can see if the phone is using a different userid when unregistered.
Same with sp1, but an entry won't be created if it's not connected to GV.
I "think" the stuck in "Connecting" is a Google server problem. I'm having the same problem after a reboot. Just try another reboot. A power cycle might work better.
BlakeN:
SP4 is a good example - that is the phone / line I am using to debug
Works fine for inbound calls PSTN to GV to (SP1) Obi200 (SP4) to Cisco phone line 2 (user 1002)
Here is my config for SP4 X_InboundCallRoute {1002>911|933:sp2},{1002>(Msp1):sp1}
Replace with {1002>Ph} and still fast busy and no call history
Even tried to dial 933 - same outcome
On the other issue - tried unplugging and replugging in device / reconfiguring through Obi Dashboard and still have - Connecting to 64.9.242.172 in status and no inbound calls on that GV line
Thanks again for the help
Oh - and about pulled what little hair I have left out before I remembered that call log is only available when you log directly into the device. I guess I am getting too old to try to dive into this stuff only once a year. The memory is not what it use to be and I have a nice map drawn out.
Is it possible that when new GV upgrade is rolled out we can connect direct from SIP phone?
SteveInWA:
Quote from: BlakeN on May 10, 2018, 02:12:36 pm
SP4 is a good example - that is the phone / line I am using to debug
Works fine for inbound calls PSTN to GV to (SP1) Obi200 (SP4) to Cisco phone line 2 (user 1002)
Here is my config for SP4 X_InboundCallRoute {1002>911|933:sp2},{1002>(Msp1):sp1}
Replace with {1002>Ph} and still fast busy and no call history
Even tried to dial 933 - same outcome
On the other issue - tried unplugging and replugging in device / reconfiguring through Obi Dashboard and still have - Connecting to 64.9.242.172 in status and no inbound calls on that GV line
Thanks again for the help
Oh - and about pulled what little hair I have left out before I remembered that call log is only available when you log directly into the device. I guess I am getting too old to try to dive into this stuff only once a year. The memory is not what it use to be and I have a nice map drawn out.
Is it possible that when new GV upgrade is rolled out we can connect direct from SIP phone?
If your 200 series device(s) has/have firmware 5859EX or higher, and you are using Google Voice, then your Google account has been converted to use Google's new infrastructure. You can't go back, and you can't down-level the firmware. There are various reports of problems (e.g. no audio on one or the other or both directions, or server connection problems). So far, a few bugs have been identified and fixed, including one fixed yesterday. It's difficult to identify the root cause of a problem, given that this is a moving target, and the universe of devices being updated includes many that have been user-modified locally.
I see an assortment of issues reported today, but no clear pattern. The previous users' issues have mainly been caused by user modifications to their device configurations. So, it's worthwhile, if you can't figure out your issue, to just factory-restore the device and start over, and stick with the defaults loaded by OBiTALK until you get it working, and optionally make changes later.
No, the Google Voice upgrade does not enable connecting to any non-OBi SIP phones.
Taoman:
Quote from: BlakeN on May 10, 2018, 08:52:29 am
The other one after changes above received inbound calls (did not realize until my wife called) but fast busy on outbound. Will work to debug.
Try unchecking X_EnforceRequestUserID under SIP Credentials.
Blake4913:
:o Wow
So I have two Obi 200s and 2 GV lines. One is our home phone. Connected to a traditional cordless system. It still works great. Because I have two SIP phones and 911 service I actually have both 200s connected to the same GV account. Both are connected just fine. With some coaching from the great people on this forum I have inbound calls from that same line to my SIP phones (no love on outbound dialing).
The second GV line is for me. It routes to only one 200 but connects to both sip phones. It will not connect to GV at all.
So here is the real kicker. I have been debugging an ugly echo problem that is very intermittent (posted in GV area). I got a message from somewhere that prime members get a great deal on a 1062. I can use it to help troubleshoot my issue and have a phone to take to my folks house when I am there. So it arrived this evening. Out of the box no modes, no expert mode, just Obi dashboard config of GV accounts. No love on either GV account. It is giving me the backing off message. I am betting your going to tell me that the firmware for the 1062 does not support the new GV connection yet.
And they ask me why I drink? :)
Navigation
[0] Message Index
[#] Next page
[*] Previous page