<p>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 </p>
<p><blockquote type="cite">On Dec 17, 2009 1:07 PM, "Kristian Kielhofner" <<a href="mailto:kristian.kielhofner@gmail.com">kristian.kielhofner@gmail.com</a>> wrote:<br><br>Hello everyone,<br>
<br>
I've got two profiles running: s2s and trunk. The context for s2s is<br>
defined as s2s-in. The context for trunk is defined as trunk-in.<br>
trunk is bound to 192.168.168.3.<br>
<br>
recv 481 bytes from udp/[192.168.168.76]:5065 at 18:43:37.309706:<br>
------------------------------------------------------------------------<br>
REFER <a href="http://sip:mod_sofia@192.168.168.3:5060" target="_blank">sip:mod_sofia@192.168.168.3:5060</a> SIP/2.0<br>
Via: SIP/2.0/UDP 192.168.168.76:5065;branch=z9hG4bK__7539073431157335561_9<br>
To: "NONAME" <<a href="mailto:sip%3A19415551212@192.168.168.3">sip:19415551212@192.168.168.3</a>>;tag=BagvZeKSrj7yH<br>
From: <sip:9412848354@192.168.168.76:5065;transport=udp>;tag=203332153_1430350929_10<br>
Call-ID: e505f332-65de-122d-d183-eb12ad0ec1ac<br>
CSeq: 2 REFER<br>
Max-Forwards: 70<br>
Refer-To: <<a href="mailto:sip%3A6463959906@192.168.168.3">sip:6463959906@192.168.168.3</a>><br>
Contact: <sip:ssp@192.168.168.76:5065;transport=udp><br>
Content-Length: 0<br>
<br>
------------------------------------------------------------------------<br>
send 592 bytes to udp/[192.168.168.76]:5065 at 18:43:37.316093:<br>
------------------------------------------------------------------------<br>
SIP/2.0 202 Accepted<br>
Via: SIP/2.0/UDP 192.168.168.76:5065;branch=z9hG4bK__7539073431157335561_9<br>
From: <sip:9412848354@192.168.168.76:5065;transport=udp>;tag=203332153_1430350929_10<br>
To: "NONAME" <<a href="mailto:sip%3A9415551212@192.168.168.3">sip:9415551212@192.168.168.3</a>>;tag=BagvZeKSrj7yH<br>
Call-ID: e505f332-65de-122d-d183-eb12ad0ec1ac<br>
CSeq: 2 REFER<br>
Contact: <<a href="http://sip:mod_sofia@192.168.168.3:5060" target="_blank">sip:mod_sofia@192.168.168.3:5060</a>><br>
User-Agent: FreeSWITCH<br>
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE,<br>
SUBSCRIBE, NOTIFY, REFER, UPDATE, REGISTER, INFO<br>
Supported: precondition, path, replaces<br>
Allow-Events: talk, refer<br>
Content-Length: 0<br>
<br>
FS routed this to the s2s-in context, even though it was sent to the<br>
trunk profile. Shouldn't it have ended up in trunk-in? For the time<br>
being I wrote some crazy dialplan for s2s-in to transfer the call to<br>
trunk-in but I'm wondering what could be going on here.<br>
<br>
--<br>
Kristian Kielhofner<br>
<a href="http://www.astlinux.org" target="_blank">http://www.astlinux.org</a><br>
<a href="http://blog.krisk.org" target="_blank">http://blog.krisk.org</a><br>
<a href="http://www.star2star.com" target="_blank">http://www.star2star.com</a><br>
<a href="http://www.submityoursip.com" target="_blank">http://www.submityoursip.com</a><br>
<a href="http://www.voalte.com" target="_blank">http://www.voalte.com</a><br>
<br>
_______________________________________________<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</blockquote></p>