Page History

...

...

SBC supports processing Destination Trunk Group (DTG) and Originating Trunk Group (OTG) parameters received in Contact and Request-URI messages, and transparently passing this information or inserting it in response messages or egress INVITE headers. When configured this way, even if OTG or DTG values are included in the received messages they are not used in processing of trunk group values for response and egress.

If the PES receives destination trunk group parameters (tgrp and trunk-context) in the policy request and if “Process Destination Tgrp” and “Process Destination Trunk Context” flags are enabled for the ingress trunk group, PES performs a light policy lookup and skips full policy dip. In this scenario, the ERE uses the trunk group name received in the tgrp parameter (similar to the dtg parameter). Also, the trunk-context parameter value is ignored. If DTG is present, it is also ignored.

...

• Associate the profile with a SIP trunk group:

  Code Block
  language none
  % set addressContext default zone defaultSigZone sipTrunkGroup defaultDEFAULT_TG policy featureControlProfile DEFAULT_IP

Routing Calls to ASX or SIP Server Using defaultSigZone

...

% set addressContext default zone defaultSigZone sipTrunkGroup defaultSipTrunkGroup ingressIpPrefix 10.7.6.40 32
% set addressContext default zone defaultSigZone sipTrunkGroup defaultSipTrunkGroup media mediaIpInterfaceGroupName DLIG
% set addressContext default zone defaultSigZone sipTrunkGroup defaultSipTrunkGroup state enabled mode inServicinService

SIP Signaling Port

% set addressContext default zone defaultSigZone sipSigPort 1 ipAddressV4 10.7.15.146 portNumber 5060 transportProtocolsAllowed sip-udp
% set addressContext default zone defaultSigZone sipSigPort 1 ipInterfaceGroupName DLIG
% set addressContext default zone defaultSigZone sipSigPort 1 mode inService state enabled

See zone sipTrunkGroup Zone - SIP Trunk Group - CLI for command syntax and parameter descriptions.

...