Genesys CTI User Forum

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

Title: DN's and Alias DN's
Post by: Jocelyn on January 01, 1970, 12:00:00 AM

We currently have an issue with TServer not attaching data because the DN's do not match the Alias DN's. TServer says the DN is invalid. We're using Alias DN's to get the call to the site because our sites are not unique in DNs. They all have the same queue number within the 5 sites. Has anyone addressed this issue before or can advise me how we can?

Title: DN's and Alias DN's
Post by: Fariborz on January 01, 1970, 12:00:00 AM

What is the exact TServer error message?
How did you configure these DNs Alias?
How do you make your target selection?
Is this problem occurs only when you make a Multisite routing?
What's happen when you route directly to one of these DNs?

Title: DN's and Alias DN's
Post by: Jocelyn on January 01, 1970, 12:00:00 AM

The TServer message in short, stated that the DN does not match the Alias DN. We've configured the Alias DN's with; 1001_TPA while the DN is 1001 for the ACD. The target selection is based on queues and the CLID. This issue occurs when multisite routing. No problem when you directly route to one site.

Title: DN's and Alias DN's
Post by: Fariborz on January 01, 1970, 12:00:00 AM

It seems that you route to ACDQ from a RP in an original site to a destination site. right?
If yes, check the URS log file. What is the result of RequestRouteCall event?
What is the value of the Attribute "TARGET"?
What is the value of AttributeLocation?
Is the target founded by URS match your ACDQ number and Site name?