Thanks for the hint! force_transfer_context and force_transfer_dialplan.
I've updated the wiki (I'll add an example once I test it). On Thu, Dec 17, 2009 at 5:06 PM, Anthony Minessale <[email protected]> wrote: > The calls inherit the context from the parent, I think there is a var you > can set on the chan to pick what context to use in a transfer like > transfer_context or something grep the code for it > > On Dec 17, 2009 1:07 PM, "Kristian Kielhofner" > <[email protected]> wrote: > > Hello everyone, > > I've got two profiles running: s2s and trunk. The context for s2s is > defined as s2s-in. The context for trunk is defined as trunk-in. > trunk is bound to 192.168.168.3. > > recv 481 bytes from udp/[192.168.168.76]:5065 at 18:43:37.309706: > ------------------------------------------------------------------------ > REFER sip:[email protected]:5060 SIP/2.0 > Via: SIP/2.0/UDP 192.168.168.76:5065;branch=z9hG4bK__7539073431157335561_9 > To: "NONAME" <sip:[email protected]>;tag=BagvZeKSrj7yH > From: > <sip:[email protected]:5065;transport=udp>;tag=203332153_1430350929_10 > Call-ID: e505f332-65de-122d-d183-eb12ad0ec1ac > CSeq: 2 REFER > Max-Forwards: 70 > Refer-To: <sip:[email protected]> > Contact: <sip:[email protected]:5065;transport=udp> > Content-Length: 0 > > ------------------------------------------------------------------------ > send 592 bytes to udp/[192.168.168.76]:5065 at 18:43:37.316093: > ------------------------------------------------------------------------ > SIP/2.0 202 Accepted > Via: SIP/2.0/UDP 192.168.168.76:5065;branch=z9hG4bK__7539073431157335561_9 > From: > <sip:[email protected]:5065;transport=udp>;tag=203332153_1430350929_10 > To: "NONAME" <sip:[email protected]>;tag=BagvZeKSrj7yH > Call-ID: e505f332-65de-122d-d183-eb12ad0ec1ac > CSeq: 2 REFER > Contact: <sip:[email protected]:5060> > User-Agent: FreeSWITCH > Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, > SUBSCRIBE, NOTIFY, REFER, UPDATE, REGISTER, INFO > Supported: precondition, path, replaces > Allow-Events: talk, refer > Content-Length: 0 > > FS routed this to the s2s-in context, even though it was sent to the > trunk profile. Shouldn't it have ended up in trunk-in? For the time > being I wrote some crazy dialplan for s2s-in to transfer the call to > trunk-in but I'm wondering what could be going on here. > > -- > Kristian Kielhofner > http://www.astlinux.org > http://blog.krisk.org > http://www.star2star.com > http://www.submityoursip.com > http://www.voalte.com > > _______________________________________________ > FreeSWITCH-users mailing list > [email protected] > http://lists.freeswitch.org/mailman/listinfo/freeswitch-users > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users > http://www.freeswitch.org > > _______________________________________________ > FreeSWITCH-users mailing list > [email protected] > http://lists.freeswitch.org/mailman/listinfo/freeswitch-users > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users > http://www.freeswitch.org > > -- Kristian Kielhofner http://www.astlinux.org http://blog.krisk.org http://www.star2star.com http://www.submityoursip.com http://www.voalte.com _______________________________________________ FreeSWITCH-users mailing list [email protected] http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
