Polycom firmware 2.2.0 and ring volume?
Submitted by voxter on Mon, 11/26/2007 - 5:14pm.
Ive just upgraded all my phones to polycom's 2.2.0 firmware, and changed this particular setting in sip.cfg:
< callWaiting call.callWaiting.ring="ring"/>
(Space inserted between < and callWaiting on purpose so the forum would show the tag)
It used to be "beep" but i have changed it to "ring" as this was a highly requested feature by our client.
I am now getting reports however, that it will work for a while, then over time (hours) the volume will gradually decrease until it ends up at a very low volume level, despite the ringer on the phone being set to maximum. I have made sure that I wiped all configuration files off of the server, and started from fresh copies of both phone1.cfg and sip.cfg.
Is this related to the firmware? Or the fact that I'm using "ring" in this setting, instead of the default "beep"?
Please help, I'm out of options!
Did you ever resolve this
Fri, 05/23/2008 - 2:47pm
I never did solve this, I
Fri, 05/23/2008 - 3:03pm
I never did solve this, I had to revert the firmware for the client to a previous version.
The only thing I could possibly think of is that there was something about my config files that conflicted with something in the newer firmware.
I have had only one suspicion arise, and have not been able to confirm nor deny it yet. The way i do overrides for my polycoms is (in the .cfg file,) specify the config files like "exten201.cfg, sip-overrides.cfg, phone1.cfg, sip.cfg" so that i have extension specific settings ( tag) and then global overrides, then include the stock phone1.cfg, and sip.cfg.
Now, the thing I am not sure of, is for example.. If in my sip-overrides.cfg, if there is a tag like:
< sometag>
< subtag somesetting.1.value="1">
< /sometag>
and in sip.cfg, there is:
< sometag>
< subtag somesetting.1.value="1" somesetting.2.value="1" somesetting.3.value="1" somesetting.4.value="1">
< /sometag>
Do my overrides effectively NULL out somesetting.2,3,4, or does it only override somesetting.1, and take 2, 3, and 4 from the sip.cfg?
This sort of behavior is the only thing that I am unsure of, if I am getting some sort of strange behavior out of the firmware if something like this is happening.
Otherwise, no, I have not solved the problem, and have no idea where to look.
Please do update this thread if you find something!!
I'm using the 3.0.1 firmware
Fri, 05/23/2008 - 3:22pm
I'm using the 3.0.1 firmware rpm that is available with trixbox, and I'm using their default method for organizing the configs with no overrides. Nothing fancy at all. This client is an hour away, so it's a pain to diagnose. Tonight I'm gonna go over there and try a few things... if you have any other ideas let me know!
I find it rather shocking
Fri, 05/23/2008 - 3:56pm
I find it rather shocking that of all the people using and upgrading polycoms, we're the only two people on the forums who would have run into this. I do have some phones on 2.2.0 and 3.0 deployed right now that do not exhibit the ringing issue, and i dont have any backups of my configs from when the issue did infact exist, so I dont have any way to compare... unfortunately!
All I can think to do is maybe wipe all the configs and start over and see if it goes away? I wish polycom's upgrade procedures didnt leave us with strange behavior that was next to impossible to debug...
Not yet. I ran a lot of
Sun, 05/25/2008 - 6:22pm
Not yet. I ran a lot of tests, and have plenty of information to give Polycom for a bug report. The problem is not easy to reproduce. So far it is happening on the phones that are used the most, which are all 650's. No one with 430's have reported a problem. Not all of the 650's are exhibiting the problem.
The bug is strange too. When the ringer volume gets low, it is ONLY that ring tone. The other ring tones stay at full volume. If you go to the Ring Tone menu and play each of the various ring tones, only one of the ring tones will be soft (the default ringer set by the server).
If you hit the "volume +" button it shows that the ringer is at full volume, but you can barely hear it. If you reboot the phone, the problem goes away. One time I rebooted the phone then made many test calls to it, and the sound gradually got softer. Then I rebooted the phone again and it all of a sudden acted normally. No changes were made between reboots.
To test... downgraded one phone to 2.2.0, and one to 2.1.3. I left one at 3.0.1 but did a format. I left one phone as it is (it never exhibited the problem).
For the older revisions of the software, I used the downloads from Polycom's website. The 3.0.1 phones are using the rpm provided by Trixbox. I made a minimal number of changes to the configuration. I'm going to leave it like this for a few days to see if they have the problem again... then I'll add Alert groups and such.
Are you using different ring tones for incoming calls/paging/intercom, etc?
I actually just looked and
Tue, 05/27/2008 - 12:39am
I actually just looked and noticed that i am on 2.2.0 and there is no problem, but the way i "fixed" it was to not use partial includes like i had described earlier, with my concern as to wether the way I did it was a problem. Instead, i modified the 2.2.0 phone1.cfg for each extension, and used the 2.2.0 global sip.cfg along with it, effectively using only two config files for each phone. What are you doing for this? Just using the standard trixbox method?
Can you tell me what your settings are? The only one setting that I did anything to that could have affected this was the "ring" setting, mentioned above, for call waiting.
After reverting to using the two config file includes, (the box in question that has this problem is infact not a trixbox) and changing the call waiting tone back to "beep" the problem seems to have gone away, but im not sure what fixed it. It's been a while since this came up.
I use the same ring tone across the board.
So I had a 601 (the only 601
Wed, 05/28/2008 - 1:36pm
So I had a 601 (the only 601 on this site) using firmware 1.6.7 for a while, and just moved it back to 2.2.0, with minimal configuration changes (basically just added in the extension info, etc) and the ringing volume problem is back.
Did you solve this problem? Or could you tell me which options you change in your config files, so maybe we can find a common denominator?
Dayton
Here are the configs that I
Wed, 05/28/2008 - 2:16pm
Here are the configs that I was having problems with. I changed the ips, passwords, etc.
http://www.justinmitchell.net/voip/sample.zip
Sorry for not giving you a detailed list of all of the options I've modified. I honestly don't remember. It's something I will go through as soon as I have time. I do have it ring instead of beep when they are already on the line. I also have different ringers set for internal/external calls and paging/intercom.
FYI, the client says they have had no problems with the ringer volume ever since I changed firmwares. I'm going to give it a few more days and then customize the config a bit.
Are you using the configs from trixbox's yum repository, or the official polycom ones?
No, not at all. As soon as I
Wed, 05/28/2008 - 6:35pm
No, not at all. As soon as I got these phones I upgraded to 3.0.1, and that is where I had the problem. I downgraded two phones to 2.1.3 and 2.2.0 and have not yet had the problem... but it's only been 3 days.
Where did you get the firmwares & base configs that you're using?
They are the polycom base
Wed, 05/28/2008 - 7:05pm
They are the polycom base configs that I modified myself entirely. nothing to do with trixbox configs. I havent gone to 3.x yet, my problem exists on 2.2.0.
Confirmed today that it does infact only affect the selected ringtone (in this case low trill) and switching to another ringtone appears to be okay.
I'm not sure what the heck is going on here, and i think i am now more confused.
Any updates? ive opened
Tue, 06/24/2008 - 1:16pm
Hmm. Do you have a ticket #
Tue, 06/24/2008 - 2:12pm
Hmm. Do you have a ticket # or URL to the ticket? I think other people can comment on tickets. It would help to have multiple people complain about the same thing.
I haven't changed the ring setting yet. I forgot. But they haven't had any problems with the current config. Next time I go over there I'll change the ring setting.
I also have this problem
Tue, 07/01/2008 - 3:35pm
I also have this problem with Polycom 550's and 330"s. Both are running bootrom 4.0 and SIP 3.0. The symptoms are identical with the volume just getting lower and lower. This occured after I enable "ring" in place of "beep". I changed to ring so that the users could hear the phone ring on call waiting. I am about to upgrade to the latest firmware and I will report the results here.
rsrussell, did you have any
Mon, 08/04/2008 - 8:53pm
rsrussell, did you have any luck with the new firmware?
This problem just cropped up again for me.
Previously, this was only happening with the Polycom 650's. No problem with the 430's.
However, the 650's were "operators", and these were the only phones that rang when an outside call came in. Recently we change the system so that every phone rings when a call comes in. We immediately ran into the same ringer-volume problem with the 430's.
I just changed callWaiting call.callWaiting.ring back to "beep" (it was "ring"). I imagine that will solve the problem for now.
Member Since:
2007-11-20