RE: [Sip-implementors] To-Tag value

[Attila Sipos]

Title: Message

 

 

I think this is illegal.

 

The 300 is a FINAL response already (anything >= 200 is a FINAL response)

so you cannot send another final response afterwards.

 

I think the correct thing to do would be:

 

 UAC                                   UAS

------                                ------

-------------------------------> INVITE

<------------------------------- 300 Multiple choices

--------------------------------> ACK

<------------------------------- BYE

--------------------------------> OK (to BYE)

 

In the BYE request, you can specify a disconnection reason, if you like,

using the "The Reason Header Field for the Session Initiation Protocol (SIP)"

in RFC3326:

http://www.faqs.org/rfcs/rfc3326.html

 Regards,

Attila

 

Attila Sipos   
Software Engineer

<http://www.vegastream.com>

VegaStream : A World of difference for your Integrated Communications

-----Original Message-----
From: P Rajmohan Banavi-A17190 [mailto:[EMAIL PROTECTED]
Sent: 01 September 2003 14:11
To: [EMAIL PROTECTED]
Subject: [Sip-implementors] To-Tag value

Hi,

 

This is related to INVITE transaction on unreliable transport.

 

 UAC                                   UAS

------                                ------

-------------------------------> INVITE

<------------------------------- 300 Multiple choices

--------------------------------> ACK

<------------------------------- 500 Server internal error (before the Timer D fires)

--------------------------------> ACK

 

Suppose the "To-tag" in the second final response (500) sent by UAS is different than the one in the initial response (300),

 

1. how should the UAC behave?

 

2. And what should be the value of the "To-Tag" in the ACK sent by UAC for 500 response?

 

regards,

Rajmohan

_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors