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 yet, so they have to
prefix all their stuff with "cisco-" since it's really proprietary to them
still. But in the VALUE itself, they have embedded the "proposed" name for
the attribute, h323-disconnect-cause, along with the value.
What I just finished doing was modifying our parsing algorithm for our
accounting data. Now, when it sees a prefix such as "cisco-", it searches
the value to find the "true" attribute name (along with the value). That
solves the attribute problem. But you're still stuck with the numeric "10"
as the value. I don't think there's any easy way around that unless you can
get the Gateway to stop embedding the attributes like this in the first
place.
If you DO find the way to get the Gateway to fix this, let me know!!
Dave
:)
> -----Original Message-----
> From: Ken Sain [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 23, 2001 9:45 AM
> To: [EMAIL PROTECTED]
> Subject: (RADIATOR) dictionary issue - log complains of missing values
>
>
> radiator 2.17.1
> mysql 3.22.32
> cisco 5300
>
> for almost every single call, i get the following error in my
> log file:
>
> 22/01/2001 23:24
> There is no value named h323-disconnect-cause=10 for
> attribute cisco-h323-disconnect-cause. Using 0.
>
> however, in my dictionary file:
>
> VENDORATTR 9 cisco-h323-disconnect-cause 30 string
> and
> # Voice return codes. REVISIT: whats the VENDORATTR?
> VALUE cisco-h323-disconnect-cause Success-Proceed
> 0
> VALUE cisco-h323-disconnect-cause
> Failed-Invalid-Account 1
> VALUE cisco-h323-disconnect-cause
> Failed-Invalid-Password 2
> VALUE cisco-h323-disconnect-cause
> Failed-Account-In-Use 3
> VALUE cisco-h323-disconnect-cause Failed-Zero-Balance
> 4
> VALUE cisco-h323-disconnect-cause Failed-Card-Expired
> 5
> VALUE cisco-h323-disconnect-cause Failed-Credit-Limit
> 6
> VALUE cisco-h323-disconnect-cause Failed-User-Denied
> 7
> VALUE cisco-h323-disconnect-cause
> Failed-Service-Not-Available 8
> VALUE cisco-h323-disconnect-cause
> Failed-Called-Number-Blocked 9
> VALUE cisco-h323-disconnect-cause
> Failed-Num-Of-Retries-Exceeded 10
> VALUE cisco-h323-disconnect-cause
> Failed-Invalid-Argument 11
> VALUE cisco-h323-disconnect-cause Back-To-PSTN
> 50
> VALUE cisco-h323-disconnect-cause
> Redirect-To-Called-Party 51
> VALUE cisco-h323-disconnect-cause
> Redirect-To-Customer-Service 52
> VALUE cisco-h323-disconnect-cause
> Connect-Leg-To-Redirect-Addr 53
>
> only thing i can think of is that like with some other of
> these cisco VSA's,
> you have to tweak the values to be 'cisco-h323-disconnect-cause=10'
>
> any one seen this, and know if i'm correct?
>
> thanks!
>
> #---------------------------------------------------------------#
> # Ken Sain [EMAIL PROTECTED] #
> # Systems Administrator 850.309.7999 -
> office #
> # Genesis Communications Network 888.598.8942 - pager #
> #---------------------------------------------------------------#
>
> ===
> Archive at http://www.starport.net/~radiator/
> Announcements on [EMAIL PROTECTED]
> To unsubscribe, email '[EMAIL PROTECTED]' with
> 'unsubscribe radiator' in the body of the message.
>
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
