RFC Errata
Found 4 records.
Status: Held for Document Update (4)
RFC 3398, "Integrated Services Digital Network (ISDN) User Part (ISUP) to Session Initiation Protocol (SIP) Mapping", December 2002
Source of RFC: sipping (rai)
Errata ID: 2580
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Stephen James
Date Reported: 2010-10-19
Held for Document Update by: Gonzalo Camarillo
Date Held: 2011-01-27
Section 8.1.3 says:
Item 6. The gateway also sends a CANCEL message to the SIP node to terminate any initiation attempts.
It should say:
Drop this statement. Section 8.1.3 item 6 should be updated to "The gateway also sends a CANCEL message to the SIP node to terminate the initiation attempt if a provisional response has been received." The situation illustrated in section 8.1.3 does not distinguish the "provisional response received" case from the "provisional response not received" case, so the commentary should cover both cases. (The specific example diagrammed shows the "no provisional response received" case.) A similar change should be made to section 8.1.4 item 7, "The REL will trigger a CANCEL request to the SIP node if a provisional response has been received." A similar change should be made to section 8.1.7 item 7, "Upon receipt of a REL message before an INVITE final response, the gateway will send a CANCEL towards the SIP node if a provisional response has been received.
Notes:
No CANCEL is sent on INVITE transaction timeout. This is per 3261 "If no provisional response has been received, the CANCEL request MUST NOT be sent; rather, the client MUST wait for the arrival of a provisional response before sending the request."
Errata ID: 2161
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Andrew Miller
Date Reported: 2010-04-13
Held for Document Update by: Robert Sparks
Section 8.2.6.1 says:
504 Version Not Supported 127 Interworking (+)
It should say:
505 Version Not Supported 127 Interworking (+)
Notes:
504 appears twice with different text. From the context, it looks like the text in the second entry is correct, and the number is wrong.
Errata ID: 2977
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Jeff Dyer
Date Reported: 2011-09-21
Held for Document Update by: Robert Sparks
Section 7.2.4.1 says:
(+) If the cause location is 'user' than the 6xx code could be given rather than the 4xx code (i.e., 403 becomes 603)
It should say:
(+) If the cause location is 'user', then the 6xx code could be given rather than the 4xx code (i.e., 403 becomes 603)
Notes:
"Than" is used for comparisons. "Then" is used to denote something follows in sequence.
Errata ID: 2980
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Pablo Varela
Date Reported: 2011-09-27
Held for Document Update by: Robert Sparks
Section 7.2 says:
+---------+ +----------------------->| Idle |<---------------------+ | +----+----+ | | | | | | INVITE/6.2.1 | | V | | T7/6.2.2 +-------------------------+ REL/6.2.4 | +<----------------+ Trying +------------>+ | +-+--------+------+-------+ | | CANCEL/6.2.3 | | | | | +<----------------+ | E.ACM/ | ACM/ | CON/ANM | | | 6.2.5 |6.2.6 | 6.2.7 | | V | | | | T9/6.2.8 +--------------+ | | | +<----------+ Not alerting | | | | | +-------+------+ | | | | CANCEL/6.2.3 | | | | | |<--------------+ | CPG/ | | | | | 6.2.9 | | | | V V | | | T9/6.2.8 +---------------+ | REL/6.2.4 | +<----------------+ Alerting |-|-------------------->| |<----------------+--+-----+------+ | | | CANCEL/6.2.3 | ^ | | | | CPG/ | | | ANM/ | | | 6.2.9 +--+ | 6.2.7 | | | V V | | +-------------------------+ REL/9.2 | | | Waiting for ACK |------------>| | +-------------+-----------+ | | | | | | ACK/6.2.10 | | V | | BYE/9.1 +-------------------------+ REL/9.2 | +<----------------+ Connected +------------>+ +-------------------------+
Notes:
References in figure to 6.2 should point to 7.1.