Re: (PM) PM3 not sending Stop records for second B-channel (fwd)

Christopher Masto (chris@netmonger.net)
Thu, 29 Jan 1998 17:08:09 -0500

On Tue, Dec 16, 1997 at 09:16:39PM -0800, MegaZone wrote:
> Once upon a time stephen white shaped the electrons to say...
> >> It is an ordering thing, we should wait to send accounting until after the
> >> bundling is successful or not. But traditionally we sent Starts when an
> >> individual link was successful.
> >Is it being fixed?
>
> Right now I'm not sure it is actively being addressed, there were other
> things already being worked on. But it is known and will be addressed.

I haven't installed 3.7.2c yet, but I don't see this in the release
notes. I think it would placate people to just send a STOP record
when that channel is killed (heck, put "Over-Limit" in the disconnect
reason or something). It would at least be a quick fix for the cheesy
RADIUS servers that don't properly check whether the port is in use.
I'm sure Lucent wouldn't avoid fixing a problem because their
commercial RADIUS server isn't affected by it and their competition
is.

-- 
= Christopher Masto        = chris@netmonger.net = http://www.netmonger.net/  =
= NetMonger Communications = finger for  PGP key = $19.95/mo unlimited access =
= Director of Operations   =   (516)  221-6664 	 = mailto:info@netmonger.net  =


    "... who'd want a lossy TIFF?"  -- Kibo
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.