| Summary: | ASTERISK-09112: Status-line in sipfrag notify is missing a CRLF | ||
| Reporter: | Robert Arritt (rarritt) | Labels: | |
| Date Opened: | 2007-03-27 10:46:02 | Date Closed: | 2007-06-30 09:20:10 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/chan_sip/Transfers |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) missingCRLF.pcap ( 1) transfer.log ( 2) transfer2.log | |
| Description: | RFC 3515 says: Each NOTIFY MUST contain a body of type "message/sipfrag" [3]. The body of a NOTIFY MUST begin with a SIP Response Status-Line as defined in [1](RFC 3261). -RFC 3215 - 2.4.5 The Body of the NOTIFY RFC 3261 defines the status line as: Status-Line = SIP-Version SP Status-Code SP Reason-Phrase CRLF -RFC 3261 - 7.2 Responses When Asterisk sends the Notify after a REFER, the sipfrag portion contains the status line SIP/2.0 200 OK without a CRLF. Files: missingCRLF.pcap - shows a blind transfer with packet 49 containing a notify without a CRLF. transfer.log - a debug trace from asterisk | ||
| Comments: | By: Serge Vecher (serge-v) 2007-03-27 10:54:12 rarritt: can you please make sure that the console line in logger.conf contains the "debug" verb, then add "set debug 4" on console and repeat the log please, thanks. By: Russell Bryant (russell) 2007-04-03 18:25:08 This should be fixed in 1.2 as of revision 60016. Thanks! | ||