Hello, Something that has been bugging me for a while is the behaviour when receiving an incoming ring from a pots connection. If the incoming connection stops ringing, it takes Freeswitch ages for it to realize. In fact, I have found even if the phone stops ringing after the first ring, Freeswitch doesn't realize until after it activates voicemail (IIRC 20 second delay). I can understand that Freeswitch can't work out the instant the phone has stopped ringing, but the delay seems to be excessively long - is it possible to tweak it? If so how? I am using freetdm with a TDM400 card. Thanks -- Brian May <brian@microcomaustralia.com.au>
it's a lack of hangup detection on the line itself. you can try using tone_detect on your inbound dialplan <action application="tone_detect" data="busy 425 r 0 hangup 'normal_clearing' 3"/> This will listen for busy signal in the background and hangup if it encounters it. On Tue, Aug 24, 2010 at 6:47 PM, Brian May <brian@microcomaustralia.com.au> wrote:
Hello,
Something that has been bugging me for a while is the behaviour when receiving an incoming ring from a pots connection.
If the incoming connection stops ringing, it takes Freeswitch ages for it to realize. In fact, I have found even if the phone stops ringing after the first ring, Freeswitch doesn't realize until after it activates voicemail (IIRC 20 second delay).
I can understand that Freeswitch can't work out the instant the phone has stopped ringing, but the delay seems to be excessively long - is it possible to tweak it? If so how?
I am using freetdm with a TDM400 card.
Thanks -- Brian May <brian@microcomaustralia.com.au>
_______________________________________________ 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/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org googletalk:conf+888@conference.freeswitch.org pstn:+19193869900
On 25 August 2010 10:43, Anthony Minessale <anthony.minessale@gmail.com> wrote:
it's a lack of hangup detection on the line itself. you can try using tone_detect on your inbound dialplan
<action application="tone_detect" data="busy 425 r 0 hangup 'normal_clearing' 3"/>
This will listen for busy signal in the background and hangup if it encounters it.
No, that is only after the call is answered. I am talking about a caller that hangs up before it is answered. -- Brian May <brian@microcomaustralia.com.au>
The problem is in the drivers or the config for the analog interface. If the CO switch supports it, a CPC signal gets sent down the line to tell your interface to cancel. This was called fxs_ks in zaptel. It should be possible to implement a timer that considers it canceled if it goes beyond a preset time between rings and nobody has answered. It's 6 seconds in North America. This goes back to the driver though, and isn't really a freeswitch problem I don't imagine. -Tim Brian May wrote:
On 25 August 2010 10:43, Anthony Minessale <anthony.minessale@gmail.com> wrote:
it's a lack of hangup detection on the line itself. you can try using tone_detect on your inbound dialplan
<action application="tone_detect" data="busy 425 r 0 hangup 'normal_clearing' 3"/>
This will listen for busy signal in the background and hangup if it encounters it.
No, that is only after the call is answered.
I am talking about a caller that hangs up before it is answered.
participants (3)
-
Anthony Minessale
-
Brian May
-
Tim St. Pierre