Klaus,<div><br></div><div> Thank you for this detailed explanation. This is essentially what I figured was happening. I was able to use htable to work around it.</div><div><br></div><div>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 years I would think this would confuse others.</div>
<div><br></div><div>Let me know if it is somewhere else, otherwise I will add it to the Kamailio wiki.</div><div><br></div><div>Sincerely,</div><div>Brandon Armstead</div><div><br><div class="gmail_quote">On Tue, Aug 7, 2012 at 2:32 AM, Klaus Darilion <span dir="ltr"><<a href="mailto:klaus.mailinglists@pernau.at" target="_blank">klaus.mailinglists@pernau.at</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">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.<br>
<br>
Workarounds are:<br>
- store data in SIP headers and retrieve it later (ugly)<br>
- use htable module to store data during transaction 1 and retrieve it during transaction 2. Therefore you need a known "key" which is identical in this 2 transactions only (e.g. use "$ci$ft" as base for the key).<br>
<br>
regards<br>
Klaus<div><div class="h5"><br>
<br>
<br>
<br>
<br>
On 07.08.2012 00:27, Brandon Armstead wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
Hello,<br>
<br>
I am curious if there is any documentation on how AVP's processing<br>
works in the following scenario below.<br>
<br>
UAC 1 -> KAMAILIO -> KAMAILIO -> DEST<br>
<br>
It seems that AVP's I set between UAC 1 -> KAMAILIO are lost once I<br>
relay back to the same KAMAILIO proxy (self)?<br>
<br>
Is there any documentation on why or when this would occur?<br>
<br>
Is there a better way to handle such a scenario? i.e. more dynamic<br>
internal routing, vs relaying to self.<br>
<br>
Thanks as always in advance!<br>
<br>
Sincerely,<br>
Brandon Armstead<br>
<br>
<br></div></div>
______________________________<u></u>_________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/<u></u>cgi-bin/mailman/listinfo/sr-<u></u>users</a><br>
<br>
</blockquote>
</blockquote></div><br></div>