Transfer problem

[Marco]

Hello,
We have a problem with transfer. We have a meridian 81c Rls 25,15 with symposium 3.0 and Genesys 6.5.
If a exterbal client calls a CDN / RP the call wil be routed by the strategie of Genesys to the softphone from agent skill A, Agent A transfers the call to another agent skill B. This agent B wants to transfer the call again to agent skill C.
And that works with no problem, but if I try this same scenario with a internal call we get a TServer message Destination Acces Blocking.

Has some one the same problem and does some one know the solution of it.

With kind regards marco

[KM]

Can you please post part of the log where you get this error? What version of tserver are you using?

[Marco]

We use TLib 6.5.100.00 TServer 6.5.101.56 on the production side and on the test we use TServer 6.5.303.01.
But both sides don't work with internal transfer. We use a meridian 81C with release 25.15 and symposium 3.0.

[John Doe]

I believe if you have "Destination Acces Blocking" it is a case of getting your PBX people to check out the Meridian's class of service permissions. I saw this a while back where Genesys tried to transfer a call but the Meridian said no to the transfer.

Hope this helps

[Marco]

Thanks for your reply, can you tell me the specifik feature in the cls.

[R]

Do you have the AST feature set for the keys?

[Vic]

Marco,

can you please post the part of the log where this error occurs? We are unable to replicate your problem in our lab here.

My first guess would be the setting for your AST key, where you are trying to transfer to ACD position, but I don't think you would be doing that, would you?

[Marco]

Yes we have programmed the ast 00 02 because it is a M3820, otherwise Tserver don't register the phone.
Or do you mean another feature.

[Marco]

Vic, can you tell me witch setting of the COS.
I cant find anything.

Thanks Marco