Adam B. Roach ([EMAIL PROTECTED]):
> I'm adding code to our client Real Soon Now that will render
> messages with displayable Content-Types for the user. I was
> particularly impressed by some implementations at this bakeoff
> that send back messages like:
>
> ---------------------------------------------------------------------------
> SIP/2.0 400 Malformed SDP
> To: sip:[EMAIL PROTECTED]
> From: sip:[EMAIL PROTECTED]
> Call-ID: [EMAIL PROTECTED]
> Content-Type: text/plain
> Content-Length: 45
>
> Could not parse m= line: no codecs listed.
> ---------------------------------------------------------------------------
>
> (Although, admittedly, they probably shouldn't have done it under the
> circumstances, since I didn't indicate that I accept text/plain...)
Even if the remote end does not indicate that they accept text/plain,
I'd send the message anyways. It's not like you're going to put a
session description in a 400 response, You might as well give whatever
aids you can to the poor person debugging the conversation.
I wouldn't send text/html, but text/plain.....
--
Billy Biggs [EMAIL PROTECTED]
http://www.div8.net/billy [EMAIL PROTECTED]
