No subject

Specifically, a SIP transaction consists of a single request and any
responses to
   that request, which include zero or more provisional responses and
   one or more final responses.

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).  


For completeness,
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.
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.
 

 


WBR, Anton Zagorskiy
VoIP Developer, Oyster Telecom
Phone.: +7 812 601-0666
Fax: +7 812 601-0593

a.zagorskiy at oyster-telecom.ru

www.oyster-telecom.ru


From: users-bounces at lists.opensips.org
[mailto:users-bounces at lists.opensips.org] On Behalf Of mayamatakeshi
Sent: Tuesday, November 30, 2010 4:13 PM
To: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] BYE processing and AVP



On Tue, Nov 30, 2010 at 10:07 PM, Anton Zagorskiy
<a.zagorskiy at oyster-telecom.ru> wrote:
Hello.

During INVITE processing I'm setting up some avp variables. When I'm
receiving a BYE request all avps are null. Why does this happen?
A part of the script:

if (has_totag())
{
       if (loose_route())
       {
               if (is_method("BYE"))
               {
                       xlog("*** BYE $avp(i:2)");