Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The SIP REGISTER request is constructed using the rules specified in [RFC3261] section 10 and the following extensions.
Zero or one Event header MAY be present in a REGISTER request. If an Event header is present, it MUST have the value "registration". This creates an implicit subscription for sending the registration state-change notifications specified in [RFC3265] section 7.2.1.
The UAC SHOULD add the option tags defined in section 2.2.1.5 to the Supported header field in the REGISTER request.
The UAC MAY add at most one ms-keep-alive header field, as specified in [MS-CONMGMT] section 2.2.1, in the REGISTER request.
The constructed REGISTER request MUST also conform to the rules specified in Section 3.4 of [MS-SIPRE].