Extended ENUM Record Length

In some cases, when a user registers a contact from a UA, the Contact: header’s contents are too long to be inserted into the DNS-based user database as presented in the NAPTR record.

To mitigate this, the Oracle Communications Unified Session Manager stores contact-related metadata, i.e. parameter key and value pairs, in a related TXT record.

If the contents of the Contact: header do not exceed 255 bytes, there is generally no need to extract the metadata to store in an additional TXT record, so the Oracle Communications Unified Session Manager will not enact this process.