I need an automated way to see what numbers my users are connecting to at say 5 minute intervals. I have a TC1000 box that has about 15 different cities going to 5 PRI lines. We are having to do a capacity study and I need to know which cities are being dialed and whom is connected to those cities. This way I will know which cities we need to upgrade trunking capacity in? Thanks, Kris
Your Radius server should have all of that. I have a my radius server post the "Whose On" info to the "intranet" every 15 mins and alert me when a chassis is max'ing out. Cheers, -Tom On 7 Feb 2005 at 14:05, Duracom Support wrote:
I need an automated way to see what numbers my users are connecting to at say 5 minute intervals. I have a TC1000 box that has about 15 different cities going to 5 PRI lines. We are having to do a capacity study and I need to know which cities are being dialed and whom is connected to those cities.
This way I will know which cities we need to upgrade trunking capacity in?
Thanks,
Kris
_______________________________________________ USR-TC mailing list USR-TC@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc
I can do that also, but I am needing to know how many people we have connected to each dial in number, for trunking purposes. I run mrtg to query my boxes for number of users dialed in, but I need to be able to tell the number of users dialed in to each dial in number. Since we have Mux solution we have about 15 cities pointed to 5 PRI's, so there is no way to segement by each PRI because there can be random numbers on every PRI. Thanks, Kris -----Original Message----- From: usr-tc-bounces+support=duracom.net@mailman.xmission.com [mailto:usr-tc-bounces+support=duracom.net@mailman.xmission.com] On Behalf Of GiGoNET Support Sent: Monday, February 07, 2005 7:58 PM To: Discussion relating to the 3Com/US Robotics Total Control modem systems. Subject: Re: [USR-TC] USR Scripting Your Radius server should have all of that. I have a my radius server post the "Whose On" info to the "intranet" every 15 mins and alert me when a chassis is max'ing out. Cheers, -Tom On 7 Feb 2005 at 14:05, Duracom Support wrote:
I need an automated way to see what numbers my users are connecting to at say 5 minute intervals. I have a TC1000 box that has about 15 different cities going to 5 PRI lines. We are having to do a capacity study and I need to know which cities are being dialed and whom is connected to those cities.
This way I will know which cities we need to upgrade trunking capacity in?
Thanks,
Kris
_______________________________________________ USR-TC mailing list USR-TC@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc
_______________________________________________ USR-TC mailing list USR-TC@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc
On Tue, 2005-02-08 at 08:50 -0600, Duracom Support wrote:
I can do that also, but I am needing to know how many people we have connected to each dial in number, for trunking purposes. I run mrtg to query my boxes for number of users dialed in, but I need to be able to tell the number of users dialed in to each dial in number. Since we have Mux solution we have about 15 cities pointed to 5 PRI's, so there is no way to segement by each PRI because there can be random numbers on every PRI.
The TC should send the calling and called directory numbers to your RADIUS server in the Calling-Station-Id and Called-Station-Id attributes, respectively (at least so long as it can get that info in the first place--try LIST DNIS_CONNECTIONS via telnet to the ARC.) Whether or not your RADIUS server keeps those around or discards them is another story, though... If you're insistent on SNMP, you can get both numbers from the NMC with enterprises.usRobotics.nas.mdm.mdmCs.mdmCsTable.mdmCsEntry.mdmCsLastNumberDialedIn.<modemNumber> and enterprises.usRobotics.nas.mdm.mdmCs.mdmCsTable.mdmCsEntry.mdmCsLastCallingPartyNum.<modemNumber> (.1.3.6.1.4.1.429.1.6.9.1.1.4.<modemNumber> and .1.3.6.1.4.1.429.1.6.9.1.1.5.<modemNumber>); modemNumber is slotNumber*1000 + modemNumber, so slot:4/mod:6 would be 4006.
Thanks,
Kris
-- Ben Winslow <rain@bluecherry.net>
participants (3)
-
Ben Winslow -
Duracom Support -
GiGoNET Support