It seems to me that "489 Bad Event" is a strange response. Normally "Bad Event" is used in response to a NOTIFY for an event that the receiver didn't recognise.
Taken From: http://www.faqs.org/rfcs/rfc3265.html 7.3.2. "489 Bad Event" Response Code The 489 event response is added to the "Client-Error" header field definition. "489 Bad Event" is used to indicate that the server did not understand the event package specified in a "Event" header field. I have never seen such a response to a REFER request. If you look at http://www.faqs.org/rfcs/rfc3515.html (The SIP Refer Method), you will see that the Event header is only used by the NOTIFY (as you would expect) and not in the REFER message. I think you should ask the maker of the UA which sent you the "489" response. Why have they sent such a response? Either that or try to send REFER with the line: Event: refer However, the use of such a header here seems wrong to me. Regards, Attila Attila Sipos Let's talk Business, Let's talk VoIP http://www.vegastream.com >> -----Original Message----- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] Behalf >> Of Aarthy G - >> CTD, Chennai. >> Sent: 02 August 2005 07:38 >> To: [EMAIL PROTECTED]; [email protected] >> Subject: [Sip-implementors] 489 Bad Event Regarding >> >> >> Hello All, >> >> I have sent the following REFER message and I received 489 Bad Event. >> Can you please explain me on what should be changed to get a >> 202 Accepted. >> >> REFER sip:[EMAIL PROTECTED]:5060 SIP/2.0 >> Via: SIP/2.0/UDP >> 10.100.12.242:5060;rport;branch=z9hG4bK1dceab6d894fe22fab106a >> b75cd03725 >> From: >> sip:[EMAIL PROTECTED];tag=1a8dc5adb74fd5d4488bdc0f8e7b503f >> To: sip:[EMAIL PROTECTED];tag=032f16a98bf6214c004dd0048813bfc2 >> Call-ID: [EMAIL PROTECTED] >> CSeq: 16113 REFER >> Contact: sip:[EMAIL PROTECTED] >> Route: <sip:10.100.12.96:5060;lr> >> Content-Length: 0 >> Max-Forwards: 70 >> Organization: XXX >> Proxy-Authorization: DIGEST >> username="6442421001",realm="HDCHCTDVDP1279",nonce="264c72dd3 >> baf012b4f370c00 >> 7aa26e5bae0d0418",uri="sip:[EMAIL PROTECTED]",response= >> "0705aec273ffdd >> ac586432b070321c11",algorithm=MD5 >> Refer-To: sip:[EMAIL PROTECTED]:5060 >> User-Agent: YYY >> Authorization: DIGEST >> username="6442421001",realm="HDCHCTDVDP1279",nonce="264c72dd3 >> baf012b4f370c00 >> 7aa26e5bae0d0418",uri="sip:[EMAIL PROTECTED]",response= >> "0705aec273ffdd >> ac586432b070321c11",algorithm=MD5 >> Referred-By: sip:[EMAIL PROTECTED] >> >> >> SIP/2.0 489 Bad Event >> Via: SIP/2.0/UDP >> 10.100.12.242:5060;rport=1059;branch=z9hG4bK1dceab6d894fe22fa >> b106ab75cd03725 >> From: >> sip:[EMAIL PROTECTED];tag=1a8dc5adb74fd5d4488bdc0f8e7b503f >> To: sip:[EMAIL PROTECTED];tag=032f16a98bf6214c004dd0048813bfc2 >> Call-ID: [EMAIL PROTECTED] >> CSeq: 16113 REFER >> Record-Route: <sip:10.100.12.96:5060;lr> >> Content-Length: 0 >> Organization: XXX >> User-Agent: YYY >> Allow-Events: presence >> >> >> thanks, >> Aarthy G. >> >> DISCLAIMER >> This message and any attachment(s) contained here are >> information that is >> confidential, proprietary to HCL Technologies and its >> customers. Contents >> may be privileged or otherwise protected by law. The >> information is solely >> intended for the individual or the entity it is addressed >> to. If you are not >> the intended recipient of this message, you are not >> authorized to read, >> forward, print, retain, copy or disseminate this message or >> any part of it. >> If you have received this e-mail in error, please notify the sender >> immediately by return e-mail and delete it from your computer. >> >> >> _______________________________________________ >> Sip-implementors mailing list >> [email protected] >> http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors >> _______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
