...
The SIP Signaling Registration facility enables SBC
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.
...
SIP Signaling Subscription enables SBC enables
to relay out-of-dialog “subscribe” and “notify” requests between unregistered endpoints. Unknown registration to
the SBC the may occur because
the SBC 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
SBC..The
The SBC supports implicit registration of SIP endpoints. In other words,
the SBC 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
SBC. 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.
| Code Block |
|---|
|
admin@SBC> show status addressContext default sipActiveRegisterNameStatus 67891 0
state completed;
contactURI sip:67891@10.54.80.101:7070;
nextHopIpAddress 10.54.80.101;
nextHopPortNum 7070;
registrarIpAddress 10.54.19.168;
registrarPortNum 7080;
externalExpirationTime 1800;
internalExpirationTime 3600;
creationTime 2016-01-28T06:39:34+00:00;
registrarDomainName "";
endPointBehindNapt 0;
natPinholeLearningStatus none;
securityMechanismType none;
registrationType normal;
e2aeMediaSecurity none;
isRoaming 0;
transportProtocolToEndpoint udp;
transportProtocolToAS udp;
externalExpirationTimeLeft 1602;
internalExpirationTimeLeft 3052;
[ok][2016-01-28 12:12:53]
|
Example 2: In this case, entire AOR name (userPart+hostname) is used as first parameter to get the information.
| Code Block |
|---|
|
admin@SBC> show status addressContext default sipActiveRegisterNameStatus 67891@10.54.80.101 0
state completed;
contactURI sip:67891@10.54.80.101:7070;
nextHopIpAddress 10.54.80.101;
nextHopPortNum 7070;
registrarIpAddress 10.54.19.168;
registrarPortNum 7080;
externalExpirationTime 1800;
internalExpirationTime 3600;
creationTime 2016-01-28T06:39:34+00:00;
registrarDomainName "";
endPointBehindNapt 0;
natPinholeLearningStatus none;
securityMechanismType none;
registrationType normal;
e2aeMediaSecurity none;
isRoaming 0;
transportProtocolToEndpoint udp;
transportProtocolToAS udp;
externalExpirationTimeLeft 1606;
internalExpirationTimeLeft 3056;
[ok][2016-01-28 12:12:48] |
Bulk Registration Support
The
The SBC 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.
...
| Info |
|---|
To configure SIP Authentication, see the following pages: |
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.| Caption |
|---|
| 0 | Figure |
|---|
| 1 | Quick Re-registration on Alternate SIP Server When Primary Server is Down |
|---|
|
 Image Added |
| Note |
|---|
- This feature requires Pathcheck support using OPTIONS Ping and ARS static blacklisting to detect the reachability of a particular IP/FQDN.
- If both request command and IPSP flags are configured, command takes the preference over IPSP flags.
|