Versions Compared

Old Version 2

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version 3

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

 

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

Command Syntax

Code Block
languagenone
% 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>
	sendRouteUriToPsx <disabled | enabled>
	useRouteSet <disabled | rcbNextHopAndStored | received | roamingOrStored | stored | storedAll>

Command Parameters

Caption
0Table
1Zone 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
sendRouteUriToPsxN/A

Use this flag to control the sending of Route-URI to PSX.

  • disabled (default) – Route-URI is not sent to PSX.
  • enabled – Route-URI is sent to PSX
Note

This flag works in conjunction with "Perform Route Header based Routing" flag configured from PSX Feature Control Profile screen. See PSX documentation for details.

useRouteSetN/AThis parameter determines the routeset used when routing a call.
  • disabled (default) – Request is routed using routing database.
  • rcbNextHopAndStored – Request from a registered subscriber is routed to the same next hop (registrar IP stored in registration), and the stored Service Route is copied to egress.
  • received – Request is routed using the received routeset in the request.
  • roamingOrStored – If the UE is in roaming mode, request is routed based on Destination Trunk Group (DTG) loopback where DTG is the route obtained during REGISTRATION. If UE is not in roaming, the request is routed in same manner as stored option.
  • 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.
Note

Attributes rcbNextHopAndStored and roamingOrStored are not supported on ERE and are intended for use with an external PSX and/or ePSX only.