You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

This page describes CLI syntax and parameters for the SIP Trunk Group 'callRouting' object.

Use this object to configure the method to route a call or request to the next-hop entity for this SIP trunk group.

 

As a best practice, always use UPPERCASE for trunk group names.

Command Syntax

% set addressContext <name> zone <name> sipTrunkGroup <name> callRouting 
	addStoredPathAsTopRoute <disabled | enabled>
	ansSupervisionTimeout <0-1000>
	ansSupervisionTimeoutAction <release | trapAndRestart>
	crankBackProfile <profile name>
	dnsCrankback <disabled | enabled>
	internationalNoaPlus <disabled | enabled>
	useRouteSet <disabled | received | stored | storedAll>

Command Parameters

Zone SIP Trunk Group Parameters

ParameterLength/RangeDescription
addStoredPathAsTopRouteN/AWhen enabled, adds the stored Path header as the topmost Route header (on top of stored Service-Route headers) in the   outgoing out-of-dialog requests when useRouteSet is set to "stored".
  • disabled (default)
  • enabled
ansSupervisionTimeout0-1000Configure this parameter on the ingress trunk group specifying the timeout period (in seconds) for the egress trunk group to receive the first backwards message from the called party exchange (SIP 180 - “Ringing" and SIP 183 - “Progress") until the call is answered. If the timeout period expires, the answer supervision action specified is triggered. A value of "0" disables this timer (default = 300).
ansSupervisionTimeoutActionN/AAction to take if the answer supervision timer expires.
  • release (default)
  • trapAndRestart 
crankbackProfileN/ACrankback profile name.
dnsCrankbackN/A

Enable flag to apply DNS crankback profile for the received SIP error response.

  • disabled (default)
  • enabled
internationalNoaPlusN/AEnable flag to set CPN and CIN NOA to “International” when number begins with '+'.
  • disabled (default)
  • enabled
useRouteSetN/AThis parameter determines the routeset used when routing a call.
  • disabled (default) – Request is routed using routing database.
  • received – Request is routed using the received routeset in the request.
  • stored – Request is routed using Path or Service-Route stored during registration.
  • storedAll – All requests (including refresh registers) are routed using Path or Service-Route stored during registration.
  • No labels