You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

This profile specifies the configuration for Surrogate Registration.

To View and Edit Surrogate Registration

On SBC main screen, go to Configuration > System Provisioning > Category: Trunk Provisioning > Ip Peer > Surrogate Registration. The Surrogate Registration window is displayed.

The Surrogate Registration can be checked for each Address Context, for each Zone, for each Ip Peer created or for all the Address Contexts, Zones and Ip Peers created. Use the drop-down box to select the desired Address Context, Zone and Ip Peer.

Ip Peer - Surrogate Registration Main Fields

 

The Edit Surrogate Registration window is displayed.

Policy - Surrogate Registration Edit Window

 

The following fields are displayed:

IP Peer - Surrogate Registration Parameters

 


Parameter


Description

User Part

Specifies the user part for this Surrogate Registration.

Auth User Name

Specifies the authorization User Name for surrogate registration. The value ranges up to 127 characters.

The SBC is enhanced to remove character restrictions for Auth User Name. The valid value for Auth User Name is a string up to 127 characters.

Retry Timer

Specifies the time, in milliseconds, after which the REGISTRATION is retried after a failure. The Value range from 50 - 10000000 milliseconds. The default value is 900000 milliseconds (15 minutes).

Reg Auth
Password

Specifies the DES3 (triple Digital Encryption Standard) encrypted string authentication password for surrogate registration. All ASCII characters from 33 to 126 (except 34 - double quotes) are allowed. SBC users "Admin" and "Operator" have full access to surrogate registration passwords.

If Reg Auth Password contains ASCII characters, enclose the entire password string with " " (double quotes).

Example using double quotes
"1234567890123456789012340\!$$@#$!@#!@#!@#"

"Field Service" and "Guest" users do not have access to Reg Auth Password field.

State

Specifies if the Surrogate Registration should be enabled or not.

The options are:

  • enabled
  • disabled
Send Credentials

Defines how the Credentials are sent. Options are:

  • challengeForAnyMessage – The SBC sends credentials for REGISTER, INVITE, PRACK, UPDATE, REINVITE and BYE when these messages are challenged.
  • challengeForAnyMessageAndInDialogRequests – The SBC sends credentials for REGISTER, INVITE, PRACK, UPDATE, REINVITE and BYE when these messages are challenged. The SBC also sends credentials by default as per last challenge in the in-dialog requests such as PRACK, UPDATE, REINVITE and BYE when any one of these methods is challenged earlier in the call.
  • challengeForRegister (default) – The SBC sends credentials only for REGISTER when challenged. Challenges for any other messages are returned to the IP-PBX.

Refresh REGISTER and De-REGISTER are always sent without credentials. If such a REGISTER is challenged, then SBC responds with a new REGISTER with credentials.

The SBC mirrors the credentials to the standby of an HA System. If the sendCredentials is set to 'challengeForAnyMessageAndInDialogRequests', upon a switchover the SBC can send in-dialog requests such as REINVITE/UPDATE/BYE with credentials.

Suppress Reg Retry After Auth Fail

Use this flag to control sending registration retries when a REGISTER with credentials is challenged (with stale ≠ true and realm is identical to previous realm received).
When stale = true or realm is not identical to previous realm received, the SBC immediately sends REGISTER.

  • disabled (default) – Send REGISTER when a 401 or 407 in response to REGISTER with credentials is received.
  • enabled – Do not attempt to send REGISTER after receiving a 401 or 407 response.
Surr Reg ProfileSpecifies the name of the Surrogate Registration Profile.
Use Next Surr Reg For Call

When this flag is enabled, it tries to use the next available pilot number to resend the INVITE.

Crank back profile should be configured for 4xx (403) response.

Use User Name As PAI

 When this flag is enabled, the configured userName in surrogateRegistraion should be used as userName in the outgoing INVITE.

This flag indicates sending PAI in outgoing Invite. The flag, Include Privacy must be disabled:

Host Part When this flag is configured with a name, the assigned name is used as a hostname of RURI, FROM, TO headers of all outgoing calls.

Make the required changes and click Save at the right hand bottom of the panel to save the changes made.

 

  • No labels