AES and two T-Servers

[Mirv]

Dear Genesys Professionals,

I am told to look into a possibility of connecting two T-Servers to the same PBX, Avaya 8720. This is necessary to facilitate to different companies that are using the same PBX, with one not wanting other company to be able to read its T-Server log files because it may contain a lot of confidential attached user data.

My questions are:
1. Is it possible to setup two T-Servers which will be controlling for example DN 20000-40000 and 60000-80000 respectively on the same PBX?
2. Are there any environments like this already?
3. What are some of the settings that should be taken into consideration when doing something like this?
      a. PBX settings
      b. Genesys settings

Thank you very much!
[hr]

"Our culture teaches us to buy things we don't need, with money we don't have, to impress people we don't like."
[right][/right]Gordon Bishop
[hr]

[Fra]

I don't think it's possible; from "Genesys 7 Supported Media Interfaces Reference Manual":

[i]Note: S8700 multi-link support is provided using a single TServer; T-Server version 7.1.0 and above is required. Genesys
does not support a "switch partitioned" environment (multipleMAPD/Co-Resident DLG, multiple T-Servers, in a multi-site
environment for a single switch).[/i]

[IanDS]

Technically i think it is actually possibly, but you will find that Genesys would not have tested it.


1 tserver - connects to aes port 5678 - registers extns range 1
2 tserver - connects to aes port 5678 - registers extn range 2

[victor]

[quote author=Fra link=topic=1870.msg6143#msg6143 date=1160984524]
I don't think it's possible; from "Genesys 7 Supported Media Interfaces Reference Manual":

[i]Note: S8700 multi-link support is provided using a single TServer; T-Server version 7.1.0 and above is required. Genesys
does not support a "switch partitioned" environment (multipleMAPD/Co-Resident DLG, multiple T-Servers, in a multi-site
environment for a single switch).[/i]


[/quote]


Fra,

yes, I read that too... I am not sure why it would not support, plus how would it work with their multi-tenant CME? You have on T-Server and multiple environments??? Well, maybe it will work if you are  EchoPass and are in a business of providing CTI popup to companies, but if you are talking about just having one large PBX and many companies wanting to use it, but not wanting each other's IT departments to see the logs, multi-tenant with single T/Server would not work...

We are running into a problem now because with Avaya 8720's almost infinite capacity, we have one PBX running several companies in one building and if you have, for example, Goldman Sachs and Morgan Stanley in the same building, you can be pretty sure that would not want a shared T/Server log.

I really wonder why Genesys would say they do not support it when there seem to be no problem with PBX... What am I missing here?

[Fra]

Victor, Mirv,

I think I have clearer thoughts now 
When Genesys says "multi-site" it denotes that there will be ISCC connectivity between the TServers; so with that note they mean you cannot transfer a call between different T-Servers within the same Avaya! (pretty logical). But if Mirv just wants to have two separated "single-site" without transferring calls each other, it will work.

About multi-tenant: you [i]must[/i] have different T-Servers among different tenants, cause you must select the tenant in the T-Server config (unless that you have a Network T-Server defined under the Enviroment section... ); having different T-Servers, belonging to different tenants, with one Avaya...well I guess it's the same of separated "single-site"...

[victor]

So, to summarize:

1. single sites can be created by using more than one TServer connected to the same PBX
2. DN range for each PBX can be controlled via CME
3. Genesys supports this configuration

Am I off somewhere?

Vic

[Fra]

Victor wrote:[quote]So, to summarize:

1. single sites can be created by using more than one TServer connected to the same PBX
2. DN range for each PBX can be controlled via CME
3. Genesys supports this configuration

Am I off somewhere?[/quote]

just that you can use also a multi-site configuration BUT the sites can not transfer calls each other.