All,
I have a unique issue where we have a single cti (tserver) that is linked to multiple pbx's.
We have one command CTI application that connects to pbx a or pbx b via this common tserver.
On pbx a we do all sorts of stuff like making calls, placing monitors on devices/stations, monitoring inbound calls, working adjunct route requests, etc. Everthing appears to work fine.
On pbx b we are attempting to do the same exact things with the same exact tserver and cti code. Literally the same executable code. However on this pbx we encounter short term memory loss.
For example:
pbx sends adjunct route request - When our cti answers the request, sometimes the pbx recalls the routeCrossRefId - and other times is says it's invalid.
pbx sends us an unsolicted event of a ringing and two-three minutes after our agent puts the call on hold through our cti, the tserver or pbx says the callID that just showed up earlier from the answer/ring event is invalid.
Basically... Its like the thing has short term memory.
If anyone is aware of what could be wrong... Please advise.
I have a unique issue where we have a single cti (tserver) that is linked to multiple pbx's.
We have one command CTI application that connects to pbx a or pbx b via this common tserver.
On pbx a we do all sorts of stuff like making calls, placing monitors on devices/stations, monitoring inbound calls, working adjunct route requests, etc. Everthing appears to work fine.
On pbx b we are attempting to do the same exact things with the same exact tserver and cti code. Literally the same executable code. However on this pbx we encounter short term memory loss.
For example:pbx sends adjunct route request - When our cti answers the request, sometimes the pbx recalls the routeCrossRefId - and other times is says it's invalid.
pbx sends us an unsolicted event of a ringing and two-three minutes after our agent puts the call on hold through our cti, the tserver or pbx says the callID that just showed up earlier from the answer/ring event is invalid.
Basically... Its like the thing has short term memory.
If anyone is aware of what could be wrong... Please advise.