CTI dialer issue with AES-CM integration

[jmazis]

I have this issue,
CTI dialer (Altitude) with TSAPI connected to AES (4.2.4/SP2) and through cti link connected to CM (5.2.1/SP 10).
CTI dialer when increases number of predictive calls then observes delay and after few minutes blocked , from AES's side i get many errors ,

a) request C_3PDC_REQ to switch timed out
b) PBX Driver detected an invalid digit 'C' (0x43) in device ID "CharPtr::NULL"
c) Unrecognized ASAI message - C_3PCE(2), C_REQUEST(0)

and from last investigation we get these AES's logs,
TSAPI:mk_ase:CRV(a, b) for link 32 already in use

Additionally from yesterday's TSAPI traces we get these errors,
REQUEST_TIMEOUT_REJECTION(78)
INVALID_CSTA_CONNECTION_IDENTIFIER(13)
RESOURCE_BUSY(33)

We checked CM side (denial events , availability of ISDN primary channels that used for outbound calls , no found problem).
Do you have some other similar problem?

[jmazis]

We will investigate with CTI's support.

[jmazis]

We found some kind of conflict on tsapi link (2 cti users uses same invoke ids)..
Avaya support has proposes ,upgrade Tsapi client to latest version
Have any one similar issue??

Thanks
John

[jmazis]

knows somebody. how many is the maximum simultaneous CTI calls that can manage the AES (sw 4.2.4).
Exists some kind of restriction/limit about simultaneous 100 CTI calls?

We get on g3trace logs that, on ASAI Message A3PMCAck --> callingDev,Party CharPtr::NULL,1.

Anyone can help us??