NEC Switch and Lab environment

[Kevin S]

I have a question for the experts...

I've just entered an environment that has an NEC switch. It is my understanding that all DNs, trunks, etc need to be defined in the configuration so events can be monitored, even if it gets configured as an "unlicensed DN".

One of my tasks is to create a lab environment. Unfortunately, I only have the one switch [production] to work with. My question is: if all DNs, etc., need to be defined in the production environment, how am I supposed to register DNs, trunks, etc in my lab environment? For DNs used in my pro environment, would I enter these as "unlicensed DNs" in my lab environment and vice versa?

[tcolombo]

Assuming you are interfacing with Genesys.  You will need to have and additional CTI Link for your test environment and an additional Tserver.  With that, you will have a TServer per link, a switch per TServer, and DN resources per switch within CME.

Tony
Braintrust PS

[Kevin S]

Yes, I am referring to a Genesys environment...

I am looking to make a completely (well, almost) separate installation - from a new Config DB on up - with the only common components being the PBX and the phone set.

Just to make sure I'm on the same page, by "additional CTI Link" you're referring to configuring a separate Switching Office Object and Switch Object within Genesys, correct? Since I'm planning on creating a separate config environment, I think that almost goes without saying...

[Haldane]

Kevin,
    You'll need an extra CTI link configured on the NEC switch. So firstly ensure that this is possible in your environment. The dn's on your second link must not be currently monitored by the active link i.e Only 1 Tserver can control a DN. I setup something similar before on a Meridian till I purchased a separate test switch.

[rosshartford]

The NEC supports the following (from the T-Server for NEC manual):

Large-system switches with appropriate software and
configuration are capable of supporting up to eight applications
simultaneously monitoring the same DN. Check with your switch
vendor to confirm support capability of your release of switch
software.

Small-system switches can support up to four T-Servers
monitoring the same DNs simultaneously.

If you can tightly control the call flows within the test environment, you should be able to get away with only the necessary DN's for the test environment configured.  But if you as much as pickup the phone and dial a non-monitored DN, then "unpredictable results" will occur.

[victor]

Ok,

for fear of repeating something already said:

for NEC there are two types of licenses that you need to worry about:

- active DNs and monitored DNs

The cool thing about monitored DNs is that even though you cannot (officially) control them, you still will receive events for those DNs.

So, in your case, you actually do not have to register ALL of DNs used by the production TServer in your Lab CME, but you should register all of the DNs that you imagine your LAB environment might be sending the call to, even if those DNs are not controlled by your TServer_Lab.

In other words:
for Monitored in Lab: all of DNs that would be receiving or sending call to/from you but are not directly controlled by your CTI application.
For DNs under switch - all of DNs that your application WILL control.

You should not care about DNs used by the Production TServer because for obvious reasons you do not want them to mix.

License would be: active DNs= activeDNs of Production TServer + activeDNs on LAB TServer. :>