help-gnu-radius
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Help-gnu-radius] cisco 3640 - voip


From: Cornel Cristea
Subject: [Help-gnu-radius] cisco 3640 - voip
Date: Tue, 11 Jun 2002 12:59:42 +0300

Hi

   I receive only stop accounting from a cisco 3640 - voip. I see that some
information is missing in radacct/<NAS-IP-Address>/details. I need User-Name
and Calling-Station-Id from the original radius packet. Those information
are sent by Cisco router. I dont use rewriting rules.

This is what is recorded in radacct/<NAS-IP-Address>/details

        NAS-IP-Address = 19x.xxx.xxx.xxx
        NAS-Port-Type = Async
        User-Name =
        Called-Station-Id = 0048xxxxxxx
        Acct-Status-Type = Stop
        Service-Type = Login-User
        Cisco-AVPair = h323-incoming-conf-id=20783432 B9E07C3 0 15E66E44
        Acct-Session-Id = 000003E8
        Acct-Input-Octets = 194620
        Acct-Output-Octets = 235760
        Acct-Input-Packets = 9731
        Acct-Output-Packets = 11788
        Acct-Session-Time = 234
        Cisco-AVPair = subscriber=RegularLine
        Cisco-AVPair = pre-bytes-in=0
        Cisco-AVPair = pre-bytes-out=0
        Cisco-AVPair = pre-paks-in=0
        Cisco-AVPair = pre-paks-out=0
        Cisco-AVPair = nas-rx-speed=0
        Cisco-AVPair = nas-tx-speed=0
        Acct-Delay-Time = 20
        Timestamp = 1023720469
        Request-Authenticator = Verified

But the radius packet is as folowing:

Attribute NAS-IP-Address  19x.xxx.xxx.xxx
Attribute NAS-Port-Type  Async
Attribute User-Name  1905                    This value is missing
Attribute Called-Station-Id  0048...
Attribute Calling-Station-Id  1905         This value is missing also
Attribute Acct-Status-Type  Stop
Attribute Service-Type  Login
Attribute Acct-Session-Id  0000...
Attribute Acct-Input-Octets 194620
Attribute Acct-Output-Octets 235760
Attribute Acct-Input-Packets  9731
Attribute Acct-Output-Packets  11788
Attribute Acct-Session-Time  234
Attribute Acct-Delay-Time  0
Attribute Vendor-Specific  Cisco-NAS-Port ISDN...
Attribute Vendor-Specific  h323-gw-id h323...
Attribute Vendor-Specific  h323-conf-id h323...
Attribute Vendor-Specific  Cisco-AVPair h323...
Attribute Vendor-Specific  h323-call-origin h323...
Attribute Vendor-Specific  h323-call-type h323...
Attribute Vendor-Specific  h323-setup-time h323...
Attribute Vendor-Specific  h323-connect-time h323...
Attribute Vendor-Specific  h323-disconnect-time h323...
Attribute Vendor-Specific  h323-disconnect-cause h323...
Attribute Vendor-Specific  h323-voice-quality h323...
Attribute Vendor-Specific  Cisco-AVPair subscriber=RegularLine
Attribute Vendor-Specific  Cisco-AVPair h323...
Attribute Vendor-Specific  Cisco-AVPair pre-bytes_in=0
Attribute Vendor-Specific  Cisco-AVPair pre-bytes-out=0
Attribute Vendor-Specific  Cisco-AVPair pre-packs-in=0
Attribute Vendor-Specific  Cisco-AVPair pre-packs-out=0
Attribute Vendor-Specific  Cisco-AVPair nas-rx-speed=0
Attribute Vendor-Specific  Cisco-AVPair nas-tx-speed=0

Is there any reason for this behaviour ?

Cornel Cristea





reply via email to

[Prev in Thread] Current Thread [Next in Thread]