Meridian America Link/Customer Controlled Routing manual Creating a Phantom Set

Chapter 12: Meridian 1 configuration for Meridian Link/CCR 351

Creating a Phantom Set

After configuring the phantom loop, an AST Meridian 1 proprietary set can be designated to a specific device group which can be controlled by applications. Therefore, when an application wants to originate a call on behalf of an idle TN, it can use a phantom TN. This idle TN is an AST Meridian 1 proprietary set which is defined on a phantom loop. There is no upper limit on the number of devices per group defined by a Phantom DN. The upper limit is the limit of the number of TNs that can be defined for the loop card. This number is dependent on the density of the loop card. The ITNA and DGRP prompts need to be configured as shown in Table 133.

Note: A phantom set cannot be created for an ACD agent.

Table 133

LD 10ÑCreating a Phantom Set

Prompt	Response	Comment
REQ	NEW	New
TYPE	aaaa	Telephone type, where:
		aaaa = SL1, 2006, 2008, 2009,
		2016, 2018, 2112, 2216, 2317,
		2616, or 3000.
TN	l s c u	Terminal number
	c u	Terminal number for the Option 11
¥		Press [Return] until the CDEN
¥		prompt appears.
¥
CDEN	SD, DD, 4D	Card density
		SD = Single density
		DD = Double density
		4D = Quad density
DES	phanDN	One-to-six character Office Data
		Administration System (ODAS)
		Station Designator

Ñ continued Ñ

Meridian Link Release 5C/CCR Release 3C Installation and Upgrade Guide