Page History

Require Registration

N/A

 Use this

feature 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-

• group
  • If this option is selected for an ingress IP trunk group concerning 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 the existing registration in the zone, messages are accepted.
  • If this option is selected for an egress IP trunk group concerning 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 

• • If this option is selected for an ingress IP trunk group

• • concerning a received call (

• • for example, a call from the IP-PBX towards the 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

• • the existing registration in the zone, messages are accepted.
  • If this option is selected for an egress IP trunk group

• • concerning a received call (

• • for example, a call from the AS towards the IP-PBX), the user part check between registered AoR and Request-URI of the INVITE does not occur, and the call is accepted.

• • This flag also prevents unregistered IADs from making or receiving non-priority calls. All emergency calls are allowed even if the source IP/port fails to fetch RCB.
• 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.

NOTE:

Set Require Registration

to

"Supported-

group" for the IP Peer on

which surrogate registration functionality is

enabled.

NOTE: In loopback scenarios for SIP-

H.323 calls, you must set Require Registration

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

NATted.

The default value is 3600.

Inside Expires Minimum

0-100000

 Controls the initial expire value (in seconds) in a REGISTER relayed to a registrar.

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

N/A

 Enable this flag to insert the X

-ORIGINAL-ADDR header into the REGISTER message. 

• Disabled (default) 
• Enabled

Bulk Register Format

N/A

 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 minimum factor for random number calculation for internal refresh timeout.

The default value is 0.

0-1000

Defines the maximum factor for random number calculation for internal refresh timeout.

The default value is 0.

NOTE: If

Int Refresh Factor Max

 is less

than Int Refresh Factor Min

or

if both parameters 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 minimum factor for random number calculation for external refresh timeout.

The default value is 0.

0-1000

Defines the maximum factor for random number calculation for external refresh timeout.

The default value is 0.

NOTE:

If Ext Refresh Factor Max

 is less than

Ext Refresh Factor Min

, or

if both parameters 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.

N/A

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.

• Disabled (default)
• Enabled

N/A

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.

• Disabled (default)
• Enabled

N/A

If disabled, the Global Loop Detection flag takes precedence.

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

• Disabled (default)
• Enabled