[sr-dev] [kamailio] P-Charging-Vector handling as RFC3455 (#214)

[Emmanuel BUU]

Here are some proposed modifications to handle the P-Charging-Vector header as defined in rfc3455 section 4.6 to
 - parse charging vector from SIP message
 - generate new unique charging vector
 - remove a charging vector header

a new pseudo variable

pseudo variables are exported and enable Read onlly access to charging vector fields

$pcv = whole field
$pcv.value = icid-value field (see RFC3455 section 5.6)
$pcv.genaddr = icid-generated-at field (see RFC3455 section 5.6)

a new function acc_charging_vector()

- g = generate a new charging vector or forward the orginal one 
- f = generate a new charging vector regardless of the orginal charging vector
- r = remote the P-Charging vector header from the packet
You can view, comment on, or merge this pull request online at:

  https://github.com/kamailio/kamailio/pull/214

-- Commit Summary --

  * P-Charging-Vector implementation
  * Merge remote branch 'upstream/master'

-- File Changes --

    A modules/acc/chargingvector.c (435)
    A modules/acc/chargingvector.h (18)

-- Patch Links --

https://github.com/kamailio/kamailio/pull/214.patch
https://github.com/kamailio/kamailio/pull/214.diff

---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/214
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-dev/attachments/20150618/1c9754a9/attachment.html>