RFC 6140, "Registration for Multiple Phone Numbers in the Session Initiation Protocol (SIP)", March 2011Source of RFC: martini (rai)
See Also: RFC 6140 w/ inline errata
Errata ID: 3144
Publication Format(s) : TEXT
Reported By: David Hancock
Date Reported: 2012-03-01
Verifier Name: Robert Sparks
Date Verified: 2012-06-07
Section 5.2 says:
<none -- new text being added>
It should say:
<Insert following new paragraph between existing 2nd and 3rd paragraph> The registrar MUST populate the Contact header field of the 200 (OK) response to REGISTER only with the explicitly registered Contact URIs identified in the REGISTER request (i.e., for bulk number registration, the Contact URIs containing the “bnc” parameter). The Contact header field of the 200 (OK) response MUST NOT contain the multiple contact addresses that are implicitly created by the bulk number registration procedure.
The proposed text clarifies how the MUST statement in RFC 3261 section 10.3 item-8 applies in the case of bulk number registration.
RFC 3261 section 10.3 item-8 says ...
8. The registrar returns a 200 (OK) response. The response MUST
contain Contact header field values enumerating all current
bindings. <... text deleted...>
For bulk number registration, this means that the Contact header field in the 200 (OK) response to REGISTER contains the Contact URI with the "bnc" parameter, and not the multiple derived contact URIs that are bound to the multiple E.164 numbers associated with the registering PBX.