You shouldn't have to live with it.  I suspect your problem is cabling, and if it is cabling it could either be your patch cable or the proprietary dongle in the back of the cabinet. ... View more

You might check your cabling first.  In many cases CRC errors indicate a physical cabling problem.  You might try replacing your network cable with a known good cable. Now the bad news, if you're running a TN799DP CLAN card, I'm assuming it is probably in some sort of Avaya shelf.  It's been a few years since I've messed with them, but at least the older Avaya shelves had a proprietary dongle that cabled the back of the actual shelf to the cabling panel where you would plug in your ethernet cable to the CLAN card.  The really old shelves did not have CAT rated "dongle", and were not supported for speeds over 10mbps.  I have seen these dongles go bad, and it usually required an Avaya tech to replace. ... View more

I don't believe the 28xx/38xx uses the license key, so you don't need to purchase a license.  Just download the image with the same feature set you currently have just like you do with the 12.4 code releases.  I've upgrade a few dozen of my 2821 and 3845's and they don't use the license.  If you are upgrading your feature set (e.g. IP SERVICES to ADVANCED ENTERPRISE SERVICES), then you are "required" to purchase an upgrade license.  However, all you get is a piece of paper you stick in a drawer. When you have a 28xx or 38xx on version 15, you'll see somem reference to the license, but it will remain blank.  The box will operate with the feature set you load on it: XXXXX>sho ver Cisco IOS Software, 3800 Software (C3845-ADVIPSERVICESK9-M), Version 15.1(1)XB,                                                RELEASE SOFTWARE (fc1) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2009 by Cisco Systems, Inc. Compiled Mon 21-Dec-09 03:52 by prod_rel_team Cisco 3845 (revision 1.0) with 478208K/46080K bytes of memory. Processor board ID FTX1324AHVR 2 Gigabit Ethernet interfaces 4 Channelized E1/PRI ports 1 Virtual Private Network (VPN) Module 16 Voice E & M interfaces DRAM configuration is 64 bits wide with parity enabled. 479K bytes of NVRAM. 255488K bytes of ATA System CompactFlash (Read/Write) ... License Info: License UDI: ------------------------------------------------- Device#   PID                   SN ------------------------------------------------- *0        CISCO3845-MB          FOCXXXXXXXXXX Configuration register is 0x2102 The 29xx and 39xx, however, do use the common image and the license, and you will see sho ver Cisco IOS Software, C3900 Software (C3900-UNIVERSALK9-M), Version 15.0(1)M1, RELEASE SOFTWARE (fc1) Technical Support: http://www.cisco.com/techsupport License Info: License UDI: ------------------------------------------------- Device#   PID                   SN ------------------------------------------------- *0        C3900-SPE100/K9       FOCXXXXXXXXX Technology Package License Information for Module:'c3900' ---------------------------------------------------------------- Technology    Technology-package          Technology-package               Current       Type          Next reboot ----------------------------------------------------------------- ipbase        ipbasek9      Permanent     ipbasek9 security      None          None          None uc            uck9          Permanent     uck9 data          None          None          None Configuration register is 0x2102 ... View more

I'm not really sure about your first problem, however, resetting the FXO port and the gateway in CUCM might help.  Usually when MGCP is acting wierd, resetting everything usually fixes it. For your second problem, I've seen that a few times.  Cisco FXO ports pickup the phone on the first ring detect and then generate their own ringback while the IP phone is being signaled.  If the remote end hangs up the FXO port is expecting to get a battery-reversal indicating the disconnect.  If it doesn't get the battery-reversal the port does not know the line has been disconnected and continues to signal the phone.  Contact your telephone provider and ask them to add disconnect supervision to the line. An easy way to test your line for disconnect supervision is to hook up a test set (or an analog telephone) directly to the phone line.  Place a call to or from that line to another phone (like your cell phone), it doesn't matter which direction you place the call.  Hang up the remote end, but keep listening on the phone line.  If you hear a click followed by a dialtone then you have the battery-reversal disconnect supervision enabled.  If not you'll just hear dead air.  Don't listen for too long to the dead air because the telco will play a off-hook tone which can be loud. ... View more