On 3/3/2011 10:51 AM, ed guy wrote:
Steve, try sipsak. /ed
Thanks, that looks like just what I needed! This is going to integrate into an existing monitoring solution (not nagios), so the nagios plugins that others recommended is overkill for me.
Sipsak has the downside of having extraordinarily, egregiously long timeouts in case the endpoint does not respond. It would block a lot of other scheduled checks on a busy Nagios install in unacceptable ways. The Net::SIP approach is superior, but goddamn if I can ever figure out that API from the "documentation." -- Alex Balashov - Principal Evariste Systems LLC 260 Peachtree Street NW Suite 2200 Atlanta, GA 30303 Tel: +1-678-954-0670 Fax: +1-404-961-1892 Web: http://www.evaristesys.com/
There are timeouts you can implement in PERL w/o having to wait for sipsak to timeout. -----Original Message----- From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Alex Balashov Sent: Thursday, March 03, 2011 2:26 PM To: voiceops at voiceops.org Subject: Re: [VoiceOps] SIP options "ping" Sipsak has the downside of having extraordinarily, egregiously long timeouts in case the endpoint does not respond. It would block a lot of other scheduled checks on a busy Nagios install in unacceptable ways. The Net::SIP approach is superior, but goddamn if I can ever figure out that API from the "documentation." -- Alex Balashov - Principal Evariste Systems LLC 260 Peachtree Street NW Suite 2200 Atlanta, GA 30303 Tel: +1-678-954-0670 Fax: +1-404-961-1892 Web: http://www.evaristesys.com/ _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
On 03/03/2011 04:34 PM, Ujjval Karihaloo wrote:
There are timeouts you can implement in PERL w/o having to wait for sipsak to timeout.
Yeah, we said that. -- Alex Balashov - Principal Evariste Systems LLC 260 Peachtree Street NW Suite 2200 Atlanta, GA 30303 Tel: +1-678-954-0670 Fax: +1-404-961-1892 Web: http://www.evaristesys.com/
Hi, I propose the check_sip plugin too. For simple SIP-ping jobs, you can call it from command-line and it exits either with a success- or fail-state. If you need more configurable scenarios, I strongly recommend sipp. br Michael On 2011-03-03 17:03, Steve Teti wrote:
On 3/3/2011 10:51 AM, ed guy wrote:
Steve, try sipsak. /ed
Thanks, that looks like just what I needed! This is going to integrate into an existing monitoring solution (not nagios), so the nagios plugins that others recommended is overkill for me. _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
-- Michael Hirschbichler, Mag. Dipl.-Ing. Institute of Telecommunications Technische Universitaet Wien A-1040 Wien, Favoritenstr. 9-11/389 Tel: +43 1 58801 38846
But does the check_sip plug perform an options ping? Frank -----Original Message----- From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Michael Hirschbichler Sent: Friday, March 04, 2011 11:00 AM Cc: VoiceOps at voiceops.org Subject: Re: [VoiceOps] SIP options "ping" Hi, I propose the check_sip plugin too. For simple SIP-ping jobs, you can call it from command-line and it exits either with a success- or fail-state. If you need more configurable scenarios, I strongly recommend sipp. br Michael On 2011-03-03 17:03, Steve Teti wrote:
On 3/3/2011 10:51 AM, ed guy wrote:
Steve, try sipsak. /ed
Thanks, that looks like just what I needed! This is going to integrate into an existing monitoring solution (not nagios), so the nagios plugins that others recommended is overkill for me. _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
-- Michael Hirschbichler, Mag. Dipl.-Ing. Institute of Telecommunications Technische Universitaet Wien A-1040 Wien, Favoritenstr. 9-11/389 Tel: +43 1 58801 38846 _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Jepp, it does: Code sniplet check_sip line 179-188 $req.= "OPTIONS $dsturi SIP/2.0\r\n"; $req.= "Via: SIP/2.0/UDP $localhost:$localport;branch=z9hG4bKhjhs8ass877\r\n"; $req.= "Max-Forwards: 70\r\n"; $req.= "To: $dsturi\r\n"; $req.= "From: $fromuri;tag=$tag\r\n"; $req.= "Call-ID: $idtag\@$localhost\r\n"; $req.= "CSeq: 1 OPTIONS\r\n"; $req.= "Contact: <$user\@$localhost:$localport>\r\n"; $req.= "Accept: application/sdp\r\n"; $req.= "Content-Length: 0\r\n\r\n"; BR Michael Am 2011-03-04 19:17, schrieb Frank Bulk:
But does the check_sip plug perform an options ping?
Frank
-----Original Message----- From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Michael Hirschbichler Sent: Friday, March 04, 2011 11:00 AM Cc: VoiceOps at voiceops.org Subject: Re: [VoiceOps] SIP options "ping"
Hi,
I propose the check_sip plugin too. For simple SIP-ping jobs, you can call it from command-line and it exits either with a success- or fail-state. If you need more configurable scenarios, I strongly recommend sipp.
br Michael
On 2011-03-03 17:03, Steve Teti wrote:
On 3/3/2011 10:51 AM, ed guy wrote:
Steve, try sipsak. /ed
Thanks, that looks like just what I needed! This is going to integrate into an existing monitoring solution (not nagios), so the nagios plugins that others recommended is overkill for me. _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Thanks. A read of http://tools.ietf.org/html/draft-jones-sip-options-ping-02 helped me better understand. Frank -----Original Message----- From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Michael Hirschbichler Sent: Friday, March 04, 2011 1:59 PM Cc: VoiceOps at voiceops.org Subject: Re: [VoiceOps] SIP options "ping" Jepp, it does: Code sniplet check_sip line 179-188 $req.= "OPTIONS $dsturi SIP/2.0\r\n"; $req.= "Via: SIP/2.0/UDP $localhost:$localport;branch=z9hG4bKhjhs8ass877\r\n"; $req.= "Max-Forwards: 70\r\n"; $req.= "To: $dsturi\r\n"; $req.= "From: $fromuri;tag=$tag\r\n"; $req.= "Call-ID: $idtag\@$localhost\r\n"; $req.= "CSeq: 1 OPTIONS\r\n"; $req.= "Contact: <$user\@$localhost:$localport>\r\n"; $req.= "Accept: application/sdp\r\n"; $req.= "Content-Length: 0\r\n\r\n"; BR Michael Am 2011-03-04 19:17, schrieb Frank Bulk:
But does the check_sip plug perform an options ping?
Frank
-----Original Message----- From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Michael Hirschbichler Sent: Friday, March 04, 2011 11:00 AM Cc: VoiceOps at voiceops.org Subject: Re: [VoiceOps] SIP options "ping"
Hi,
I propose the check_sip plugin too. For simple SIP-ping jobs, you can call it from command-line and it exits either with a success- or fail-state. If you need more configurable scenarios, I strongly recommend sipp.
br Michael
On 2011-03-03 17:03, Steve Teti wrote:
On 3/3/2011 10:51 AM, ed guy wrote:
Steve, try sipsak. /ed
Thanks, that looks like just what I needed! This is going to integrate into an existing monitoring solution (not nagios), so the nagios plugins that others recommended is overkill for me. _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
participants (6)
-
abalashov＠evaristesys.com -
frnkblk＠iname.com -
jaybinks＠gmail.com -
sipp＠hirschbichler.biz -
steti＠monmouth.com -
ujjval＠simplesignal.com