SipURI Interface

The SipURI interface represents sip and sips URIs. These URIs resemble email addresses in their format, appearing as user@host, where the user can be a username or a telephone number, and the host can be a domain name, a numeric IP address, or a hostname. In addition to the basic format, SipURI objects can include parameters and headers, though headers are not valid in all contexts. While syntactically identical, sip and sips URIs differ in semantics; the sips scheme specifies that the resource must be contacted securely using TLS, ensuring secure communications from the UAC to the domain and beyond, depending on the domain's policies. This distinction allows any sip URI to be "upgraded" to a sips URI for secure communication, as per RFC 3261. The SipURI interface abstracts both types of URIs due to their similar usage and syntax. It ensures that escaped characters in the string representation of these URIs are unescaped before they are presented to servlets, and any reserved or excluded characters in values passed to setter methods are properly escaped by the SIP servlet container.

Methods:

getUser