Hello François,<div><br></div><div><div class="gmail_quote">On Fri, Feb 5, 2010 at 11:18 AM, François Legal <span dir="ltr"><<a href="mailto:devel@thom.fr.eu.org">devel@thom.fr.eu.org</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<p>That lead me to think that maybe this is a non implemented feature and maybe the data in fsk_buffer should be sent somewhere to the card.</p>
<p> </p>
<p>Could anybody shed me some light on this.</p></blockquote></div><div>I am not terribly familiar with the analog code, but ...</div><div><br></div><div>The fsk buffer seems to be sent when calling send_caller_id(), which is called from ZAP_CHANNEL_STATE_CALLWAITING.</div>
<div><br></div><div>In any case, there is not much places where the modulated signal can be sent, everything goes down the file descriptor of the channel via zap_channel_write(). As I said, is done through send_caller_id() -> zap_channel_send_fsk_data() which sets the write function pointer to zchan_fsk_write_sample() and is then called back when calling zap_fsk_modulator_send_all().</div>
<div><br></div><div>May be you should take a look at src/testcid.c to learn about the API usage and src/zap_callerid.c to see the implementation.</div><div><br></div>-- <br>Moises Silva<br>Senior Software Engineer<br>Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON L3R 9T3 Canada<br>
t. 1 905 474 1990 x 128 | e. <a href="mailto:moy@sangoma.com">moy@sangoma.com</a><br>
</div>