Partition for CTI ports

[mmelbourne]

Is it possible to place CTI ports in their own partition, so that only the Route Points' CSS contains this partition (and the the agents' DNs are in a partition accessible through the CTI ports' CSS). From the testing I've done, the origin calling device also requires access to the partition containing the CTI ports. In other words, the CSS of the Route Points appears not to be used.

Does the Route Point redirect the caller to a CTI port using the caller's CSS, rather than the Route Point CSS?

[anup.anand]

Try this.

In the CRS Admin, go to SubSystem > JTAPI > CTI Port Group > Select a group and set the "Calling Search Space for Redirect" to "Redirecting Party".

Please see attached a screen shot of this page.

Regards,

Anup

[mmelbourne]

The "Calling Search Space for Redirect" is already set to "Redirecting Party". Isn't this effectively the CSS used when CTI ports redirect calls to agents' extensions?

[adignan]

JTAPI applications unfortunately do not exactly follow the same guidelines when it comes to partitions and calling search spaces.

When calling a JTAPI Applicaiton, the originating device CSS must contain EVERY single partition it will hit in its path on its way to the application/agent.

Normally you can have translation patterns, etc to change an originating devices "effective" CSS but not when it comes to JTAPI applications unfortunately.

please rate helpful posts

adignan - berbee

[anup.anand]

Yes, you are right. The CSS for Redirect doesn't take effect for incoming calls to the CTI port.

Regards,

Anup