This is a followup to a prior post about CallManager Express and Splunk integration.
---ETC---
This is a followup to a prior post about CallManager Express and Splunk integration.
---ETC---
Posted on January 17, 2009 at 05:45 PM in Integration, IP Telephony, Network Monitoring, XML-XSLT | Permalink | Comments (0) | TrackBack (0)
Had a bunch of fun today with getting the correct number tagged onto our 911 calls. Note: Some telco providers override your call ID number with the primary number for your PRI when you call 911. This is a problem if you have a central VoIP phone system that services two or more separate physical locations. Before 911 starts ignoring you altogether because of the incessant test calls, get your telco to allow you to present your own callID number to E911.
Posted on August 22, 2008 at 10:19 PM in IP Telephony | Permalink | Comments (0) | TrackBack (0)
Here is a really quick (and even dirtier) way to quickly determine if you are overextending your PRI usage.
This is a really simple script for Nagios to run and report how many concurrent calls you have.
Fill in the blanks for NAMEOFHOST (CallManager hostname), COMMUNITYNAME (snmp read only community name for CallManager Express) and ifnums. ifnums are the integer values for IF-MIB::ifIndex.** where ** is the interface number for your PRI. you will have to do some snmpwalking to figure this out. I left some values in the script to show how to format your entries.
This script requires the check_ifoperstatus Nagios plugin to work. I will clean this up soon and re-post.
This script throws a critical warning if the PRI usage is 7 or more concurrent calls
#!/bin/sh
# SNMP test for number of interfaces up in a particular range
#
export NAG_PLUG_PATH=/usr/lib/nagios/plugins
export IF_STAT_PLUG=check_ifoperstatus
export NAMEOFHOST=_____________
export COMMUNITY_NAME=____________
ifnums=( 23 24 25 26 27 28 29 30 31 32 )
CTR1=0
for interface in ${ifnums[@]}
do
VAR1=`$NAG_PLUG_PATH/$IF_STAT_PLUG -k $interface -H $NAMEOFHOST -C $COMMUNITY_NAME`
if [ "${VAR1%*\:*\:*}" = "CRITICAL" ]; then
VAR2=0
else
CTR1=`expr $CTR1 + 1`
fi
done
if [ "$CTR1" -ge "7" ];
then
STATUSCODE=CRITICAL
else
STATUSCODE=OK
fi
echo "PRI $STATUSCODE - $CTR1 calls currently"
Posted on July 24, 2008 at 12:54 AM in Integration, IP Telephony, Network Monitoring | Permalink | Comments (0) | TrackBack (0)
*** DISCLAIMER*** I am not responsible for damage to your equipment or downtime incurred by your following my instructions. Research this and be sure of what you are doing before you do it. ******************* Here's a neat way to get a quick (and dirty) view into how many calls your company is taking in through Cisco CallManager Express using Splunk. Assuming you already have a syslog server set up and working... Install Splunk on the syslog server and verify that it is working Set up the CallManager Express to send syslog entries to the syslog server (see http://www.linuxhomenetworking.com/wiki/index.php/Quick_HOWTO_:_Ap04_:_syslog_Configuration_and_Cisco_Devices AND page 11-6 in http://www.cisco.com/univercd/cc/td/doc/product/voice/its/cmesrnd/managcme.pdf ) Telnet into the CME and do a show run. Look at your voice translation rules. The first number in each rule will appear in log entries as cdn:#### for inbound calls. For example, if you have voice translation-rule 5 rule 1 /5202/ /1007/ rule 2 /5203/ /1006/ rule 3 /5204/ /1007/ rule 4 /5205/ /1007/ rule 5 /5206/ /1007/ rule 6 /5207/ /1009/ rule 7 /5208/ /1006/ rule 8 /5209/ /1007/ rule 9 /5210/ /1008/ rule 10 /5211/ /1007/ and someone calls in using 555-5204, the log entry should contain cdn:5204 . You can use this to build some saved searches that will show your call traffic by DID by hour, minute, or whatever. Cheers, -Ash
L
Posted on December 06, 2007 at 07:14 AM in Integration, IP Telephony, Network Monitoring | Permalink | Comments (0) | TrackBack (0)
Found out something really interesting... Typically ANI will only resolve if your outbound 911 calls have the billing phone number attached... so if your location has numerous DIDs, tag the outbound calls to 911 with the billing phone number. Also, if you have trouble faxing to some numbers (weird errors, etc...) it is likely that you are being blocked because of ANI funnies as well. I think some telcos block non-resolving numbers to prevent fax spam.
Posted on August 14, 2007 at 12:14 AM in IP Telephony | Permalink | Comments (0) | TrackBack (0)
DISCLAIMER: I am NOT responsible for what you do with this information. If you take my advice and screw up, it's on YOU, bud. I'm also not responsible for what may happen to any warranty or service contract you have on your machine if you follow these instructions. Setup: Cisco CallManager Express + Cisco Unity Connection Problem: Corporate management wants to monitor all incoming calls for all inbound numbers using Unity Connection's Call Manager Traffic report... but they want the customer to reach a real human first, without hearing anything pre-recorded. Caveat: If you've dealt with Unity Connection, you know that you can pass a call through a call handler with a blank greeting, but just before the transfer occurs the call handler tells the customer that their call is being transferred. According to Cisco there is no 'supported' way to disable that little voice prompt. Solution: Every system voice prompt is stored on the Unity Connection server in WAV files in subdirectories under G:\Cisco Unity Connection\TuiResources\Prompts\ENU\G711\ or G:\Cisco Unity Connection\TuiResources\Prompts\ENU\G729\ So, I replaced the unwanted WAV file with a blank one and Voila! The customer gets passed through the call handler, gets tallied for reporting purposes and rings the sales phones directly. Here's how to find the file: search the G711 directory for files named prompt.ini containing the text that is spoken in the file you seek. Dig around in the results to find a reference to the offending file (may take a while). Copy the file to a network share if you are using Remote Desktop to access the machine... DO NOT PLAY IT IN A REMOTE DESKTOP SESSION!!! Playing audio in an RD session can ruin audio settings throughout the Unity Connection software package. Test the WAV to make sure it's what you want and rename the original to {original filename}.wav.OLD. Copy a blank WAV file into the same directory and name it so as to replace the original, unwanted file. What I was looking for in particular was ...\G711\AvPHGreet\AvPHGreetENU005.wav . The file I replaced it with was originally named AvAddrSearchENU003.wav (under another folder) No server restart was required and the system now works beautifully!
Posted on August 09, 2007 at 03:36 AM in Integration, IP Telephony | Permalink | Comments (0) | TrackBack (0)