That assumes there is a SIP standard that includes this and your gateway supports it. In my case, I added a custom header to send extra information (DNIS in my case.) Caller ID is sent in the call_info, but ANI is different than Caller ID and your gateway could insert any or none of these in there. Norman Franke Answering Service for Directors, Inc. www.myasd.com On Mar 10, 2008, at 3:07 PM, Jo?o Mesquita wrote: > I think you just need to parse the call_info struct and get the > remote_contact. > > Mesquita > > On Mon, 2008-03-10 at 10:07 -0700, logan wrote: >> Hi, >> >> I need to have ANI support in my application. Does PJSIP support it? >> If not then how should I go about to add it? >> >> Thanks. >> >> Best Regards, >> Hitesh >> >> _______________________________________________ >> Visit our blog: http://blog.pjsip.org >> >> pjsip mailing list >> pjsip at lists.pjsip.org >> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip at lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20080310/796d11e3/attachment.html
