* This is the VOP Radius mailing list * I would love to hear how those out there are making the inaccurate data accurate. Are you just leaving it there and giving it to your customers as accurate?
We see problems with people being cut off at the limit of hours like say 200 with Qwest but in our timebank they are only at say 174 or worse. That is a LOT to be off by and this seems to be the norm for a higher usage user. What we need is for our numbers to match exactly with our wholesale vendor/aggregator etc. So far we have some of our vendors which offer a CSV file of all the usage data for each user month to date. We have written some code that goes out and grabs this file every 24 hours and updates the timebank field in our Radius DB for each user. This method has been the best solution so far. This begs the question, what the heck good is timebanking at all in a wholesale environment? Bugs the hell out of me honestly that we always have data that is inaccurate. To me, if the data is inaccurate then it is useless. It seems worse to show a high usage user an inaccurate number than no number at all. Thanks for the feedback so far, I am glad to hear all that can be said about this. Thanks, Todd -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Dean Sent: Thursday, August 14, 2003 10:28 AM To: [EMAIL PROTECTED] Subject: [VOPRadius] Time Bank * This is the VOP Radius mailing list * Todd, It's all relative. We receive nearly 200,000 STOP records per day. We lose some..maybe about a dozen. Often these are from certain regions..maybe the carriers reboot the NAS...maybe something else..who knows. I have never seen an improvement..but instead there are a general 1/10 of 1% loss or fewer. There are a few things about VOP that I would love if they would implement and have been lobbying for years: 1) If a session limit is assigned to a user, then expire that session from the UsersOnline listing after the period has passed..or at least allow a "maximum sesssion" value 2) If an incoming Auth request has the exact same CallingStationID as the one listed, then the user must have dropped..permit it. 3) Currently, there is a linkage between port-limits, UsersOnline, and timebanking. It's a queer,unnecessary relationship...they should be independently configurable. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Todd > Sent: Thursday, August 14, 2003 10:45 AM > To: [EMAIL PROTECTED] > Subject: [VOPRadius] Time Bank > > > * This is the VOP Radius mailing list * > Would love to hear from some on the list that are using Time Banking with > VOP Radius. We have been using it for some time but see terrible accuracy. > We are using it 100% with wholesale network providers like Qwest and such. > We are well aware of the problems associated with time banking, outsourced > POPs and lost stop packets etc. We still think it should be MUCH more > accurate than it is. We use more than one network provider/aggregator and > see very poor results with all of them when it comes to time banking. > > We have tried many things to increase the accuracy like placing our Radius > server in different facility with better connections to the net > overall. We > have tried putting our Vop Radius on a machine with more horsepower and so > on. Nothing seems to help really.. > > Are we doomed to basically never have any useful usage data for > our subs as > long as we use outsourced POP's or is this a problem with Vop Radius and > their Time Banking. The reason I ask is because I have had > several people in > the past laugh when I said I was using Vop Radius for time banking. > Basically they said it downright did not work for beans. So, I am not > suggesting this is the problem, just trying to see how many of you use it > and actually feel it's accurate. It makes it very difficult to run our > business with basically useless usage data in our Radius DB. > > Any input on this is appreciated. > > Thanks, > Todd > > > > > ** > To leave this list, send an email to [EMAIL PROTECTED] > and put the word "LEAVE" in the BODY of the email. > > > ** To leave this list, send an email to [EMAIL PROTECTED] and put the word "LEAVE" in the BODY of the email. ** To leave this list, send an email to [EMAIL PROTECTED] and put the word "LEAVE" in the BODY of the email.
