Sorry to beg like everyone else, but I do have access to the Unify portal but am not allowed to download system software/firmware because I am identified as "CUST" status so they won't let me at the software. I can download clients and DERT and things like that, and I have the software release notes, but I guess if you're going to post the image you should include those for everyone else's benefit.
Also, how many of you folks out there use the DLS server? Mine has been working fine for over a year, but the last couple months or so I have been having problems getting it to autodeploy. I create the new phone with @MAC, put in all the relevant initial data, assign the profile, assign the station number in the gateway area, etc, like I have done 100 times. The phone boots up and Sees the DLS server, but sits on enter terminal number and does not go past. If I enter the terminal number on the phone and save it a new record is created for that phone in the DLS - same MAC address and everything, even though there is already a record for that phone with the @ and etc specified. When it creates the new record it of course does not have the profile and gateway settings so the phone will sit there in telephony down mode. In oder to get it going I have to remote into my office, delete the original record I initially set up and modify the one the phone created before the phone will go on line. I don't know all the intricacies of the DLS server, but I have been using it for about 16 months and have never had any problems.
Only things changed recently are that the vendor tech performed a software upgrade (but this started a while before that), and when he did that upgrade he renamed all of the phone profiles to correct a mistake he made when he first built the system, which introduces a whole new set of problems for later on down the road, but neither of those issues have anything to do with the autodeployment process (the profile name issue only affects existing phones and not new ones).
I am wondering if my fellow IT buddies may have changed any of the settings we put into the network switches for VOIP, or if any other network issue could be causing this??
THANKS!
Also, how many of you folks out there use the DLS server? Mine has been working fine for over a year, but the last couple months or so I have been having problems getting it to autodeploy. I create the new phone with @MAC, put in all the relevant initial data, assign the profile, assign the station number in the gateway area, etc, like I have done 100 times. The phone boots up and Sees the DLS server, but sits on enter terminal number and does not go past. If I enter the terminal number on the phone and save it a new record is created for that phone in the DLS - same MAC address and everything, even though there is already a record for that phone with the @ and etc specified. When it creates the new record it of course does not have the profile and gateway settings so the phone will sit there in telephony down mode. In oder to get it going I have to remote into my office, delete the original record I initially set up and modify the one the phone created before the phone will go on line. I don't know all the intricacies of the DLS server, but I have been using it for about 16 months and have never had any problems.
Only things changed recently are that the vendor tech performed a software upgrade (but this started a while before that), and when he did that upgrade he renamed all of the phone profiles to correct a mistake he made when he first built the system, which introduces a whole new set of problems for later on down the road, but neither of those issues have anything to do with the autodeployment process (the profile name issue only affects existing phones and not new ones).
I am wondering if my fellow IT buddies may have changed any of the settings we put into the network switches for VOIP, or if any other network issue could be causing this??
THANKS!