Configure Avaya SBC only on the primary device in an HA deployment.
Procedure
Log on to the EC2 Management Console.
Power off and power on the virtual machine on the EC2 Management Console page.
Use any Windows machine deployed in AWS and Accessible as RDP from client machine to configure the Avaya SBC instance from EMS.
You can log on the EMS GUI from https://<Avaya SBC IP address>/ using following credentials:
Username : ucsec
Password: ucsec
You can log on to the Avaya SBC instance CLI by using port 222 and ipcs user with the password set during installation.
Note:
When you log on the first time, you must change the default password.
Configure Avaya SBC with network, media, signalling interfaces, and other standard Avaya SBC features.
For more information, see Administering Avaya Session Border Controller.
Disable Avaya SBCMedia Anchoring and use Media Tromboning Only in Call Type for Media Unanchoring for a remote worker Avaya SBC configuration on AWS.
On the AWSEC2 Management Console, attach the elastic public IP address to the A1/A2 interface of the device. If you are deploying an HA configuration, you only have to do this on the primary device. The secondary device will be automatically configured.
Use the Allow Reassignment option for the elastic public IP address. Avaya SBC data interfaces A1/A2 and B1/B2 should have secondary IP addresses. These secondary IP addresses are used for all media and signalling configurations.
Important:
Ensure that the InstanceId for a particular SBC is stored in the aws_instance_id column of the Global_nodes table. If the InstanceId is not administered, manually run the following command to store the InstanceId:
HA deployment in Avaya SBC uses elasticity in secondary IP addresses configured in Step 6. During a failover, Avaya application process assigns floating secondary IP addresses to secondary Avaya SBC. Perform the following steps only for an HA deployment:
