Genesys CTI User Forum

Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: GondiPee on January 01, 1970, 12:00:00 AM

Title: TServer to TServer communication
Post by: GondiPee on January 01, 1970, 12:00:00 AM

Hi

We have a very large genesys framework setup, using multiple CallCon,s TServers, VRUs etc.
Now when a call is routed from one switch to another and the other switch si linked to a different TServer, the call is recorded in the database as a new call.
This call has a new connid itself.
How do I maintain the same connid and just create a new leg in SCDR?


Thanks,

Gondi

Title: TServer to TServer communication
Post by: Jeff on January 01, 1970, 12:00:00 AM

Good morning, Gondi.
Just a quick question do you have a CGE? I would recommend it.
As for new ConnID this is because you need something like NOM or IR for a multisite environment, since you need to transfer attach data from TServer A to TServer B, as well as notify the satellites which call is what.

Do you have NOM or IR?

Title: TServer to TServer communication
Post by: GondiPee on January 01, 1970, 12:00:00 AM

Jeff

Thanks. We do have a CGE but we are having political problems..That's the reason of me fighting this battle.
We are using NOM.

Let me know.

Thanks,

GondiPee

Title: TServer to TServer communication
Post by: Jeff on January 01, 1970, 12:00:00 AM

Have you checked if NOM is working? Do you have attach data delivered to the satellite TServer?

Title: TServer to TServer communication
Post by: Ed on January 01, 1970, 12:00:00 AM

HAve you tried 'External Router'? this feature is built into Tserver.

Title: TServer to TServer communication
Post by: Akiko Negishi on January 01, 1970, 12:00:00 AM

But you need interactive router server to use it.

Title: TServer to TServer communication
Post by: Ed on January 01, 1970, 12:00:00 AM

Yes, Why not use it? If you are trying to get CCON to build some sort of reasonable data ( especially with multi sites ) then you have to use it.

Title: TServer to TServer communication
Post by: Richard on January 01, 1970, 12:00:00 AM

First and formost what type of switches are you using? If you are using Lucent switches you can pass the call id from one switch to the another and secure the connid for the call. If you are using Nortel switches you need to implement NACD which will provide a Network callid so that you can track the call as one call across switches that way you can maintain the connid.

Title: TServer to TServer communication
Post by: Ed on January 01, 1970, 12:00:00 AM

WHAT!

Title: TServer to TServer communication
Post by: Jim on January 01, 1970, 12:00:00 AM

With some switchs external router will not work. With our Lucent to pass info from site to site we need to use Network Overflow Manager (NOM) that uses the UCID from the switch to reattach data when the calls are transferred from site to site.

Title: TServer to TServer communication
Post by: Ed on January 01, 1970, 12:00:00 AM

Jim

true some switches do not support external routing ( lucent does but I'm not sure about others ) anyway, I am suggesting the genesys external routing feature and that would require IR. NOM is mainly to handle the switch capability to re oute a call if all agents are busy once call has arrived at PBX. GondiPee is asking how to keep same connid with externally routed call with tserver to tserver communication. External routing with genesys is how this is accomplished.

Title: TServer to TServer communication
Post by: jack on January 01, 1970, 12:00:00 AM

Ed is right. Its very easy to setup as well!!