Administering Avaya Aura Media Server signaling group on Communication Manager

Last Updated : Jan 24, 2023 |

About this task

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.

Procedure

  1. On the CLI, type the add signaling-group x command.
  2. Press Enter.
  3. On the SIGNALING GROUP screen, set Group Type to SIP.
  4. Set Transport Method to one of the following:

    • TCP

    • TLS

  5. Set Peer Detection Enabled ? to n.
  6. Set Peer Server to AMS.
  7. 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.

    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


  Peer Detection Enabled? n  Peer Server: AMS



   Near-end Node Name: procr                 Far-end Node Name: AMS
 Near-end Listen Port: 9061                Far-end Listen Port: 5061
                                        Far-end Network Region: 1

Far-end Domain: 172.30.32.49