Resend to the list
Sip - Specific Event Notification (http://www.ietf.org/rfc/rfc3265.txt) defines the NOTIFY Method. Within the above RFC the Content-Length header is designated with a "t" under the NOT (Notify) column (Section 7.1).
The "t" designation is defined in the SIP (http://www.ietf.org/rfc/rfc3261.txt) definition as follows:
t: The header field SHOULD be sent, but clients/servers need to be prepared to receive messages without that header field. If a stream-based protocol (such as TCP) is used as a transport, then the header field MUST be sent.Hope this helps
Regards, Norm
Chris Robson wrote:
Is the field "Content-length" a required field in a NOTIFY message? I see that it is part of almost every message from OpenSER except the NOTIFY message. This is causing some issues with Gaim SIMPLe interface which processes the header based on the header string "Content-Length". Note Gaim does not care about the value associated with the header string just the fact that the string "Content-Length" exists. Therefore, since OpenSER isnt sending the string, Gaim is core dumping. FYI on the core dump. Yes, Gaim still has a bug on how it is processing what it sees as unknown SIP messages which actually is causing the core dump, the real problem is the fact that Gaim is processing the header, expecting to see the field "Content-length". So before I report this to Gaim as a bug, I wanted to get insight into whether the field is a required field.
Thanks......
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users