TServer 7.2 versus TServer 7.1 Problem

[xav_net]

Hi everybody!!

We've been reporting a failure in TServer 7.2 and I would want to know if it had happened something similar to anybody.

If we use TServer 7.1 and LDS TProxy 7.1 we can call an agent in an internal call using its agent number or the extension he is logged in, doesn't matter, it works always.

If we change to TServer 7.2 and LDSTProxy 7.2 we can't call to the agents using the agent number (we hear the occupied sound) it seems if the TServer is not able to associate the agent number with the extension the agent is logged in.

We are using an Avaya PBX with AES 3.0.

Has happened something similar to anybody?

Thank you a lot!

[Steve]

Have you tried rolling back to 7.1 to ensure that it is a T-Server problem? If you rollback does the problem go away?

Are you sure nothing else has changed, either within your switch or Genesys environment.

When you upgraded to 7.2 did you create a new application in CME? If so have you got all the parameters correct? Have you tried to use the old CME application.

Have you tried only upgrading the T-Server but left the old LDS?

I don't really see this being an LDS issue, it sounds switch/T-Server related. But for fault finding you should only ever make one change and then test.

[xav_net]

Yes, I've rolled back several times, actually I have 7.1 running until I can see what happens.

Yes, I've created a new application in CME for T-Server 7.2 with the same options as T-Server 7.1.

I've tried with T-Server 7.1 and LDSTProxy 7.2 and it also works, and I tried with TServer 7.2 and LDSTProxy 7.1 and doesn't work, that is why I suppose it's a T-Server 7.2 problem.

I don't think it will be a PBX problem, because with 7.1 version works.

[Fra]

xav_net,

could you post, attach or email the part of Tserver log covering the issue?

Thanks