[SIPForum-discussion] RES: Why ACK is separate transaction for INVITE

[RODRIGO DUARTE YANSSEN YANSSEN]

Hi Bihari Lal Gupta,

Other important point to be considered is that , following RFC3261 the ACK can contain some body and can´t be rejected, even the body with unknown fields, so is not appropriated to send a separated ACK for any message different that 2XX responses.

It wouldn´t be secure to your network.

Regards.

Rodrigo Yanssen
+ 55 19 3721-6520
+ 55 19 9350-1281

De: discussion-bounces at sipforum.org [mailto:discussion-bounces at sipforum.org] Em nome de sunitha r
Enviada em: sexta-feira, 17 de junho de 2011 03:30
Para: biharilal gupta
Cc: discussion at sipforum.org
Assunto: Re: [SIPForum-discussion] Why ACK is separate transaction for INVITE

Hi Bihari Lal Gupta,

In Sip, 2XX will be the final response for INVITE. So from INVITE to 2XX  is one completee transaction and after 2XX response whatever comes it will be considered as a separate transaction.

Thank you and Regards,
Sunitha.R


On Thu, Jun 16, 2011 at 12:11 AM, biharilal gupta <guptabihari at yahoo.com<mailto:guptabihari at yahoo.com>> wrote:
Hi,

Can anyone pls tell me why ACK is a separate transaction in case of 2xx (Final response) of INVITE request, and why ACK is not considered a separate transaction in case of 486 busy response of INVITE.

Thanks & Regards,
Bihari Lal Gupta


_______________________________________________
This is the SIP Forum discussion mailing list
TO UNSUBSCRIBE, or edit your delivery options, please visit http://sipforum.org/mailman/listinfo/discussion
Post to the list at discussion at sipforum.org<mailto:discussion at sipforum.org>


________________________________
AVISO DE CONFIDENCIALIDADE
Esta mensagem e seus anexos são de uso exclusivo de pessoas e entidades autorizadas pela Embratel e podem conter informações confidenciais e/ou privilegiadas. É proibido revelar, alterar, copiar, divulgar ou se beneficiar, direta ou indiretamente, destas informações sem a autorização de seus autores. Se você recebeu este e-mail por engano, por favor, informe o remetente e apague a mensagem imediatamente. A Embratel se reserva o direito de pleitear ressarcimento pelos prejuízos decorrentes do uso indevido das informações e de requerer a aplicação das penalidades cabíveis.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20110617/c83a6e38/attachment-0002.html>