So I bought this batch of Poly 601s. They came in with 3.2 bootroms (a couple with 3.1), so when I didn't seem to be able to cobble together a config file that the supplied 2.0.3 SIP code liked, I didn't worry about it too much -- that's new enough to run 3.1.2, the most recently publicly released SIP code (I'm having some trouble getting the current GA from my reseller, but for the discount I got, I'll tolerate that.)
I set up a MAC.cfg file that loads the sip.ld, and these config files:
x6300.cfg, phone1.cfg, company-ppk.cfg, and sip.cfg
in that order, where the first and third are copies of the second and fourth, resp. I added the obvious requirements, server IP and such, to the first and third files, and then booted a phone.
It pulled down the 3.1.2 SIP code, validated it, booted, and this is when my problem crops up: the phone does its self-tests, and paints on its screen the gray wash on the left for the line keys, and the dark half-curved-rectangle that surrounds the display area... and then locks up hard.
It will push a log file, and the pertinent entry is ...
unaccessible just now because the box it's on is pulling one of its intermittent "I refuse to answer to ssh" tantrums, but it includes an error 0x20. The most common reported reason for that error, an unescaped ampersand somewhere in the file, I've checked for already; there are none.
The only other possible pertinent item is that I pretty-printed the XML files before I started editing them, using the pretty printer from here and the nts switches (to break the attributes apart on separate lines for ease of editing and sort them), hopefully the XML interpreter in the SIP code is sensible enough to ignore that valid extra whitespace and not break anything, but I'd be willing to be convinced that's my entire problem.
Any Polycom wizards out there of a Mother's Day?
I'll upload config and log files later if they're needed.
I set up a MAC.cfg file that loads the sip.ld, and these config files:
x6300.cfg, phone1.cfg, company-ppk.cfg, and sip.cfg
in that order, where the first and third are copies of the second and fourth, resp. I added the obvious requirements, server IP and such, to the first and third files, and then booted a phone.
It pulled down the 3.1.2 SIP code, validated it, booted, and this is when my problem crops up: the phone does its self-tests, and paints on its screen the gray wash on the left for the line keys, and the dark half-curved-rectangle that surrounds the display area... and then locks up hard.
It will push a log file, and the pertinent entry is ...
unaccessible just now because the box it's on is pulling one of its intermittent "I refuse to answer to ssh" tantrums, but it includes an error 0x20. The most common reported reason for that error, an unescaped ampersand somewhere in the file, I've checked for already; there are none.
The only other possible pertinent item is that I pretty-printed the XML files before I started editing them, using the pretty printer from here and the nts switches (to break the attributes apart on separate lines for ease of editing and sort them), hopefully the XML interpreter in the SIP code is sensible enough to ignore that valid extra whitespace and not break anything, but I'd be willing to be convinced that's my entire problem.
Any Polycom wizards out there of a Mother's Day?
I'll upload config and log files later if they're needed.
Phone System 