[cisco-nas] X.75 (LAPB-TA) - get ISDN port into Radius Acct?

[Gert Doering]

Hi,

On Wed, Jul 13, 2011 at 05:36:40PM -0700, Aaron Leonard wrote:
> 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 ...

... and so it does, *iff* configured properly.  Based on your hint, I
found this document:

  http://www.cisco.com/en/US/docs/ios/12_1t/12_1t3/feature/guide/dt_aaara.html

and that suggests I should use "default", not a named AAA list, so I 
configured:

  aaa accounting resource default start-stop-failure group radius

now (default instead of "DIALIN"), and here we gooo...


Code:       Accounting-Request
Attributes:
  Acct-Session-Id:     000001E8
  Acct-Status-Type:    Start
  NAS-Port:            30202
  NAS-Port-Id:         BRI1/2:2
  NAS-Port-Type:       ISDN
  Calling-Station-Id:  008912003682
  Called-Station-Id:   691
  NAS-IP-Address:      192.168.41.175
  Acct-Delay-Time:     0
VSA for vendor 9
    Cisco-AVPair:        connect-progress=No Progress
    Cisco-NAS-Port:      BRI1/2:2

Attributes:
  Acct-Session-Id:     000001E9
  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

Attributes:
  Acct-Session-Id:     000001E9
  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


(and similar on disconnect).  

Interesting enough, for ISDN/X.75 dialups (as above), I get two different 
"Acct-Session-Id:" values, while for ISDN/*modem* dialups, I get the 
same Id (so correlation is easier):

Attributes:
  Acct-Session-Id:     000001EA
  Acct-Status-Type:    Start
  NAS-Port:            30202
  NAS-Port-Id:         BRI1/2:2
...
Attributes:
  Acct-Session-Id:     000001EA
  Acct-Authentic:      Local
  Acct-Status-Type:    Start
...
  NAS-Port-Id:         tty75
  NAS-Port-Type:       Async
  Connect-Info:        31200 V34+/V42bis/LAPM
...
Attributes:
  Acct-Session-Id:     000001EA
  Login-Service:       Telnet
  Login-IP-Host:       192.168.41.7



--- but however, I think everything I need is here now :-) - I just need
to hack together some radius-side scripting to correlate the data into
something more terse :-)

Thanks a lot for that pointer!

 (... if you happen to be in Munich one day, I owe you a beer :-) ).

gert
-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             gert at greenie.muc.de
fax: +49-89-35655025                        gert at net.informatik.tu-muenchen.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 305 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-nas/attachments/20110714/34ab7edd/attachment.pgp>