|Sonus Documentation Portal|
Use this window to create and configure a static IP Peer in a zone.
If an IP Peer is configured to use an FQDN port (other than port 5061), the SBC increments the configured port number by 1 and uses it as the new port number for SIP over TLS signaling.
If the IP Peer is configured to use port 5061 and the transport is TLS, no changes are made to the configuration.
On the SBC main screen, go to Configuration > System Provisioning > Category: Trunk Provisioning > IP Peer. The IP Peer window is displayed. The IP Peer list can be filtered by Address Context and/or Zone using the drop-down lists.
To create a new IP Peer, click New IP Peer. The Create New IP Peer window is displayed.
The following fields are displayed:
The name of the IP Peer.
Specifies the IPv4 or IPv6 address of the peer.
The IP port for this peer.
Default for IP
Set to 'true' if this peer should be used for the IP Address and ephemeral port on ingress, or 'false' if this peer will not be used for the IP Address and ephemeral port on ingress.
|SIP Response Code Stats|
Specifies whether SIP response code statistics are collected for the IP Peer.The options are:
Enabling the collection of statistics on trunk groups or IP peers may have significant impact on network performance of an SBC system under heavy load.
|CAC Profile||Specifies the SIP endpoint CAC profile for the IP peer.|
|Description||Specifies the description of this IP Peer.|
|Specifies the name of the Packet Service Profile used for this IP Peer.|
|Specifies the name of the IP Signaling Profile used for this IP Peer.|
|Policy - SIP|
|FQDN||Specifies the FQDN value to use for sending egress calls/requests to the IP peer.|
|Specifies the FQDN port number for sending egress calls/requests to the IP Peer.|
|Profile||Specifies the path check profile name used for OPTIONS ping.|
|Host Name||Specifies the FQDN value of the peer. It will be resolved using DNS and the resulting servers will be pinged using SIP OPTIONS requests. The value ranges up to 63 characters.|
|Host Port||Specifies the TCP/UDP port number of the peer. The peer's servers will be pinged using SIP OPTIONS requests at this port. The value ranges from 0 to 65535 and the default value is 0.|
Specifies if the active pinging is enabled or not. The options are:
Specifies if the status update support should be enabled for this peer or not. The options are:
|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.|
|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).
"Field Service" and "Guest" users do not have access to Reg Auth Password field.
Specifies if the Surrogate Registration should be enabled or not. The options are:
|Send Credentials|| |
Defines how the Credentials are sent. Options are:
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
|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).
|Surr Reg Profile||Specifies the name of the Surrogate Registration Profile.|
|User Next Reg Call For Call|
When this option is enabled, it tries to use the next available pilot number to resend the INVITE.
Crankback profile should be configured for 4xx (403) response.
|Use User Name As PAI|
When this option is enabled, the configured User Name in Surrogate Registration should be used as the User Name in the outgoing
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 R-URI, From, and To headers of all outgoing calls.|
|Int Challenge Response|
Enable this flag on the ingress IP Peer to allow the SBC to reply to local authentication challenges autonomously. If this flag is disabled, the SBC will not reply to authentication challenges locally even if credentials are configured on the egress IPTG.
|Inc Internal Credentials|
Enable this flag on the ingress IP Peer to allow egress IPTG authentication to be internally created using the authorization information in mid-dialogue without being challenged.
If Int Challenge Response is disabled, Inc Internal Credentials are not used.