No, it's not included. The patch is attached to this JIRA bug report. Go to jira.freeswitch.org, then find the freetdm section, and look for open/in progress issues. You'll find one which is tagged OPENZAP-100. Then inside this one, there is a file patch-mwi1.txt attached. It should be the one to go. Patch your freetdm source tree with this file, then rebuild mod_freetdm and install the lib in your freeswitch setup. You then have to add the lines modem_type = FSK_V23_FORWARD_MODE1 (or the modulation type that best fits your setup) in freetdm.conf, and you should be good to go. Or at least try. François On Wed, 8 Sep 2010 19:49:12 +1000, Brian May <brian@microcomaustralia.com.au> wrote:
On 8 September 2010 19:11, François Legal <devel@thom.fr.eu.org> wrote:
Well, there seem to be a specific standard for Australia. You should maybe dig about how CID is supposed to be signaled in this standard. Here in France, CID has to be sent before the first ring pulse, or between first and second ring pulse. I made a patch for freetdm and this works for me.
Hmmm. You might be on to something here. It wouldn't surprise me at all if out standards are similar to France.
Unfortunately having problems finding anything more definite then this, except for pages for Asterisk that say I have to change:
sendcalleridafter=1
to
sendcalleridafter=2
<http://www.voip-info.org/wiki/view/Australia+Asterisk+Details>
I did make an update to latest trunk a month ago, and the patch could be almost successfully applied. It should be attached to JIRA OPENZAP-100.
What do you mean by "JIRA OPENZAP-100"?
I have updated to the latest Freeswitch Trunk, not sure if you mean your patch has been included or not.