Hi, The P-Charging-Vector is supported by MSC-S only if SIP call is routed to or from a trusted domain. Whether a network domain is trusted or not can be configured in the MSC Server on a route basis.
TRUSTPL parameter determines whether a Trust Policy is supported on the SIP/SIP-I route. When Trust Policy is not supported on SIP/SIP-I route header fields P-Asserted Identity, Privacy and P-Charging Vector are ignored if received and are never generated i think , this can be set using ROUTE parameters .However the The network identity is defined configuring the parameter NETID1 (and optionally NETID2) in command to change Local Host Name. Network identity is defined per network domain basis. After network identity definition the node will use this information to assign a value to Orig-IOI and so enable the generation of the ICID-value. So i dont think this is possible to meet the requirement on ROUTE basis. Regards Sampat On Friday, 11 July 2014 9:15 PM, Sourav Dhar Chaudhuri <[email protected]> wrote: Hi, Is it possible to configure custom IOI and/or FNI filed in P-Charging-Vector in SIP message header per traffic route? Thanks & Regards, Sourav Dhar Chaudhuri _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
