Entry Expiration

The Oracle Communications Unified Session Manager employs a process to remove expired contacts from the ENUM database whether they were entered by the active Oracle Communications Unified Session Manager or other Oracle Communications Unified Session Manager. After determining that a contact is expired, the Oracle Communications Unified Session Manager removes the contact in a subsequent DDNS update.

To do this, the Oracle Communications Unified Session Manager includes an expiration parameter in the Contacts it insert into the ENUM database. Expiration is indicated with a ts= parameter. This parameter’s value is set to the initial registration time measured on the Oracle Communications Unified Session Manager plus the REGISTER message’s Expires: header value or Expires parameter in the Contact header value. This value is measured in seconds after the epoch. In a DDNS update, a ts= parameter appears as follows:

Regex: "!^.*$!sip:234-hchse6c0d01u2@172.16.101.51:5060;ts=1313493824!"

After the Oracle Communications Unified Session Manager retrieves contacts for an AoR in a NAPTR record that are expired, based on ts= parameters, the Oracle Communications Unified Session Manager’s next Dynamic update tells the server to remove those contacts from the ENUM database.

In this way, all Oracle Communications Unified Session Manager members of a domain may remove expired contacts from the ENUM database.