Hey Mikko, 

Yes it is for internal purposes at this stage (I am working on Ro charging interface). However, with time, etc we may start exposing various IMS pseudovars (e.g. iccid, orig_ioi, etc) to config script.

Cheers
Jason


On Fri, Apr 5, 2013 at 10:39 AM, Mikko Lehto <mslehto@iki.fi> wrote:
2013-04-05 (Fri) 09:37 UTC +0200  Jason Penton <jason.penton@gmail.com>:

> Module: sip-router
> Branch: master
> Commit: 98d76f94f2a4587b7a93e8e9982ff8017cabd9a3
> URL:    http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=98d76f94f2a4587b7a93e8e9982ff8017cabd9a3
>
> Author: Jason Penton <jason.penton@smilecoms.com>
> Committer: Jason Penton <jason.penton@smilecoms.com>
> Date:   Fri Apr  5 09:09:00 2013 +0200
>
> lib/ims: Added cscf_get_p_charging_vector to retrieve icid,term_ioi,orig_ioi

Hello Jason

I am currently handling P-Charging-Vector with $hdr() and append_hf().

Is cscf_get_p_charging_vector something that will be available to script
writer or is it used only internally by some IMS module?

--
Mikko

_______________________________________________
sr-dev mailing list
sr-dev@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev