Hi Pekka, Thank you for replying to my email.
> > Do you have multiple nta_agent_t instances running, or how do you > handle the UAS side? What kind of task you plan to implement in the > cloned task, some kind of db lookup? > Yes, I am using DB to store routing information. > If you want to see later messages from UAC, you need to insert a > Record-Route header into the request which you forward towards the > UAS. I am looking at http://sofia-sip.sourceforge.net/refdocs/sip/group__sip__record__route.html which shows how to creat a record_route structure. How do I add it to the outgoing sip message? Which api should I use? Also, should I store both UAC-related RR and UAS-related RR in the RR-URI's user part? In the hash table you suggested, should I use an UUID to represent each leg ( one for UAC and the other one for UAS) and then store the leg corrspond to each UUID? Also, I don't understand why it matter whether I am using one or two nta_agent_t. I still need two UUID ( one for each leg ) regardless of whether I use one or two nta_agent_t right? Or am I missing something? > > You have to remove the resulting Route headers when processing the > later messages, too. Which API can I use to remove the Route header and when you say later messages, what are you referring to? When should the Route header be removed? I have learn a lot from all those emails you posted in the mailing list. Thanks alot for all your help. P ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel