<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello,<br>
<br>
The current kamailio devel supports a single P-Asserted-ID or
P-Preferred-ID header value, but the RFC allows one or two either in
one or two headers. [<a href="http://tools.ietf.org/html/rfc3325">RFC3325</a>]<br>
I am most of the way through coding a fix, but Daniel's comment
about kamailio module licensing has prompted me to wonder about why
parse_ppi/pai is in lib/kcore.<br>
The dev-guide says new headers should be put in
parser/parse_xxx.[ch], but I wasn't going to change the location
unless something forces me to.<br>
<br>
Is there any guidance on whether I should leave the parse_pai/ppi
files in /lib/kcore or if they should be placed with other files in
/parser/?<br>
<br>
For information, my change extends the $ai, $pd, $pu, $pn and $pU
psuedo variables so they can be accessed with an index (e.g. $ai[0]
and $ai[1]) for the first and second instances of the header values,
whether they occur on one header (comma separated) or on two
headers. Existing usage will not be changed as $ai will continue to
return the first instance.<br>
<br>
Regards,<br>
Hugh<br>
<pre class="moz-signature" cols="72">--
Hugh Waite
Principal Design Engineer
Crocodile RCS Ltd.</pre>
</body>
</html>