Thus spake Paul Farber
But wouldn't the trap have to have the correct call fail reason? The call failure is what triggered the trap.
Ah...you're dealing with traps...I missed that part.... I don't see any traps that include mdmCsConnectFailReason in them... RADIUS logging from the NMC includes the equivalent value in there with some of its logs, but it doesn't seem to be sent with any actual SNMP traps from what I can see...perhaps I'm wrong though.
As for off by on.. that would make the vaule -1 (0 - 1 = -1).
But the number in the mib file that I have starts with 1, not 0...perhaps we're looking at different mib files? not sure. We seem to be talking past each other, but I'm not sure why...
TCM seems to have at least different reasons for call failures... no way to be sure they are correct... but at least they change.
Hrmm...I'm pretty sure TCM doesn't pull it from traps, it just polls, but I'm not sure what its pulling. -- Jeff McAdams Email: jeffm@iglou.com Head Network Administrator Voice: (502) 966-3848 IgLou Internet Services (800) 436-4456 - To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.