[VOPRadius] "Ghost users causing simultaneous login limit exceeded" (wholesale ports)

[Gary Carr]

I'm not sure if my previous post made it or not so I will send again, Checking the ghosting against the nas port would be a better solution I think. This is how Aleron does it and it makes better sense then trying to key off of caller-id. It would still require interim accounting packets to be accurate accounting wise, which any ISP (wholesale or retail) should support.   Their method is as follows: If a user goes off-line but no stop packet is sent (that is we view them as being on line) the next time a call comes in on that DS0 (read NASPortID) and our session tracking systems thinks it is occupied, the stale session (the one that has dropped off) is closed and the last interim accounting packet is used as the stop time. Interim accounting is sent every 15 min so we will under-bill up to 15 min when no stop packet is sent.       Gary         Ramsey, Sylvain is investigating this concept as a possible solution.  The negative comments I've heard so far are as follows: It would not work if the user has their caller id blocked. It would clean up ghost users allowing the actual user online, however, connect time reports would be incorrect since there would be no way to know when the user had actually disconnected. The way I see it this solution would still solve the majority of my problems.   Steven Bastardi The Home Town Network Inc. ----- Original Message ----- From: Ramsey Abu-Absi To: [EMAIL PROTECTED] ; [EMAIL PROTECTED] ; [EMAIL PROTECTED] ; [EMAIL PROTECTED] Sent: Thursday, May 20, 2004 4:26 PM Subject: [VOPRadius] "Ghost users causing simultaneous login limit exceeded" (wholesale ports) At 11:19 AM 5/20/2004, Steven Bastardi wrote: This operational issue is not going to go away unless a creative solution is implemented.  In my opinion just such a solution was suggested some time ago on this mail list.  The recommendation is as follows: " if the calling station-id was stored with the rest of the users information in the online users table in radius, a ghost user could be cleaned up when they try to reconnect from the same phone number."  The assumption is that it would not be impossible to be simultaneous from the same originating number. What Steven wrote above is a clearer way of saying what I was trying to say a few posts back: Now this brings up a question I hadn't thought of before:  Can VOP perform the same logic (i.e. check the called-from number, and if it is the same as the active session, allow the user to log in)?  This would also provide us with a fix. Steven, have you and Sylvain been able to make any progress on this?  It seems to me that this would be a very valuable feature for the user base. Thanks, Ramsey * * * C O N F I D E N T I A L I T Y S T A T E M E N T * * * This E-MAIL message and any accompanying documents contain confidential information intended for a specific individual and purpose. The information contained within is private and protected by law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of this message is strictly prohibited. If you have received this communication in error, please notify us by return e-mail or by telephone at 419-661-1233 so that we can prevent a reoccurrence. Thank you in advance for your strict compliance and assistance.