This screen defines the parameters controlling registration relay behavior.
To View and Edit Registration
On the SBC main screen, go to Configuration > System Provisioning > Category: Trunk Provisioning > Trunk Group > SIP Trunk Group > Signaling > Registration.
The Registration window is displayed.
SIP Trunk Group - Signaling - Registration
The following fields are displayed:
SIP Trunk Group - Signaling - Registration
Parameter | Description |
---|
Require Registration | Use this flag to specify the type of endpoint registration validation required. 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 | 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. NOTES: - 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.
- 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.
|
Int Refresh Factor Min | Defines the minimum factor for random number calculation for internal refresh timeout. The range values from 0 to 1000 and the default value is 0. |
Int Refresh Factor Max | 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. |
Ext Refresh Factor Min | Defines the minimum factor for random number calculation for external refresh timeout. The range values from 0 to 1000 and the default value is 0. |
Ext Refresh Factor Max | 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. |
Always Random Int Expires | 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
|
Always Random Ext Expires | 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
|
Use RUri For Register Routing | 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
|
Preserve Rcb On Refresh Register Err Response | 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.
|
Make the required changes and click Save at the right hand bottom of the panel to save the changes made.