Hello Ken -
I would like to see a trace 4 debug showing what is happening with
the packets that cause this log message.
thanks
Hugh
At 9:45 -0500 01/1/23, Ken Sain wrote:
radiator 2.17.1
mysql 3.22.32
cisco 5300
for almost every single call, i get the following error in my log file:
I know what your problem is.
We have the same problem. Your accounting is no doubt coming back as:
cisco-h323-disconnect-cause = "h323-disconnect-cause=10"
My guess is that Cisco is hoping attributes such as "h323-disconnect-cause"
become RADIUS standards. Unfortunately, they haven't
Hello Ken, Hello Dave -
The best way to deal with this is in a hook, in which you would do
the additional processing to check any cisco-h323... attribute and
correct the value to be in the format that the dictionary expects.
hth
Hugh
At 13:00 -0500 01/1/23, Kitabjian, Dave wrote:
I know
On Wed, 24 Jan 2001, Hugh Irvine wrote:
The best way to deal with this is in a hook, in which you would do
the additional processing to check any cisco-h323... attribute and
correct the value to be in the format that the dictionary expects.
i have a couple of friends at cisco, one of
On Wed, 24 Jan 2001, Hugh Irvine wrote:
Hello Ken, Hello Dave -
The best way to deal with this is in a hook, in which you would do
the additional processing to check any cisco-h323... attribute and
correct the value to be in the format that the dictionary expects.
terriblly gross, but
