9620L issue 1

[Class26]

thread690-1569972


I am having what seems to be the exact same issue.

We are using CM
System: G3xV13 Software Version: R013x.01.5.642.3

I am trying release 3.1 on the firmware side but have also tried older releases and there is no difference.

Basically a 9620 phone works perfectly. Loads the update and reads the settings file then saves, reboots and comes up ready to use.

The 9620L phone seems to talk to the DHCP fine, and even connects with the HTTP server and reads the 96xxupgrade file, then gives the 1 -906 line and then flashes to " Bad FileSv Address "..


Any help would be greatly appreciated.

Clayton

 

[Class26]

Well, We discovered a solution. Ill write it in if anyone finds this at a later time.


We had 2 seperate issues occuring, the one mentioned above getting Bad FileSv Address was an issue with our DHCP scope. There was an entry for DSN Domain name. The newer phones were searching only that domain.

For example. the DNS Domain name is rrisd.local... The Http server was set to Avayaphone.rrasd.org

The 9620L Phone read and searched for Avayaphone.rrasd.org.rrisd.local

The 9620 / 9650 phones ignored that field and searched and found avayaphone.rrasd.org

The other issue we had was a known issue for avaya. The 9620L phones out of the box were R3.0. When updating them to 3.1 we had an issue where the phones would get stuck in the data vlan. A simple addition to the 96xx upgrade file resolved this issue.

https://support.avaya.com/css/P8/documents/100092537

Here is the link, according to their products affected category the phones did not have the issue but it did fix the problem for us.

Hope it helps if anyone has similar issues.

 

[atervoort]

Thanks Class26 this fixed our very similar issue !