<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">You have access to the full sdp in channel vars, so you can condition on those with regex.<div><br></div><div>Mike</div><div><br><div><br><div><div>On Sep 17, 2009, at 6:25 PM, Tihomir Culjaga wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi Michael, thanks for your response.<br><br>i think it will be enough to check the call capability... we always know the call is fax. We just need to apply the correct protocol :P<br><br><br>let's suppose you have 2 incoming calls:<br>
<ol><li>SDP containing G711, gsm, T.38 caps</li><li> SDP containing G711, gsm caps</li></ol><br>the caps will be known on within INVITE message and FS can act accordingly.<br><ul><li>If there is no T.38 support within SDP, start fax application (SpanDSP).</li>
<li>If there is T.38 suport within the SDP, route the call to some predefined gateway meant for T.38 fax receiving.</li></ul>In both cases, the fax should be received :P.<br><br>So, any chance to route the call according to T.38 caps within SDP message?<br>
<br><br><br>Now, for sending faxes there is some challenge.... we still have 2 calls:<br><br>we start sending a fax inband (SpanDSP) as this is the only thing we know... and:<br><ul><li>if we receive 200 OK with SDP containing G711, anyCaps => continue with InBand Fax</li>
<li>if we receive 200 OK with DSP containing anyCompressedCaps, T.38 => drop the call without sending ACK to 200 OK ... and move the fax to be sent into a different directory.</li></ul>well, as i said, while receiving faxes will work 100%, sending is tricky... but it might work.<br>
<br>what do you guys think?<br><br>T.<br><br><br><br><br><div class="gmail_quote">On Thu, Sep 17, 2009 at 10:51 PM, Michael Collins <span dir="ltr"><<a href="mailto:msc@freeswitch.org">msc@freeswitch.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br><br><div class="gmail_quote"><div class="im">On Tue, Sep 15, 2009 at 8:45 AM, Tihomir Culjaga <span dir="ltr"><<a href="mailto:tculjaga@gmail.com" target="_blank">tculjaga@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br><br>is there any way to route fax calls according to the call capability?<br><br>I mean .. if the fax call supports T.38 i'd like to route it to a T.38 capable gateway. All other fax calls (meaning inband) should be handled by FS/SpanDSP.<br>
Of course, I know that every fax call starts as a voice call and upon fax tone detection additional capabilities are being negotiated(T.38 or G711). Can it be done in early media, before the call is even answered?<br><br>
</blockquote></div><div>I don't claim to be an expert in all this, especially T.38, but if I understand correctly, in both cases the call needs to be answered first. I'm pretty sure that the sending fax machine won't start emitting the 1100Hz tone until the receiving end answers. Also, with T.38 doesn't the call have to come up and then T.38 gets negotiated? (I don't know, I have only read about it.)<br>
-MC<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">
<br><br>So, here the goal is to have a T.38 capable GW handling T.38 calls while SpanDSP handling T.30...<br><br><br>Any chance to do that with FS?<br><br><br>
<br></div>_______________________________________________<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>
<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>
<br></blockquote></div><br>
_______________________________________________<br>FreeSWITCH-users mailing list<br><a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>http://lists.freeswitch.org/mailman/listinfo/freeswitch-users<br>UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users<br>http://www.freeswitch.org<br></blockquote></div><br></div></div></body></html>