Call Control on Phantom Terminals for Option 11

[ipl]

All,

We need to set up phantom extensions on Option 11 (rel.25)such that calls can be both placed, answered and controlled (via the CTI link) on the phantom extension. So far we have only been able to call a phantom extension, but not answer calls nor place calls from the phantom terminal.

We have done this on Avaya Definity previously. Help on configuration for Option 11 greatly appreciated.

IPl

 

[janaya]

If I am correct. When using any CTI app, you need to receive messaging from the Nortel. We are using a Genesys Environment and we need AST licenses on Key 0 and the Primary Extension Key Assignment.

AST licenses do not work on Phantom TN's of any sort, so messaging will not be sent from calls to or from Phantom Sets.

John Anaya

 

[ipl]

Thanks,

Even if Phantom Terminals can not be monitored -- I would hope/assume the call including the phantom terminal can be monitored at the other party involved in the call (e.g. the calling/receiving trunkline or terminal)? Do you know if it is still possible to execute CTI call control commands on the (non-AST)phantom terminals?

Alternatively, is there an alternative mechanism to configure a digital extension as 'virtual' without having a real physical terminal connected to it?

IPl

 

[janaya]

If you are in an environment where you want to get information from a particular terminal. In the instance of Genesys TServer:

they receive messages like: EventRinging, EventEstablished, EventAnswered, EventDisconnect.

It uses these messages to follow the call flow and present attatched data in a CTI environment, where you are presenting screen pops to call agents. Without the AST license on the appropriate keys, you cannot know when the call agent logs in, becomes ready and is busy. I am not sure how the other CTI apps work in this relationship, but we just went through a two site Genesys implementation and AST's on the phoneset are required. I did try to get around with phantom tns because of nortels limitation of 2 AST licenses per phoneset, but in the documentation on phantom TN progrmming you cannot get that function. It is one of the Feature limitations listed in the NTP.

On getting the Phantom Superloop to be Analog you would enter an N in front of the SUPL listing in 97, or you could build a quad density loop in Ld 17 by listing the loop with an N in front of the Loop number at the TERD command.

In 97 I think you would go

REQ: CHG
TYPE: SUPL
SUPL: NXXX <--- must be divisible by 4
I don't recall if you need an XPE assingment for the controller card on a Phantom Loop this way, but you can build one of those just as easy.

I use the Quad Density setup in LD 17 because it allows me to use a card slot that is not being used, and can't because of physical limitations.

archaic, but it works.....phantoms work real well with hotel seating and phantom DN's (side note)

Hope this helps

 

[ipl]

Thanks for your help.

We do some pretty advanced CTI algorithms that preferably should be done on non-physical call control enabled endpoints/extension. We will aim for using a second AST enabled line on the physical extensions for now as a call control endpoint, but if anyone have any idea of how we can define a non-physical AST enabled line -- it would be very good. Licensing is not the issue.

One such idea we are just now looking into is e.g. defining non-existent AST enabled VoIP extensions.

IPl