asterisk users - Apr 2007 - Polycom 501 sluggish keys: found the problem!

Here is what I had to change on the phone1.cfg file:
 
I had this value in my 1.6.7 file, put in there following suggestions from
the Wiki
(http://www.voip-info.org/wiki/index.php?page=Polycom+Soundpoint+IP+501) :
reg.1.server.1.expires="30"

Now, this worked flawlessly with 1.6.7.  But with 2.x, this seizes up the
phone with a huge CPU load (approaching 100% at times) and makes it
unresponsive.  I had to remove it, fixing the problem.
 
Now, I have two follow-up questions:
1) Is that normal? (my guess is no)
2) This has little to do with the issue, but is a line seize?  I keep on
coming accross Polycom configs with reg1.server1.lineseize.expires=30 or
something.  What does this do?
 
Mike
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20070413/f073bfb3/attachment.htm

On 4/13/07, Mike <list@virtutel.ca> wrote:
> reg.1.server.1.expires="30"
My understanding is that the above causes the phone to re-register
with its server (asterisk) every 30 seconds. I would expect a
registration to be a "heavy" operation, so that does explain the high
CPU load, possibly leading to the sluggishness.

My 501 has its server expiration set to 1 hour ("3600"), never seen
the sluggishness here with SIP load 2.0.3

-- 
"I am Dyslexic of Borg. Fusistance is retile. Your ass will be
laminated!"

True, but that being said 1.6.7 did re-register every 30 seconds with no
issues.

Did the phone loss in performance after the upgrade?

Mike

-----Original Message-----
From: asterisk-users-bounces@lists.digium.com
[mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Kai-Uwe Jensen
Sent: Friday, April 13, 2007 10:01
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] Polycom 501 sluggish keys: found the problem!

On 4/13/07, Mike <list@virtutel.ca> wrote:
> reg.1.server.1.expires="30"
My understanding is that the above causes the phone to re-register with its
server (asterisk) every 30 seconds. I would expect a registration to be a
"heavy" operation, so that does explain the high CPU load, possibly
leading
to the sluggishness.

My 501 has its server expiration set to 1 hour ("3600"), never seen
the
sluggishness here with SIP load 2.0.3

--
"I am Dyslexic of Borg. Fusistance is retile. Your ass will be
laminated!"
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

On 4/13/07, Mike <list@virtutel.ca> wrote:
> True, but that being said 1.6.7 did re-register every 30 seconds with no
> issues.
>
> Did the phone loss in performance after the upgrade?
Not for me. Did not observe any lesser performance.

Mike wrote:
> Here is what I had to change on the phone1.cfg file:
Which means we caught you red-handed! Remember when I asked you about
whether you were using the default configs from the new firmware package?
> I had this value in my 1.6.7 file, put in there following suggestions
> from the Wiki
> (http://www.voip-info.org/wiki/index.php?page=Polycom+Soundpoint+IP+501) :
> *reg.1.server.1.expires="30"*
That tells me right there that you didn't use the default sip.cfg and
phone1.cfg files.
> Now, this worked flawlessly with 1.6.7.  But with 2.x, this seizes up
> the phone with a huge CPU load (approaching 100% at times) and makes it
> unresponsive.  I had to remove it, fixing the problem.
I have learned the hard way that using old configs with new firmware is
asking for trouble. It is much better to keep your custom configurations
in a MAC specific overrides file and replace the sip.cfg and phone1.cfg
files completely.

This doesn't guarantee that you won't have problems, but it's a lot
easier to troubleshoot an overrides file with a dozen items in it than
to sift through big, customized sip.cfg files.
> Now, I have two follow-up questions:
> 1) Is that normal? (my guess is no)
Well, you shouldn't need to re-register every 30 seconds, either. What
was the reason for configuring your phones like that?

-Stephen-