| Excerpt |
|---|
This profile specifies the configuration for Surrogate Registration. To View and Edit Surrogate RegistrationOn the SBC main screen, go |
...
...
...
...
...
...
> 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  Image Modified
The Edit Surrogate Registration window is displayed. |
...
Policy - Surrogate Registration Edit Window Image Modified |
The following fields are displayed:
Table 1: IP Peer - Surrogate Registration Parameters
Parameter Descriptions: Parameter | Description |
|---|
User Part | Specifies the user part for this Surrogate Registration. | | Auth User Name | |
|
...
authorized User Name for surrogate registration. The value ranges up to 127 characters. | Note |
|---|
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. | Note |
|---|
If 'Reg Auth Password' contains ASCII characters, enclose the entire password string with " " (double quotes). |
| Code Block |
|---|
| language | none |
|---|
| title | Example using double quotes |
|---|
| "1234567890123456789012340\!$$@#$!@#!@#!@#" |
| Note |
|---|
"Field Service" and "Guest" users do not have access |
|
|
...
...
| State | Specifies if the Surrogate Registration should be enabled or not. The options are: | | Send Credentials | Defines how the Credentials are sent. Options are: - Challenge For Any Message
|
|
...
- – The SBC sends credentials for REGISTER, INVITE, PRACK, UPDATE, re-INVITE and BYE when these messages are challenged.
- Challenge For Any Message And In Dialog Requests
|
|
...
- – The SBC sends credentials for REGISTER, INVITE, PRACK, UPDATE, re-INVITE and BYE when these messages are challenged. The SBC also sends credentials by default as per the last challenge in the in-dialog requests, such as PRACK, UPDATE, re-INVITE and BYE when any one of these methods is challenged earlier in the call.
- Challenge For Register (default) –
|
|
...
- When challenged, the SBC sends credentials only for REGISTER
|
|
...
- . Challenges for any other messages are returned to the IP-PBX.
| Note |
|---|
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. |
| Note |
|---|
The SBC mirrors the credentials to the standby of an HA System. If the Send Credentials is set to 'Challenge For Any Message And In Dialog Requests', upon a switchover, the SBC can send in-dialog requests such as re-INVITE/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 the 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 Profile | Specifies 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. |
|
...
Ensure to configure the Crankback Profile for 4xx (403) response. |
| | Use User Name As PAI | When this flag is enabled, the SBC uses the configured User Name in Surrogate Registration as the User Name in the outgoing INVITE. |
|
...
sending a PAI in the outgoing Invite. Ensure the flag 'Include Privacy' is disabled to use this feature. |
| | Host Part | When this flag is configured with a name, the assigned name is used as |
|
...
...
| of RURI, FROM, TO headers of all outgoing calls. |
Make the required changes and |
...