[Freeswitch-dev] Openzap and CLIP

devel at thom.fr.eu.org devel at thom.fr.eu.org
Mon Feb 15 14:40:38 PST 2010



I’m very happy to announce I could finally get this to work.


So far I only have a very dirty patch so I’ll try to arrange this a little bit, then I’ll post it to the list.


Does anybody have an idea on how to make the CID feature configurable (for the different standards used BELL/V23) ?




De : freeswitch-dev-bounces at lists.freeswitch.org [mailto:freeswitch-dev-bounces at lists.freeswitch.org] De la part de Moises Silva
Envoyé : mardi 9 février 2010 07:33
À : freeswitch-dev at lists.freeswitch.org
Objet : Re: [Freeswitch-dev] Openzap and CLIP


Hello François,


On Fri, Feb 5, 2010 at 11:18 AM, François Legal <devel at thom.fr.eu.org> wrote:

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.


Could anybody shed me some light on this.

I am not terribly familiar with the analog code, but ...


The fsk buffer seems to be sent when calling send_caller_id(), which is called from ZAP_CHANNEL_STATE_CALLWAITING.


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().


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.


Moises Silva
Senior Software Engineer
Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON L3R 9T3 Canada
t. 1 905 474 1990 x 128 | e. moy at sangoma.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-dev/attachments/20100215/b22fa5a4/attachment.html 

More information about the FreeSWITCH-dev mailing list