[Freeswitch-dev] openzap information + mod_say_fr contribution

devel at thom.fr.eu.org devel at thom.fr.eu.org
Mon Jan 18 15:15:51 PST 2010

I’d be glad to be that test lab if that is the meaning of your message.


About ring_on_ms, changin this value may not be a good fix. I try to solve
my problems in an empiric way. I found out that setting ring_time to -1
could solve my intermittent ringing problem, but that may cause problems
with CLIP then (I took time to find the right document where CLIP FSK is
defined). I don’t know how it is implemented in openzap (which TAS is


I’d be really happy to help, but I will need some pointers to start.






De : freeswitch-dev-bounces at lists.freeswitch.org
[mailto:freeswitch-dev-bounces at lists.freeswitch.org] De la part de Anthony
Envoyé : lundi 18 janvier 2010 23:24
À : freeswitch-dev at lists.freeswitch.org
Objet : Re: [Freeswitch-dev] openzap information + mod_say_fr contribution



Thanks for the assistance.

jira.freeswitch.org is where you submit code 

ring_on_ms is currently hard coded in ozmod_wanpipe.c:1069

We anticipate problems with CLIP in non-US lines since I do not have any to
work with.
We can work together with Sangoma to get this working right in the future
once we have test lab to reproduce it.

On Mon, Jan 18, 2010 at 4:01 PM, <devel at thom.fr.eu.org> wrote:



First let me congratulate for this great software.


I was trying to diagnose a problem with my analog sangoma card, and FXS port
giving intermitent ringing and not sending CLIP.


I could see the intermitent ringing comes from this line.

zchan->ring_time = zap_current_time_in_ms() + wp_globals.ring_on_ms;


Setting zchan->ring_time could solve my problem, so could anybody indicate
how to configure ring_on_ms (preferably in an XML configuration)



The second point about CLIP is more difficult. First, let me indicate that
I’m residing in France and therefore using carrier and phones complying to
european standard.

About CLIP, I could see the V23 standard modulating frequencies are being
populated (in fsk_modem_definitions in fsk.c). However, in
zap_channel_send_fsk_data in zap_io.c, I could see that the BELL standard is
hardcoded. Replacing the modem type with FSK_V23_FORWARD_MODE2 (which by
what I could read seem to apply to me), I could see no difference.


As I could not find as much relevant information as I would like in V23
(apart from the frequencies for the FSK), I was wondering what were I could
find some information that could help to fix this.


I don’t know exactly what carrier_bits_start, carrier_bits_stop and
chan_sieze_bits refer to, but I could find in that document
(http://www.cs-strumentazione.com/manuali_pdf/clip.pdf) that « The Channel
Seizure is present only in FSK-V23 Protocol. It

consists in a series of 90 to 300 alternate SPACE/MARK bits


Considering this, I guess that I should use the else branch in the test «
zchan->token_count > 1 ». What does this token_count refer to and where
should I set it.


I’m still trying to figure this out (and will of course contribute the
result of all this), so any help appreciated.


I also did a contribution to mod_say_fr (to take into account the specific
french idioms in saying date and time). Could you please tell me how to
contribute this ?


Thanks in advance




FreeSWITCH-dev mailing list
FreeSWITCH-dev at lists.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 at hotmail.com
<mailto:MSN%3Aanthony_minessale at hotmail.com> 
GTALK/JABBER/PAYPAL:anthony.minessale at gmail.com
<mailto:PAYPAL%3Aanthony.minessale at gmail.com> 
IRC: irc.freenode.net #freeswitch

FreeSWITCH Developer Conference
sip:888 at conference.freeswitch.org
<mailto:sip%3A888 at conference.freeswitch.org> 
iax:guest at conference.freeswitch.org/888
googletalk:conf+888 at conference.freeswitch.org
<mailto:googletalk%3Aconf%2B888 at conference.freeswitch.org> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-dev/attachments/20100119/18edf9f8/attachment-0001.html 

More information about the FreeSWITCH-dev mailing list