SIP Registrar
To configure the Oracle Communications Core Session Manager to act as a SIP Registrar:
-
In Superuser mode, type
configure terminal and press Enter.
ORACLE# configure terminal
-
Type
session-router
and press Enter to access the session router path.
ORACLE(configure)# session-router
-
Type
sip-registrar and press Enter. The system
prompt changes to let you know that you can begin configuring individual
parameters.
ORACLE(session-router)# sip-registrar ORACLE(sip-registrar)#
- name—Enter a name for this SIP registrar configuration element.
- state—Set this to enabled to use this SIP registrar configuration element.
- domains—Enter one or more domains that this configuration element will invoke SIP registration for. Wildcards are valid for this parameter. Multiple entries can be entered in quotes, separated by commas.
- subscriber-database-method—Set this to CX.
- subscriber-database-config—Enter the home-subscriber-server configuration element name that will handle REGISTER messages for this domain. The HSS configuration element includes the actual IP address of the server that SAR’s are sent to.
- authentication-profile—Enter a sip-authentication-profile configuration element’s name. The sip authentication profile object referenced here will be looked up for a REGISTER message with a matching domain in the request URI. You may also leave this blank for the receiving SIP Interface to handle which messages require authentication if so configured.
- home-server-route—Enter the identification for this Oracle Communications Core Session Manager that will be sent as the Server-Name in MAR and SAR messages to the HSS. This value should be entered as a SIP URI.
- location-update-interval—Keep or change from the default of 1400 minutes (1 day). This value is used as the timer lifetime for core-side HSS updates.
- Type done when finished.