Please see sec. 2.2 of draft-ietf-sipping-sip-offeranswer-04.txt
From: subhodeep.sarkarwipro.com [mailto:subhodeep.sarkarwipro.com] Sent: Thursday, December 20, 2007 3:16 PM To: sipietf.org; sippingietf.org Subject: [Sip] PRACK/Offer Answer
Hi,
I have a call scenario, where UAC had sent an offer (not initial) in PRACK and the UAS needs to refuse the offer. Can the UAS refuse the offer using a 4xx response (e.g. 488) ? I don't find any specific example in the currently available RFCs and/or drafts.
Cheers,
Subhodeep
RE: PRACK/Offer Answer
United States
2007-12-21 07:35:06
The 200 Ok can have the port number in m line set to 0 to
indicate that the media stream is not acceptable.
From: subhodeep.sarkarwipro.com
[mailto:subhodeep.sarkarwipro.com] Sent: Friday, December 21, 2007
3:06 AM To: Sanjay Sinha (sanjsinh); sipietf.org;
sippingietf.org Subject: RE: [Sip] PRACK/Offer
Answer
OK. But what should be
the body of the 200 OK PRACK (Pattern 5) before sending 488 to INVITE
for termination of the dialog.
Please see sec. 2.2 of
draft-ietf-sipping-sip-offeranswer-04.txt
From: subhodeep.sarkarwipro.com
[mailto:subhodeep.sarkarwipro.com] Sent: Thursday, December 20,
2007 3:16 PM To: sipietf.org; sippingietf.org Subject:
[Sip] PRACK/Offer Answer
Hi,
I have a call scenario, where UAC had
sent an offer (not initial) in PRACK and the UAS needs to refuse the offer.
Can the UAS refuse the offer using a 4xx response (e.g. 488) ? I don't
find any specific example in the currently available RFCs and/or
drafts.
Cheers,
Subhodeep
The information contained in
this electronic message and any attachments to this message are intended
for the exclusive use of the addressee(s) and may contain proprietary,
confidential or privileged information. If you are not the intended
recipient, you should not disseminate, distribute or copy this e-mail.
Please notify the sender immediately and destroy all copies of this
message and any attachments.
WARNING: Computer viruses can be
transmitted via email. The recipient should check this email and any
attachments for the presence of viruses. The company accepts no
liability for any damage caused by any virus transmitted by this
email.