Hi, does SER support Path header field as described in RFC3327?
Thanks, Lada
I think someone did it by the way of scripting.
-jiri
At 09:07 12/03/2008, Ladislav Andel wrote:
Hi, does SER support Path header field as described in RFC3327?
Thanks, Lada
Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-- Jiri Kuthan http://iptel.org/~jiri/
From Vaclav in an earlier thread:
Hi, I don't know about the patch, but for storing something with registered contact you can use "reg_avps" (AVPs stored with contact; you need only to set a flag to them before you call save and if you want to get them back, you can call "read_reg_avps"). So if you are able to translate Path into AVP(s) you can use it... It is not tested and not described but it can work... :-)
Something like this was working some time ago:
avpflags regavps;
modparam("usrloc", "reg_avp_table", "contact_attrs"); modparam("usrloc", "reg_avp_flag", "regavps")
route { ...
if (method=="REGISTER") { $t.a = @msg["P-Avp"]; $t.neco = "pokus"; setavpflag("$t.a","regavps"); setavpflag("$t.neco","regavps");
save("location"); break; } ... }
branch_route[1] { read_reg_avps("location", "$t.uid"); xlog("L_ERR", "$t.a = %$t.a"); ... }
If somebody will be interested, I can try to describe it better (and test a bit with Ottendorf)...
Vaclav
Jiri Kuthan wrote:
I think someone did it by the way of scripting.
-jiri
At 09:07 12/03/2008, Ladislav Andel wrote:
Hi, does SER support Path header field as described in RFC3327?
Thanks, Lada
Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-- Jiri Kuthan http://iptel.org/~jiri/
Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers