Victor, Jesus, thanks for the replies. 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).
regards, takeshi On 7/19/08, Victor Pascual Ávila <[EMAIL PROTECTED]> wrote: > > On Fri, Jul 18, 2008 at 2:33 PM, Jesus Rodriguez <[EMAIL PROTECTED]> > wrote: > > You can use both Remote-Party-ID and PAI headers for sending the > > caller id to the gateway: > > > > append_rpid_hf() for rpid or append_hf() for PAI. > > > Jesus is right. > > Please, bear in mind that Remote-Party-ID is not standard and has been > replaced with PAI-- anyway RPID is implemented in most Cisco stuff. > > My two cents, > -- > > Victor Pascual Ávila >
_______________________________________________ Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users
