I will open a JIRA issue tomorrow. 
-----Original Message-----
From: "Todd Hodgen" <[email protected]>
Date: Tue, 17 Aug 2010 18:20:23 
To: 'Matthew Kitchin \(public/usenet\)'<[email protected]>; 'Tony 
Graziano'<[email protected]>
Cc: <[email protected]>
Subject: RE: [sipx-users] 4.2.1 - Polycom error - Config file error 0x0

I would agree that it is an issue.  The Polycom 450 was supported in 4.0.2.
Auto discovery of the Polycom phones was introduced in 4.2.    You should be
able to get a phone up and running, without a line, and you can actually
make calls with it prior to assigning a line to it.   Time to write up a
JIRA issue me thinks.

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Matthew Kitchin
(public/usenet)
Sent: Tuesday, August 17, 2010 2:47 PM
To: Tony Graziano
Cc: [email protected]
Subject: Re: [sipx-users] 4.2.1 - Polycom error - Config file error 0x0

  It seems to me something has changed or is broken.
I have never had any problem booting a Polycom soundpoint 450, 550, or 
soundstation 6000 on a 4.0.4 or a 4.2.1 system and I have never created 
and/or pushed a profile first. I have always booted them first to get 
the IP/MAC. It had become a breeze on 4.2.1 as they were always even 
auto configured for me. I just added a line and changed the description.

On 8/17/2010 4:21 PM, Tony Graziano wrote:
> I think there is an issue here. I know that a line "should" preconfigure
in
> 4.2.x, without the need to have a config file for the phone. The 0x0 error
> means there is bno config file to load.
>
> ============================
> Tony Graziano, Manager
> Telephone: 434.984.8430
> Fax: 434.984.8431
>
> Email: [email protected]
>
> LAN/Telephony/Security and Control Systems Helpdesk:
> Telephone: 434.984.8426
> Fax: 434.984.8427
>
> Helpdesk Contract Customers:
> http://www.myitdepartment.net/gethelp/
>
> ----- Original Message -----
> From: Matthew Kitchin (public/usenet)<[email protected]>
> To: Tony Graziano<[email protected]>
> Cc: [email protected]<[email protected]>
> Sent: Tue Aug 17 17:11:30 2010
> Subject: Re: [sipx-users] 4.2.1 - Polycom error - Config file error 0x0
>
>    Sure enough. That did it.
> That is weird to me. I certainly haven't built as many systems as many
> of you guys, but I have never had to do that on 4.0.4 or 4.2.1.
> On 4.0.4, I have always booted the phone, let it pull the firmware and
> bootrom, and it boots up without a line associated with it.
> I then look at the IP, do an arp -a<IP>  on the server to get the MAC
> address. Paste that in to create the new phone.
> On 4.2.1, the phone has been automatically discovered under phones by
> the time I click on the tab. I simply put in a description and add a line.
> I am not making that up. It isn't like I have only done this a few
> times. We add a new handset or 2 to our main 4.0.4 system every week.
> That is how it works for me every single time.
> I just built a 10 handset 4.2.1 system about a month ago. That is how it
> worked. Maybe moving the handsets from one system to another could
> trigger something like this? Maybe a brand new one out of the box
> behaves different?
> Oh well. Thank you for the help. I wish I knew why it was behaving
> differently for me than my other systems have.
>
> On 8/17/2010 3:56 PM, Tony Graziano wrote:
>> You HAVE TO push the profile in order for the phone to find one. Add a
>> line to one of them, push the profile, manually reboot the phone.
>>
>> On Tue, Aug 17, 2010 at 4:50 PM, Matthew Kitchin (public/usenet)
>> <[email protected]<mailto:[email protected]>>  wrote:
>>
>>      I am using the split file.
>>      I have pushed the profile to the server. I don't have any phones
>>      to push the firmware to yet. Normally I would wait until it is
>>      booted and Sipx has discovered it or I can pull the MAC off it.
>>      It does load the bootrom and firmware successfully (either one I
>>      activate)
>>      It gets the error after the screen with
>>      Welcome...
>>      Processing configuration.....
>>
>>
>>
>>
>>      On 8/17/2010 3:44 PM, Tony Graziano wrote:
>>>      Correct. Only suppoorted in 3.2.x and later on the 450.
>>>
>>>      So you are using the SPLIT file, right?
>>>
>>>      When the phone boots and grabs the firmware and bootrom it works?
>>>      It gives you the error code when trying to get the config file
only?
>>>
>>>      Are you SURE you pushed the profile? Gotta ask...
>>>
>>>      On Tue, Aug 17, 2010 at 4:41 PM, Matthew Kitchin (public/usenet)
>>>      <[email protected]<mailto:[email protected]>>
wrote:
>>>
>>>          Brand new from scratch.
>>>          I have done nothing except add the Polycom firmwares.
>>>
>>>          On 8/17/2010 3:36 PM, Tony Graziano wrote:
>>>>          Was this a restore/upgrade? If so did you push the profiles
>>>>          once the update was done?
>>>>
>>>>          On Tue, Aug 17, 2010 at 4:24 PM, Matthew Kitchin
>>>>          (public/usenet)<[email protected]
>>>>          <mailto:[email protected]>>  wrote:
>>>>
>>>>              They are Soundpoint 450s.
>>>>              The files I'm using should definitely be supported. I
>>>>              have used these exact zip files on 4 other systems, so I
>>>>              don't see how that could be it.
>>>>              I have tried this combination:
>>>>                  spip_ssip_BootROM_4_2_1_release_sig.zip
>>>>                  spip_ssip_vvx_3_1_3RevC_release_sig_split.zip
>>>>
>>>>              and this combination:
>>>>                  spip_ssip_BootROM_4_2_2_release_sig.zip
>>>>                  spip_ssip_vvx_3_2_3_release_sig_split.zip
>>>>
>>>>              The first one is running at my corporate office on 200
>>>>              phones and 1 small satellite office.
>>>>              The second is running at 2 small satellite offices.
>>>>
>>>>              The xferlog contents are below if that gives any info.
>>>>
>>>>              Tue Aug 17 20:20:21 2010 1 10.81.4.249 29200
>>>>              /2345-12450-001.sip.ld b _ o r PlcmSpIp ftp 0 * i
>>>>              Tue Aug 17 20:20:26 2010 1 10.81.4.249 0
>>>>              /0004f22704b2-boot.log b _ i r PlcmSpIp ftp 0 * i
>>>>              Tue Aug 17 20:20:35 2010 1 10.81.4.249 23360
>>>>              /2345-12450-001.bootrom.ld b _ o r PlcmSpIp ftp 0 * i
>>>>              Tue Aug 17 20:20:41 2010 1 10.81.4.249 3234
>>>>              /000000000000.cfg b _ o r PlcmSpIp ftp 0 * c
>>>>              Tue Aug 17 20:20:41 2010 1 10.81.4.249 29200
>>>>              /2345-12450-001.sip.ld b _ o r PlcmSpIp ftp 0 * i
>>>>              Tue Aug 17 20:20:41 2010 1 10.81.4.249 23501
>>>>              /polycom_phone1.cfg b _ o r PlcmSpIp ftp 0 * c
>>>>              Tue Aug 17 20:20:42 2010 1 10.81.4.249 198273
>>>>              /polycom_sip.cfg b _ o r PlcmSpIp ftp 0 * c
>>>>              Tue Aug 17 20:21:25 2010 1 10.81.4.249 29200
>>>>              /2345-12450-001.bootrom.ld b _ o r PlcmSpIp ftp 0 * i
>>>>              Tue Aug 17 20:21:26 2010 1 10.81.4.249 3234
>>>>              /000000000000.cfg b _ o r PlcmSpIp ftp 0 * c
>>>>              Tue Aug 17 20:21:26 2010 1 10.81.4.249 23360
>>>>              /2345-12450-001.sip.ld b _ o r PlcmSpIp ftp 0 * i
>>>>              Tue Aug 17 20:21:31 2010 1 10.81.4.249 0
>>>>              /0004f22704b2-boot.log b _ i r PlcmSpIp ftp 0 * i
>>>>              Tue Aug 17 20:21:41 2010 1 10.81.4.249 29200
>>>>              /2345-12450-001.bootrom.ld b _ o r PlcmSpIp ftp 0 * i
>>>>              Tue Aug 17 20:21:46 2010 1 10.81.4.249 3234
>>>>              /000000000000.cfg b _ o r PlcmSpIp ftp 0 * c
>>>>              Tue Aug 17 20:21:47 2010 1 10.81.4.249 29200
>>>>              /2345-12450-001.sip.ld b _ o r PlcmSpIp ftp 0 * i
>>>>              Tue Aug 17 20:21:47 2010 1 10.81.4.249 23501
>>>>              /polycom_phone1.cfg b _ o r PlcmSpIp ftp 0 * c
>>>>              Tue Aug 17 20:21:48 2010 1 10.81.4.249 198273
>>>>              /polycom_sip.cfg b _ o r PlcmSpIp ftp 0 * c
>>>>              Tue Aug 17 20:22:30 2010 1 10.81.4.249 29200
>>>>              /2345-12450-001.bootrom.ld b _ o r PlcmSpIp ftp 0 * i
>>>>              Tue Aug 17 20:22:31 2010 1 10.81.4.249 3234
>>>>              /000000000000.cfg b _ o r PlcmSpIp ftp 0 * c
>>>>              Tue Aug 17 20:22:31 2010 1 10.81.4.249 29200
>>>>              /2345-12450-001.sip.ld b _ o r PlcmSpIp ftp 0 * i
>>>>              Tue Aug 17 20:22:36 2010 1 10.81.4.249 0
>>>>              /0004f22704b2-boot.log b _ i r PlcmSpIp ftp 0 * i
>>>>              Tue Aug 17 20:22:45 2010 1 10.81.4.249 29200
>>>>              /2345-12450-001.bootrom.ld b _ o r PlcmSpIp ftp 0 *
>>>>
>>>>              On 8/17/2010 3:16 PM, Tony Graziano wrote:
>>>>>              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]
>>>>>              <mailto:[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]
>>>>>                  <mailto:[email protected]>
>>>>>                  List Archive:
>>>>>                  http://list.sipfoundry.org/archive/sipx-users/
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>              --
>>>>>              ======================
>>>>>              Tony Graziano, Manager
>>>>>              Telephone: 434.984.8430
>>>>>              sip: [email protected]
>>>>>              <mailto:[email protected]>
>>>>>              Fax: 434.984.8431
>>>>>
>>>>>              Email: [email protected]
>>>>>              <mailto:[email protected]>
>>>>>
>>>>>              LAN/Telephony/Security and Control Systems Helpdesk:
>>>>>              Telephone: 434.984.8426
>>>>>              sip: [email protected]
>>>>>              <mailto:[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.
>>>>>
>>>>
>>>>
>>>>
>>>>          --
>>>>          ======================
>>>>          Tony Graziano, Manager
>>>>          Telephone: 434.984.8430
>>>>          sip: [email protected]
>>>>          <mailto:[email protected]>
>>>>          Fax: 434.984.8431
>>>>
>>>>          Email: [email protected]
>>>>          <mailto:[email protected]>
>>>>
>>>>          LAN/Telephony/Security and Control Systems Helpdesk:
>>>>          Telephone: 434.984.8426
>>>>          sip: [email protected]
>>>>          <mailto:[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.
>>>>
>>>
>>>
>>>
>>>      --
>>>      ======================
>>>      Tony Graziano, Manager
>>>      Telephone: 434.984.8430
>>>      sip: [email protected]
>>>      <mailto:[email protected]>
>>>      Fax: 434.984.8431
>>>
>>>      Email: [email protected]
>>>      <mailto:[email protected]>
>>>
>>>      LAN/Telephony/Security and Control Systems Helpdesk:
>>>      Telephone: 434.984.8426
>>>      sip: [email protected]
>>>      <mailto:[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.
>>>
>>
>>
>>
>> --
>> ======================
>> Tony Graziano, Manager
>> Telephone: 434.984.8430
>> sip: [email protected]
>> <mailto:[email protected]>
>> Fax: 434.984.8431
>>
>> Email: [email protected]<mailto:[email protected]>
>>
>> LAN/Telephony/Security and Control Systems Helpdesk:
>> Telephone: 434.984.8426
>> sip: [email protected]
>> <mailto:[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/

_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to