Getting Polycom IP501s to register

Discussion in 'General' started by howwhi, Jun 14, 2009.

  1. howwhi

    Joined:
    Jun 11, 2009
    Messages:
    25
    Likes Received:
    0
    Thanks to all who contribute,

    I have been using Asterisk and Polycom for five plus years. Have Elastix 1.5.2 installed. Analog phones may dial amongst themselves, connected to Elastix via TDM422B, adding known good IP501s. Copied Polycom load files into /tfptboot. IP501s are getting IP addresses from DHCP but are unable to completely register.

    I create the extension, then set the phone in the endpoint manager (thank you, dicko, for pointing out the need for the "/24"!!). Phone is recognized as a Polycom and the {MAC}.cfg and {MAC}reg.cfg files are created.

    Latest incarnation yields this message on IP501 LCD: "Error loading {MAC}.cfg"

    Anybody got a checklist?? Happy to post files as needed but want to start with the "is the power connected to the server?" questions first...
     
  2. dicko

    Joined:
    Oct 24, 2008
    Messages:
    4,099
    Likes Received:
    0
    Does your /tftboot/server.cfg reflect reality as to where the tftpd server is available to the phones on eth1?
    (I assume, of course, that the phones are set up for tftp configuration)

    for polycoms in Elastix I suggest a modification of the /etc/xinetd.d/tftp file to:

    server_args = -vvv -c -s /tftpboot


    so your can follow the progress of the tftp server in /var/log/messages and allow the phones to save/restore their directories/logs//overrides to the Elastix box, (in which you poke around at /tftpboot/polycom/{service}/{mac}. (I assume you knew that, that's for others who might be benighted with polycoms))
     
  3. howwhi

    Joined:
    Jun 11, 2009
    Messages:
    25
    Likes Received:
    0
    Thank you again, dicko.

    With two networks "colliding" on one box, I was confused as to which network to identify in the server.cfg file. Multiple gotchas cleaned up; phones now register.

    Thank you for the xinetd server_args. That made it obvious that my option tftp-server line was in error in the dhcpd.conf file.

    Now on to dahdi (nee zap) trunks.
     
  4. dicko

    Joined:
    Oct 24, 2008
    Messages:
    4,099
    Likes Received:
    0
    You're Welcome:
    Avoid collisions, use routing. :)

    p.s. be careful of that "tftp-server line" , not all phones agree!
     

Share This Page