<div dir="ltr">I spoke too soon. Exporting sip_call_id doesn't throw an error, but it doesn't seem to do anything either. I'm not sure what I was looking at the first time.<div><br></div><div>Your second recommendation of setting the origination_uuid and having the outbound param set does indeed work for. Triple checked. :)<div>
<br></div><div><br></div><div>Thanks,</div><div>Jeff</div><div><br></div><div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Aug 21, 2013 at 1:22 PM, Jeff Pyle <span dir="ltr"><<a href="mailto:jpyle@fidelityvoice.com" target="_blank">jpyle@fidelityvoice.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">You're right, I had quite a bit wrong. This is very helpful.<div><br></div><div>Exporting sip_call_id works. Thanks!</div>
<span class="HOEnZb"><font color="#888888"><div><br></div><div><br></div><div><br></div><div>- Jeff</div></font></span><div><div class="h5"><div><br></div><div>
<div><div><div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Wed, Aug 21, 2013 at 9:53 AM, Steven Ayre <span dir="ltr"><<a href="mailto:steveayre@gmail.com" target="_blank">steveayre@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span style="font-family:arial,sans-serif;font-size:13px">They didn't seem to have any effect - I still saw a new SIP callid on the b-leg INVITE</span></blockquote>
<div><br></div></div><div>Perhaps you're misunderstanding the purpose of them.</div><div><br></div><div>Every channel in FreeSWITCH has a UUID. On a bridge you have two different channels (inbound & outbound). Their UUIDs -must- be different, to tell them apart.</div>
<div><br></div><div>The setting you found sets the UUID from the Call-ID on the inbound channel, and visa versa for the outbound channel. That mostly makes it easier to match up packet traces to calls, and your CDRs to a customers (since they know the Call-ID but not your internal UUID).</div>
<div><br></div><div>If you set both the UUID of the incoming channel will be the incoming Call-ID, the outgoing UUID will be generated by FreeSWITCH and the outgoing Call-ID will match the outgoing UUID. You cannot set the same UUID for both.</div>
<div><br></div><div>Have you tried exporting the sip_call_id variable from the aleg to the bleg? I don't know if that variable is read-only though. If sofia will read from that should be sufficient, you won't need to tweak the UUIDs of the channels.</div>
<div><br></div><div>If that doesn't work you could also try setting origination_uuid to sip_call_id in the bridge dialstring, along with the outgoing parameter you found.</div><div><br></div><div>-Steve</div><div><div>
<div><br>
</div><div class="gmail_extra">
<br><br><div class="gmail_quote">On 21 August 2013 13:21, Jeff Pyle <span dir="ltr"><<a href="mailto:jpyle@fidelityvoice.com" target="_blank">jpyle@fidelityvoice.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div>I was afraid of that on the inbound side. It makes sense.<br></div><div><br></div><div>The short answer is sometimes I want full topology-hiding, other times I want the same SIP callid all the way through. Managing it per-profile could work. It has to do with correlating voice-quality monitoring on the private side with other measurements from the public side. In cases where this happens, the same callid on both sides makes things much, much easier.</div>
<div><br></div><div>Yesterday I tried enabling both inbound-use-callid-as-uuid and outbound-use-uuid-as-callid on both the public and private profiles. They didn't seem to have any effect - I still saw a new SIP callid on the b-leg INVITE. I wasn't sure how to debug it from there.</div>
<div><br></div><div><br></div><div class="gmail_extra"><div><div dir="ltr"><div>- Jeff</div></div></div>
<br><br><div class="gmail_quote"><div><div>On Wed, Aug 21, 2013 at 6:17 AM, Steven Ayre <span dir="ltr"><<a href="mailto:steveayre@gmail.com" target="_blank">steveayre@gmail.com</a>></span> wrote:<br></div>
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div>
It would be too late for inbound in the dialplan as the channel already exists, therefore already has a uuid. Though you can change the uuid, you'd still have issues whenever a call hung up so quickly it never reached the dialplan (yes, I've seen that happen).<div>
<div><div><br></div><div><div>Outbound you may have a chance with - but I don't know if such a variable exists.<span></span></div><div><br></div><div>Is there a reason you can't just set it on the profile?</div><div>
<div><div>
<br></div><div><br></div><div><br>On Tuesday, August 20, 2013, Jeff Pyle wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div><div dir="ltr">
<div>Hello,</div><div><br></div><div>Is it possible to set the equivalent of inbound-use-uuid-as-callid or outbound-use-uuid-as-callid per channel from within the dialplan?</div><div><br>
</div><div><br></div><div>- Jeff</div><div><br></div></div></div>
</div>
</blockquote></div></div></div></div></div></div>
<br></div></div>_________________________________________________________________________<br>
Professional FreeSWITCH Consulting Services:<br>
<a href="mailto:consulting@freeswitch.org" target="_blank">consulting@freeswitch.org</a><br>
<a href="http://www.freeswitchsolutions.com" target="_blank">http://www.freeswitchsolutions.com</a><br>
<br>
FreeSWITCH-powered IP PBX: The CudaTel Communication Server<br>
<a href="http://www.cudatel.com" target="_blank">http://www.cudatel.com</a><br>
<br>
Official FreeSWITCH Sites<br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<a href="http://wiki.freeswitch.org" target="_blank">http://wiki.freeswitch.org</a><br>
<a href="http://www.cluecon.com" target="_blank">http://www.cluecon.com</a><br>
<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org" target="_blank">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>
<br></blockquote></div><br></div></div>
<br>_________________________________________________________________________<br>
Professional FreeSWITCH Consulting Services:<br>
<a href="mailto:consulting@freeswitch.org" target="_blank">consulting@freeswitch.org</a><br>
<a href="http://www.freeswitchsolutions.com" target="_blank">http://www.freeswitchsolutions.com</a><br>
<br>
FreeSWITCH-powered IP PBX: The CudaTel Communication Server<br>
<a href="http://www.cudatel.com" target="_blank">http://www.cudatel.com</a><br>
<br>
Official FreeSWITCH Sites<br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<a href="http://wiki.freeswitch.org" target="_blank">http://wiki.freeswitch.org</a><br>
<a href="http://www.cluecon.com" target="_blank">http://www.cluecon.com</a><br>
<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org" target="_blank">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>
<br></blockquote></div><br></div></div></div></div>
<br>_________________________________________________________________________<br>
Professional FreeSWITCH Consulting Services:<br>
<a href="mailto:consulting@freeswitch.org" target="_blank">consulting@freeswitch.org</a><br>
<a href="http://www.freeswitchsolutions.com" target="_blank">http://www.freeswitchsolutions.com</a><br>
<br>
FreeSWITCH-powered IP PBX: The CudaTel Communication Server<br>
<a href="http://www.cudatel.com" target="_blank">http://www.cudatel.com</a><br>
<br>
Official FreeSWITCH Sites<br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<a href="http://wiki.freeswitch.org" target="_blank">http://wiki.freeswitch.org</a><br>
<a href="http://www.cluecon.com" target="_blank">http://www.cluecon.com</a><br>
<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org" target="_blank">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>
<br></blockquote></div><br></div></div></div></div></div></div></div></div>
</blockquote></div><br></div></div></div></div>