RFC Errata
RFC 3325, "Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks", November 2002
Note: This RFC has been updated by RFC 5876, RFC 8217
Source of RFC: sip (rai)See Also: RFC 3325 w/ inline errata
Errata ID: 5499
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Richard Phernambucq
Date Reported: 2018-09-20
Verifier Name: Orie Steele
Date Verified: 2024-03-29
Section 10 says:
* F4 proxy.cisco.com -> proxy.pstn.net (trusted) INVITE sip:+14085551212@proxy.pstn.net SIP/2.0 Via: SIP/2.0/TCP useragent.cisco.com;branch=z9hG4bK-124 Via: SIP/2.0/TCP proxy.cisco.com;branch=z9hG4bK-abc
It should say:
* F4 proxy.cisco.com -> proxy.pstn.net (trusted) INVITE sip:+14085551212@proxy.pstn.net SIP/2.0 Via: SIP/2.0/TCP proxy.cisco.com;branch=z9hG4bK-abc Via: SIP/2.0/TCP useragent.cisco.com;branch=z9hG4bK-124
Notes:
As per RFC 3261, chapter 16.6, step 8:
The proxy MUST insert a Via header field value into the copy before the existing Via header field values.
The order of Via headers should be reversed. This applies to the following message examples:
chapter 10.1: F4, F5
chapter 10.2: F4, F5, F6
Text and examples in RFC3261 Section 20.42 supports the argument that the order is reversed.