TECHNICAL COMMUNICATION No. TC0868 Ed.

02

OmniPCX Enterprise Nb of pages : 16 Date : 27 July 2007

URGENT

NOT URGENT TEMPORARY PERMANENT

SUBJECT: REAL TIME ACCOUNTING OVER ETHERNET

Please find hereafter the description of the real time accounting (or on the fly) over Ethernet designed
to emit tickets towards an external accounting application.

1
 OmniPCX Enterprise
REAL TIME ACCOUNTING OVER ETHERNET

CONTENTS

1. OVERVIEW...................................................................................3
1.1. Operating conditions ................................................................................ 3
1.2. PCX management ..................................................................................... 4

2. EXCHANGE BETWEEN PCX AND EXTERNAL APPLICATION ...........5

2.1. Dialog: principle ....................................................................................... 5
2.2. Connection with the application ............................................................... 5
2.3. Dialog initialization .................................................................................. 5
2.3.1. Identifying the CPU role....................................................................................5
2.3.2. Server initialization ...........................................................................................5
2.4. Maintain of dialog connection (keep alive) ............................................... 6
2.5. Accounting ticket ...................................................................................... 6

3. INTERFACE & ARCHITECTURE ......................................................6

4. TOOLS.........................................................................................7
4.1. eaccclt....................................................................................................... 7
4.2. Ethernet ticket accounting simulator ......................................................... 9

5. TROUBLESHOOTING .................................................................10
5.1. Alarms .................................................................................................... 10
5.2. If no tickets are sent towards the external application ............................ 10
5.3. Check if keep alive requests are sent every 30 seconds .......................... 11

6. LIMITATIONS .............................................................................12

7. ETHERNET ACCOUTING APPLICATION PROTOCOL ...................12

7.1. Example.................................................................................................. 12

Ed. 02 / 27 July 2007 1 TC0868

 OmniPCX Enterprise
REAL TIME ACCOUNTING OVER ETHERNET

TC0868 2 Ed. 02 / 27 July 2007

 OmniPCX Enterprise
REAL TIME ACCOUNTING OVER ETHERNET

1. OVERVIEW
The real time accounting (or on the fly) over Ethernet has been designed to emit tickets towards an
external accounting application.
These tickets can be masked on the level of the number emitted according to the type of
communication (normal, business and personal). The type of tickets (public, private, outgoing,
incoming and so on) can be filtered.
The format of the tickets is identical to that of the tickets stored in compressed form
(/usr4/account/*.DAT).
IMPORTANT
The use of the real time accounting is exclusive: the selection of the tickets via Ethernet prohibits the
use of the output of the tickets on V24 interface and vice-versa.
To ensure correct management of on the fly accounting, the following items must be taken into
account:
• Operating conditions
• PCX management

PSTN

LAN client

Tickets
Accounting
application

1.1. Operating conditions

The following software locks (license) must be available:
− V24MeteringOnFly (Number 51)
− AccountingEthernet (Number 83)
− TicketsABCNetCalls (Number 99) requested if the tickets must be sent back to the
subscriber's node

Ed. 02 / 27 July 2007 3 TC0868

 OmniPCX Enterprise
REAL TIME ACCOUNTING OVER ETHERNET

1.2. PCX management

Configure the Accounting objects as follows:

Applications > Accounting

Attributes:
Internal Accounting = Yes
Real Time Tickets Output = Ethernet

WARNING
Accounting filters can be set so that only the required tickets are emitted.
Select among the list below only the type of tickets exploited by the external application:
ApplicationS > Accounting
Attributes: Real-Time Tick. Outp. Parameters
Filters:
Public Outgoing PCX calls (The major outgoing ticket when PCX is stand alone)
Public Outgoing Network Calls
PCX Network Calls (2)
Private Outgoing PCX Calls
Private Outgoing Network Calls
Public Incoming PCX Calls
Public Incoming Network Calls
Private Incoming PCX Calls
Private Incoming Network Calls
Priority Incoming Calls
Data Outgoing/Incoming Calls
Public Outgoing 0 Unit Calls (1)
Non Ticketed User
PCX PCX Calls (2)
PCX Transit Calls (2)
PCX/Netw Count. Tick. Duration 0
CDR (Tickets) Management (2)

Notes
1 If no pulses are computed by the PCX or received from the public operator, all the tickets with 0
unit will be stopped. So, it is better to add this filter when no tickets are sent to the external
accounting application.
2 CAUTION: 'Internal', 'transit' and 'management' tickets are not available for the 'V24 Real time'
feature. If these tickets are selected, you can no more select Real Time Tickets Output =
V24 except if before they were deleted in the filter.

TC0868 4 Ed. 02 / 27 July 2007

 OmniPCX Enterprise
REAL TIME ACCOUNTING OVER ETHERNET

2. EXCHANGE BETWEEN PCX AND EXTERNAL APPLICATION

The exchange is described below:
− Dialog: principle
− Connection with the application
− Dialog initialization
− Maintain of dialog connection (keep alive)
− Accounting ticket

2.1. Dialog: principle

The OmniPCX Enterprise is considered to be a server and the external application to be a client.
The external machine initiates the connection. The PCX provides the transmission of available tickets.
Note
If the external application is not available or the link to it is broken, tickets are stored in a buffer of
the PCX which comprises up to 500 tickets. Beyond this figure all the tickets are lost.

2.2. Connection with the application

The PCX being in permanent listening on port 2533, the external application sends one 'Connect'
frame containing the port number proposed to perform the dialog in the direction PCX -> External
application.
The 'Connect' frame is reversed and returned back to the external application.
Once connected, the dialog can be initiated.

2.3. Dialog initialization

2.3.1. Identifying the CPU role

"S" (Start) is the first message sent to the PCX:
00H 01H 53H
["S" message used to select the accounting server (SvTSE) through Ethernet]
The PCX replies with the message:
00H 01H 50H if the CPU is Main
When the CPU is duplicated, the external application must always address the main CPU.

2.3.2. Server initialization

The external application sends the message:
00H 02H 00H 00H ("INIT_REQ")
The PCX replies with the message:
03H 04H ("INIT_RSP")

Ed. 02 / 27 July 2007 5 TC0868

 OmniPCX Enterprise
REAL TIME ACCOUNTING OVER ETHERNET

2.4. Maintain of dialog connection (keep alive)

To check that the remote application is still present, the PCX sends test frames every 30 seconds.
The PCX sends the message:
54H 45H 53H 54H 5FH 52H 45H 51H ("TEST_REQ"")
The external application must reply with the message:
00H 08H 54H 45H 53H 54H 5FH 52H 53H 50H("TEST_RSP")
If two 'TEST_REQ' messages remain unanswered, the PCX considers that the external application can
no longer be reached. It closes the connection and releases associated resources.
Since the external application is client, the dialog must be started by itself again by sending "S"
message.

2.5. Accounting ticket

When a ticket is available, the PCX sends the message:
TICKET_INFO with 772 data byte length
An acknowledgement is expected from the client via a Ticket- ACK message:
00H 02H 00H 03H

3. INTERFACE & ARCHITECTURE

Netaccess is a Unix process (MIX) in the OmniPCX Enterprise. It's the interface between the TCP/IP
stack and the PCX's applications (CMIS, ABC-A, incidents and SvTSE*).
*SvTSE: accounting server through Ethernet.

Application 1 Application 2 Application 3

SvTSE

Netaccess server

TCP/IP stack

Ethernet driver
OmniPCX Enterprise

LAN

Client external application

or
Ethernet ticket accounting simulator Figure 1

TC0868 6 Ed. 02 / 27 July 2007

 OmniPCX Enterprise
REAL TIME ACCOUNTING OVER ETHERNET

4. TOOLS

4.1. eaccclt
eaccclt is an embedded tool which can help troubleshooting or getting information about the
ticket format.
Real time tickets can be displayed but they are not sent at this step through the LAN.
It is mandatory to disconnect the external application when using eaccclt.

> eaccclt
eaccclt - ethernet accounting client
eaccclt -[aelv]
-a attribute number
list of attributes to print.
-ascii
one ticket per line and ascii printing.
-cpu hostname|IP address
list of cpu.
-e accounting|mao
lists all known ticket editions.
-help
this help.
-l accounting|mao
meanings of the enumerated and bitstring attributes.
-time time limit
time limit in case of connection failure (default=15mn).
-v
prints the values of the attributes (default is meaning).
-waiting waiting time
waiting time after a connection failure (default=30s).

Generated tickets can be displayed in real time :

Example
302)xa003002> eaccclt -cpu 10.41.3.53
connected to 10.41.3.53
---[10.41.3.53:1]-------------------------------------------
TicketVersion = ED5.1
CalledNumber = 0155666400
ChargedNumber = 6410
ChargedUserName = M Tailor
ChargedCostCenter =
ChargedCompany =
ChargedPartyNode = 302
Subaddress =
CallingNumber =
CallType = PublicNetworkCall (0)
CostType = 2
EndDateTime = 20051206 12:59:36
ChargeUnits = 2
CostInfo = 24

Ed. 02 / 27 July 2007 7 TC0868

 OmniPCX Enterprise
REAL TIME ACCOUNTING OVER ETHERNET

Duration = 4
TrunkIdentity = 15
TrunkGroupIdentity = 10
TrunkNode = 302
PersonalOrBusiness = Normal (2)
AccessCode =
SpecificChargeInfo = PBXGeneratedChargeUnits (2)
BearerCapability = Speech (2)
HighLevelComp = Telephony (1)
DataVolume = 0
UserToUserVolume = 0
ExternalFacilities = CallingLineIdentificationPresentation (0)
InternalFacilities = BasicCall (23)
CallReference = 33
SegmentsRate1 = 0
SegmentsRate2 = 0
SegmentsRate3 = 0
ComType = Voice (1)
X25IncomingFlowRate = Unspecified (0)
X25OutgoingFlowRate = Unspecified (0)
Carrier = 0
InitialDialledNumber =
WaitingDuration = 0
EffectiveCallDuration = 0
RedirectedCallIndicator = 0
StartDateTime = 20051206 12:59:32
ActingExtensionNumber = 6410
CalledNumberNode = 9999
CallingNumberNode = 9999
InitialDialledNumberNode = 9999
ActingExtensionNumberNode = 302
TransitTrunkGroupIdentity = 32767
NodeTimeOffset = 0

Type Ctrl C to exit the tool.

The fields of each ticket version can be displayed :
Note
Ticket edition = 5.1 since Release 3.2
(302)xa003002> eaccclt -e accounting
ED5.1 (00) TicketVersion..............[001-005]
(01) CalledNumber...............[006-035]
(02) ChargedNumber..............[036-065]
(03) ChargedUserName............[066-085]
(04) ChargedCostCenter..........[086-095]
(05) ChargedCompany.............[096-111]
(06) ChargedPartyNode...........[112-116]
(07) Subaddress.................[117-136]
(08) CallingNumber..............[137-166]
(09) CallType...................[167-168]
(10) CostType...................[169-169]
(11) EndDateTime................[170-186]
(12) ChargeUnits................[187-191]
(13) CostInfo...................[192-201]
(14) Duration...................[202-211]

TC0868 8 Ed. 02 / 27 July 2007

 OmniPCX Enterprise
REAL TIME ACCOUNTING OVER ETHERNET

(15) TrunkIdentity..............[212-216]
(16) TrunkGroupIdentity.........[217-221]
(17) TrunkNode..................[222-226]
(18) PersonalOrBusiness.........[227-227]
(19) AccessCode.................[228-243]
(20) SpecificChargeInfo.........[244-250]
(21) BearerCapability...........[251-251]
(22) HighLevelComp..............[252-253]
(23) DataVolume.................[254-263]
(24) UserToUserVolume...........[264-268]
(25) ExternalFacilities.........[269-308]
(26) InternalFacilities.........[309-348]
(27) CallReference..............[349-358]
(28) SegmentsRate1..............[359-368]
(29) SegmentsRate2..............[369-378]
(30) SegmentsRate3..............[379-388]
(31) ComType....................[389-389]
(32) X25IncomingFlowRate........[390-391]
(33) X25OutgoingFlowRate........[392-393]
(34) Carrier....................[394-395]
(35) InitialDialledNumber.......[396-425]
(36) WaitingDuration............[426-430]
(37) EffectiveCallDuration......[431-440]
(38) RedirectedCallIndicator....[441-441]
(39) StartDateTime..............[442-458]
(40) ActingExtensionNumber......[459-488]
(41) CalledNumberNode...........[489-493]
(42) CallingNumberNode..........[494-498]
(43) InitialDialledNumberNode...[499-503]
(44) ActingExtensionNumberNode..[504-508]
(45) TransitTrunkGroupIdentity..[509-513]
(46) NodeTimeOffset.............[514-519]

4.2. Ethernet ticket accounting simulator

This tool allows to simulate the dialog with the OmniPCX Enterprise. It can be supplied by the Alcatel
Technical Support if requested. Just enter the cpu@address and click on Connect button.
Every 30 seconds, you should see 'Keep alive ACK' then 'Keep alive demande'.
The PCX destination port number is always 2533 and the source port number is allocated
automatically at every new connection.
Note
This tool is not sold and is provided as is. Alcatel-Lucent gives no official Technical Support for this
tool. Alcatel-Lucent does not commit to do any correction or software modification in case you should
encounter any technical problem.

Ed. 02 / 27 July 2007 9 TC0868

 OmniPCX Enterprise
REAL TIME ACCOUNTING OVER ETHERNET

5. TROUBLESHOOTING

5.1. Alarms
As soon as the external application is disconnected, the following alarm is displayed:
07/12/05 13:27:21 003002M|--/--/-/---|=0:2663=Erreur IPC Chorus : appli
SERV_APL oper 7 err -1
When the external application is disconnected for a long time, the following alarm is displayed:
06/12/05 05:25:51 003002M|--/--/-/---|=2:0276=External accounting
application ??? : NO RECOVERY
This incident is cyclical (every 4 hours).

5.2. If no tickets are sent towards the external application

If no tickets are sent towards the external application, the following steps are suggested to be
performed.
In order to display the tickets, launch the eaccclt tool with the following arguments: (if the external
application is kept connected, no ticket will go through the Ethernet link).
1 Launch the commands
eaccclt –cpu <IP address> (main @ip address is required in case of duplicated CPU)
Ctrl C to exit.
2 Generate some tickets from a telnet session in another window. To do that you can use the
account justif tool. It is very helpful to generate any tickets. There is no need to perform
outgoing tickets from a telephone set. Just enter the charged number in the first line and CR for
the other ones.

TC0868 10 Ed. 02 / 27 July 2007

 OmniPCX Enterprise
REAL TIME ACCOUNTING OVER ETHERNET

3 If no tickets are generated, verify the accounting management and the locks. Refer to sections
1.1 & 1.2 .
If the tickets are properly generated, that means the accounting management and the locks are
correct. Go to step 4 .
REMINDER
In case of a PCX network and no trunk group on the node where the real time accounting is
managed, the tickets must be sent back by the 'Subscriber Node Accounting' feature from the node
where the trunk group is located.
System > Other System Param. > Accounting Parameters
Attribute: Accounting Ticket To User Node = All or Administrative or Guest

Tickets sent back if CPN # TN

TN = 201

Node 1 ABC-F link Node 2

Network number = 2
LAN client

CPN = 201 CPN = 202 Accounting

application

Extension A with CPN = 1 Extension B with CPN = 2

Figure 2
CPN: Charged Party Node

TN : Trunk Node

In this example (Figure 2), the Accounting Ticket To User Node must be set in node 1.

5.3. Check if keep alive requests are sent every 30 seconds

4 The external application or the simulator must be connected to the PCX (if the external
application was kept connected in step 1, disconnect and connect it again).
The external application is a client regarding the PCX. So, the client takes the initiative in sending
the TEST_REQ.
The keep alive requests get the netaccessd process started.
The netaccesd process depends itself on the xinetd process.

Ed. 02 / 27 July 2007 11 TC0868

 OmniPCX Enterprise
REAL TIME ACCOUNTING OVER ETHERNET

Check if they are running by entering the commands below:

(302)xa003002> ps -edf |grep xint*
root 597 1 0 Jan31 ? 00:00:00 xinetd -stayalive -reuse -pidfil
mtcl 13779 1912 0 08:53 ttyS0 00:00:00 grep xint*
(302)xa003002> ps -edf |grep netac*
root 13665 597 0 08:40 ? 00:00:00 netaccessd
root 13666 13665 0 08:40 ? 00:00:00 netaccessd
root 13669 13665 0 08:40 ? 00:00:00 netaccessd
root 13670 13665 0 08:40 ? 00:00:00 netaccessd
mtcl 13781 1912 0 08:53 ttyS0 00:00:00 grep netaccessd
(302)xa003002>

If the TCP/IP keep alive requests are working fine but no tickets are sent to the external
application yet, the IP rooting can be wrong. So, connect the simulator or the external
application directly to the PCX Ethernet access in order to avoid a possible firewall filtering or
wrong routing through the customer LAN.

6. LIMITATIONS
Tickets will be lost as soon as the buffer gets full or when the link is cut.

7. ETHERNET ACCOUTING APPLICATION PROTOCOL

7.1. Example
Note
Keep alive requests are not shown.

TC0868 12 Ed. 02 / 27 July 2007

 OmniPCX Enterprise
REAL TIME ACCOUNTING OVER ETHERNET

SERVER CLIENT

Write :
Read - 3 bytes length
- ‘S’
HEX >00 01 53

Write :
- 3 bytes length Read
- ‘P’
HEX >00 01 50

Write :
- 4 bytes length
Read - DEST_4400
- INIT_REQ
HEX >00 02 00 00
Write :
- 2 bytes length
- DEST_EXT
- INIT_RSP Read
HEX >03 04

Write :
- 772 bytes length Read
- DEST_EXT
- TICKET_INFO
HEX >XY ZW 01 02_ _ _ …
Write :
- 4 bytes length
- DEST_4400
Read - TICKET_ACK
HEX >00 02 00 03

Close Close

Ed. 02 / 27 July 2007 13 TC0868

 OmniPCX Enterprise
REAL TIME ACCOUNTING OVER ETHERNET

TC0868 14 Ed. 02 / 27 July 2007