Registering Capabilities at the Oracle Communications Core Session Manager
Endpoints register their capabilities by listing them in the Contact headers of the REGISTER request. The Oracle Communications Core Session Manager stores these feature parameters in its registration cache along with the other contact information. In the case of ENUM databases, the Oracle Communications Core Session Manager also sends capabilities information to the ENUM infrastructure so that it can maintain capabilities records.
In addition to the standard set of tags, the Oracle Communications Core Session Manager supports storing custom feature tags. Tags formatted with a + sign preceding the tag are recognized as custom tags. The exception to this are tags formatted using +sip.<tagname>, which are registered sip media feature tags.
An example of a contact header specifying audio, video and methods capabilities is shown below:
Contact: sip:u1@h.example.com;audio;video;methods="INVITE,BYE";q=0.2