Posts Tagged ‘Cisco’

Scrambled UC500 Brains

Troubleshooting | Posted by admin
Apr 13 2009

I had the opportunity recently to troubleshoot some erratic and intermittent UC500 problems.  The issues were everything from dropped calls to echo on some calls.

It seemed that two phones were actually bad and had to be replaced.  But the real fun came when I checked out the log:

 070782: Apr 9 xx:xx:xx.xxx: %IP-3-LOOPPAK: Looping packet detected and dropped -
src=192.168.1.101, dst=192.168.1.1, hl=20, tl=229, prot=17, sport=138, dport=138
in=Vlan1, nexthop=192.168.1.1, out=Vlan1
options=none -Process= “IP Input”, ipl= 0, pid= 75, -Traceback= 0x80E38860 0x8131DCDC 0x8131F3C4 0x81560EC4 0x815611E8 0x81562A64 0x81306F24 0x8130ADD0 0x8130BC04 0x8130BCF4 0x8130BEB8 0x801778EC 0x8017A1EC

These entries were filling up the log fairly quickly.  The first thing I noticed was that all the packets had the same port numbers: netbios.  At this point I checked the interface configurations and found a configuration like this:

interface Vlan 1
 ip address 192.168.1.1
 ip helper-address 192.168.1.1

I can’t think of any good reason the helper-address would be pointed to itself, so I removed it.  This resolved all the issues the customer was having outside of broken phones. 

Simple fix, but very interesting impact on system functionality.

The First Challenge

Challenges | Posted by admin
Apr 09 2009

I’ve decided to start posting weekly practice labs.  I hope everyone will enjoy studying them as much as I am enjoying writing them.

The answers will be posted the following week.

Challenge 1

Command Line? on a CE-500

Tips & Tricks | Posted by admin
Apr 08 2009

I was recently told about a method to gain command line access to a CE-500.  Since I much prefer the command line to the GUI interfaces, I was thrilled.  After investigating however, I found that the “command line” was actually a web based frontend to the cli.  In my opinion, it’s better than the GUI, but I would prefer a telnet/ssh connection.

To get to the web command line interface go to :

http://switch-address/exec/

ArcExpress

Third-Party Software | Posted by admin
Apr 03 2009

If you’ve worked with Cisco IP Telephony products, you’re probably familiar with their Attendant Console software.  The software allows receptionists to manage incoming calls from their PC.  This allows them to transfer calls with simple drag and drop functions.  It also provides a quick list of user line status, whether they are on the phone or available.  There are a number of additional features in this software but it is outside the scope of my rant.  Using standard Cisco software, this software doesn’t exist for Callmanager Express (CME) patforms.  The reccomended replacement is to use an expansion module which gives a phone “switchboard like” functionality.

ArcSolutions provides software that has similar functionality to Cisco’s Attendant console.  This software is, in my opinion, one of the worst add-on technologies I have ever seen.  I’ll explain and let you make up your own mind though.

ArcExpress requires that a “server” installation be configured on a single PC.  That PC houses a SQL database for all other clients to attatch to.  This PC has to remain on at all times, or the ArcExpress users all lose functionality.  The “server” software is configured using the CME Configuration utility.  This utility logs into the CME system and reads the configuration.  At this point it attempts to make several configuration changes.  Some of  these changes include :

  • Adding virtual phone configurations
  • Adding virtual extension numbers for ArcExpress feature support

This was my first issue.  In order to complete the CME Configuration, you must have at least 2 free phone licenses available.  It also requires several available directory numbers for feature support.  If your licensing does not allow for the recommended changes, the configuration will not continue.

At least the configuration utility gave me a list of the changes it was going to make.  From that list I was able to adjust the changes to fit within the licensing constraints of the system.

At this point however, even though the ArcExpress virtual phone showed registered in the CME system, it did not function.  Attempting to call Tech Support resulted in sitting on hold for an eternity.  But I understand that problem.  When you have a product as shoddy as this, one must expect a lot of tech-support calls.  Their techs were probably all just very busy.

After many hours of work trying to get ArcExpress to function I have decided that it is not worth the effort.  I will never work on another project using this software if I can at all help it.