SIP phones no longer connected after 3.2.1 (Build: 5794EX) Saturday 1/21/18
BlakeN:
Quote from: azrobert on May 13, 2018, 07:22:27 pm
It seems the 488 error is a codec problem.
See:
https://supportforums.cisco.com/t5/ip-telephony/message-sip-with-488-not-acceptable-here/td-p/2077189
The link suggests forcing G711a, but I know GV works with G711u. I checked my OBi200's codec profile and the G711a codec is disabled. I don't remember if I disabled it. Check which codec profile your GV is using then see whether any codecs in that profile are disabled. See if you can force G711u in your Cisco phone.
Thanks - I goofed with it a bit and setting Use Pref Codec Only to yes in the Cisco phone seemed to solve the issue. I tried it with both G711u and G711a as the preferred vocoder - both worked. In my 200 config I have both 711 codecs enabled, G729 and G726R32 enabled. I tried to disable G711a and that did not solve issue.
I will work with my other phones/lines and try to document all changes to enable working SIP phone with latest connection.
BTW - what are the down sides to not having registration? I assume you don't know if the 200 dies until you try to pick up the phone and dial?
RFC3261:
Quote from: Blake4913 on May 13, 2018, 04:41:29 pm
There is likely no incentive for Polycom to allow a Cisco phone to work or any SIP phone for that matter.
If this was a request for a new feature, I would have no reason to have believed that Obihai would invest in development to add it. In this case, however, some changes broke a capability that Obihai, themselves, documented. Hanlon's razor suggests it is a bug introduced accidentally (perhaps due to other changes, such as support for the GV changes?). An alternative is that violating RFC specified authentication process was introduced intentionally to break downstream SIP clients. Only Obihai knows for sure, and as you say, they have so far not even answered the question(s).
SteveInWA:
Quote from: BlakeN on January 22, 2018, 04:23:18 pm
Trust me - I thought about saying I would be happy to pay them $10 to fix it. I put this together about 3 years ago. It probably took me 2 hours just to remember what I had done even though everything was backed up and I had drawn diagrams and tables of IP addresses, etc. It sucks to get old. But hey, it is better than paying Verizon $70/month for a POTS line. Thanks again for your insight!!
So: this thread is about five months old and three pages long, and you're still trying to experiment with those Cisco phones. Think of how much time you've spent so far. Are you employed? If so, how much is your time worth per hour? You could have bought a case of OBi IP phones by now for that much money. I know people love to experiment and mod stuff, be it cars, boats, musical instruments, or whatever, but I can think of better things to do than play with old, discontinued, ugly-UI Cisco phones.
Clearance sale:
https://smile.amazon.com/Obihai-Gigabit-Phone-Built-Bluetooth/dp/B00TEFGVD2/ref=sr_1_1?ie=UTF8&qid=1526348107&sr=8-1&keywords=obi+1062
BlakeN:
Quote from: SteveInWA on May 14, 2018, 06:36:09 pm
So: this thread is about five months old and three pages long, and you're still trying to experiment with those Cisco phones. Think of how much time you've spent so far. Are you employed? If so, how much is your time worth per hour? You could have bought a case of OBi IP phones by now for that much money. I know people love to experiment and mod stuff, be it cars, boats, musical instruments, or whatever, but I can think of better things to do than play with old, discontinued, ugly-UI Cisco phones.
So, first let me say that Obi has been good to me. They created a fantastic product and have evolved it over time. Not sure about Polycom but I am starting to get the picture.
So, I did buy a 1062 and so far I am not feeling the ease of configuration. I had to submit a ticket to get it upgraded to the latest code so that it would connect to GV (it would not upgrade). Even thought I put in a very recognizable label for GV it shows on the phone as some long string of characters. I attached my iPhone to the phone in hopes to download my contacts. Said yes to the allowing access to my contacts but no download. It is not intuitive on how to add my iPhone to line key so that I can use it as a speakerphone for my iPhone. I have spent some time with the manual but not feeling any savings in time so far. Is there a quick start configuration guide somewhere that I am missing?
So, for several years I have been using the Cisco phones with no issues. The investment was outstanding. A few bucks to Anveo, the hardware (which you needed anyway other than the Obi200) and no need to pay Verizon big money each month for antiquated service. The Cisco phones are solid (Fantastic speaker phone and super durable and a simple straight forward UI). So, in January Obi or Polycom forced my unit to upgrade software and broke my system. I downgraded code and went back to my life. Last week it happened again and low an behold this time someone figured out a way to ensure that you can't downgrade and maybe tossed in a new bug with the codec. So, by incompetence or plan he we are.
So, sure I am willing to shell out some bucks for a couple of 1062s to replace my Cisco phones but give me some motivation. Convince me they are easier to configure, new and better features and they won't be orphaned by Polycom or rendered useless by a forced software upgrade.
BTW - why is the 1062 on "clearance"
So, yes I have a job and yes I am a geek and kind of like doing some of this stuff. But I rather be fishing.. ;D
BlakeN:
Hi All,
To make it easier to follow I have tried to document the items I changed in one place for the Obi 200 work around for SIP phone connectivity issues with latest code (2 issues - registration bug & codec issue). It appears that the registration issue was introduced in Jan and I am making an educated guess the codec issue in this latest release (I am making a leap here as others are complaining of no outbound calling but inbound still works).
I am coming from 5757EX and as of last week was updated automatically to 5859EX. As of 5757EX I had Obi 200 with GV line and Cisco SPA514G SIP phone that worked perfectly with registration and no forced codec.
For reference I have GV coming in on SP1 and my SIP phone on SP4.
To work around the registration issue we are basically not requiring registration:
On Obi200 SP4 or the SPX service connected to the SIP phone
Uncheck X_RegisterEnable
Uncheck X_EnforceReguestUserID
Uncheck X_Proxy
For X_InboundCallRoute take out reference to user ID
Mine had {1002>(Msp1):sp1}
I changed to {>(Msp1):sp1}
On Obi200 SP1 or the SPX service connected to GV
For X_InboundCallRoute add @IPaddr:SIP port where the IP address is the IP address of the SIP phone/line and the SIP port
Mine had {sp4(1002)}
I changed to {sp4(1002@192.168.4.50:5064)}
On Cisco SIP phone using admin advanced login on the line tab that is connected to SP4
Change Register to No
Change Make Call Without Reg to yes
Change Answer Call Without Reg to yes
To work around the codec issue I am forcing the Cisco IP phone to only use one codec (in my case the G711u):
On Cisco SIP phone using admin login on the line that is connected to SP4
Change Use Pref Codec Only to yes (note that In the 3 slots for preferred codecs I only have the first filled in with G711u)
I assume there are downsides to this configuration over what I had. If you have a connectivity failure or your Obi devices fails I do not believe you will know that until you pick up the phone and dial a number. I am not sure there is any downside to forcing only one codec.
Thanks again to azobert, Taoman and SteveInWA efforts in helping me stumble through putting this workaround.
Navigation
[0] Message Index
[#] Next page
[*] Previous page