We have a strange situation with one of our clients. We are using the tsapi exerciser to route a call to a specific agent for testing purposes however we keep getting a invalid routing cross ref id error. we have verified through the exerciser logs that the cross ref id we sent is exactly the same as the one we received and we are responding withing 100 ms of receiving the route request. We have also verified that we have the advanced tsapi license for routing and the credentials we used to log into the AES has unrestricted cti access. Any idea whats going on?

Make sure there is some sort of wait step in the vector after the adjunct route step to give the application time to respond. e.g.

02 adjunct routing link 1
03 wait-time 2 secs hearing silence

Hello Martin thx for the quick response. We have confirmed that we used the settings you suggested and we are still seeing the same error. Any other ideas?

My only other suggestion is that the Routing Request or Selection messages are actually being delayed somewhere. If your problem only happens under load, I think this is the most likely reason.

It looks like the issue was a faulty aes link that was configured in the client's vector. We will schedule another test with the client to confirm. Thanks for you help.