Jump to content

Porter

Members
  • Posts

    33
  • Joined

  • Last visited

Everything posted by Porter

  1. There is a slight problem with the new version, at least on the Debian build. The pnp.xml seems to be malformed, at least the version viewable through the Web Page Control tab. It truncates in the fifth "file" section at: <file name="snom_3xx.xml" encoding="xml"> <pattern>snom3?0-############.htm</pattern> <vendor>snom</vendor> <protocol>tftp,http,https</protocol> <pnp-vendor>snom</pnp-vendor> <pnp-model>snom3[026]0</pnp-model> <pnp-version>^6</pnp-version> <pnp-content-type>application/url</pnp-content-type> <pnp-url>http://provisioning.snom.com/update6t And that's it... it just stops. Restoring "default" has no change, and trying to manually enter the missing segments of the file and save has no effect. The save button doesn't seem to do anything at all. Any ideas? [EDIT] I figured out the problem... it looks like the text display field in Web Page Control truncates at 4096 characters, and throws away anything that comes after that. The files themselves are ok as long as you don't attempt to edit, but if you do attempt to save a file that has been truncated, even without editing anything, it breaks the file because it is saving a broken/truncated version of the file over the original. The "restore default" button is probably working, but on long files it has no effect because the field it's loading the text into is still truncating the data before it saves. I have submitted a bug report, ticket ID 20110204794.
  2. Do you have the DIDs configured on each extension account? The DIDs should be in the "Account number(s)" field, (after the extension number) not in the ANI.
  3. Just FYI... the information at that link seems to have suffered some sort of editing error. There are IP Routing examples in the IP Replacement section, and the text seems to be a bit of a jumble between the two sections as well.
  4. Thanks for the link! Coincidentally, I found it myself when searching around earlier, it took some digging. I came back to post the link and found you'd beaten me to it... but thanks anyway!
  5. I found a "leftover" copy! For those searching, here you go... the section on "Separation by Route" is extremely important for those of us running public IP for trunks and private IP for phones. Setting up explicit routes is the key, it's much more powerful (and has fewer unwanted side-effects) than the IP Replacement method. http://kiwi.pbxnsip.com/index.php/Office_with_private_and_public_IP_addresses
  6. Is there a current valid URL for this resource? I am seeing this link in many places, and can't find the new location of the document.
  7. Is there a new correct URL for this document? I can't find it anywhere.
  8. I'm about to pull my hair out on this one, so if anyone can help, it would be greatly appreciated. For some reason, after upgrading all of our devices to 8.4.18, now I am unable to get any of the phones to connect with the server to provision settings. They provisioned fine previously with 7.3.26, so I'm stumped. Here is the log I get on the SnomONE server when a unit tries to connect to provision: [6] 2011/01/19 19:48:24: TFTP: Request for snom320.htm from 192.168.2.130:12126 [7] 2011/01/19 19:48:24: UDP: Opening socket on 0.0.0.0 [7] 2011/01/19 19:48:24: Open TFTP port 34857 [6] 2011/01/19 19:48:24: TFTP: Request for snom320-000413313A4C.htm from 192.168.2.130:12126 [7] 2011/01/19 19:48:24: UDP: Opening socket on 0.0.0.0 [7] 2011/01/19 19:48:24: Open TFTP port 38210 And then nothing. The phone does not seem to get anything from the server at all, it eventually says "Provisioning Failed". We are using SnomONE 4.2.0.3958 on linux, if that is relevant. Using DHCP option 66 to point the phones to the SnomONE box. Any advice? Thanks! Porter
×
×
  • Create New...