PSN100180 – Some IP phones are not automatically forced to unregister from the LSP/ESS and register back to their main server after an LSP/ESS server falls back to the main.


Doc ID:    PSN100180
Version:    1.0
Status:    Published
Published date:    09 Aug 2013
Author:   
heetland
 

Severity

High

Urgency

When Convenient

Releases

Avaya Aura® Communication Manager (CM), Releases 6.3; Avaya Aura® Solution for Midsize Enterprise, Releases 6.2.x

Problem Description

This problem occurs in Avaya Aura® Communication Manager (CM) Release 6.3.

 

Some IP phones are not automatically forced to unregister from the LSP/ESS and register back to their main server after an LSP/ESS server falls back to the main. This can result in an invalid configuration when IP phones are forced off an LSP or ESS due to automatic fallback of survivable servers. Some IP phones will be registered with an inactive survivable server.

 

This occurs because there is a problem with the associated “disable nr-registration” System Access Terminal (SAT) command, which is used to move endpoints between main servers and survivable servers, depending on the situation. The problem happens when there are more than 10 IP phones in the network region. Only the first 10 phones in the network region will be forced to unregister instead of all of them. This can result in a configurations with IP phones remaining registered to undesirable servers that may not have VoIP resources to service them. The “disable nr-registration” SAT command is used for automatic fallback of survivable servers, the split registration feature, and can also be used manually by running the command on the SAT.

 

Also affected by this problem is the split registration feature which uses the “disable nr-registration” command to automatically disable network regions to force phones and H.248 Media Gateways off main servers to their associated survivable server. If split registration is in effect, only the first 10 IP phones will be forced off the main server.

Workaround / Alternative Remediation

Manually force phones to unregister (force unregister) in the impacted network regions.

Resolution

This problem is fixed in CM 6.3 Service Pack (SP) 1 (20850) and higher SPs/Releases.

Patch Availability

Available via Download

Patch Version/ID

CM 6.3 SP 1 (20850) and higher SPs/Releases

Patch Download URL

https://support.avaya.com

Patch Impact

Refer to Patch Installation Notes

Patch Installation Notes

Patch installation instructions are available on “support.avaya.com”.

 

CM Service Pack/patch activation is service impacting on non-duplicated servers, and on all servers running CM 5.2 and lower releases. For servers running CM 5.2.1 and higher releases, SPs/patches can be activated in a connection preserving manner.

Patch Removal Notes

Patch installation (activation) instructions include removal (deactivation) instructions.

Patch Success/Failure Verification

Patch installation instructions include verification instructions. Contact Technical Support regarding patch failures.

Avaya Security Vulnerability Classification

Not Applicable

PSN Contacts & Disclaimer

For additional support, contact your Authorized Service Provider. Depending on your coverage entitlements, additional support may incur charges. Support is provided per your warranty or service contract terms unless otherwise specified.

Avaya Support Contact

Telephone
U.S. Remote Technical Services - Enterprise 800-242-2121
U.S. Remote Technical Services – Small Medium Enterprise 800-628-2888
U.S. Remote Technical Services – BusinessPartners for Enterprise Product 877-295-0099
BusinessPartners for Small Medium Product Please contact your distributor.
Canada 800-387-4268
Caribbean and Latin America 786-331-0860
Europe, Middle East, and Africa 36-1238-8334
Asia Pacific 65-6872-8686

Disclaimer: ALL INFORMATION IS BELIEVED TO BE CORRECT AT THE TIME OF PUBLICATION AND IS PROVIDED "AS IS". AVAYA INC., ON BEHALF OF ITSELF AND ITS SUBSIDIARIES AND AFFILIATES (HEREINAFTER COLLECTIVELY REFERRED TO AS “AVAYA”), DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND FURTHERMORE, AVAYA MAKES NO REPRESENTATIONS OR WARRANTIES THAT THE STEPS RECOMMENDED WILL ELIMINATE SECURITY OR VIRUS THREATS TO CUSTOMERS’ SYSTEMS. IN NO EVENT SHALL AVAYA BE LIABLE FOR ANY DAMAGES WHATSOEVER ARISING OUT OF OR IN CONNECTION WITH THE INFORMATION OR RECOMMENDED ACTIONS PROVIDED HEREIN, INCLUDING DIRECT, INDIRECT, CONSEQUENTIAL DAMAGES, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF AVAYA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
THE INFORMATION PROVIDED HERE DOES NOT AFFECT THE SUPPORT AGREEMENTS IN PLACE FOR AVAYA PRODUCTS. SUPPORT FOR AVAYA PRODUCTS CONTINUES TO BE EXECUTED AS PER EXISTING AGREEMENTS WITH AVAYA.

All trademarks identified by ® or TM are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners.
 



Avaya -- Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy