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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
firmware openstage 40
- Thread starter george82
- Start date
- Thread starter
- #3
- Thread starter
- #5
Hi,
I have one problem:
After starting or receiving a call, the line is dead (I can not hear the other person nor can the person hear me) after a few seconds but the line is still active.
I need to start a conference and then "Retrieve held call" to get the "voice" back. After a while it all starts from the beginning.
I am using the deployment-Pin: 40001998
I am a bit confused cause the Release Notes says.
When upgrading to V3R3 from a version lower than V2R2 it is necessary to upgrade to V2R2 first. If you upgrade directly from V2R0/1 to V3R1 all the stored passwords and certificates will become invalid. For upgrades from V2R0/1 please follow the procedure below, upgrades from V1 are not supported.
For upgrades directly from V2R0/1 to V3R1, the certificates and passwords will be invalid and there is an additional procedure to follow to ensure a smooth upgrade process summarized below:
Prior to upgrade the phone/DLS need to be set to non-secure mode
The certificates should be removed
Upgrade the phone
Re-install the certificates
Set user and admin passwords via DLS
Before upgrading please check the correct SIP port settings. The SIP transport protocol uses port 5061 for TLS and port 5060 for TCP and UDP. The default port setting is 5060. If TLS is used, the port settings must be changed to 5061.
If Web pages are left open during upgrade (e.g. from V2R2 to V3R1), then it is recommended that the web page is refreshed before use on the new version. Failure to do this could result in corrupted display screens and missing configuration, especially with Microsoft IE8.
In General:
A reboot is recommended before performing the upgrade of the SW.
Since V3R3.24.0 the SW is signed and will also only accept Signed SW. The Phone will care about config parameter (default true) and refuse further downloads of SW that is not signed. Any bind will then need to be signed. The config parameter needs to be changed if customer wants to install older software or other not signed SW like trace/test binds.
Can it be a problem that I just upgraded directly to V3?
If so, how can I set the "upgrade-options" mentioned above to upgrade it again with these settings?
Thank you
I have one problem:
After starting or receiving a call, the line is dead (I can not hear the other person nor can the person hear me) after a few seconds but the line is still active.
I need to start a conference and then "Retrieve held call" to get the "voice" back. After a while it all starts from the beginning.
I am using the deployment-Pin: 40001998
I am a bit confused cause the Release Notes says.
When upgrading to V3R3 from a version lower than V2R2 it is necessary to upgrade to V2R2 first. If you upgrade directly from V2R0/1 to V3R1 all the stored passwords and certificates will become invalid. For upgrades from V2R0/1 please follow the procedure below, upgrades from V1 are not supported.
For upgrades directly from V2R0/1 to V3R1, the certificates and passwords will be invalid and there is an additional procedure to follow to ensure a smooth upgrade process summarized below:
Prior to upgrade the phone/DLS need to be set to non-secure mode
The certificates should be removed
Upgrade the phone
Re-install the certificates
Set user and admin passwords via DLS
Before upgrading please check the correct SIP port settings. The SIP transport protocol uses port 5061 for TLS and port 5060 for TCP and UDP. The default port setting is 5060. If TLS is used, the port settings must be changed to 5061.
If Web pages are left open during upgrade (e.g. from V2R2 to V3R1), then it is recommended that the web page is refreshed before use on the new version. Failure to do this could result in corrupted display screens and missing configuration, especially with Microsoft IE8.
In General:
A reboot is recommended before performing the upgrade of the SW.
Since V3R3.24.0 the SW is signed and will also only accept Signed SW. The Phone will care about config parameter (default true) and refuse further downloads of SW that is not signed. Any bind will then need to be signed. The config parameter needs to be changed if customer wants to install older software or other not signed SW like trace/test binds.
Can it be a problem that I just upgraded directly to V3?
If so, how can I set the "upgrade-options" mentioned above to upgrade it again with these settings?
Thank you
- Status