Docwikibot: Bot: Adding {{Template:Required Metadata}}

2009-12-18T19:22:40Z

Bot: Adding {{Template:Required Metadata}}

← Older revision		Revision as of 19:22, 18 December 2009
Line 1:		Line 1:
		+	{{Template:Required Metadata}}
	== Tracking the call in Unified ICM ==		== Tracking the call in Unified ICM ==

Cchetty: 1 revision

2009-06-10T22:11:17Z

1 revision

← Older revision

Revision as of 22:11, 10 June 2009

Cchetty: /* Tracking the call in Unified ICM */

2009-06-09T18:50:39Z

Tracking the call in Unified ICM

New page

== Tracking the call in Unified ICM ==

{| border="1"
|-
! '''Problem Summary'''
| Once CVP has received the call, Cisco-Guid is in the user.media.id ECC variable. ECC Variable records are written one per variable, per TCD record. To find the user.media.id ECC variable, you need to know its internal ID (a number in the 5xxx range), and do a join from the corresponding TCD record where Termination_Call_Detail.
RecoveryKey = Termination_Call_Variable.TCDRecoveryKey.
|-
! '''Error Message'''
| None.
|-
! '''Possible Cause'''
| By default, Unified ICM does not store ECC variables in the database. In order for this to work, you must set the variable to '''persistent''' in the ECC variable config tool.
|-
! '''Recommended Action'''
| Search these log files:
:* Unified ICM VRU PIM Trace logs - these contain all the CVP - ICM GED-125 messaging and is always enabled.
:* Unified Expert Advisor PG OPC log.
Search the Historical Database:
:* Termination_Call_Variable – written as each ICM call leg ends, for each PG.
:* Call_Route_Variable – written as each routing script ends.
|-
! '''Release'''
| Release 7.6(1)
|-
! '''Associated CDETS #'''
| None.
|-
|}

[[Category:Unified Expert Advisor, Release 7.6(1)]]

Call Tracing: Tracking the call in Unified ICM - Revision history

Docwikibot: Bot: Adding {{Template:Required Metadata}}

Cchetty: 1 revision

Cchetty: /* Tracking the call in Unified ICM */