It usually means the bootrom or firmware that sipx is trying to load on the
phone is not supported on that model.

You left out an important detail. Phone model.

On Tue, Aug 17, 2010 at 4:13 PM, Matthew Kitchin (public/usenet) <
[email protected]> wrote:

>  Wow. I think Mr. Murphy and his laws have taken up residence in my
> office today.
> Fresh (3rd time today) install of 4.2.1 on CentOS 5.5 64 Bit.
> Everything, including DNS and DHCP are running on the server.
> Any Polycom 450 handset I try gets stuck in a reboot loop. It always
> ends up on:
> config file error
> error is 0x0
>
> I have searched for this error, and I can't find anything that even
> remotely seems to apply to me.
>
> I get one warning on the diagnostic test. I can't find a great deal of
> info on this.
> DHCP (Option 120) Test       8/17/10 2:41 PM        Warning
> Unknown test result: 1
>     * Hide details
> Starting DHCP server test.
> Socket Bind Exception: Address already in use
> DHCPACK responce received.
>   Message Type: DHCPACK
>   Server Identifier: 10.81.4.5
>   Subnet Mask: 255.255.255.0
>   Router: 10.81.4.1
>   Domain Name: bartlett.voip
>   DNS Server: 10.81.4.5, 127.0.0.1, 10.85.0.10
>   TFTP Server: 10.81.4.5
>   SIP Server: sipx.bartlett.voip
>   NTP Server: 207.171.7.152, 66.7.96.1, 149.20.54.20
> Starting SIP servers test.
> Testing connectivity to SIP Server: sipx.bartlett.voip
>
>
> My DHCP conf file looks the same as it does on my working servers.
> [r...@sipx tmp]# cat /etc/dhcpd.conf
> authoritative;
> ddns-update-style  none;
> option sip-servers-name code 120 = text;
>
> subnet 10.81.4.0 netmask 255.255.255.0 {
>    range                        10.81.4.10  10.81.4.250;
>    default-lease-time           43200;
>    max-lease-time               43200;
>    option routers               10.81.4.1;
>    option subnet-mask           255.255.255.0;
>    option domain-name           "bartlett.voip";
>    option tftp-server-name      "10.81.4.5";
>    option sip-servers-name      "sipx.bartlett.voip:12000/cmcprov/login";
>    option domain-name-servers   10.81.4.5,10.85.0.10;
>    option ntp-servers           sipx.bartlett.voip;
>
> I have tried using both 3.2.3 and 3.1.3. I have both of these working on
> other setups. It does take whichever firmware I activate, but gets the
> same error.
> I will be glad to provide any more info, but I'm not sure where to
> start. Any ideas?
> _______________________________________________
> sipx-users mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>



-- 
======================
Tony Graziano, Manager
Telephone: 434.984.8430
sip: [email protected]
Fax: 434.984.8431

Email: [email protected]

LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: [email protected]
Fax: 434.984.8427

Helpdesk Contract Customers:
http://www.myitdepartment.net/gethelp/

Why do mathematicians always confuse Halloween and Christmas?
Because 31 Oct = 25 Dec.
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to