[cisco-nas] X.75 (LAPB-TA) - get ISDN port into Radius Acct?
Aaron Leonard
Aaron at cisco.com
Wed Jul 13 20:36:40 EDT 2011
Actually, it *was* resource accounting ("aaa accounting resource") not
connection accounting ("aaa accounting connection") that I was thinking
of, that *should* show the ISDN B channel and caller/called number.
So you say that this is not showing anything for your X.75 calls? I
thought that all Q.931 calls, of whatever call type, would generate
resource accounting records ...
--------------------------------------------------------------------------
On 7/13/2011 11:45 AM, gert at greenie.muc.de (Gert Doering) wrote:
> Hi,
>
> On Wed, Jul 13, 2011 at 10:33:24AM -0700, Aaron Leonard wrote:
>> I think you can use "aaa accounting connection" to get the ISDN
>> signaling information, which you could then correlate back to to the
>> X.75 calls.
> That's already in there...
>
> aaa accounting connection DIALIN start-stop group radius
>
> ... and indeed I get multiple start/stop records:
>
> Connect:
>
> Code: Accounting-Request
> Attributes:
> Acct-Session-Id: 0000015A
> Acct-Authentic: Local
> Acct-Status-Type: Start
> NAS-Port: 135
> NAS-Port-Id: tty135
> NAS-Port-Type: Virtual
> Calling-Station-Id: 008912003682
> Called-Station-Id: 691
> Service-Type: NAS-Prompt-User
> NAS-IP-Address: 192.168.41.175
> Acct-Delay-Time: 0
> VSA for vendor 9
> Cisco-NAS-Port: tty135
>
>
> Code: Accounting-Request
> Attributes:
> Acct-Session-Id: 0000015A
> Login-Service: Telnet
> Login-IP-Host: 192.168.41.7
> Login-TCP-Port: 8023
> Acct-Authentic: Local
> Acct-Status-Type: Start
> NAS-Port: 135
> NAS-Port-Id: tty135
> NAS-Port-Type: Virtual
> Calling-Station-Id: 008912003682
> Called-Station-Id: 691
> Service-Type: Login-User
> NAS-IP-Address: 192.168.41.175
> Acct-Delay-Time: 0
> VSA for vendor 9
> Cisco-AVPair: connect-progress=Estab\'d Telnet Conn
> Cisco-NAS-Port: tty135
>
>
> Disconnect:
>
> Code: Accounting-Request
> Attributes:
> Acct-Session-Id: 0000015A
> Login-Service: Telnet
> Login-IP-Host: 192.168.41.7
> Login-TCP-Port: 8023
> Acct-Input-String: 260
> Acct-Output-String: 40
> Acct-Input-Packets: 14
> Acct-Output-Packets: 22
> Acct-Authentic: Local
> Acct-Session-Time: 88
> Acct-Terminate-Cause: User-Request
> Acct-Status-Type: Stop
> NAS-Port: 135
> NAS-Port-Id: tty135
> NAS-Port-Type: Virtual
> Calling-Station-Id: 008912003682
> Called-Station-Id: 691
> Service-Type: Login-User
> NAS-IP-Address: 192.168.41.175
> Acct-Delay-Time: 0
> VSA for vendor 9
> Cisco-AVPair: connect-progress=Estab\'d Telnet Conn\|disc-cause-ext=TS User Exit
>
>
> Code: Accounting-Request
> Attributes:
> Acct-Session-Id: 0000015A
> Login-Service: Telnet
> Login-IP-Host: 192.168.41.7
> Login-TCP-Port: 8023
> Acct-Authentic: Local
> Acct-Terminate-Cause: User-Request
> Acct-Session-Time: 88
> Acct-Status-Type: Stop
> NAS-Port: 135
> NAS-Port-Id: tty135
> NAS-Port-Type: Virtual
> Calling-Station-Id: 008912003682
> Called-Station-Id: 691
> Service-Type: NAS-Prompt-User
> NAS-IP-Address: 192.168.41.175
> Acct-Delay-Time: 0
> VSA for vendor 9
> Cisco-AVPair: disc-cause-ext=TS User Exit\|connect-progress=Estab\'d Telnet Conn
> Cisco-NAS-Port: tty135
>
>
> ... but the hardware interface used isn't there :(
>
> I've experimented with different "radius-server attribute nas-port"
> settings but couldn't find one that had the desired effect - it changed
> the numbers from "135" to "something else" but the Cisco-NAS-Port
> and the NAS-Port-Id always staid at "tty135" (for ISDN calls).
>
>
> Your post made me curious, though, so I tried "aaa accounting resource ...",
> but that didn't make any effect at all :-(
>
> gert
>
More information about the cisco-nas
mailing list