HTTP 905 Error on 96xxupgrade.txt

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • brgnewman
    Member
    • May 2012
    • 4

    HTTP 905 Error on 96xxupgrade.txt

    Lately I've noticed when our phones boot up the following prompts/messages come up on the phone's display and new/edited configuration files are not processed by the deskphones:
    DHCP (* to program)
    HTTPS: 1 10.0.201.60
    HTTPS: 1 https://10.0.201.60:411/96xxupgrade.txt
    HTTPS: 1 -1
    HTTP: 1 10.0.201.60
    HTTP: 1 http://10.0.201.60:80/96xxupgrade.txt
    HTTP: 1 -905
    Contacting call server...
    As I mentioned above, I have been attempting to alter some of our configuration files and create new ones, but the deskphones never process the newly updated/created ones. Once the phone receives the HTTP 905 error with the 96xxupgrade.txt file, it just contacts the call server and logs the user into their phone with the existing stored configuration files. When I open the link http://10.0.201.60:80/96xxupgrade.txt through the web browser on my computer, I can see the changes I have made - but this 905 error stops the phone from seeing them.

    Our Call Server (10.0.201.60) is a IP Office 500 (R8) and it hosts everything from the file server (SD Card), HTTP/HTTPS/TFTP server, and DHCP server - the only thing running on a separate box is the Voicemail Server.

    Unless there is something special that I am suppose to do after uploading files to IP Office's SD Card (through the IP Office Manager's File Management tool), I think we have a problem here. To verify that the configuration files are not at fault I have successfully loaded them onto an individual phone using Avaya's MV_IPTel utility.
  • pdgavin
    Guru
    .
    • Aug 2010
    • 167

    #2
    HTTP 905 Error on 96xxupgrade.txt

    Which phones are you using? The older 9600 series phones, 9620L, 9620C, 9630G, 9640, 9640G, 9650, 9650C can be upgraded using the SD card but the newer 96x1 phones require an external HTTP server due to the size of the bin files. If you have installed IIS on the Voicemail Pro server you can use that as your HTTP server. In Manager in the system tab you would put the IP address of that computer as the HTTP server and for Phone File Server Type: leave it as Custom.

    You would have to setup IIS as a file server in the wwwroot folder put all the bin files from the administration DVD.

    Pete

    Comment

    • brgnewman
      Member
      • May 2012
      • 4

      #3
      We currently have a mix of 1616, 9608, 9620L, and 9650C models on our network.

      I just logged into the Avaya IP Office Manager and noticed the following on the System tab:
      TFTP Server IP Address: 10.0.201.61
      HTTP Server IP Address: 10.0.201.61
      Phone File Server Type: Manager
      Manager PC IP Address: 0.0.0.0

      However, 10.0.201.61 is our Voicemail Server and 10.0.201.60 is our IP Office 500 (R8)...so, shouldn't it be:
      TFTP Server IP Address: 10.0.201.60
      HTTP Server IP Address: 10.0.201.60
      Phone File Server Type: Memory Card
      Manager PC IP Address: 0.0.0.0

      The joys of taking over someone else's IT infrastructure!

      EDIT: And yes, the IIS role is not installed on our Voicemail Server.

      Comment

      • brgnewman
        Member
        • May 2012
        • 4

        #4
        I was able to take down our phone system this weekend and switch the Phone File Server Type from Manager to Memory Card.

        After the restart, all our phones came back online and successfully downloaded the 96xxupgrade and 46xxsettings from our IP Office

        Comment

        • pdgavin
          Guru
          .
          • Aug 2010
          • 167

          #5
          http://support.avaya.com/forums/showthread.php?p=4665#post4665

          Good,

          Pete

          Comment

          • psinghsolank
            Hot Shot
            .
            • Jul 2012
            • 12

            #6
            Good to know the issue is resolved

            Comment

            Loading