SIP Registration

Overview

The SIP Signaling Registration facility enables

to relay SIP endpoint registration information between these endpoints and the Registrar. The SIP Trunk group commands configure the time span allowed for an IAD before requiring re-registration.

The registration facility allows different expiration time on the untrusted versus trusted network. This can be used to reduce the registration refresh load on the registrars without sacrificing fast detection of failed IADs.

SIP Signaling Subscription enables 

to relay out-of-dialog “subscribe” and “notify” requests between unregistered endpoints. Unknown registration to the  may occur because the  is not located between an IAD and its Registrar. The Registrar’s default IP address is 0.0.0.0, and the portNum is “0”. This, or any other configured address, is overridden by per-transaction routing data from the .

The 

supports implicit registration of SIP endpoints. In other words, the  supports a SIP registrar returning a set of associated URIs that are implicitly registered in response to a “Register” message for a single Address of Record (AoR). The 200 response to the “Register” request identifies each implicitly registered URI in a P-Associated-URI header. P-Associated-URI headers in the 200 response are passed transparently by the . Up to 20 P-Associated-URIs (each up to 103 bytes in length) can be carried in a single 200 response, except on NOTIFY where only 20 P-Associated-URIs are supported.

uses the entire AOR name to search the registration name status wherever the AOR name is present in the statistics table.  supports to search the registration name status based on the part of the AOR and the entries, which are not in the statistics table but registered in the application using a part of the AOR name or the entire AOR name. The registration ID (RegID) is also used as a search function. In case of unknown registration ID, 0 is specified as a wildcard entry. AOR consists of userPart (user name) and hostname (user name end point IP address), and is expressed in the userPart@hostname format.

Search Method Using AOR and RegID in show Command

To retrieve the entry status that is not in the table but registered in SBC application, provide two parameters (AOR and RegID) in show command. If the RegID is unknown, use 0 as a wildcard to complete the command. Use userPart or the entire AOR name (userPart+hostname) as a first parameter to get the information. For example:

Example 1: In this case, userPart is used as first parameter to get the information.

Example 2: In this case, entire AOR name (userPart+hostname) is used as first parameter to get the information.

Bulk Registration Support

The 

supports the SIPConnect 1.1 feature as per the RFC 6140 “Registration for Multiple Phone Numbers in the SIP” (bulk registration) with the addition of “gin” option tag to Proxy-Require/Require headers. Additionally, in at least one Contact header, a Contact URI containing “bnc” parameter must be included to signify it is a bulk registration value. The default SIP To and From header username is sip:sbc@sonusnet.com.

To set registration requests to bulk registration format, use following CLI syntax:

Registration Establishment

The 

servers can function as registration proxies for access subscribers by accepting SIP REGISTERs and relaying the requests to an inside registrar. Additionally, the  can significantly offload the registrar by locally handling the registration refreshes and only periodically updating the registrar. This function is particularly critical in NAPT environments when the endpoints need to send a REGISTER as fast as every 30 seconds.

See SBC Product Specifications page for the maximum initial REGISTER rate when coincident with REGISTER refreshes and background call load for existing registrations. Note that the maximum initial REGISTER rate without any background load is much higher. However, customers should use these numbers for planning purposes since the absence of other background load is unrealistic in real networks. 

This initial register rate is for the case when initial registers are challenged for authentication by the registrar. While the unchallenged initial register rate is much higher, the best practice is to securely authenticate subscribers before accepting registrations.

For best performance, use the default overload control settings and configure the unknown peer policer to admit the appropriate initial register rate for your subscriber environment. This ensures that the system provides acceptable performance when the actual initial register attempt rate is much higher than the values below (for example, after a major city comes back online after a power outage).

SIP session and registration capacity limits are derived using the following call flow baseline:

1. INVITE
2. 100 Trying
3. 180 Ringing
4. 200 OK
5. ACK
6. <talk time>
7. BYE
8. 200 OK

The basic initial REGISTER flow in this example consists of the following four-message exchange:

1. REGISTER
2. 401 (Unauthorized)
3. REGISTER
4. 200 OK

A refresh register flow consists of:

• REGISTER
• 200 OK

Surrogate Registration Support

The 

supports configuring surrogate registration information for a single IP Peer. Up to 256 Surrogate Registration entries are supported for each IP Peer.

The

also supports configuring multiple AoRs for the same IP-PBX using the Surrogate Registration Profile. Surrogate registration specific statistics are generated separately per surrogate AoR, as applicable, even if the statistics are associated with the same IP Peer. 

When configuring surrogate registration, only one of the following mutually exclusive parameters should be enabled at the IP Peer Surrogate Registrationlevel depending upon the number of AoRs per IP Peer desired.

• Only one AoR per IP Peer to for surrogate registration—Configure only userPart at the surrogate registration level. With this method, you cannot associate a surrRegprofile with this peer.
• Multiple AoRs for IP Peer for surrogate registration—Associate more than one AoR to the same peer by configuring and attaching a surrRegprofile to the IP peer. When using this profile, you cannot configure userPart at the surrogate registration level.

In Access and Enterprise scenarios, the

can act as a surrogate registration entity between a non-registering IP-PBX (or SIP UA) and a REGISTRAR requesting registration. As an example, a new REGISTER request is sent towards the REGISTRAR to help the core network forward the incoming call to . The then forwards call to SIP UA based on SIP Registration Data and PSX configuration. An optional keep-alive message (based on OPTIONS Ping) is sent towards SIP UA to determine reachability of the UA from Access Server (AS), and the subsequent outage is reported to REGISTRAR with a ‘deregister’ message. On determining reachability of SIP UA, the UA is registered again with Registrar by the .

When the

forwards requests coming from the IP-Peer to the AS, in some cases the AS will challenge the requests coming from IP-PBX. If IP-PBX does not support authentication handling, the can be configured to respond to challenges from the AS on behalf of the IP-PBX using the "sendCredentials" parameter in the surrogate registration configuration for IP peers. The "sendCredentials" parameter supports three configurable options:

• Challenge for any message
• Challenge for any message and in-dialog requests
• Challenge for register 

The 

supports responding to challenges from AS for the following methods:

1. REGISTER
2. INVITE
3. PRACK
4. UPDATE
5. REINVITE
6. BYE

 

SIP Authentication Using Dedicated User Name

The

supports configuring a case-sensitive “Authentication ID” and password under the IP Peer object associated with an IP Peer which allows user to configure pilot number other than authorization user name. If IP Peer password is not empty, and if surrogate AoR password is empty, IP Peer password is used for credentials for all applicable methods, (e.g. REGISTER, INVITE).

In support of Surrogate Registration, when a REGISTER message is (re)sent with an Authorization or Proxy-Authorization header field in response to a challenge for authentication, the

retrieves the “Authentication ID” from the associated “IP Peer” object.

The selected “Authentication ID” is also used among other parameters, e.g., password, nonce, etc., in computing the “response” parameter of the header field per RFC 2617. The From/To/Contact header fields, however, continue to take the existing “User Part” from the associated “IP Peer/Surrogate Registration” entry as the “userinfo” part of the SIP URI.

To maintain backwards compatibility, during an LSWU from a previous release the value of the “Authentication ID” field is automatically filled with the existing “IP Peer/Surrogate Registration/User Part” field used for authorization in the previous release.

Quick Re-registration on Alternate SIP Server When Primary Server is Down

In Access scenarios, SIP Registrars on core side are considered as primary-secondary/alternate for a particular user. The users are registered to the Primary Registrar when it is available and registered with the Secondary Registrar only when the Primary is down. After the Primary Registrar goes down, the Secondary Registrar allows any new calls or requests only after the completion of Successful registration. Whenever the Primary is down,

sends any subsequent refresh registration from the user to the Secondary Registrar to establish the binding at the Secondary Registrar. Similarly when the Primary comes back up, sends the next subsequent refresh registration to the Primary Registrar. Any delay in this scenario causes loss of traffic until the registration is successful. Currently, when the primary SIP server goes down, does not register the alternate SIP server immediately.  does not send the refresh REGISTER to the primary SIP server until the internal refresh timer expires (3600 seconds). This results in a long downtime before the refresh REGISTER is passed on to the alternate SIP server for registration.

To overcome this issue, 

relays the first refresh REGISTER after it detects any status change in the primary SIP Server. This is controlled by introducing new flags in IP Signaling Profile (IPSP).  registers to the alternate SIP server immediately when Primary is down and reverts when Primary SIP server is up. The status of the servers is detected through Address Reachability Service (ARS) blacklist. For every switch from primary to secondary/alternate or from secondary/alternate to primary, queries the ERE/PSX to get the latest routing information and route refresh REGISTERs.

also supports a CLI request command to query PSX on new refresh REGISTERs.

IPSP Configuration

Four new flags are added to the registrarRecovery parameter. These new flags are introduced to the IPSP profile to configure this feature.

• registrarRecovery
  • newRegistrarIndex      
  • overRideInternalExpires
  • registrarFqdn  
  • registrarIpAddress

For configuring IPSP flags on PSX, refer to PSX Configuration.

request Command

A new CLI request queryPsxOnNextRefreshRegister command is used to force PSX query on subsequent refresh REGISTER. This enables new routing information configured in PSX to reflect in SBC when registrations are active for long time.

The CLI request command syntax is :

The queryPsxOnNextRefreshRegister command is used for one sequence of refresh REGISTERs on all active registrations, which is routed after a PSX query. The routes are selected from the new PSX query response.

The queryPsxOnNextRefreshRegister command has following optional values:

• newRegistrarIndex      
• overRideInternalExpires
• registrarFqdn  
• registrarIpAddress