Cisco Cisco IPCC Web Option Technical References

Network_Event_Detail Table

This table is in the 

. To see database rules for these tables, click 

Provides carrier network events associated with calls processed by a Network Applications
Manager (NAM). The data in this table includes events related to all call legs that happen under
the control of the NIC. This includes the incoming call leg, any temporary call legs (IVR sessions
under NIC control), and all outgoing call legs.

This table can become very large. Running custom reporting queries against it while it is on the
HDS can degrade performance. To optimize performance, extract the data from the HDS into
your own custom database on a separate server (one that is not used for other ICM/IPCC
components). Use only DBDateTime (date and time of the record that was written to the HDS
database) to perform the extraction. The table on the custom database can be indexed according
to the custom reporting needs.

RecoveryKey

clustered, unique, unique key located
on PRIMARY

XAK1Network_Event_Detail

DateTime

nonclustered located on PRIMARY

XIE1Network_Event_Detail

NOT NULL

DBSMALLINT

The LegID identifies the calling party the event pertains to. LegIDs
are typically numbered starting with 1 (for example: LegID1 =

CallLegID

Calling Party) and incremented for the next party (agents are
typically LegID2).

NULL

DBDATETIME

Timestamp of receipt of event at the NIC (in UTC)..

DateTime

NULL

DBINT

The duration is written for DISCONNECT/UNKNOWN events.
Unless an error occurs, the Disconnect even will be written with

Duration

the duration. If the call ends for a reason other than Disconnect
event (e.g. - network aborts call), an Unknown event will be written
with the duration.

NULL

DBSMALLINT

Valid values are:

Event

• 1 = RouteSelectFailure

• 2 = CallPartyBusy

• 3= NoAnswer

Database Schema Handbook Cisco ICM/IPCC Enterprise & Hosted Editions 7.2(2)