Creating a trunk server flow

Last Updated : Jan 08, 2024 |

Procedure

  1. Log in to the EMS web interface with administrator credentials.
  2. From the Device menu, click the SBC name to administer.
  3. Navigate to Network & Flows > End Point Flows.

    The system displays the End Point Flows page.

  4. In the Server Flows tab, click Add.

    The system displays the Add Flow page.

  5. In the Flow Name field, type a name for the server flow.

  1. Unless the customer has special requirements, use the default (*) values for the URI Group, Transport, and Remote Subnet options.

  1. In the Signaling Interface field, click the name of the interface that receives all of the SIP traffic from the trunk server.
  2. In the Media Interface field, select the name of the interface that receives all media traffic from the trunk.

  1. In the End Point Policy Group field, use the default value: default-low.
    Note:

    If the phones use TLS/SRTP, select the appropriate end policy group.

  2. In the Routing Profile field, click the name of the routing profile that points toward the trunk server.
  3. In the Topology Hiding Profile field, keep the default value or select the appropriate topology hiding profile.
  4. In the Signaling Manipulation Script field, select the signaling manipulation script to be used for the server flow.
  5. In the Remote Branch Office field, keep the default value Any or select another remote branch office.

    The Remote Branch Office field lists all servers configured for remote branch office.

  6. Enable the Link Monitoring from Peer option to enable handling of incoming SIP OPTIONS messages.

    The Link Monitoring from Peer option is used to support the Avaya Aura® SIP Resiliency feature. Avaya SBC must support the SIP Resiliency feature in the OPTIONS response Contact header. Session Manager should know the SIP Resiliency supported for neighboring elements to change the call/message sequence behavior for the Session Manager failover/failback scenarios.

    When Link Monitoring from Peer is enabled, Avaya SBC sends a success (200OK) response if the OPTIONS request is matched to that server flow.

    When Link Monitoring from Peer is disabled, the OPTIONS request is relayed to the destination server.

  7. Click Finish.