<br><br><div class="gmail_quote">On Tue, Nov 30, 2010 at 11:19 PM, mayamatakeshi <span dir="ltr"><<a href="mailto:mayamatakeshi@gmail.com">mayamatakeshi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br><div class="gmail_quote">2010/11/30 Anton Zagorskiy <span dir="ltr"><<a href="mailto:a.zagorskiy@oyster-telecom.ru" target="_blank">a.zagorskiy@oyster-telecom.ru</a>></span><div class="im"><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Why BYE isn't a part of the transaction?<br></blockquote></div><div><br>From RFC3261:<br>
<pre>Specifically, a SIP transaction consists of a single request and any responses to<br> that request, which include zero or more provisional responses and<br> one or more final responses.</pre>
But when opensips docs say transaction, it is also implying that you are
using module tm (if you don't use tm functions, then you are doing
stateless processing and no AVP will be saved).
<br></div></div></blockquote><div><br>For completeness,<br>the BYE is part of the dialog established by the INVITE transaction that ended when "200 OK" was received. But the BYE itself starts another transaction.<br>
So, the AVPs you set in the processing of the INVITE will be available (as long as you use module tm) when your process responses for that INVITE (180, 183, 200 etc), but not when you are handling other requests in the dialog.<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="gmail_quote"><div><br></div><div><div></div><div class="h5"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
WBR, Anton Zagorskiy<br>
VoIP Developer, Oyster Telecom<br>
Phone.: +7 812 601-0666<br>
Fax: +7 812 601-0593<br>
<div><a href="mailto:a.zagorskiy@oyster-telecom.ru" target="_blank">a.zagorskiy@oyster-telecom.ru</a><br>
</div><a href="http://www.oyster-telecom.ru" target="_blank">www.oyster-telecom.ru</a><br>
<br>
<br>
From: <a href="mailto:users-bounces@lists.opensips.org" target="_blank">users-bounces@lists.opensips.org</a><br>
[mailto:<a href="mailto:users-bounces@lists.opensips.org" target="_blank">users-bounces@lists.opensips.org</a>] On Behalf Of mayamatakeshi<br>
Sent: Tuesday, November 30, 2010 4:13 PM<br>
To: OpenSIPS users mailling list<br>
Subject: Re: [OpenSIPS-Users] BYE processing and AVP<br>
<div><div></div><div><br>
<br>
On Tue, Nov 30, 2010 at 10:07 PM, Anton Zagorskiy<br>
<<a href="mailto:a.zagorskiy@oyster-telecom.ru" target="_blank">a.zagorskiy@oyster-telecom.ru</a>> wrote:<br>
Hello.<br>
<br>
During INVITE processing I'm setting up some avp variables. When I'm<br>
receiving a BYE request all avps are null. Why does this happen?<br>
A part of the script:<br>
<br>
if (has_totag())<br>
{<br>
if (loose_route())<br>
{<br>
if (is_method("BYE"))<br>
{<br>
xlog("*** BYE $avp(i:2)");<br>
<br>