Hello, we have two servers running Radiator 3.6-1. Since outsourcing our NASes in some locations to two vendors, we've been having problems with unterminated calls.
After examining packet dumps of the traffic from Vendor A, I've noticed that they are often sending duplicate accounting-start packets to us, with the second one coming 15 or 30 seconds after the first. They claim that this is normal behavior, as their network drops "low-priority" (their words) traffic (i.e. responses from our Radius servers) between their Radius proxies and their NASes during periods of peak utilization. The problem is, when one of our customers disconnects immediately after the session starts, our Radius servers have already terminated the session by the time that the retransmitted start packet comes in, so we see it as beginning a new session (interestingly, the stop packets do not seem to be retransmitted). Vendor A recommends that we work around this by starting sessions based on the access-request packet, rather than the accounting-start. I haven't been able to examine any packet dumps from Vendor B, as our customers use their phone numbers much less frequently, but they claim that the problem is occurring because their sub-vendors' NAS servers are sometimes rebooted or restarted, which causes all current sessions to be abandoned. Vendor B recommends that we start examining the Calling-Station-Id attributes that they are passing us and terminate any ongoing sessions that match the phone numbers being used for newly-started sessions. So, my questions are a) Based on others' experiences, are these explanations plausible/acceptable, or should we start looking for other vendors? b) Has anyone tried either of the "solutions" recommended above? In particular, the one recommended by Vendor B sounds like a good workaround -- has anyone done this in Radiator? Thanks in advance, Dan === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
