On Apr 12, 2007, at 1:49 PM, Kevin P. Fleming wrote:
Got off the phone with Polycom on this I have the same
problem with
my new 601 phone here (haven't seen the problem on the 650).
I am using an IP650 with the latest firmware (and the corresponding
sip.cfg file) and I have seen this
Hi All -
Got off the phone with Polycom on this I have the same
problem with
my new 601 phone here (haven't seen the problem on the 650).
I am using an IP650 with the latest firmware (and the corresponding
sip.cfg file) and I have seen this behavior. It is most noticeable
when
I found *something*. I've gone into my CPU graph (on the phone, in status -
diagnostic). Two phones, one running 1.6.7 and one running 2.1.0, both on
the same Hub, with the same general configuration (different SIP
registration, and each using it's version-specific sip.cfg file).
The pre-2.x
Mike wrote:
I found *something*. I've gone into my CPU graph (on the phone, in status -
diagnostic). Two phones, one running 1.6.7 and one running 2.1.0, both on
the same Hub, with the same general configuration (different SIP
registration, and each using it's version-specific sip.cfg file).
Mike,
Got off the phone with Polycom on this I have the same problem
with my new 601 phone here (haven't seen the problem on the 650).
I'm trying to find answers and Polycom's only got one reported case
of this (which I find bazaar, but whatever). The problem was
resolved, the
Jessee J Holmes wrote:
Got off the phone with Polycom on this I have the same problem with
my new 601 phone here (haven't seen the problem on the 650).
I am using an IP650 with the latest firmware (and the corresponding
sip.cfg file) and I have seen this behavior. It is most noticeable