Nick Kewney

This is a pretty dull post, but it's for reference.

Over the past couple of months, I have been experiencing problems with a Sangoma A101D card on a BT PRI ISDN-30 line.  I'd been receiving OOF, AIS and RAI alarms from our provider which were recorded in the Wanrouter messages file.  According to Sangoma, earlier versions of the Wanpipe driver are a bit too keen to report OOF errors and this has been corrected in 3.5.11 and beyond.

Updating to the latest version of Wanpipe for Asterisk seems to correct the problems, and I'm monitoring the situation by tailing the /var/log/messages file on the Asterisk box with the script at the bottom of this post. 

If this doesn't work for you, try disabling the echo canceller on the card to isolate this hardware.  Just issue wan_ec_client wanpipe1 disable on your Asterisk machine to disable the echo canceller.

#!/bin/bash

mv /home/nkew/messages_latest.mail /home/nkew/messages_latest.mail.old

tail -100 /var/log/messages > /home/nkew/messages_latest.mail

OLD_SIZE=`ls -l /home/nkew/messages_latest.mail.old | awk '{print $5}'`
echo $OLD_SIZE

echo "Subject: [JHL-Alert]: Sangoma Message Log Changed" >> tempfile 
echo -e "Hi Asterisk Admins,\n\nThis is an update to let you know that the Sangoma /var/log/messages file has been updated\n\nThe last 200 lines of the file are inclued below:\n" >> tempfile 

cat /home/nkew/messages_latest.mail >> tempfile
mv tempfile /home/nkew/messages_latest.mail

NEW_SIZE=`ls -l /home/nkew/messages_latest.mail | awk '{print $5}'`
echo $NEW_SIZE

if [ $NEW_SIZE -ne $OLD_SIZE ];
 then
   echo "Since the file size has changed, let's trigger an e-mail." 
   /usr/lib/sendmail xx@xx.com < /home/nkew/messages_latest.mail
   /usr/lib/sendmail xx@xx.com < /home/nkew/messages_latest.mail
 else
   echo "Nothing has changed"
fi

View Post (610) or Add Comments (4)

If want to branch together multiple Trixbox phone systems, whether they are on your local network or not, this can be done with IAX. If the two machines are on different networks, you'll need to open UDP port 4569 on both ends and point it to the Trixbox systems. Now follow these simple steps to connect up your system and make low cost point to point calls over the Internet with your hardware or software IP phones.

1. On the secondary system, login to the admin console (Free PBX) and go to the extensions tab.
2. Create an IAX2 extension with any number you would like, example: 200
3. On your primary system, login to the admin console and go to the trunks tab.
4. Create a new IAX2 trunk with any name. Under PEER, paste something like this:username=200 type=friend trunk=yes secret=extension secret host=xxx.xxx.xxx.xxx <-- Your secondary Trixbox address context=from-internal
5. Under 'outbound routes' on the primary box, create a new route. Let's say, for example, we want to dial extensions in the 500 range on the secondary box. Just insert 5XX in the dial plan.
6. Under Trunk Sequence, select your IAX trunk you have just created.
7. On the primary system, create a new IAX extension.
8. On the secondary system, go to Trunks and make a new IAX2 trunk. Under PEER, paste something like this:username=201 type=friend trunk=yes secret=extension secret host=xxx.xxx.xxx.xxx <-- Your primary Trixbox address context=from-internal
9. Go to 'outbound routes' and make a new route. Let's say, for example, we want to dial extensions in the 400 range on the primary box. Just insert 4XX in the dial plan.
10. Under Trunk Sequence, select your IAX trunk you have just created.

Test and Enjoy! Good times...

View Post (2248) or Add Comments (2)