Victor, Jesus,<br>thanks for the replies. <br>But the use of Remote-Party-ID/PAI (or non-use, depending on the terminating equipment), is a subsequent step. First I have to identify the subscriber based on the alias: the subscriber will have several of them and will send any one of them to us in the INVITE. The alias will be set in the header From, so what I need is a way to perform its lookup at table dbaliases. Then, authenticate the subscriber and finally relay the INVITE (using Remote-Party-ID/PAI or not).<br>
<br>regards,<br>takeshi<br><br><div><span class="gmail_quote">On 7/19/08, <b class="gmail_sendername">Victor Pascual Ávila</b> <<a href="mailto:victor.pascual.avila@gmail.com">victor.pascual.avila@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Fri, Jul 18, 2008 at 2:33 PM, Jesus Rodriguez <<a href="mailto:jesusr@voztele.com">jesusr@voztele.com</a>> wrote:<br> > You can use both Remote-Party-ID and PAI headers for sending the<br> > caller id to the gateway:<br>
><br> > append_rpid_hf() for rpid or append_hf() for PAI.<br> <br> <br>Jesus is right.<br> <br> Please, bear in mind that Remote-Party-ID is not standard and has been<br> replaced with PAI-- anyway RPID is implemented in most Cisco stuff.<br>
<br> My two cents,<br> --<br> <br>Victor Pascual Ávila<br> </blockquote></div><br>