305 Response to Registrations on Secondary Interfaces
Certain devices are provisioned with point of contact (POC) lists for registration. In the context of geographic redundancy, if a UE is unable to register with its primary POC, it proceeds to its secondary POC. It is desirable to designate certain Oracle Communications Session Border Controller as secondary in order to redirect the UE to re-register with the primary SBC.
This feature is designed for Oracle Communications Session Border Controllers sitting behind Oracle Communications Subscriber-Aware Load Balancers (SLBs). This feature allows users to designateOCSBCs sitting behind SLBs as secondary. When registered endpoints in a realm attempt to register with the primary POC, and registration fails, the UEs proceed to their secondary point of contact (POC). Once connection to the primary POC has been restored, users can execute a command to offload the UE registrations in a given realm with a 305 response to the UEs in order for the UEs to re-register with the next POC. When the scenario consists of two POCs, the endpoint re-registers with the primary POC.
You enable this feature with an option through the SIP interface of the secondary SBC. The notify sipd offload-users <realm> command marks endpoints associated with a given realm to receive a 305 message. Once this command is executed, any subsequent requests from UEs in this designated realm receive a 305 message. Once a 305 message is issued, the registration cache is cleared to allow the UE request to be forwarded to the primary SBC. If the UE re-registers again with the secondary SBC, it will not receive a second 305 message. The notify sipd offload-users <realm> command must be executed again in order to repeat the process.
The show registration command is expanded to include a counter for the number of registrations received on secondary interfaces, as well as the number of endpoints marked to receive a 305.
SNMP support for this feature tracks the total count of registrations on secondary interfaces. The apSipSecInterfaceRegThresholdExceededTrap is generated when the total number of registrations on secondary interfaces exceeds the configured threshold, and apSipSecInterfaceRegThresholdClearTrap is generated when the total count falls below the configured threshold.
ACLI Instructions and Examples
To enable this feature, you must select an option for the SIP-interface of the secondary Oracle Communications Session Border Controller:
notify sipd offload-users
The notify sipd offload-users <realm> command marks the endpoints associated with the given <realm> to receive a 305 message. Once this command is executed, any re-registrations received from an endpoint in that realm receives a 305 message.
A confirmation message is sent if the command succeeds:
Realm <realm> is marked to offload users at HH:MM:SS
If the given <realm> is not a secondary realm, the following message is displayed:
Realm <realm> is not secondary
If the given <realm> does not exist, the following message is displayed:
Realm <realm> is not found
Note:
This command is only valid for secondary systems. If the secondary option is not enabled for theOracle Communications Session Border Controller, this command produces an error message.show registration
The show registration command displays the total number of endpoints associated with secondary interfaces, and the total number of endpoints marked to receive a 305 response.
Note:
The total number of SIP calls to receive a 305 response are included in the Registrations marked for 305 counter.The total number of SIP calls associated with secondary realms are included in this count.
AcmePacket# show registration
11:02:13-102
SIP Registrations -- Period -- -------- Lifetime --------
Active High Total Total PerMax High
User Entries 1 1 1 1 1 1
...
Secondary Interface Registrations=NNN
Registrations marked for 305=MMM
access1: N1
access2: N2
show registration sipd
The show registration sipd command includes the following parameters:
show registration sipd sec-by-ip—displays the registrations sent to secondary interfaces by IP address.
Registration Cache MON FEB 06 2012 16:33:49
Num
IP Address User Contacts Registered at
---------------- ------------------------------ -------- ---------
. . . .
show registration sipd sec-by-user—displays the registrations sent to secondary interfaces by user name.
Registration Cache MON FEB 06 2012 16:33:49
Num
Phone Number User Contacts Registered at
---------------- ------------------------------ -------- ------------
. . . .
show sipd endpoint-ip
If the registered endpoint is associated with a secondary SIP interface, the show sipd endpoint-ip command displays SIP Interface: secondary.
# show sipd endpoint-ip 1
User <sip:12341@172.16.101.67>
Contact exp=290
UA-Contact: <sip:12341@172.16.26.1:5060> UDP keep-acl
realm=net172 local=172.16.101.67:5060 UA=172.16.26.1:5060
SD-Contact: <sip:12341-2k86jbp9bj925@192.168.101.67:5060> realm=net192
Call-ID: 1-839@172.16.26.1'
SA=192.168.26.2
Service-Route='<sip:h19216806003.dg.com;lr>'
SIP Interface: secondary
