Trunks Down and sending an Alert Email (anything like this available?)

If i'm allowed to say this,

I think that's the way where the TrixboxPRO version is headed, when i look at the status page, and see that they can see the exact status on your trunks.

I do believe, that that's the direction the the PRO and CC version is headed, and the not the CE version,

Taking not that FreeBPX is heading the other direction, maybe, u can ask those guys over there to add it as a scripted feature..

Or as your noted, roll up your sleeves, and start scripting away..
Nice idea anyway, i would sure like to have a feature like that....
but afterall, i'm not a coder, so wouldn't know where to start...

keep us up todate, if u find such tool, or coded one yourself..

There is another thread requesting something similar and the discussion is to do this monitoring from inside your box or outside. If your box gets cut off, then you won't be able to get the message out.

FreePBX already does some monitoring of Trunks on the System Status page and this is done realtime when the status page is up. We plan on moving some of that into a daemon where the same information would be obtained to be passed to the status page when active, so it would be reasonable to allow that daemon to also provide errors and alerts. It's actually an extension to the Notification Panel. Today you can get emails about new module updates. That will become more general with other notifications as well. It's just a simple matter of developing the interface to allow you to setup what you want to hear about and the daemon that we discussed....

So ... as far as the direction that FreePBX is going (by reflection, CE) ... yes it is going that way and you can already see the beginnings of that in the System Status console with the Trunk info and the Notifications panel.

ddwyer - FYI, that is why it is called "opensource". If it gets done, it is for the benefit of us all. You asked "why should somebody else do this work for you for free?" but then tell the same person to do the work and provide it to others for free...ironic and contradicting. And somebody is bringing TB CE to you for free, I am quite sure you did not ask them why they did the work for you fo free. If you can help out, just do that, but if you can't then step aside for those who can.

All, I use Nagios from a hosted server to watch my boxes. But I usally watch the FW and the Trixbox. Always figured that if I could not get to the boxes OS (ssh) then things were down. I actually like the idea of watching the status of the trunks.

For those of you not into Server Monitoring you also should check out a product called Servers Alive.

.........

here is a quick test when i take down my babytel SIP trunk (change the IP in /etc/hosts) so it wont register.

perl trunkalert.pl
============================================================
SIP Trunk information
============================================================
houston we have a problem
There is a sip trunk not registering

============================================================
IAX2 Trunk information
============================================================
There are 2 Registered IAX2 trunks

As soon as I change tghe /etc/hosts file back to the proper IP I have for my Babytel setup.. I quicking run my perl script and it will change to registered...

Next on to the Mail out function./ Right now this would probably work for 1 SIp and 1 IAX trunks once the email function is there..

everybody is standing aside that is the true irony of opensource. enough said

Has anyone used MON? I see it's a feature on Webmin but I haven't installed the daemon on the server. Considering it as we had Asterisk freeze on a box a few days ago and I'd like to get an email when that happens. Not sure if it could notify if a trunk stops responding.

the right way to go should be imho to have asterisk snmp enabled. This way you can monitor things like current calls and trunk status in a snmp management machine, and do the alerting from there

Jim,

I would love a copy of this script. I am a les.net customer (maybe not for much longer) and have been having problems with my DID and SIP registration failing. I would like to know about the problem when it happens, so I fix it before my customers have to tell me they can't get through to me.

Thanks!

--
Joe LaGreca
Founder & Owner, BIGnet Online
619-393-1733 Office
619-318-3246 Cell
www.BIGnetOnline.com

Ya I took the easy route 1st. I want to get it working a lot better. The script only took about 20 mins or so to write. Plus most people ar enot running freepbx 2.3.x yet. I jsut upgraded to that yesterday so have not had a chance to look into that. I will today or tonite,

I am looking at doing an AGI script but have not had time.

for those who emailed me I am not ignoring you I have a few of you interested in this script so rather than emailing out I am going to setup a link on a website I will email out to everyone.

If one of these options is really good, please let me know and we will look into adding it into trixbox with a nice interface to configure it.

Since a few of you have downloaded this script, I have a few questions.

1) Was the setup easy for you?
2) is the script working (easiest way to test is change the password on your SIP/IAX trunk and viola a dead trunk)

Please post some feedback.. I did not get a chance this weekend to look at AGI as I was not home much., I do not think this will work out of the box..

Jim

I had to use the port number as well in order for it to work.

e.g.
63.211.239.28:4569

I also had to modify the trunkalerts.pl file depending on the TrixBox version as the position of "Registered" in the response to iax2 show registry changed between two of the versions

Line 56 (in my file) is
$iaxtrunks = `/usr/sbin/asterisk -rx "iax2 show registry" |/bin/grep \"$_\" | awk '{print $5}'`;

{print $5} is the position of Registered (or not) in the iax2 show registry command response string.

Regards
Garry

I have created the iaxtrunks file so it is ip:port e.g. 63.211.239.28:4569 I have 3 IAX accounts and they are entered each on a seperate line, and I am still having problems.

$iaxtrunks is "Binary file (standard input) matches", I can never get it to be Registered or Request. If I put a / in front of $5 {print /$5} I get "matches". Field 5 is the correct field for the awk command, I can run awk from the command line and I get the correct response for field 1 and field 5.
# asterisk -rx "iax2 show registry" | awk 'NR==3, NR==5 {print $1,$5}'
63.211.239.28:4569 Registered
192.246.69.186:4569 Request
64.2.142.30:4569 Registered

Does it matter where I put the perl file? It is in /etc/asterisk/perl_scripts and I have changed the permissions to 755 so it is executable.

sounds like a great idea to me..... feature request, perhaps??

I am working on an interrupt driven Perl daemon for this exact thing building off of the code posted above. I realize that this is an old thread, but I have found nothing to accomplish this.

If I am wasting my time please feel free to let me know. If the scripting goes well it should be done fairly soon as it is not that complicated.

EDIT:
Code complete, Its not pretty, but it appears to work :) email me at chance (dot) fulton (at) gmail (dot) com if you are interested.
Thanks,

EDIT:

I found some errors in my code, mainly id doesn't work... I had to move the order of some things around,

I opened the trunk files at the start of the main loop, and then never closed them. I forgot my C++ in the fact that you may have to rewind a file in order to read from it again, So basically the file was at EOF after the first iteration, and would never process the trunks again.

I fixed this by placing an open, and a close inside each of the monitor subroutines, it now appears to work just fine, Sorry to have to post this here, as I just "cleaned" out my mailbox, losing the list of members who emailed me for a copy of the script.

Im going to make it easy n you all, and allow http access to the file soon, but for now:

#!/usr/bin/perl -w 
###############################################Forward ######################################
#### This script was written to monitor asterisk SIP/IAX2 trunks. It does the job well
#### Please feel free to do whatever you please to this as it was written with code
#### from many other contributors.
#### I take no responsability for anything that this script does badly. 
#### I am not a perl wizard!
###############################################Configuration ################################
#### You have to create two text files inside of /etc/asterisk called trunkalerts_sip.conf, 
#### and trunkalerts_iax.conf inside put the host that you get back from the command
#### asterisk -rx "sip show registry" and asterisk -rx "iax show registry"
#### I may add a cli flag that creates these with all trunks inside on first run.
#### You also have to parse the script and change any specific instances of email addresses,
#### and intervals etc. They are pretty much all commented.
##############################################Contact#######################################
#### chance dot fulton at gmail dot com if you have any questions.
##############################################The End########################################

use strict;
use warnings;

use constant LOG_DIR    => '/var/log/MonitorTrunks';
use constant LOG_FILE   => 'MonitorTrunks.log';
#use constant PIDDIR     => LOG_DIR;

use Proc::PID::File;
use Proc::Daemon;
use Log::Dispatch;
use Log::Dispatch::File;
use Date::Format;
use File::Spec;

print "Prototypes\n";
sub dienice ($);
sub MonitorSip();
sub MonitorIAX2();
sub mailalert();
#
# fork and background process
#
print "Forking Process\n";
our $ME = $0; 
$ME =~ s|.*/||;
#our $PIDFILE = PIDDIR."/$ME.pid";
print "PID File /var/run/$ME.pid\n"; #$PIDFILE\n";

print "Starting Daemon\n";
startDaemon();

#
# Setup the script variables for email
# Please modify these, as I do not want your email.
#
our $EmailContact = "To:<Sum1semail\@somedomain.com>\n";
our $from= "FROM: <Sum1semail\@somedomain.com>\n";
our $reply_to = "Reply-to: <Sum1semail\@somedomain.com\n";
# Interval to look at the trunks.
our $monitorInterval = 20;
# Interval that we will send a "heartbeat" to the log.
our $logMarkInterval = 1800;

#
# Setup a logging agent
#
our $HOSTNAME = `hostname`;
chomp $HOSTNAME;
our $log = new Log::Dispatch(
      callbacks => sub { my %h=@_; return Date::Format::time2str('%B %e %T', time)." ".$HOSTNAME." $0\[$$]: ".$h{message}."\n"; }
);
$log->add( Log::Dispatch::File->new( name      => 'file1',
                                     min_level => 'warning',
                                     mode      => 'append',
                                     filename  => File::Spec->catfile(+LOG_DIR, LOG_FILE),
                                   )
);
$log->warning("Starting Processing:  ".time());


#
# Setup signal handlers so that we have time to cleanup before shutting down
#
my $keep_going = 1;
$SIG{HUP}  = sub { $log->warning("Caught SIGHUP:  exiting gracefully"); $keep_going = 0; };
$SIG{INT}  = sub { $log->warning("Caught SIGINT:  exiting gracefully"); $keep_going = 0; };
$SIG{QUIT} = sub { $log->warning("Caught SIGQUIT:  exiting gracefully"); $keep_going = 0; };
$SIG{TERM} = sub { $log->warning("Caught SIGTERM:  exiting gracefully"); $keep_going = 0; };

#
# enter main loop
# In this loop we will look at the trunks inside of SIPTRUNKS, and then IAXTRUNKS to determine their state.
# We will then sleep for a predefined interval, and do it all over again.
# When our Interval Counter reaches another predefined limit (multiple of our monitorInterval) we will then send
# <Mark> to the log so everybody knows we arent dead.
#
#debugging lines No longer needed
print "Opening trunk Files\n";
my $logMarkIntervalCounter = 0;
while ($keep_going) {
	print "SipStuff";	
	MonitorSip();
	print "iax2Stuff";
	MonitorIAX2();
	print "$monitorInterval\n";
	sleep $monitorInterval;
	$logMarkIntervalCounter += $monitorInterval;
	if($logMarkIntervalCounter == $logMarkInterval)
	{
		print "Log MARK";
		$log->warning("<Mark>");
		$logMarkIntervalCounter = 0;
	}
}

#
# Mark a clean exit in the log
#
$log->warning("Stopping Processing:  ".time());
#Set the date so that it can be used later.
#handled by the logger
#my $date = `date`;

################################################## ##################################################
#### Initial attempt to daemonize this script as to free up some resources.
#### 20090602
#### Wish me luck...
#### Attempt succeded, I have fixed a bug wher the files were not rewound after the initial run of the
#### script. 
#### Changed from using Proc::PID_File which wa old to PROC::PID::File works a bit differently in that
#### it only puts the lock PID file in /var/run
################################################## #################################################
####
#### Trunk Alerts script written by Jim Hribnak Oct 7th 2007
#### if there is any questions please feel free to drop me an email at jimh at domain nucleus.com
####
################################################## ##################################################
####
#### Script modified by Charles Pippin Feb 21st 2009 - Added counters for loop retry.
#### if there is any questions please feel free to drop me an email at cwpippin at domain gmail.com
####
################################################## ##################################################
####
#### Create the following 2 files in /etc/asterisk
####
#### in the files below add the hosts entry from asterisk -rx "sip show registry" and
#### from asterisk -rx "iax2 show registry".
####
#Startup Code

#
# startDaemon
#
# Fork and detach from the parent process
#
sub startDaemon {

  #
  # Fork and detach from the parent process
  #
  
  #eval { close __DATA__ }; # having __END__ will trigger __DATA__ to open and should be closed
  eval { Proc::Daemon::Init; };
  #
  # Get a PID file
  #
  eval {Proc::Daemon::Init(); };
  #
  # Get a PID file
  #
  dienice("Already running!") if Proc::PID::File->running();
}

#
# dienice
#
# write die messages to the log before die'ing

#I need to figure out a way to stop using $_ as I hate it!
sub dienice ($) {
  my ($package, $filename, $line) = caller;
  $log->critical("$_[0] at line $line in $filename");
  #Close the log handle;
  close(log) if ($log);
  die $_[0];
}


sub MonitorSip(){
################################################## ##################################################
####
#### SIP Related Code
####
	#print "Opening SIP trunk file\n";
	#Moved to open/close everytime this sup is called so the file is rewound, and not stuck at EOF.
	# 07/16/2009
	open(SIPTRUNKS,"</etc/asterisk/trunkalerts_sip.conf");
	while (<SIPTRUNKS>) {
		chomp;
		#Test trunk 5 times to make sure its Up or DOWN before moving on. 
		my $upcounter = 5;
		my $dncounter = 5;
		until ($upcounter == 0) {
			#I need to figure out a way to stop using $_ as I hate it!
			my $siptrunks = `/usr/sbin/asterisk -rx "sip show registry" | grep \"$_\" | awk '{print \$4}'`;
			#print $siptrunks;
			if ($siptrunks =~ "Registered") {
				$upcounter = $upcounter - 1;
			}
			else {
				$dncounter = $dncounter - 1;
				$log->warning("$_ is down\n") ;
				#When dncounter reaches 0 fire an email that tells someone about the error
				if ($dncounter == 0) {
					mailalert();
					#I need to figure out a way to stop using $_ as I hate it!
					$log->warning("houston we have a problem, $_ trunk is not registering");
					`/usr/sbin/asterisk -rx "module reload chan_sip"`;
					$log->warning("sip reload processed");
					$logMarkIntervalCounter = 0;
					$upcounter = 0;
				}
			}
		}
	}
	close SIPTRUNKS;
#end of while loop (read SIP file)
}
sub MonitorIAX2(){
################################################## ##################################################
####
#### IAX Related Code
####
	#print "Opening IAX trunk file\n";
	#Moved to open/close everytime this sup is called so the file is rewound, and not stuck at EOF.
	# 07/16/2009	
	open(IAXTRUNKS,"</etc/asterisk/trunkalerts_iax.conf");
	while (<IAXTRUNKS>) {
		chomp;
		#Test trunk 5 times to make sure its Up or DOWN before moving on.
		my $upcounter = 5;
		my $dncounter = 5;
		until ($upcounter == 0) {
			#I need to figure out a way to stop using $_ as I hate it!
			my $iaxtrunks = `/usr/sbin/asterisk -rx "iax2 show registry" |/bin/grep \"$_\" | awk '{print \$6}'`;
 			#print $iaxtrunks;
			if ($iaxtrunks =~ "Registered") {
				$upcounter = $upcounter - 1;
			}
			else {
				$dncounter = $dncounter - 1;
				$log->warning("$_ is down\n");
				#When dncounter reaches 0 fire an email that tells someone about the error
				if ($dncounter == 0) {
					mailalert();
					#I need to figure out a way to stop using $_ as I hate it!
					$log->warning("houston we have a problem, $_ trunk is not registering");
					`/usr/sbin/asterisk -rx "module reload chan_iax2"`;
					$log->warning("IAX2 reload processed");
					$logMarkIntervalCounter = 0;
					$upcounter = 0;
				}
			}
		}
	} 
	close IAXTRUNKS;
	#end of while loop (read IAX file)
}
################################################## ##################################################
####
#### Email Subroutines
#### Change anywhere below where there is an email address an email addres
#### must have \@ as perl needs to escape the @ symbol
####
################################################## ##################################################
#I need to figure out a way to stop using $_ as I hate it!
sub mailalert() {
    my $sendmail = "/usr/sbin/sendmail -t";
    my $subject = "Subject: $_ is DOWN!!!!\n";
    my $content = "PBX TRUNK $_ is DOWN!!!!\n A reload of the trunk has been processed";
    open(SENDMAIL, "|$sendmail") or dienice("Cannot Open sendmail Email failed!");
    print SENDMAIL $from;
    print SENDMAIL $reply_to;
    print SENDMAIL $subject;
    print SENDMAIL $EmailContact;
    print SENDMAIL $content;
    close(SENDMAIL);
    $log->warning("An email has been sent to $EmailContact!");
}

Chance