asterisk users - Apr 2007 - Polycom Provisioning Problems

Hello

I am having some difficulties provisioning a set of polycom 501 phones,
while another set of phones are working just fine.

My Asterisk box is dual homed. On one network, where the asterisk box
runs dhcpd and there are only phones, provisioning works as expected.

However, for phones that are connected thru the other interface (and
receive their IP address from a separate router), they are not provisioning.
To add to the confusion, it seems that they fail in inconsistent ways.

Even after specifying the FTP server address, name and password, these
phones will complain that they cannot connect to the server, and begin loading
the stored configuration. In addition,
when they come up, their dates are set to Jan 1, 2001. (I think I can fix this
by specifying the snmtp address, but the other phones seem to be able to find
the snmtp on their own.)

In inspecting the <MAC>-boot.log files, the phones that fail have CDP
enabled,
while the phones that succeed have CDP disabled. I think this is
Continual Data Protection,
but don't see where to disable it on the phone interface. Is this a
cause of the failure?

Any insight will be greatly appreciated.

Thanks

-- 
Jim Freeze

Access the phones through the web interface,
Compare version numbers with the phones that work
Compare only with other 501 phones
Make sure all settings are identical, most polycom web interfaces will loose
there setting adjustments if you click on another tab, so do one page at a
time, click save, then let it reboot, then go to next section.

Also, is you asterisk server local?
If remote, and the above does not work, look at routing.
Are you behind NAT?
Try and access the phone via telnet from a remote server to the auth ports
of the phone and vice verse. (I know you can telnet from a Cisco phone, I
would imagine polycom has a similar features)

Let me know if this helps!!!
Polycom is very picky!

Brad

-----Original Message-----
From: asterisk-users-bounces@lists.digium.com
[mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Jim Freeze
Sent: Wednesday, April 25, 2007 4:37 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: [asterisk-users] Polycom Provisioning Problems

Hello

I am having some difficulties provisioning a set of polycom 501 phones,
while another set of phones are working just fine.

My Asterisk box is dual homed. On one network, where the asterisk box
runs dhcpd and there are only phones, provisioning works as expected.

However, for phones that are connected thru the other interface (and
receive their IP address from a separate router), they are not provisioning.
To add to the confusion, it seems that they fail in inconsistent ways.

Even after specifying the FTP server address, name and password, these
phones will complain that they cannot connect to the server, and begin
loading
the stored configuration. In addition,
when they come up, their dates are set to Jan 1, 2001. (I think I can fix
this
by specifying the snmtp address, but the other phones seem to be able to
find
the snmtp on their own.)

In inspecting the <MAC>-boot.log files, the phones that fail have CDP
enabled,
while the phones that succeed have CDP disabled. I think this is
Continual Data Protection,
but don't see where to disable it on the phone interface. Is this a
cause of the failure?

Any insight will be greatly appreciated.

Thanks

-- 
Jim Freeze
_______________________________________________
--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

Jim Freeze wrote:
> In inspecting the <MAC>-boot.log files, the phones that fail have CDP
> enabled,
> while the phones that succeed have CDP disabled. I think this is
> Continual Data Protection,
> but don't see where to disable it on the phone interface. Is this a
> cause of the failure?
CDP is Cisco Discovery Protocol. Your phones are trying to talk to the
nearest Cisco equipment and being totally ignored.

Turn off CDP and try again.

-Stephen-