Configuring a Relay Port for TCP Relay

Overview

The SBC Core supports the relaying TCP traffic (in addition to SIP/SDP traffic) with the use of a Relay Profile object and a Relay Port configuration on a per-Zone basis.

The Relay Port is used to establish end-to-end TCP relay connections between the TCP endpoints and the servers. the SBC terminates the connections initiated by the device and initiates connections towards the respective servers. TCP traffic policing and routing are performed based on the SBC local IP and port on which the connection is terminated. The SBC can send policy requests for TCP (along with the other types of protocols such as HTTP, XCAP, SyncML, XMPP, USS) to PSX for further processing.

Procedure

Use the following procedure to accomplish the following:

1. Create a Relay Profile

Create a Relay Profile specifying ingress and egress CAC parameters as well as TCP keep-alive value.

% set profiles services relayProfile RP1 maxEgressConn 10 maxEgressRate 50 maxIngressConn 100 maxIngressRate 80 tcp keepAlive 100

2. Assign the Relay Profile to ingress and egress TCP relay ports

Create an ingress egress TCP relay port and assign the relay profile (Use the IP Address of the SIP Signaling port).

% set addressContext AC1 zone AC1Z1 id 2 relayPort 3 ipAddress 10.7.14.41 portNumber 2024 ipInterfaceGroupName IG1 transportProtocolsAllowed tcp relayProfile RP1 state enabled mode inService

3. Create IP Peer routing label

Create Routing Label for IP Peer.

% set global callRouting routingLabel RL_EGRESS routingLabelRoute 1 routeType ipPeer ipPeer ipPeer1

4. Create a Relay Route to specify how to route incoming call

Create a Relay Route to specify how the call coming in on a particular relay port must be routed.

% set global callRouting route none Sonus_NULL Sonus_NULL relay 3 Sonus_NULL all all ALL none Sonus_NULL routingLabel RL_EGRESS