[reSIProcate] more complete support for RFC 3455 headers and parameters?

[Scott Godin]

No reason that I know of.  Yes, please post the diffs if you add these.

Thanks,
Scott


On Fri, May 23, 2014 at 1:11 PM, John Gregg <jgregg at aylus.com> wrote:

>
> A quick grep in resip/stack for the string "3455" shows that there is
> native resiprocate support for P-Called-Party-ID and P-Associated-URI, but
> no others (like P-Charging-Vector, P-Charging-Function-Addresses, etc.) or
> their associated parameters ("ecf", "ccf"). Is there a reason for this? If
> I add more of these RFC 3455 headers and parameters, should I bundle up the
> diff files and post them here for possible inclusion in future releases?
>
> -John Gregg
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at resiprocate.org
> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20140523/89e861a5/attachment.htm>