Thanks everyone
aarenot, LOL! I have actually had that thought a couple times. I have to wonder about all these other systems they claim to have installed that are "100% stable and happy". I mean come one, how many small businesses in a rural area with a tourist driven economy actually have that kind of need (or money)? Anyway, that is a great suggestion about the answering machine and alarm clock! I might have to give that a try.
mattKnight, the IPO is running through a switch, and it is auto-negotiating the port speed/duplexing, but so far I haven't seen them drop to 10 or half (I am monitoring it with solar winds) Likewise I haven't had packet drops, or anything else on the WAN link.
What IS intertesting is that I have had no reports of drops since Thursday. I tweaked the QoS yesterday morning, and all fo a sudden I am seeing af41 and ef stats on my trouble site router. I changed it from a class-map match-any to a class-map match-all.
Before the tweaks, all I could see that was being handled by the policy was cs6. NOW I can see large quantites of af41
and ef, as well as a few cs6. BUT I only see that on the router at the trouble site, on the router here at the Main, I can see only some ef packets even though the policy matches at both ends.
I am inclined to think that there were 2 problems:
1. The VCM. After it was replaced we continued to drop calls, but NOT in clusters, it was one here and one there and greatly reduced.
2. The QoS. If it wasn't handling packets correctly before now, it apears to be doing so at this point. Although the QoS is only in place between the Main and the trouble site, no one else has the sheer volume of calls that they receive.
I am almost holding my breath <g>.
If I get through the next few days without any drops that I can tie directly to the error above, I might just cancel the vendor meet, because if I never see my BP again, it will be too soon.