SIP Trunk Group - Signaling - Registration

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.

• 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.
• Required-group-nonpriority – Use this option to prevent unregistered IADs from making or receiving non-priority calls. All emergency calls are allowed even if the source IP/port fails to fetch RCB.

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

NOTE: In loopback scenarios for SIP-H323 calls, Require Registration must be set to none.

Expires

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.

NOTES:

1. Since the SBC expects an expires value greater than 540 seconds (9 minutes) from the registrar, do not set Inside Expires Minimum value less than 540 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. 
• Follow Ingress – No changes are made to the Egress Register with respect to RFC 6140.

Defines the maximum factor for random number calculation for internal refresh timeout. The range values from 0 to 1000 and the default value is 0.

NOTE: If "Int Refresh Factor Max" is less than "Int Refresh Factor Min" or both "Int Refresh Factor Max" and "Int Refresh Factor Min" are set to 0, the random factors are ignored and the timeouts or the deadlines are calculated using a random number between x and x/2.

Defines the maximum factor for random number calculation for external refresh timeout. The range values from 0 to 1000 and the default value is 0.

NOTE: If "Ext Refresh Factor Max" is less than "Ext Refresh Factor Min" or both "Ext Refresh Factor Max" and "Ext Refresh Factor Min" are set to 0, the random factors are ignored and the timeouts or the deadlines are calculated using a random number between x and x/2.

If enabled, the internal expire timeout will be randomized for the initial and the refresh REGISTER.

If disabled, the internal expire timeout will be randomized for the initial REGISTER.

The options are:

• Disabled (default)
• Enabled

If enabled, the external expire timeout will be randomized for the initial and the refresh REGISTER.

If disabled, the external expire timeout will be randomized for the initial REGISTER.

The options are:

• Disabled (default)
• Enabled

If disabled, Global Loop Detection flag takes precedence.

If enabled, Loop Detection is disabled, irrespective of Global Loop Detection flag.

The options are:

• Disabled (default)
• Enabled

Enable this parameter to allow the SBC to preserve the RCB on receiving error response (4xx/5xx/6xx, except 401, 407, 408, and 7xx) for the Refresh REGISTER.

If disabled, the SBC deletes the RCB.

• Disabled (default)

• Enabled

NOTE:

• If the error response is any of 401, 407, 408, and 7xx, the SBC exhibits the default characteristics even if the parameter is enabled.
• When this parameter is disabled (as the default behavior), and the SBC gets error response for the REFRESH REGISTER, it changes the RCB state from REFRESHING to TERMINATED and starts a 64 second timer. If the SBC receives a Re-REGISTER request (REFRESH or UPDATE) within the next 64 seconds, it does not relay the request to the Registrar and locally responds to the UE with the previously preserved error message (because the RCB state is TERMINATED). However, if the SBC receives an Un-REGISTER request from the UE within the 64 seconds, it deletes the information about the earlier registration failures, and allows the next REGISTER attempt to go through.
• When this parameter is enabled, on receiving an error response for REFRESH REGISTER attempts, the SBC sets the RCB state to COMPLETED instead of TERMINATED. On receiving subsequent REFRESH REGISTER requests, instead of locally relaying the previously stored error message to the UE, the SBC relays the REFRESH REGISTER request to the Registrar. In general, whenever the RCB is COMPLETED, the SBC relays the REFRESH REGISTER requests to the Registrar.