Ok, guys.....last resort before the company pulls out VISA card for Nortel 2nd level/Design. Customer has MICS 6.1 WI G10 (more on this in a minute). Call Pilot is 3.00.72.22. There is an AT+T prime into the Norstar. When a caller selects the path to the Call Center (and this ONLY happens on xfers to the Call Center from the AA, not AA calls to an xtn or to another path), there is a burst of static that the caller hears.
The history is that they started out with MICS 4.1 and a NAM 4.1 a few years ago and had almost the same issue. Given that all transfers went through the Combo card, I replaced it with a new (non-refubed) part. The problem dissapeared for 6 months (and it wasn't the reboot that cleared it as I had taken it down before the swap). After it returned, I captured the NAM logs and ran the MTT Logger for the switch and gave it to Nortel 2nd level. They didn't see anything in the logs and had us upgrade to 6.1 G10. That didn't work. We rekeyed the database in by hand and put in a new (non- refurbed) KSU as well as a new VRAM cartridge. After all that and no fixxy, Nortel gave us a brand new CP 150 3.0 to replace the NAM (when 3 first came out with the new h/w platform. My 1 claim to fame...I singlehandedly shut down production of CP 3.0 for 2 weeks while they revamped the h/w to work with the new 3.0 s/w...). Viola......it seemed to work. Well, the problem is here again....2 years later. Everything has been changed and I think it is an issue in the CP. Before I go capture logs again and make the boss's wallet hurt,any ideas?
The history is that they started out with MICS 4.1 and a NAM 4.1 a few years ago and had almost the same issue. Given that all transfers went through the Combo card, I replaced it with a new (non-refubed) part. The problem dissapeared for 6 months (and it wasn't the reboot that cleared it as I had taken it down before the swap). After it returned, I captured the NAM logs and ran the MTT Logger for the switch and gave it to Nortel 2nd level. They didn't see anything in the logs and had us upgrade to 6.1 G10. That didn't work. We rekeyed the database in by hand and put in a new (non- refurbed) KSU as well as a new VRAM cartridge. After all that and no fixxy, Nortel gave us a brand new CP 150 3.0 to replace the NAM (when 3 first came out with the new h/w platform. My 1 claim to fame...I singlehandedly shut down production of CP 3.0 for 2 weeks while they revamped the h/w to work with the new 3.0 s/w...). Viola......it seemed to work. Well, the problem is here again....2 years later. Everything has been changed and I think it is an issue in the CP. Before I go capture logs again and make the boss's wallet hurt,any ideas?
