On 2006-10-17 09:00:51 -0700, Bjoern Metzdorf
<[EMAIL PROTECTED]> said:
I run into that from time to time for this business account we have
where channels were staying open for a long time so I made a script run
from cron to hang up any extension over X amount of time:
/usr/sbin/asterisk -rx "show channels concise" |awk -F : '($11 > 5400)
{print "/usr/sbin/asterisk -rx \"soft hangup " $1 "\""} '|sh
This looks at any calls over 90 minutes then hangs it up. You can
modify it for your issue say something like:
/usr/sbin/asterisk -rx "show channels concise" |awk -F :
'/YOUR_X_SIPURA_NUMBER/'|awk -F : '($11 > 5400) {print
"/usr/sbin/asterisk -rx \"soft hangup " $1 "\""} '|sh
Not practical though for saving money... If someone is on for say 1
minute and there is an issue with the channel not hanging up, 5399
minutes would still be billed.
What version are you using?
I never had these issues with asterisk 1.0.x in 15 months. That leads
me to a problematic 1.2.x or to faulty bristuff-patches.
I will upgrade asterisk asap to latest 1.2.x and add an absolute
timeout to those destinations.
But: Are we the only ones experiencing this?
That really doesn't sound at all the same to me as what he is
describing? In his case (ie not hung up calls) if you are using SIP
handsets, then the rtptimeout setting can cut the calls off when there
is no audio data flowing.
Good Luck,
Marty
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
