The description is implicit: "AVPs are special variables that are
attached to SIP transactions." As a spiral causes 2 transactions there
are two different contexts for AVPs.
Feel free to improve/extend the description.
regards
Klaus
On 07.08.2012 21:49, Brandon Armstead wrote:
Klaus,
I
Klaus,
I see the following:
AVPs are special variables that are attached to SIP transactions. It is a
list of pairs (name,value). Before the transaction is created, the AVP list
is attached to SIP request. Note that the AVP list works like a stack, last
added value is retrieved first, and ther
Once you know it you will find it :-)
http://www.kamailio.org/wiki/cookbooks/3.3.x/pseudovariables#avps
regards
Klaus
On 07.08.2012 18:22, Brandon Armstead wrote:
Klaus,
Thank you for this detailed explanation. This is essentially what I
figured was happening. I was able to use htable t
Klaus,
Thank you for this detailed explanation. This is essentially what I
figured was happening. I was able to use htable to work around it.
I guess however I am still confused as to where there is any public
documentation on this specific bit. Had I've not been working with
Kamailio for y
AVPs are associated with the transaction. If you "spiral" a request
through the same proxy, then for the proxy it is a new transaction.
Thus, when processing the request a second time, there is a new
transaction and you do not have access to the AVPs of the previous
transaction.
Workarounds a
Hello,
I am curious if there is any documentation on how AVP's processing works
in the following scenario below.
UAC 1 -> KAMAILIO -> KAMAILIO -> DEST
It seems that AVP's I set between UAC 1 -> KAMAILIO are lost once I relay
back to the same KAMAILIO proxy (self)?
Is there any documentation
