Use the following task to add an Avaya Aura® Media Server (MS) signaling group.
Before you begin
Ensure that you have configured the node name of Avaya Aura® MS using the change node-names ip command.
For more information, see Administering Avaya Aura® Communication Manager.
On the CLI, type the add signaling-group x command.
Press Enter.
On the SIGNALING GROUP screen, set Group Type to SIP.
Set Transport Method to one of the following:
TCP
TLS
Set Peer Detection Enabled ? to n.
Set Peer Server to AMS.
Set the node name of Avaya Aura® MS.
For TCP, the default value for both Near-end Listen Port and Far-end Listen Port is set at 5060. To use TCP as a Transport method, you must add Communication Manager as trusted node in the respective Avaya Aura® MS.
For TLS, the Near-end Listen Port default value is set at 9061, and the Far-end Listen Port is set at 5061.
ADDITIONAL INFORMATION:
Note:
The Far-end Node Name can only contain a node name that has an IPv4 address. The system displays an error if the node name does not have an IPv4 address.
The Far-end Domain is auto-populated and viewable as read-only with the IP address of the media server based on the Far-end Node Name.
The Near-end Node Name is read-only and is auto-populated with the string procr.
change signaling-group 3 Page 1 of 2 SIGNALING GROUP
Group Number: 3 Group Type: sip Transport Method: tls
