Third Party Registration for an Implicit Registration Set

When using iFCs, the Oracle Communications Core Session Manager performs third party registrations based on the iFC downloaded for each PUID. By default, the Oracle Communications Core Session Manager performs third party registration for the service profiles of all PUID's in a user's implicit registration set. This is compliant with 3GPP specifications. The system includes any shared or default iFCs that apply to each PUID during this process. The system performs this function when it receives user-initiated de-registrations, but not when it receives RTRs. If desired, the user can configure the Oracle Communications Core Session Manager to perform third party registration for only the REGISTERED PUID in the registration using a sip-registrar option.

Note:

The Oracle Communications Core Session Manager does not attempt third party registration for any barred, tel or wildcard PUIDs.

The user can verify all third party registrations using the show registration sipd by-user [user] detailed command. Example output is shown below.

ORACLE# show registration sipd by-user 234 detailed

Registration Cache (Detailed View)    Wed Sep 16 2015  10:57:44

User: sip:234@acme-ims.com
  Registered at:  2015-09-16-10:57:40    Surrogate User: false
  Emergency Registration? No
  ContactsPerAor Rejects 0
  ContactsPerAor OverWrites 0

  Contact Information:
    Contact:
      Name: sip:234@acme-ims.com
      Valid: true
      Challenged: false
      Registered at: 2015-09-16-10:57:40
      Last Registered at: 2015-09-16-10:57:40
      Expire: 3596
      Local expire: 296
      Half: 1796

      Registrar IP: 0.0.0.0
      Transport: UDP
      Secure: false
      Local IP: 192.168.53.99:5060

      User Agent Info:
        Contact: sip:234@192.168.53.181:5060
        Realm: core
        IP: 192.168.53.181:5060

      SD Info:
        Contact: sip:234-tbcktcgo177fc@192.168.53.99:5060
Call-ID: 1-5853@192.168.53.181
      Path: <sip:234@192.168.53.181:5060;lr;p-acme-serving>

    Associated URI(s):
      URI: sip:234@acme-ims.com
      Status: Non-Barred 
         Filter Criteria:
           Priority: 0
             Filter: ((method == REGISTER)) or
              ((method == INVITE))
             Application Server: sip:172.16.17.10:5060

      URI: sip:1@acme-ims.com
      Status: Non-Barred 
         Filter Criteria:
           Priority: 0
             Filter: ((method == REGISTER)) or
              ((method == INVITE))
             Application Server: sip:172.16.17.10:5060
           Priority: 1
             Filter: ((method == INVITE)) or
              ((method == REGISTER))
             Application Server: sip:172.16.53.181:5065

      URI: tel:135
      Status: Barred 
         Filter Criteria:
           Priority: 0
             Filter: ((method == INVITE)) or
              ((method == REGISTER))
             Application Server: sip:172.16.53.181:5065
           Priority: 1
             Filter: ((method == INVITE)) or
((method == REGISTER))
             Application Server: sip:172.16.53.181:5095


    Third Party Registration(s):
      Third Party Registration Host: 172.16.17.10
      Registration State: REGISTERED
      Last Registered at: Never
      Third Party Registration Host: 172.16.53.181
      Registration State: REGISTERED
      Last Registered at: Never

The user can check for third party registrations errors using the show sipd third-party-reg all command. Example output is shown below.

ORACLE# show sipd third-party-reg all
3rd Party Registrar             SA State   Requests     200OK  Timeouts    Errors
(D)111.11.17.10                   INSV         1         1        0         0
(D)111.11.53.181                  INSV         1         1        0         0

The user can disable the default behavior and perform third party registration only for the PUID in the REGISTER by configuration. Disabling this behavior can improve system performance by preventing the system from having to walk through large PUID sets for large numbers of ASs. The ACLI syntax for disabling this functionality using the disable-thirdPartyReg-for-implicit-puid setting follows.

ORACLE(sip-registrar)#options +disable-thirdPartyReg-for-implicit-puid

Note:

Prior to this version, the Oracle Communications Core Session Manager's default behavior was the same as if the disable-thirdPartyReg-for-implicit-puid option was set in the SIP registrar. Users upgrading to this version of the Oracle Communications Core Session Manager must set the disable-thirdPartyReg-for-implicit-puid option to retain the previous behavior.