In this section:
When the SBC has multiple peers (trunks) on an external/public side and a single large trunk to the C15 on an internal/private side, the C15 uses the tgrp parameter to partition out this large trunk group and to be able to track the destination of outgoing calls on the public side of the SBC, as well as tracking the public trunk from which incoming calls were received.
This requires trunkgroup naming continuity between SBC and C15 configurations.
Provision the Feature Control Profile associated with the trunkgroup facing the C15 so that processDestinationTgrp
is enabled and processDestinationTrunkContext
is disabled. For details, refer to Feature Control Profile - CLI.
Additionally, the trunkgroup referenced in tgrp= parameter of the INVITE message should have an IP Signaling Peer Group assigned which is the IP address and port to which the SBC will route the outgoing INVITE.
set profiles featureControlProfile DEFAULT_IP processDestinationTgrp enable; processDestinationTrunkContext disable; processEnumdi disable; ipProtocolFlags { useIpProtocol enable; defaultCalledUser enable; honorPhoneContextParameter enable; commit
The SBC will not natively place tgrp=”ORIGINATING_TRUNK” in the outgoing R-URI to C15, it will however place tgrp=”ORIGINATING_TRUNK” in the Contact header of the outgoing INVITE message. The IP Signaling Profile on the trunkgroup facing C15 should have egressIpAttributes sipHeadersAndParameters originatingTrunkGroupOptions includeTgrpWithIpAddress
set for this. Additionally the trunkgroup facing the C15 should have the below SMM rule defined as an egress rule to copy the parameter from Contact header to R-URI.
set profiles signaling sipAdaptorProfile AddTgrpToRURI state enabled advancedSMM disabled profileType messageManipulation #Check for tgrp in the Contact header (should be there from originatingTrunkGroupOptions includeTgrpWithIpAddress setting on IPSP) set profiles signaling sipAdaptorProfile AddTgrpToRURI rule 1 criterion 1 type message set profiles signaling sipAdaptorProfile AddTgrpToRURI rule 1 criterion 1 message messageTypes all set profiles signaling sipAdaptorProfile AddTgrpToRURI rule 1 criterion 2 type header set profiles signaling sipAdaptorProfile AddTgrpToRURI rule 1 criterion 2 header name Contact condition exist hdrInstance all set profiles signaling sipAdaptorProfile AddTgrpToRURI rule 1 criterion 3 type parameter set profiles signaling sipAdaptorProfile AddTgrpToRURI rule 1 criterion 3 parameter condition exist paramType userinfo name tgrp #Store tgrp to var1 set profiles signaling sipAdaptorProfile AddTgrpToRURI rule 1 applyMatchHeader one set profiles signaling sipAdaptorProfile AddTgrpToRURI rule 1 action 1 type parameter operation store paramType userinfo set profiles signaling sipAdaptorProfile AddTgrpToRURI rule 1 action 1 to type variable variableValue var1 variableScopeValue local set profiles signaling sipAdaptorProfile AddTgrpToRURI rule 1 action 1 from type parameter value tgrp #Check for R-URI (a formality really so we can apply the action) set profiles signaling sipAdaptorProfile AddTgrpToRURI rule 2 criterion 1 type message set profiles signaling sipAdaptorProfile AddTgrpToRURI rule 2 criterion 1 message messageTypes all set profiles signaling sipAdaptorProfile AddTgrpToRURI rule 2 criterion 2 type header set profiles signaling sipAdaptorProfile AddTgrpToRURI rule 2 criterion 2 header name request-line condition exist hdrInstance all set profiles signaling sipAdaptorProfile AddTgrpToRURI rule 2 criterion 3 variable condition not-equal-to variableID var1 value "" set profiles signaling sipAdaptorProfile AddTgrpToRURI rule 2 criterion 3 type variable #Add var1 (tgrp=xyz) to the R-URI set profiles signaling sipAdaptorProfile AddTgrpToRURI rule 2 applyMatchHeader one set profiles signaling sipAdaptorProfile AddTgrpToRURI rule 2 action 1 type parameter operation add paramType userinfo set profiles signaling sipAdaptorProfile AddTgrpToRURI rule 2 action 1 to type parameter value tgrp set profiles signaling sipAdaptorProfile AddTgrpToRURI rule 2 action 1 from type variable variableValue var1
A Layer 3 routing element must be present between the C15 and Sonus SWe SBC. This requirement ensures a quick failover when the Sonus SWe switches activity between units. If the C15 and Sonus SWe are on the same layer 2 network, the C15 will have a delayed recovery of bearer/media streams when the Sonus SWe switches activity. Typically, a routed network is set up in a redundant fashion employing VRRP or HSRP (Cisco) protocols on the local subnet for default gateway redundancy.