FYI: private emails sent from mailing lists discussions are simply ignored, keep the mailing list in the discussion. Thanks.
On 7/11/12 9:13 AM, mike wrote:
yes , i know that the path could be added by the path module , but ,the problem is the flow token,such as the path
Path: <sip:VskztcQ/S8p4WPbOnHbuyh5iJvJIW3ib@ep1.example.com mailto:S8p4WPbOnHbuyh5iJvJIW3ib@ep1.example.com;lr;ob>
the VskztcQ/S8p4WPbOnHbuyh5iJvJIW3ib is the token , so , where the kamilio 3.3 handle it ?
On Wed, Jul 11, 2012 at 3:00 PM, Daniel-Constantin Mierla <miconda@gmail.com mailto:miconda@gmail.com> wrote:
Hello, On 7/11/12 4:23 AM, mike wrote: dear kamilio developers : i read the kamilio 3.3.0' s new features , it say it support outbound , and i have place to handle reg-id and sip.instance . so , i wonder if the kamilio3.3.0 support RFC5626 now,so that the kamilio can be used as a edge proxy . i ask why because i can't find where kamilio add flow-token and path for the register request. sip.instance and reg-id are handled by the registrar/usrloc modules. Path has to be added by intermediary proxies and it is also handled by registrar module. If the intermediary proxies are kamailio, then adding path is possible via path module. Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda> - http://www.linkedin.com/in/miconda Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - http://asipto.com/u/katu Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 - http://asipto.com/u/kpw