trainedMonkey
Technical User
i have various 4600 series IP phones (4602, 4620, 4621), and they all have to time out the http before they will just tftp the files. is there a way to configure them to just tftp (or tftp first)?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
4600 ip phone tftp only?
- Thread starter trainedMonkey
- Start date
- Status
This was released with 2.3 IP Phone Firmware the code asks the Phone to try and Download the Firmware via HTTPS and Then HTTP and finally via TFTP.
There is no way to disable this as it is enterprise code running in a IPO environment.
More information on the HTTPS Interface -
As it is NON Standard on the IP Office
The 56xx only support port 411 (not 441 or 443 or anything else) for TLS config file downloading. TLS downloading currently requires the server to have an Avaya-signed certificate, and as far as I know, only CM and MV Express support this for phones.
We use port 411 because CM uses the well-known port for TLS (443) for CM web administration. It is in the 56xx code because it is in the 46xx code, but unless IP Office has an Avaya certificate and supports a TLS server on port 411, you should NOT claim that the 56xx support TLS downloading or the AUTH system value (or HTTPS backup/restore in R2.8), since the 56xx cannot operate on CM. The IP Office cannot provide the certificate; the code is only in the 56xx code because it is in the 46xx code.
I Really wish AVAYA would make the code that comes with with the releases to support what the IP Office Supports and not cut corners by using CM code.
Your thoughts People. ?
"Launching late 2006
There is no way to disable this as it is enterprise code running in a IPO environment.
More information on the HTTPS Interface -
As it is NON Standard on the IP Office
The 56xx only support port 411 (not 441 or 443 or anything else) for TLS config file downloading. TLS downloading currently requires the server to have an Avaya-signed certificate, and as far as I know, only CM and MV Express support this for phones.
We use port 411 because CM uses the well-known port for TLS (443) for CM web administration. It is in the 56xx code because it is in the 46xx code, but unless IP Office has an Avaya certificate and supports a TLS server on port 411, you should NOT claim that the 56xx support TLS downloading or the AUTH system value (or HTTPS backup/restore in R2.8), since the 56xx cannot operate on CM. The IP Office cannot provide the certificate; the code is only in the 56xx code because it is in the 46xx code.
I Really wish AVAYA would make the code that comes with with the releases to support what the IP Office Supports and not cut corners by using CM code.
Your thoughts People. ?
"Launching late 2006
- Status
Similar threads
