Setting Up Call Logging

This chapter discusses how to set up call logging. It consists of the following sections:

Before you begin

Understanding call logging

Overview of call-logging configuration tasks

Setting up system-wide call-logging values

Setting up call logging with dynamic IP addressing

Starting the RADIUS daemon with call logging enabled

Understanding call-logging records

Before you begin

Understanding call logging

The MAX TNT sends Start session, Stop session, a nd Failure-to-start session packets to a call-log host. The call-log information is sent independently of RADIUS accounting records. If both call logging and RADIUS accounting are in use, the information is sent in parallel.

Overview of call-logging configuration tasks

Setting up system-wide call-logging values

Performing required call-logging configuration tasks

• System-wide call-logging parameters

• Call-logging port in /etc/services

• Call-logging directory

1. In the External-Auth profile, set Acct-Type =RADIUS.

2. Open the Call-Logging profile.

3. Set Call-Log-Enable=Yes.

4. For each Call-Log-Host parameter, specify the IP address of a call-log host.

5. For the Call-Log-Port parameter, enter the UDP port number you specified in
   /etc/services for the authentication process of the daemon. Or, if you used the incr keyword with the -A option when starting the daemon, add 1 to the number of the UDP port for authentication services, and enter the sum.

6. For the Call-Log-Key parameter, enter the RADIUS client password, exactly as it appears in the RADIUS clients file.

radacct      1646/udp      #call logging

Specifying the call-logging directory

Performing optional call-logging configuration tasks

• Timeout value

• Retry limit

• Numeric base for the session ID

• Number of seconds that must elapse before the MAX TNT returns to using the primary call-log host

Specifying a timeout value

Specifying a retry limit

The MAX TNT always attempts at least one retry. For example, if you set the number of retries to 10, the MAX TNT makes 11 attempts: the original attempt plus 10 retries.

Specifying the numeric base for the session ID

• Acct-Base-10 (decimal) specifies that the numeric base is 10. The default value is 10.

• Acct-Base-16 (hexadecimal) specifies that the numeric base is 16.

"1234567890"

"499602D2"

Specifying the reset time

Specifying whether to send Stop packets with no user name

Example of setting up system-wide call logging

Figure 13-1. Sample network topology for setting up system-wide call logging

In addition to the required parameters, the configuration also specifies that the MAX TNT must:

• Increase the timeout value to 10 seconds.

• Increase the retry limit to 6.

admin> read external-auth

EXTERNAL-AUTH read

admin> list

auth-type=none

acct-type=none

rad-id-space=unified

rad-id-source-unique=system-unique

rad-serv-enable=no

rad-auth-client={ 0.0.0.0 0.0.0.0 0.0.0.0 0 0 "" no 0 no no no 0 yes +

rad-acct-client={ 0.0.0.0 0.0.0.0 0.0.0.0 0 0 "" 0 0 acct-base-10 0 +

rad-auth-server={ 0 no rad-serv-attr-any [ 0.0.0.0 0.0.0.0 0.0.0.0 +

tac-auth-client={ 0.0.0.0 0.0.0.0 0.0.0.0 0 0 "" 0 }

tacplus-auth-client={ 0.0.0.0 0.0.0.0 0.0.0.0 0 0 "" 0 0 }

tacplus-acct-client={ 0.0.0.0 0.0.0.0 0.0.0.0 0 0 "" }

local-profiles-first=lpf-yes

admin> set acct-type=radius

admin> write external-auth

EXTERNAL-AUTH written

admin> read call-logging

CALL-LOGGING read

admin> list

call-log-enable=no

call-log-host-1=0.0.0.0

call-log-host-2=0.0.0.0

call-log-host-3=0.0.0.0

call-log-port=0

call-log-key=""

call-log-timeout=0

call-log-id-base=acct-base-10

call-log-reset-time=0

call-log-stop-only=yes

call-log-limit-retry=0

admin> set call-log-enable=yes

admin> set call-log-host-1=10.1.2.1

admin> set call-log-host-2=10.1.2.2

admin> set call-log-host-3=10.1.2.3

admin> set call-log-port=512

admin> set call-log-key=tntpass

admin> set call-log-timeout=10

admin> set call-log-limit-retry=6

admin> write call-logging

CALL-LOGGING read

Setting up call logging with dynamic IP addressing

When Auth-Pool=Yes, the MAX TNT includes the caller's assigned IP address as the value of the Framed-Address attribute. The MAX TNT allocates this address from pool #1. (If you do not define pool #1, the call does not have an IP address during authentication.) Because an IP assignment is not usually part of an Access-Request, you must modify the RADIUS daemon. The assigned IP address might not last the duration of the connection, or it might not be meaningful. Here are five possibilities:

• If Assign-Address=No in the IP-Answer subprofile of the Answer-Defaults profile, and the caller's RADIUS user profile does not supply an IP address for the caller, the MAX TNT returns the IP address to pool #1. However, the address continues to appear in call-logging entries.

• If Assign-Address=No and the caller's RADIUS user profile supplies an IP address for the caller, the MAX TNT returns the IP address to pool #1. The IP address from the user profile appears in call-logging entries.

• If Assign-Address=Yes, and Ascend-Assign-IP-Pool in the RADIUS user profile points to a pool that has no valid IP address, the IP address from pool #1 appears in call-logging entries. The MAX TNT returns the address to the pool when the call disconnects.

• If Assign-Address=Yes and Must-Accept-Address-Assign=Yes on the MAX TNT, and Ascend-Assign-IP-Pool points to a pool that has a valid IP address, the IP address from that pool appears in call-logging entries for the duration of the call. The MAX TNT returns the address to the pool when the call disconnects.

• If Assign-Address=Yes, Must-Accept-Address-Assign=No, Ascend-Assign-IP-Pool points to a pool that has a valid IP address, and the caller does not specify an address, the IP address from the pool appears in call-logging entries. If the caller does specify an IP address, that address appears in call-logging entries.

Starting the RADIUS daemon with call logging enabled

When using a flat ASCII file

radiusd -A services | incr

If you specify the incr argument, the daemon creates the call-logging process with the UDP port specified as the call-logging port in the /etc/services file. If you have not defined the port, the daemon increments the UDP port specified for radiusd and uses that port number. This action is the default if you do not specify the -A argument.

When using a UNIX DBM database

radiusd.dbm -A services

Understanding call-logging records

• What kind of information appears in call-logging records

• Where call-logging records are stored

• What kinds of packets call-logging uses

• Which attributes appear in each type of packet

• Start session. Denotes the beginning of a session with the MAX TNT. Information about this event appears in a call-logging Start record.

• Stop session. Denotes the end of a session with the MAX TNT. Information about this event appears in a call-logging Stop record.

• Failure-to-start session. Denotes that a login attempt has failed. Information about this event appears in a call-logging Failure-to-start record.

You can use call logging to:

• Gather billing information, including who called, how long the session lasted, and how much traffic occurred during the session.

• Troubleshoot RADIUS and MAX TNT operations. Call-logging records can contain information about how many login failures occurred, and can describe the characteristics of the failed attempts.

usr/adm/radacct/host/detail

What kinds of packets does call logging use?

Start packets

The MAX TNT does not send a Start packet if a call fails authentication or otherwise fails to log in. In some cases, a session begins with a user login and then authentication follows, such as when a terminal-server user chooses PPP or SLIP after login. If User-Service=Login-User, or if User-Service is unspecified, the MAX TNT sends a Start packet after login. Information from a Start packet appears in a Start record in the log file.

Stop packets

Non-call-logging attributes in Start and Stop records

Table 13-1. Non-call-logging attributes in Start and Stop records

Attribute	Description
Ascend-Dial-Number (227)	Indicates the phone number of the device that originated the connection.
Ascend-Home-Agent-UDP-Port (186)-Stop records only	Indicates the UDP port number to use when the foreign agent sends ATMP packets to the home agent.
Ascend-Home-Network-Name (185)-Stop records, Gateway mode only	Indicates the name of the Connection profile through which the home agent sends all packets it receives from the mobile client during ATMP operation.
Caller-Id (31)	Indicates the calling-party number, which is the phone number of the user that has connected to the unit.
Class (25)	Enables access providers to classify their user sessions. The default value for the Class attribute is null.
Client-Port-DNIS (30)	Indicates the called-party number, which is the phone number the user dials to connect to the MAX TNT.
Framed-Address (8)	Indicates the IP address of the user starting the session. The default value is 0.0.0.0.
Framed-Protocol (7)	Indicates the kind of protocol the connection uses. By default, the MAX TNT does not restrict the type of protocol a user can access.
NAS-Identifier (4)	Indicates the IP address of the MAX TNT. This attribute does not appear in a Stop packet for a Failure-start-session event.
NAS-Port (5)	Indicates the port on which the MAX TNT received the call. NAS-Port does not appear in a Stop packet for a Failure-start-session event.
NAS-Port-Type (61)	Specifies the type of service in use for the established session: NAS_Port_Type_Async (0) indicates a call the MAX TNT routes to a digital modem. NAS_Port_Type_Sync (1) indicates a synchronous ISDN connection.
User-Name (1)	Indicates the name of the user starting the session.

Call-logging attributes in Start records

Table 13-2. Call-logging-specific attributes in Start records

Attribute	Description
Acct-Authentic (45)	Indicates the method the MAX TNT used to authenticate an incoming call: RADIUS (1) indicates that RADIUS authenticated the incoming call. Local (2) indicates that the MAX TNT used a local Connection profile, TACACS profile, or TACACS+ profile, or that the MAX TNT accepted the call without authentication.
Acct-Delay-Time (41)	Indicates the number of seconds the MAX TNT has been trying to send the packet. In a Start packet, this value is 0 (zero).
Acct-Session-Id (44)	Consists of a unique numeric string identified with the routing or terminal-server session reported in the packet. The string is a random number. The call-log host correlates the Start packet and Stop packet with Acct-Session-Id. Its value can range from 1 to 2,137,383,647.
Acct-Status-Type (40)	Requests that have Acct-Status-Type=Start are Start packets. The information in these packets appears in Start records. Requests that have Acct-Status-Type=Stop are Stop packets. The information in these packets appears in Stop or Failure-to-start records.
Ascend-Session-Svr-Key (151)	Identifies the user session in which a client sends a disconnect or filter-change request to the call-log host.

Call-logging attributes in Stop records

Table 13-3. Call-logging-specific attributes in Stop records

Attribute	Description	Conditions for inclusion
Acct-Authentic (45)	Indicates the method the MAX TNT used to authenticate an incoming call: RADIUS (1) indicates that RADIUS authenticated the incoming call. Local (2) indicates that the MAX TNT used a local Connection profile, TACACS profile, or TACACS+ profile, or that the MAX TNT accepted the call without authentication.	Session must be authenticated.
Acct-Delay-Time (41)	Indicates the number of seconds between the time an event occurred and the time the MAX TNT sent the packet. If the call-log host does not acknowledge the packet, the MAX TNT resends it. The value of Acct-Delay-Time changes to reflect the proper event time.	None.
Acct-Input-Octets (42)	Indicates the number of octets the MAX TNT received during the session. The value reflects only the data delivered by PPP or other encapsulation. It does not include the header or other protocol-dependent components of the packet.	Session must be authenticated. An asynchronous connection must be in use. That is, the data must be unframed.
Acct-Input-Packets (47)	Indicates the number of packets the MAX TNT received during the session. The packets are counted before the encapsulation is removed. The attribute's value does not include maintenance packets, such as keepalive or management packets.	Session must be authenticated. A framed protocol must be in use.
Acct-Output-Octets (43)	Indicates the number of octets the MAX TNT sent during the session. The value reflects only the data delivered by PPP or other encapsulation. It does not include the header or other protocol-dependent components of the packet.	Session must be authenticated. An asynchronous connection must be in use. That is, the data must be unframed.
Acct-Output-Packets (48)	Indicates the number of packets the MAX TNT sent during the session. The packets are counted before the encapsulation is removed. The attribute's value does not include maintenance packets, such as keepalive or management packets.	Session must be authenticated. A framed protocol must be in use.
Acct-Session-Id (44)	Consists of a unique numeric string identified with the routing or terminal-server session reported in the packet. The string is a random number of up to seven digits. The call-log host correlates the Start packet and Stop packet with Acct-Session-Id. Its value can range from 1 to 2,137,383,647.	None.
Acct-Session-Time (46)	Indicates the number of seconds the session has been logged in.	Session must be authenticated.
Acct-Status-Type (40)	Requests that have Acct-Status-Type set to Start are Start packets. The information in these packets appears in Start records. Requests that have Acct-Status-Type set to Stop are Stop packets. The information in these packets appears in Stop or Failure-to-start records.	None.
Ascend-Connect-Progress (196)	Indicates the state of the connection before it disconnects.	None.
Ascend-Data-Rate (197)	Indicates the rate of data received on the connection in bits per second.	None.
Ascend-Disconnect-Cause (195)	Indicates the reason a connection was taken offline.	None.
Ascend-Event-Type (150)	Indicates a cold-start notification, informing the call-log host that the MAX TNT has started up.	For a cold-start notification, the MAX TNT sends values for NAS-Identifier and Ascend-Event-Type in an Ascend-Access-Event-Request packet (code 33). The call-log host must send back an Ascend-Access-Event-Response packet (code 34), with the correct identifier, to the MAX TNT.
Ascend-First-Dest (189)	Records the destination IP address of the first packet the MAX TNT received on a connection after authentication.	Session must be authenticated.
Ascend-Home-Agent-IP-Addr (183)	Indicates the IP address of the home agent associated with the mobile client.	Session has ended. Session was authenticated and encapsulated by means of Ascend Tunnel Management Protocol (ATMP).
Ascend-Multilink-ID (187)	Reports the ID number of the Multilink bundle when the session closes.	Session must be authenticated.
Ascend-Num-In-Multilink (188)	Records the number of sessions remaining in a Multilink bundle when the session closes.	Session must be authenticated.
Ascend-Number-Sessions (202)	Indicates the number of active user sessions of a given class (as specified by the Class attribute). In the case of multichannel calls, such as MP+ calls, each separate connection counts as a session.	The MAX TNT sends the Ascend-Number-Sessions attribute in Ascend-Access-Event-Request packets. Only RADIUS daemons you customize to recognize packet code 33 respond to these request packets.
Ascend-Pre-Input-Octets (190)	Reports the number of octets the MAX TNT received before authentication. The value reflects only the data delivered by PPP or other encapsulation. It does not include the header or other protocol-dependent components of the packet.	Session must be authenticated. An asynchronous connection must be in use. That is, the data must be unframed.
Ascend-Pre-Input-Packets (192)	Reports the number of packets the MAX TNT received before authentication. The packets are counted before the encapsulation is removed. The attribute's value does not include maintenance packets, such as keepalive or management packets.	Session must be authenticated.
Ascend-Pre-Output-Octets (191)	Reports the number of octets the MAX TNT sent before authentication. The value reflects only the data delivered by PPP or other encapsulation. It does not include the header or other protocol-dependent components of the packet.	Session must be authenticated. An asynchronous connection must be in use. That is, the data must be unframed.
Ascend-Pre-Output-Packets (193)	Reports the number of packets the MAX TNT sent before authentication. The packets are counted before the encapsulation is removed. The attribute's value does not include maintenance packets, such as keepalive or management packets.	Session must be authenticated.
Ascend-PreSession-Time (198)	Indicates the length of time, in seconds, from when a call connected to when it completed authentication.	None.
Ascend-Xmit-Rate (255)	Indicates the rate of data transmitted on the connection in bits per second. For ISDN calls, Ascend-Xmit-Rate indicates the transmit data rate. For analog calls, it indicates the modem baud rate at the time of the initial connection.	None.

Call-logging attributes in Failure-to-start records

Acct-Delay-Time (41)

Acct-Session-Id (44)

Acct-Status-Type (40)

Ascend-Connect-Progress (196)

Ascend-Data-Rate (197)

Ascend-Disconnect-Cause (195)

Ascend-PreSession-Time (198)

For a brief description of each of these attributes, see Table 13-3.

Sample call-logging records

• A Pipeline 25 dialing into a MAX TNT

• A modem calling into a MAX TNT

Tue Feb 18 12:00:41 1997 /* Session startup time */

   User-Name="ht-net" /* The name of the Pipeline 25 */

   NAS-Identifier=206.65.212.46 /* The IP address of the MAX TNT */

   NAS-Port=1057 /* Call on channel 2, line 2, slot 2, shelf 1 */

   Acct-Status-Type=Start /* Start record. */

   Acct-Delay-Time=0 /* Always zero for a Start record */

   Acct-Session-Id="1234567" /* Session identification number */

   Acct-Authentic=RADIUS /* RADIUS authentication in use */

   Client-Port-DNIS="3142" /* Called-party number */

   Framed-Protocol=PPP /* PPP call */

   Framed-Address=11.0.0.1 /* IP address of the Pipeline 25 */

Tue Feb 18 12:02:48 1997 /* Session hangup time */

   User-Name="ht-net" /* The name of the Pipeline 25 */

   NAS-Identifier=206.65.212.46 /* The IP address of the MAX TNT */

   NAS-Port=1057 /* Call on channel 2, line 2, slot 2, shelf 1 */

   Acct-Status-Type=Stop /* Stop record */

   Acct-Delay-Time=18 /* MAX TNT tried to send packet for 18 seconds 
*/

   Acct-Session-Id="1234567" /* Session identification number */

   Acct-Authentic=RADIUS /* RADIUS authentication used */

   Acct-Session-Time=128 /* Number of seconds in session */

   Acct-Input-Octets=2421 /* Bytes received from the Pipeline */

   Acct-Output-Octets=1517 /* Bytes sent to the Pipeline */

   Acct-Input-Packets=79 /* Packets received from the Pipeline */

   Acct-Output-Packets=47 /* Packets sent to the Pipeline */

   Ascend-Disconnect-Cause=100 /* Session timeout */

   Ascend-Connect-Progress=60 /* LAN session up */

   Ascend-Data-Rate=31200 /* Receive data rate in bits per second */

   Ascend-Xmit-Rate=48000 /* Transmit data rate in bits per seconds */

   Ascend-PreSession-Time=0 /*Secs from connection to authentication*/

   Ascend-Pre-Input-Octets=174 /* Input octets pre-authentication */

   Ascend-Pre-Output-Octets=204 /* Output octets pre-authentication */

   Ascend-Pre-Input-Packets=7 /* Input packets pre-authentication */

   Ascend-Pre-Output-Packets=8 /* Output packets pre-authentication */

   Ascend-First-Dest=10.81.44.111 /* Dest IP address of 1st packet */

   Ascend-Multilink-ID=64 /* ID number of Multilink bundle */.

   Ascend-Num-In-Multilink=0 /* # of sessions in Multilink bundle */

   Client-Port-DNIS="3142" /* Called-party number */

   Framed-Protocol=PPP /* PPP call */

   Framed-Address=11.0.0.1 /* IP address of the Pipeline 25 */

A Start record might look like the following:

Tue Feb 18 12:00:00 1997 /* Session startup time */

   User-Name="Berkeley" /* The name of the modem caller */

   NAS-Identifier=200.65.212.46 /* The IP address of the MAX TNT */

   NAS-Port=1057 /* Call on channel 2, line 2, slot 2, shelf 1 */

   Acct-Status-Type=Start /* Start record. */

   Acct-Delay-Time=0 /* Always zero for a Start record */

   Acct-Session-Id="3456789" /* Session identification number */

   Acct-Authentic=RADIUS /* RADIUS authentication in use */

   Client-Port-DNIS="3143" /* Called-party number */

   Login-Service=Unframed-User /* Modem call */

Tue Feb 18 12:03:00 1997 /* Session hangup time */

   User-Name="Berkeley" /* The name of the modem caller */

   NAS-Identifier=200.65.212.46 /* The IP address of the MAX TNT */

   NAS-Port=1057 /* Call on channel 2, line 2, slot 2, shelf 1 */

   Acct-Status-Type=Stop /* Stop record */

   Acct-Delay-Time=18 /* MAX TNT tried to send packet for 18 seconds 
*/

   Acct-Session-Id="3456789" /* Session identification number */

   Acct-Authentic=RADIUS /* RADIUS authentication used */

   Acct-Session-Time=128 /* Number of seconds in session */

   Acct-Input-Octets=2421 /* Bytes received from the Pipeline */

   Acct-Output-Octets=1517 /* Bytes sent to the Pipeline */

   Acct-Input-Packets=79 /* Packets received from the Pipeline */

   Acct-Output-Packets=47 /* Packets sent to the Pipeline */

   Ascend-Disconnect-Cause=100 /* Session timeout */

   Ascend-Connect-Progress=60 /* LAN session up */

   Ascend-Data-Rate=31200 /* Receive data rate in bits per second */

   Ascend-Xmit-Rate=48000 /* Transmit data rate in bits per seconds */

   Ascend-PreSession-Time=0 /*Secs from connection to authentication*/

   Ascend-Pre-Input-Octets=174 /* Input octets pre-authentication */

   Ascend-Pre-Output-Octets=204 /* Output octets pre-authentication */

   Ascend-Pre-Input-Packets=7 /* Input packets pre-authentication */

   Ascend-Pre-Output-Packets=8 /* Output packets pre-authentication */

   Ascend-First-Dest=10.81.44.111 /* Dest IP address of 1st packet */

   Ascend-Multilink-ID=64 /* ID number of Multilink bundle *.

   Ascend-Num-In-Multilink=0 /* # of sessions in Multilink bundle */

   Client-Port-DNIS="3143" /* Called-party number */

   Login-Service=Unframed-User /* Modem call */

Copyright © 1998, Ascend Communications, Inc. All rights reserved.