sidradical
IS-IT--Management
Hi,
I have a NP 3.1 system single box with 2 * Integrations (1 * AES, 1 * PC4.1 Dialler).
Normally on 8.x systems where you have dialler/regular integration you need to configure the dialler tie trunks to be ignored on the switch driver.
Not doing this results in the “long” call scenario where dialler CTI records generate call records on the switch integration.
I have configured the “Rejected” devices plug-in and setup my rejected trunks like;
#*1 so that all calls on CTI trunk group 1 get ignored. I restart the integrations dispatch and can see the plug-in taking effect however calls are still being inserted on this trunk.
I have spoken to a few engineers who believe NP works slightly different that NP where you need to configure the call server to “ignore switch ID” however this seems a little drastic and I am not sure if it will resolve my problem.
Just wondering if anyone has experience with NP and regular/dialler integrations on the same interaction server as this would seemingly be quote a common setup..
I have a NP 3.1 system single box with 2 * Integrations (1 * AES, 1 * PC4.1 Dialler).
Normally on 8.x systems where you have dialler/regular integration you need to configure the dialler tie trunks to be ignored on the switch driver.
Not doing this results in the “long” call scenario where dialler CTI records generate call records on the switch integration.
I have configured the “Rejected” devices plug-in and setup my rejected trunks like;
#*1 so that all calls on CTI trunk group 1 get ignored. I restart the integrations dispatch and can see the plug-in taking effect however calls are still being inserted on this trunk.
I have spoken to a few engineers who believe NP works slightly different that NP where you need to configure the call server to “ignore switch ID” however this seems a little drastic and I am not sure if it will resolve my problem.
Just wondering if anyone has experience with NP and regular/dialler integrations on the same interaction server as this would seemingly be quote a common setup..