Edgemarc Configuration

Can't use the Firewall 2. Breaks the connection and doesn't allow rtp traffic to flow. The call setup and teardown will work but no audio will be sent or received.
The traffic shaper should be used by setting the upstream and down stream bandwidth to a little less than the circuit supports that way the edgemarc will prioritize the voice packets and drop the data packets instead of allowing random packets to dropped later in the connection because there is not enough bandwidth to support all the traffic. The suggested bandwidth value for one T1 is 1320 kbps.

Installing Nagios on Fedora

If you follow these instructions, here's what you'll end up with:

• Nagios and the plugins will be installed underneath /usr/local/nagios
• Nagios will be configured to monitor a few aspects of your local system (CPU load, disk usage, etc.)
• The Nagios web interface will be accessible at http://localhost/nagios/

• Preparing Linux for Nagios installation
• Make sure you've installed the following packages on your Fedora installation before continuing
• Apache
• GCC compiler
• GD development libraries
•  They can be installed by running
• yum install httpd
• yum install gcc
• yum install glibc glibc-common
• yum install gd gd-devel
• Become the root user.
• su -l
• Create a new nagios user account and give it a password.
• /usr/sbin/useradd -m nagios passwd nagios
• Create a new nagcmd group for allowing external commands to be submitted through the web interface. Add both the nagios user and the apache user to the group.
• /usr/sbin/groupadd nagcmd /usr/sbin/usermod -a -G nagcmd nagios /usr/sbin/usermod -a -G nagcmd apache
• Create a directory for storing the downloads.
• mkdir ~/downloads
• cd ~/downloads
• Download the source code tarballs of both Nagios and the Nagios plugins
• wget http://prdownloads.sourceforge.net/sourceforge/nagios/nagios-3.1.2.tar.gz
• wget http://prdownloads.sourceforge.net/sourceforge/nagiosplug/nagios-plugins-1.4.13.tar.gz
• Compile and Install Nagios
• Extract the Nagios source code tarball.
• cd ~/downloads tar xzf nagios-3.1.2.tar.gz cd nagios-3.1.2 
• Run the Nagios configure script, passing the name of the group you created earlier like so
• ./configure --with-command-group=nagcmd
• Compile the Nagios source code.
• make all
• Install binaries, init script, sample config files and set permissions on the external command directory.
• make install
• make install-init
• make install-config
• make install-commandmode
• Customize Configuration
• Sample configuration files have now been installed in the /usr/local/nagios/etc directory. These sample files should work fine for getting started with Nagios. You'll need to make just one change before you proceed... 
•  Edit the /usr/local/nagios/etc/objects/contacts.cfg config file with your favorite editor and change the email address associated with the nagiosadmin contact definition to the address you'd like to use for receiving alerts.
• nano /usr/local/nagios/etc/objects/contacts.cfg
• Configure the Web Interface
• Install the Nagios web config file in the Apache conf.d directory.
• make install-webconf
• Create a nagiosadmin account for logging into the Nagios web interface. Remember the password you assign to this account - you'll need it later.
• htpasswd -c /usr/local/nagios/etc/htpasswd.users nagiosadmin
• Restart Apache to make the new settings take effect.
• service httpd restart
• Compile and Install the Nagios Plugins
• Extract the Nagios plugins source code tarball.
• cd ~/downloads tar xzf nagios-plugins-1.4.11.tar.gz cd nagios-plugins-1.4.11
• Compile and install the plugins.
• ./configure --with-nagios-user=nagios --with-nagios-group=nagios make make install
• Start Nagios
• Add Nagios to the list of system services and have it automatically start when the system boots.
• chkconfig --add nagios chkconfig nagios on 
• Verify the sample Nagios configuration files
• /usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg
• If there are no errors, start Nagios.
• service nagios start
• Modify SELinux Settings
• Fedora ships with SELinux (Security Enhanced Linux) installed and in Enforcing mode by default. This can result in "Internal Server Error" messages when you attempt to access the Nagios CGIs.
• See if SELinux is in Enforcing mode.
• getenforce
• Put SELinux into Permissive mode.
• setenforce 0
• To make this change permanent, you'll have to modify the settings in /etc/selinux/config and reboot.
• Instead of disabling SELinux or setting it to permissive mode, you can use the following command to run the CGIs under SELinux enforcing/targeted mode:
• chcon -R -t httpd_sys_content_t /usr/local/nagios/sbin/ chcon -R -t httpd_sys_content_t /usr/local/nagios/share/
• Login to the Web Interface
• You should now be able to access the Nagios web interface at the URL below. You'll be prompted for the username (nagiosadmin) and password you specified earlier.
• http://localhost/nagios/ 

To make sure an snmp check is working you can issue the following command in /usr/local/nagios/libexe.

./check_snmp -H -p -w 35 -c 40 -o 1.3.6.1.4.1.1748.3.1.1.6.0
 

Preparing Fedora

# Install wget a utility for retrieving files using the HTTP or FTP protocols
yum install wget

# Install wput a utility for uploading files or whole directories to remote ftp-servers
yum install wput

#install apache
install httpd

#install GNU Compiler Collection (GCC). A compiler system produced by the GNU Project #supports languages: C, C++, Objective-C, Fortran, and Java compiler
yum install gcc

#install the corresponding desired libraries
yum install gcc-ada
yum install gcc-java
yum install gcc-objc

Meditarix Configuration

g711pcmu must be enabled to work with the voice portal, if it is not you will get a half a ring and then a fast busy

Mediatrix 1124 Firmware Upgrade

If you pick static file for the firmware you must specify the location of the folder containing the firmware (without beginning and ending "/") :
zend_crm/public/files/firmware/mediatrix/current/1124

if you pick remote file for the firmware you must specify the location of the Setup.inf file:
zend_crm/public/files/firmware/mediatrix/current/1124/Setup.inf

Installing and Configuring TFTP Server on Linux

• Install
• yum install tftp-server
• Setup 
• nano /etc/xinetd.d/tftp
• Find disable = yes, make it no 
• change server_args to the location that you want the root of the tftp server to be in 
• -v is necessary so the tftp will log all requests 
• -c option allows you to upload files to the tftp server without them first existing
• 
  
  
  
  
  
  

  server_args             = -v -s /tftpboot 

• Start TFTP Server (Note: auto-startup tftp might not be good idea)
•  /sbin/chkconfig tftp on
• /sbin/chkconfig xinetd on
• 
  
  
  
  

  /sbin/service xinetd start 

• Testing
•  touch /tftpboot/test
• From another computer, Linux, OS X:
• tftp [ip of tftp server]
• tftp get test
• tftp quit
• From another computer, Windows OS:
• tftp 192.168.0.1 GET test
• If you can see “test” under the current directory, then this TFTP server should work properly.
• If not, check the firewall, open UDP port 69. You can run system-config-security to open it.
• You can use grep tftp /var/log/messages to see the log

Upgrading Cisco 7940 Firmware and Configuring

Upgrading Firmware

• 
  

  Key things to remember before beginning the upgrade

• Must go from SCCP 3.1 to SIP 2.3 to SIP 6.3 to SIP 7.5. All version 8 software seem to go into a never ending reboot cycle
• At a certain point **# no longer unlocks the phone and you must type the password "cisco" in to configure the phone
• All of Cisco's information about upgrading firmware can be found at:
  http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/7960g_7940g/mgcp/firmware/matrix/frmwrup.html

• 
  

  Download firmware from
  http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=6.3&mdfid=268437897&sftType=Session+Initiation+Protocol+%28SIP%29+Software&optPlat=&nodecount=27&edesignator=null&modelName=Cisco+Unified+IP+Phone+7940G&treeMdfId=278875243&modifmdfid=null&imname=&treeName=Wireless&hybrid=Y&imst=N

• 
  

  Place necessary files in root of TFTP server

• The phone first looks for OS79XX.txt.  The OS79XX.TXT file must only contain the name of the file that you attempt to load, without the .bin extension.
• 
  If you convert from SCCP to SIP and the version you attempt to load is SIP 2.3 software or earlier, the OS79XX.TXT must be in the format of POS3xxyy . For example, if the SIP software version is 2.2, the file must contain POS30202.
•  If you convert from SCCP to SIP and the version you attempt to load is SIP 3.0 software or later, the OS79XX.TXT must be in the format of POS3-xx-y-zz . For example, if the SIP software version is 7.4, the file must contain POS3-07-4-00.
•  If you convert from SIP to SCCP, the OS79XX.TXT must be in the format of P003aabbccdd. For example, if the SCCP software version is 7.2(3), the file must contain P00307020300.

• 
  

  Configure network settings of the phone

• Turn DHCP off
• Set IP Address
• Set netmask
• Set default gateway
• Set DNS

• 
  

  Set address of primary TFTP server

• 
  

  Reboot the phone to begin downloading the new firmware

Configuring Phone

• The SipDefault.cnf has all of the main configuration settings that are the same for each phone.
• The SipMAC.cnf has all of the phone specific settings line/port and authentication information.
• The SEPMAC.cnf.xml just tells what load to use
• The O79XX.txt just tells what load to use (it is loaded first in most cases)