adventures of a VoIP / SIP / IMS trainer & contractor|info@rzfeeser.com

troubleshooting

Avaya phone-script from g350 to Ubuntu 12.04 TFTP server

As the Alta3 Research office network grows, I decided it was prudent to explore/develop how to bring up a TFTP (Trival File Transfer Protocol) server, primarily for use with our Avaya 46xx stations. In this post, I’ll explain how I moved the TFTP service from an Avaya G350, to an Ubuntu 12.04 LTS server.

Before I get started, some basic things about TFTP. TFTP is typically used for diskless boots (routers and phones), and across UDP port 69. TFTP offers no way to ‘list’ files available from the server. The protocol also lacks any security authentication, therefore, TFTP should never be implemented, […]

  • Permalink Gallery

    Avaya Aura Template Installation from System Platform – Could not mount DVD/CD

Avaya Aura Template Installation from System Platform – Could not mount DVD/CD

I recently spun Avaya Aura 6.2 Mid-Sized Enterprise software onto an HP DL360G7 server. After the installation of System Platform, the process requires that you install the VM templates. Avaya recommends that this be done by downloading the template *.iso files from the PLD, and burning them to DVDs. After creating the DVDs, you log into: System Platform > Server Management > File Manager, place the first template DVD into server, and click the, <View DVD/CD> button. Unfortunately, no matter how many times I tried this, or how many DVDs I burnt, I was unsuccessful in getting the Avaya Aura to mount […]

  • OpenSourceIMS_Troubleshooting_RZFeeser_Blog
    Permalink Gallery

    ./pcscf.sh: line 4: setkey: command not found || fix for OpenIMSCore

./pcscf.sh: line 4: setkey: command not found || fix for OpenIMSCore

When trying to launch the pcscf.sh, you may encounter OpenIMSCore hanging, and displaying the message:

./pcscf.sh: line 4: setkey: command not found
./pcscf.sh: line 5: setkey: command not found

I was able to fix this problem on Ubuntu 10.04 LTS by opening a terminal and typing:

sudo apt-get install ipsec-tools

Apparently, setkey is included with the ipsec-tools apt-get. After the install, my issues with this particular error went away.