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 are: - store data in SIP headers and retrieve it later (ugly) - 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).
regards Klaus
On 07.08.2012 00:27, Brandon Armstead wrote:
Hello,
I am curious if there is any documentation on how AVP's processingworks 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 on why or when this would occur?
Is there a better way to handle such a scenario? i.e. more dynamic internal routing, vs relaying to self.
Thanks as always in advance!
Sincerely, Brandon Armstead
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users