Hi,
some asked me if i could share the script ... yes, i can ... but it is
in no way a nice script. It is done by me (mostly) ... but is done FOR
me, so you may need to change a few things to make it work ... sorry
:)
Cesc
PS - there is more info on the README inside the attached tgz file
On 1/27/06, Hakan YASTI <hakanyasti(a)gmail.com> wrote:
Hi Cesc,
Could you send the your script that checks the ser activity. What I do is to
check the ser processes via ps -ax but as I see your solution is better.
Thanks,
----- Original Message -----
From: "Cesc" <cesc.santa(a)gmail.com>
To: <hgaillac-sip(a)yahoo.fr>
Cc: <serusers(a)lists.iptel.org>rg>; "Atle Samuelsen"
<clona(a)cyberhouse.no>
Sent: Friday, January 27, 2006 3:40 PM
Subject: Re: [Serusers] Monitoring
As answered, no.
What i did to monitor ser and sems was to create bash scripts which
restart ser and/or sems in case of failure.
For ser, the script sends fake REGISTER messages (with expires=0). If
the answer is 200 OK (or a 40x proxy authenticate) ... then ser is
alive. If nothing is read, then i restart ser.
For sems, i tried two approaches.
- active: send a specially crafted message (INVITE) so that you know
for sure that ser will route it to SEMS ... depending on the answer,
you should be able to know wether SEMS is alive or not ... but this
has a problem (see below for a larger explanation).
- passively: start sems so it writes its PID to a log file ... then
monitor (using ps aux) that pid ...if not there, restart SEMS.
- i seem to remember someone mentioned a status module for sems, which
would allow you to send commands via the fifo/unixsock interface, and
check actively sems (including activity statistics) ... is this true?
===== ACTIVE MONITORING PROBLEM
What i tried to do is to created unique INVITE messages, which i make
sure that ser routes to sems. They had unique call-ids and to/from
tags ... thus theoretically ser should see them as independendent
requests.
But, if sent these INV requests too often (that is, less than a minute
or so ... time enough for the transaction to be destroyed in ser mem,
i guess ... ), ser would mistakenly think they were retransmissions
...
It would also start acting weird and sending replies to the wrong port ...
This is why i went to passive monitoring ... i do not have time to
investigate any further ... but i can provide the script for someone
else to try ...
BTW, i use ser 0.9.6
Regards,
Cesc
On 1/27/06, hgaillac-sip(a)yahoo.fr <hgaillac-sip(a)yahoo.fr> wrote:
Yes I know about snmp module.
There is no way to monitor SER vi snmp !?
Harry
--- Atle Samuelsen <clona(a)cyberhouse.no> a écrit :
Hi Harry,
ser does not support SNMP. There is a module, but it
has not been
maintained for ages and does not work.
-Atle
* hgaillac-sip(a)yahoo.fr <hgaillac-sip(a)yahoo.fr>
[060127 13:05]:
Hi asterisk and ser users,
Is there a solution to monitor asterisk and ser
with
snmp ?
Regards
Harry
___________________________________________________________________________
Nouveau : t?l?phonez moins cher avec Yahoo!
Messenger ! D?couvez les tarifs exceptionnels pour
appeler la France et l'international.
T?l?chargez sur
http://fr.messenger.yahoo.com
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
___________________________________________________________________________
Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les
tarifs exceptionnels pour appeler la France et l'international.
Téléchargez sur
http://fr.messenger.yahoo.com
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers