Unable to sort it out, we reached out to Genesys and were told the following:
[quote]Higher level API has login/logout methods. For example:
container.Resolve<IAgent>().Login()/LogOff() will login/logout all available medias.
Individual medias have their login/logoff methods. You can access medias from that IAgent instance, e.g. container.Resolve<IAgent>().FirstMediaVoice.
You can get the lower level Platform SDK protocol from a media, e.g. for voice - container.Resolve<IAgent>().FirstMediaVoice.Channel.Protocol
It's important to note that if you access these properties too early in the code (e.g. inside your module's Initialize() method) they might not be yet created/available.
[/quote]
IAgent's FirstMediaVoice was null until I logged in, so that does nothing for me, and Login() failed but shed some light on the underlying problem: our Genesys users and PBX users differ in that Genesys ones have a prefix on the front, and Workspace is attempting to use that prefix on the PBX and failing.
Starting from [url=https://stackoverflow.com/a/42418070]https://stackoverflow.com/a/42418070[/url], I was able to come up with the following to force a login:
[code]
var agent = container.Resolve<IAgent>();
// If logged in, do nothing
if (!(agent?.FirstMediaVoice?.IsPossibleLogOn ?? true))
return;
var request = RequestAgentLogin.Create("<dn>", AgentWorkMode.Unknown);
request.AgentID = "<PBX user ID>";
request.Password = "<PBX password>";
var channelService = agent.EntrepriseService.Resolve<IChannelService>("channelService");
var tServerChannel = channelService.ListChannels<TServerProtocol>().FirstOrDefault();
var tServerProtocol = tServerChannel.Protocol as TServerProtocol;
tServerProtocol.Send(request);
[/code]
