Re: [Freeswitch-dev] Openzap and intermitent ringing
Hi again François, Please keep the conversation in the freeswitch-dev mailing list, unless you want private paid support ;-) See the answer to your question below ... On Wed, Jan 20, 2010 at 3:57 AM, François Legal <devel@thom.fr.eu.org>wrote:
Do you know if there is a way (except using an oscilloscope to sample the line signal) to get a dump of the data sent to the card by openzap (is it samples or something) and vice versa.
What I would like to do is see what is returned to openzap when a call arrives on an FXO port (CLIP is working in that direction) and compare it to what is being sent to the card when sending CLIP to and FXS port.
Once the call gets into the computer we're talking about digital audio samples. In a typical configuration a Sangoma board will give you 160 samples of audio each 20ms (most likely encoded in ulaw, that can be verified in /etc/wanpipe/wanpipex.conf for the FXO/FXS board, look at the TDMV_LAW parameter). There is an openzap API command to record the digital audio read from the board, check ZAP_COMMAND_TRACE_INPUT and ZAP_COMMAND_TRACE_OUTPUT. What we currently lack is a FreeSWITCH command in mod_openzap to enable/disable the audio tracing. It should be trivial to hack mod_openzap.c and add that command, if you need help with that ping me on IRC (moy). -- 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@sangoma.com
So I did modify mod_openzap to provide the od trace command to the cli. I started trying to parse the incoming clip, but I have to do it again as the incoming signal is saturated so I can't see anything interesting. I'll post my results whenever I get something. Shall I send the modified mod_openzap.c to the list ? About the difference on the modulation settings for CLIP, could anybody suggest some way to have it configurable by files ? Thanks François On Wed, 20 Jan 2010 14:01:03 -0500, Moises Silva wrote: Hi again François, Please keep the conversation in the freeswitch-dev mailing list, unless you want private paid support ;-) See the answer to your question below ... On Wed, Jan 20, 2010 at 3:57 AM, François Legal wrote: Do you know if there is a way (except using an oscilloscope to sample the line signal) to get a dump of the data sent to the card by openzap (is it samples or something) and vice versa. What I would like to do is see what is returned to openzap when a call arrives on an FXO port (CLIP is working in that direction) and compare it to what is being sent to the card when sending CLIP to and FXS port. Once the call gets into the computer we're talking about digital audio samples. In a typical configuration a Sangoma board will give you 160 samples of audio each 20ms (most likely encoded in ulaw, that can be verified in /etc/wanpipe/wanpipex.conf for the FXO/FXS board, look at the TDMV_LAW parameter). There is an openzap API command to record the digital audio read from the board, check ZAP_COMMAND_TRACE_INPUT and ZAP_COMMAND_TRACE_OUTPUT. What we currently lack is a FreeSWITCH command in mod_openzap to enable/disable the audio tracing. It should be trivial to hack mod_openzap.c and add that command, if you need help with that ping me on IRC (moy). -- 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@sangoma.com [2] Links: ------ [1] mailto:devel@thom.fr.eu.org [2] mailto:moy@sangoma.com
On Jan 27, 2010, at 3:48 AM, François Legal wrote:
So I did modify mod_openzap to provide the od trace command to the cli. I started trying to parse the incoming clip, but I have to do it again as the incoming signal is saturated so I can't see anything interesting.
I'll post my results whenever I get something.
Shall I send the modified mod_openzap.c to the list ?
We should get a bug opened on this issue on http://jira.freeswitch.org
About the difference on the modulation settings for CLIP, could anybody suggest some way to have it configurable by files ?
We should add some config option based on country or CLIP type to specify this. Lets get it working and we can think how to configure once we have that. Mike
Hello, I'm back on this. I could take samples of what is sent by my carrier as CLIP and what is sent by my FXS port as CLIP, and this is very different. The modulation to be sent out of FXS seem to be correctly built, but this seem to never get out. By further checking what could happen, I could see that for FSK/DTMF/... the data is written to some dedicated buffer (fsk_buffer/...) using the zap_buffer_write function. I continued to see what was done with this fsk_buffer, and surprisingly, it seems that nothing is done. I could find the beginning of something in ozmod_analog.c. these lines commented out : if ((zchan->dtmf_buffer && zap_buffer_inuse(zchan->dtmf_buffer)) || (zchan->fsk_buffer & //memset(frame, 0, len); //zap_channel_write(zchan, frame, sizeof(frame), continue; } so that seem to be related to fsk_buffer (by the way sending dtmf tones out of FXS does not seem to work either, tried with send_dtmf application in diaplan), but I don't really get what would be done here (if uncommented) except sending null values to that function, which would (I found this function in zap_io.c) lead to doing nothing as this function verifies the condition zchan->fsk_buffer & padding-left: 5px; margin-left: 5px; width: 100%;"> On Jan 27, 2010, at 3:48 AM, François Legal wrote: So I did modify mod_openzap to provide the od trace command to the cli. I started trying to parse the incoming clip, but I have to do it again as the incoming signal is saturated so I can't see anything interesting. I'll post my results whenever I get something. Shall I send the modified mod_openzap.c to the list ? We should get a bug opened on this issue on http://jira.freeswitch.org [1] About the difference on the modulation settings for CLIP, could anybody suggest some way to have it configurable by files ? We should add some config option based on country or CLIP type to specify this. Lets get it working and we can think how to configure once we have that. Mike Links: ------ [1] http://jira.freeswitch.org
Hello François, On Fri, Feb 5, 2010 at 11:18 AM, François Legal <devel@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@sangoma.com
Hello, 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) ? François De : freeswitch-dev-bounces@lists.freeswitch.org [mailto:freeswitch-dev-bounces@lists.freeswitch.org] De la part de Moises Silva Envoyé : mardi 9 février 2010 07:33 À : freeswitch-dev@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@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@sangoma.com
Hello, Here comes the patch. The patch fixes the CID for France (and probably other european countries except maybe england where a specific TAS has to be used), both for incoming calls and call waiting cases. If anybody can try this patch with US hardware to verify the compatibility. I added a new parameter in openzap.conf (modem-type defaulting to FSK_BELL202) so that modulation can be specified in config. The patch also adds the MWI functionnality on FXS ports (that meant to also patch mod_voicemail), by using the MWI-Account parameter in directory set to something like "openzap/x/y". Please comment on this, if any modification need to be made. François On Mon, 15 Feb 2010 23:40:38 +0100, wrote: Hello, 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) ? François DE : freeswitch-dev-bounces@lists.freeswitch.org [mailto:freeswitch-dev-bounces@lists.freeswitch.org] DE LA PART DE Moises Silva ENVOY : mardi 9 février 2010 07:33 : freeswitch-dev@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 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@sangoma.com [1] Links: ------ [1] mailto:moy@sangoma.com
where? On Feb 24, 2010, at 3:53 AM, François Legal wrote:
Hello,
Here comes the patch.
The patch fixes the CID for France (and probably other european countries except maybe england where a specific TAS has to be used), both for incoming calls and call waiting cases.
If anybody can try this patch with US hardware to verify the compatibility.
I added a new parameter in openzap.conf (modem-type defaulting to FSK_BELL202) so that modulation can be specified in config.
The patch also adds the MWI functionnality on FXS ports (that meant to also patch mod_voicemail), by using the MWI-Account parameter in directory set to something like "openzap/x/y".
Please comment on this, if any modification need to be made.
François
Oh, you're right. I always forget to attach files ;-) François On Wed, 24 Feb 2010 04:13:38 -0500, Michael Jerris wrote: where? On Feb 24, 2010, at 3:53 AM, François Legal wrote: Hello, Here comes the patch. The patch fixes the CID for France (and probably other european countries except maybe england where a specific TAS has to be used), both for incoming calls and call waiting cases. If anybody can try this patch with US hardware to verify the compatibility. I added a new parameter in openzap.conf (modem-type defaulting to FSK_BELL202) so that modulation can be specified in config. The patch also adds the MWI functionnality on FXS ports (that meant to also patch mod_voicemail), by using the MWI-Account parameter in directory set to something like "openzap/x/y". Please comment on this, if any modification need to be made. François
Can you post it to http://jira.freeswitch.org under a new feature issue? On Wed, Feb 24, 2010 at 3:27 AM, François Legal <devel@thom.fr.eu.org>wrote:
Oh, you're right. I always forget to attach files ;-)
François
On Wed, 24 Feb 2010 04:13:38 -0500, Michael Jerris <mike@jerris.com> wrote:
where?
On Feb 24, 2010, at 3:53 AM, François Legal wrote:
Hello,
Here comes the patch.
The patch fixes the CID for France (and probably other european countries except maybe england where a specific TAS has to be used), both for incoming calls and call waiting cases.
If anybody can try this patch with US hardware to verify the compatibility.
I added a new parameter in openzap.conf (modem-type defaulting to FSK_BELL202) so that modulation can be specified in config.
The patch also adds the MWI functionnality on FXS ports (that meant to also patch mod_voicemail), by using the MWI-Account parameter in directory set to something like "openzap/x/y".
Please comment on this, if any modification need to be made.
François
_______________________________________________ FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
-- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com <MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <sip%3A888@conference.freeswitch.org> iax:guest@conference.freeswitch.org/888 googletalk:conf+888@conference.freeswitch.org<googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:+19193869900
Shall I make a separate patch for the MWI and post this one as a new feature ? François On Wed, 24 Feb 2010 13:30:04 -0600, Anthony Minessale wrote: Can you post it to http://jira.freeswitch.org [1] under a new feature issue? On Wed, Feb 24, 2010 at 3:27 AM, François Legal wrote: Oh, you're right. I always forget to attach files ;-) François On Wed, 24 Feb 2010 04:13:38 -0500, Michael Jerris wrote: where? On Feb 24, 2010, at 3:53 AM, François Legal wrote: Hello, Here comes the patch. The patch fixes the CID for France (and probably other european countries except maybe england where a specific TAS has to be used), both for incoming calls and call waiting cases. If anybody can try this patch with US hardware to verify the compatibility. I added a new parameter in openzap.conf (modem-type defaulting to FSK_BELL202) so that modulation can be specified in config. The patch also adds the MWI functionnality on FXS ports (that meant to also patch mod_voicemail), by using the MWI-Account parameter in directory set to something like "openzap/x/y". Please comment on this, if any modification need to be made. François _______________________________________________ FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org [4] http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev [5] UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev [6] http://www.freeswitch.org [7] -- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ [8] ClueCon http://www.cluecon.com/ [9] Twitter: http://twitter.com/FreeSWITCH_wire [10] AIM: anthm MSN:anthony_minessale@hotmail.com [11] GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com [12] IRC: irc.freenode.net [13] #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org [14] iax:guest@conference.freeswitch.org/888 [15] googletalk:conf+888@conference.freeswitch.org [16] pstn:+19193869900 Links: ------ [1] http://jira.freeswitch.org [2] mailto:devel@thom.fr.eu.org [3] mailto:mike@jerris.com [4] mailto:FreeSWITCH-dev@lists.freeswitch.org [5] http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev [6] http://lists.freeswitch.org/mailman/options/freeswitch-dev [7] http://www.freeswitch.org [8] http://www.freeswitch.org/ [9] http://www.cluecon.com/ [10] http://twitter.com/FreeSWITCH_wire [11] mailto:MSN%3Aanthony_minessale@hotmail.com [12] mailto:PAYPAL%3Aanthony.minessale@gmail.com [13] http://irc.freenode.net [14] mailto:sip%3A888@conference.freeswitch.org [15] http://iax:guest@conference.freeswitch.org/888 [16] mailto:googletalk%3Aconf%2B888@conference.freeswitch.org
just file each patch you have under openzap category and we can have someone work on it. On Wed, Feb 24, 2010 at 3:27 PM, François Legal <devel@thom.fr.eu.org>wrote:
Shall I make a separate patch for the MWI and post this one as a new feature ?
François
On Wed, 24 Feb 2010 13:30:04 -0600, Anthony Minessale < anthony.minessale@gmail.com> wrote:
Can you post it to http://jira.freeswitch.org under a new feature issue?
On Wed, Feb 24, 2010 at 3:27 AM, François Legal <devel@thom.fr.eu.org>wrote:
Oh, you're right. I always forget to attach files ;-)
François
On Wed, 24 Feb 2010 04:13:38 -0500, Michael Jerris <mike@jerris.com> wrote:
where?
On Feb 24, 2010, at 3:53 AM, François Legal wrote:
Hello,
Here comes the patch.
The patch fixes the CID for France (and probably other european countries except maybe england where a specific TAS has to be used), both for incoming calls and call waiting cases.
If anybody can try this patch with US hardware to verify the compatibility.
I added a new parameter in openzap.conf (modem-type defaulting to FSK_BELL202) so that modulation can be specified in config.
The patch also adds the MWI functionnality on FXS ports (that meant to also patch mod_voicemail), by using the MWI-Account parameter in directory set to something like "openzap/x/y".
Please comment on this, if any modification need to be made.
François
_______________________________________________ FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
-- Anthony Minessale II
FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire
AIM: anthm MSN:anthony_minessale@hotmail.com <MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch
FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <sip%3A888@conference.freeswitch.org> iax:guest@conference.freeswitch.org/888 googletalk:conf+888@conference.freeswitch.org<googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:+19193869900
_______________________________________________ FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
-- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com <MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <sip%3A888@conference.freeswitch.org> iax:guest@conference.freeswitch.org/888 googletalk:conf+888@conference.freeswitch.org<googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:+19193869900
Done, I created a bug report for CID and a new feature for MWI. François On Wed, 24 Feb 2010 17:04:32 -0600, Anthony Minessale wrote: just file each patch you have under openzap category and we can have someone work on it. On Wed, Feb 24, 2010 at 3:27 PM, François Legal wrote: Shall I make a separate patch for the MWI and post this one as a new feature ? François On Wed, 24 Feb 2010 13:30:04 -0600, Anthony Minessale wrote: Can you post it to http://jira.freeswitch.org [3] under a new feature issue? On Wed, Feb 24, 2010 at 3:27 AM, François Legal wrote: Oh, you're right. I always forget to attach files ;-) François On Wed, 24 Feb 2010 04:13:38 -0500, Michael Jerris wrote: where? On Feb 24, 2010, at 3:53 AM, François Legal wrote: Hello, Here comes the patch. The patch fixes the CID for France (and probably other european countries except maybe england where a specific TAS has to be used), both for incoming calls and call waiting cases. If anybody can try this patch with US hardware to verify the compatibility. I added a new parameter in openzap.conf (modem-type defaulting to FSK_BELL202) so that modulation can be specified in config. The patch also adds the MWI functionnality on FXS ports (that meant to also patch mod_voicemail), by using the MWI-Account parameter in directory set to something like "openzap/x/y". Please comment on this, if any modification need to be made. François _______________________________________________ FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org [6] http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev [7] UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev [8] http://www.freeswitch.org [9] -- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ [10] ClueCon http://www.cluecon.com/ [11] Twitter: http://twitter.com/FreeSWITCH_wire [12] AIM: anthm MSN:anthony_minessale@hotmail.com [13] GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com [14] IRC: irc.freenode.net [15] #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org [16] iax:guest@conference.freeswitch.org/888 [17] googletalk:conf+888@conference.freeswitch.org [18] pstn:+19193869900 _______________________________________________ FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org [19] http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev [20] UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev [21] http://www.freeswitch.org [22] -- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ [23] ClueCon http://www.cluecon.com/ [24] Twitter: http://twitter.com/FreeSWITCH_wire [25] AIM: anthm MSN:anthony_minessale@hotmail.com [26] GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com [27] IRC: irc.freenode.net [28] #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org [29] iax:guest@conference.freeswitch.org/888 [30] googletalk:conf+888@conference.freeswitch.org [31] pstn:+19193869900 Links: ------ [1] mailto:devel@thom.fr.eu.org [2] mailto:anthony.minessale@gmail.com [3] http://jira.freeswitch.org [4] mailto:devel@thom.fr.eu.org [5] mailto:mike@jerris.com [6] mailto:FreeSWITCH-dev@lists.freeswitch.org [7] http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev [8] http://lists.freeswitch.org/mailman/options/freeswitch-dev [9] http://www.freeswitch.org [10] http://www.freeswitch.org/ [11] http://www.cluecon.com/ [12] http://twitter.com/FreeSWITCH_wire [13] mailto:MSN%3Aanthony_minessale@hotmail.com [14] mailto:PAYPAL%3Aanthony.minessale@gmail.com [15] http://irc.freenode.net [16] mailto:sip%3A888@conference.freeswitch.org [17] http://iax:guest@conference.freeswitch.org/888 [18] mailto:googletalk%3Aconf%2B888@conference.freeswitch.org [19] mailto:FreeSWITCH-dev@lists.freeswitch.org [20] http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev [21] http://lists.freeswitch.org/mailman/options/freeswitch-dev [22] http://www.freeswitch.org [23] http://www.freeswitch.org/ [24] http://www.cluecon.com/ [25] http://twitter.com/FreeSWITCH_wire [26] mailto:MSN%3Aanthony_minessale@hotmail.com [27] mailto:PAYPAL%3Aanthony.minessale@gmail.com [28] http://irc.freenode.net [29] mailto:sip%3A888@conference.freeswitch.org [30] http://iax:guest@conference.freeswitch.org/888 [31] mailto:googletalk%3Aconf%2B888@conference.freeswitch.org
participants (5)
-
Anthony Minessale
-
devel＠thom.fr.eu.org
-
François Legal
-
Michael Jerris
-
Moises Silva