Hi Anthony, Thanks for your response. I find strange that this is not a common feature, it's really difficult to get Telcos to answer to magic words such as disconnect supervision. If tone based disconnect is not used, is "current interrupt" the only supported disconnect method on a loopstart line or is it polarity reversal supported as well? Regards, On Tue, Sep 2, 2008 at 9:43 AM, Anthony Minessale < anthony.minessale@gmail.com> wrote:
openzap does not have tone based hangup detection support coded into it. That's why it only works when you use FreeSWITCH to do it in the general dialplan.
It's simply a feature we have not had demand for yet in OpenZAP. I'm sure we could add it if we can find the time/resources.
On Mon, Sep 1, 2008 at 7:47 PM, Luis F Urrea <lfurrea@gmail.com> wrote:
Hi All,
I have been working for quite a while in trying to get Openzap to recognize my country specific busy tone in order to hang up an analog FXO channel.
Basically, I am having FXO disconnect supervision issues and I wanted to know if it's possible to hang up the FXO by monitoring call progress tones so that when there is a busy tone the FXO goes on hook.
I have been tweaking the /etc/openzap/tones.conf based on the ITU.T recommendation E.180 for my country, but so far it doesn't even seem that the changes I make to the tones.conf file are considered when dealing with disconnects from the PSTN side.
I restart FS after every change I make to /etc/openzap/tones.conf with no positive results.
The Openzap Wiki states that the "loadzone" parameter in /etc/zaptel.conf is not considered when dealing with tones, which makes sense since Openzap seems to use libteletone for tone detection and generation.
Here is what I use for busy tone on /etc/openzap/tones.conf:
[us]
generate-busy => v=-7;%(330,330,450) detect-busy => 450
Therefore I set openzap.conf.xml as follows:
<param name="tonegroup" value="us"/>
I was able to check that the busy tone can be detected using the following dial plan rule:
1. <extension name="Inbound"> 2. <condition field="destination_number" expression="^1$"> 3. <action application="answer"/> 4. <action application"sleep" data="1000"/> 5. <action application="tone_detect" data="busy 450,0 r +100 hangup normal_clearing"/> 6. </condition> 7. </extension>
So that I answer the FXO and hang up when the busy tone is detected. It works fine and the FXO port does not get stuck.
Here's the output from the log for the rule above:
I do not see a reason why settings on tones.conf may not be working?
Is disconnect on busy-detect the default for Openzap? Is it power denial or battery reversal?
Does it matter if I select fxsks in /etc/zaptel.conf instead of fxsls?
Your help will be greatly appreciated.
Regards,
Luis
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Anthony Minessale II
FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/
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:213-799-1400
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org