Skip to end of metadata
Go to start of metadata

This objects defines the parameters controlling registration relay behavior.

Figure : Sip Trunk Group - Signaling - Registration

The fields displayed are:

Table : Sip Trunk Group - Signaling - Registration

Parameter

Description

Require Registration

 Use this flag to specify the type of endpoint registration validation required. 

  • none – (default) No registration validation is required. 
  • required –  Prevent unregistered IADs from making or receiving any calls. 
  • required-nonpriority – Prevent unregistered IADs from making or receiving non-priority calls. Since priority calls are exempt, unregistered endpoints are still allowed to make priority calls. 
  • supported –  Accept registrations from unregistered endpoints when the associated trunk group is used for endpoints optionally requiring registration. If an endpoint is registered, then the registration data is used to send calls to that   endpoint instead of PSX route. 
  • supported-group   – Accept registrations from unregistered users and from users whose user   names do not match with the stored URI in Registration Control Block. If an endpoint is registered, then the registration data is used to send calls to   that endpoint instead of PSX route.

  • Availability: Since 4.2.2

    required-group
      – If this option is selected for an ingress IP trunk group in relation to a received call (e.g. call from IP-PBX towards AS) so that if the source IP address and port of the INVITE/OOD request do not match the source IP address and port of an existing registration in the zone, they are rejected. However, if the AOR does not match, but if the source IP Address and the port match to the existing registration in the zone, messages are accepted.
    If this option is selected for an egress IP trunk group in relation to a received call (e.g. call from AS towards IP-PBX), the user part check between registered AoR and Request-URI of the INVITE does not occur, and the call is accepted.
  • Availability: Since 4.2.2

    required-group-nonpriority
     – Use this option to prevent unregistered IADs from making or receiving non-priority calls. The semantics are equivalent to required-group but all emergency calls are allowed even if the source IP/port fails to fetch RCB.

Set Require Registration flag to ‘supported-group’ for the IP Peer on which surrogate registration functionality is being enabled.

Expires

 The time (in seconds) a SIP endpoint's registration session lasts before requiring re-registration. This value does not apply if the endpoint is NAT'd. The value ranges from 15 to 65535 and the default value is 3600.

Inside Expires Minimum

 Controls the initial expire value (in seconds)   in a REGISTER relayed to a registrar. The value ranges from 0 to 65535 and the default value is 3600.

  1. Since the  SBC expects an expires value greater than 480 seconds (8 minutes) from the registrar, do not set “insideExpiresMinimum” value less than 480 seconds. Ideally, set this value much higher (3600 seconds is recommended) to avoid overloading registrar with register refreshes.
  2. When configuring surrogate registration, be sure to set the expires value of ingress trunk group toward IAD to the maximum default value of “3600”.

Include XOriginal Addr

 Enable this flag to insert the X Original Addr header into REGISTER message. 

  • disabled (default) 
  • enabled

Bulk Register Format

 Use this flag to determine how the   registration requests are formatted with respect to RFC 6140. 

  • disabled (default) – REGISTER message is not formatted as per RFC 6140. 
  • enabled – REGISTER message is formatted as per RFC 6140. 
  • followIngress – No changes are made to the Egress Register with respect to RFC 6140.