JohnBiggs wrote:are they SIP or H.323 or DCP or stations?
Is IP Softphone enabled?
If there is a speakerphone indication on the station form is it set to y?
I dont think there is any restriction related to auto answer.

All devices are OneX

Hello, I am not being able to register some devices through dmcc, after trying many things, I found that in all cases, those devices had "auto answer" activated at the station level. Are there any limitations to registering devices with this configuration? is there any way to solve it?

It works! Thanks.

A different behavior is occurring when a call is finished from dmcc and when it is finished from oneX

In both cases, this part of the flow is similar.
1. OneX and the application are connected to the same device (3345)
2. DMCC logs in an agent (499992) that remains in the READY state
3. I call vdn 7998 which automatically passes the call to agent 499992.

Here the result differs.
4. I end the call from OneX, the initial call, the one that called 7998 is transferred to a survey (1001).

4. I end the call from DMCC, initial call ends, no transfer to survey.

What makes terminating the call from oneX behave differently? the events that are fired are the same
getThirdPartyCallController_OnConnectionClearedEvent

To finish the call I call the method;
this.sProv.getThirdPartyCallController.ClearCall(new ThirdPartyCallController.CallIdentifier(GetDeviceIDAsString(), this.activeCallID), null);

this.activeCallID is obtained from event getThirdPartyCallController_OnDeliveredEvent:
this.activeCallID = e.getConnectionId.getCallId;

MartinFlynn wrote:If you collect DMCC traces from AES and open a Devconnect Ticket, I will take a look.

There are instructions in the Devconnect Product FAQ "How can I monitor the XML being sent and received by the AE Services Server (debug, log, trace)?". It is in the "FAQ: AE Services Device, Media, and Call Control (DMCC) -> Other" section.
https://www.devconnectprogram.com/site/global/products_resources/avaya_aura_application_enablement_services/support/faq/dmcc/index.gsp?tab=other&accordion=faq-60

This solved the problem. Thanks
sProv.ShutDown(ServiceProvider.ServiceProviderObjectDeactivatedEventArgs.ServiceProviderObjectDeactivatedReason.REQUEST_FROM_APPLICATION, string.Empty);

MartinFlynn wrote:It seems that each time you create a session you start a Call Control monitor but you never stop the monitor or the session.

Setting the ServiceProvider variable to null will not stop the DMCC session and disconnect from AE Services. You must call serviceProvider.ShutDown() to end the session.

Martin

ok, but i never got to establish a session, because the credentials were wrong. I do the startMonitor independently of the session, precisely because I need the events to understand if I was able to log in. I tried shutDown, I also tried saving the MonitorID of the last login attempt, and doing a StopMonitor of that ID, but I get an error that says that ID doesn't exist.

MartinFlynn wrote:It's not at all clear what you are asking here. Can you tell us:
1. What SDK are you using (Java or .Net)
2. What Function Call is failing
3. What events you get
4. What actual problem are you having

Martin

1 I'm Using DMCC for .Net
2 getThirdPartyCallController_OnConnectionClearedEvent is fired as many times as I tried to connect
3 same like 2
4. The problem I have is that I have to put a lot of defensive code to avoid the problems caused by events being triggered more than once. If I try to connect 10 times, the getThirdPartyCallController_OnConnectionClearedEvent event will fire 10 times when the current call is finished

In each session retry I delete (set as null) all the objects that were created in the session attempt (devices, serviceprovider, etc). I can't understand why the callbacks from the previous session attempt are stuck to the last session.

Hi. I am having a problem with a dmcc application. When I put the login credentials wrong several times (deviceid, agent, and password) and then enter the correct data, some events like this.sProv.getThirdPartyCallController are fired as many times as I tried to login.

In each login attempt I set to null and new instances for all the objects: serviceProvider, device, etc.

Can you think of what might be happening and how can I fix this?

Thanks.

JohnBiggs wrote:yep, still appears to be there. See attachment.

Thanks!!! I have a slightly old version of dmcc. I don't have that option, I'm going to update as far as the AES version allows me and try the solution you suggest.

JohnBiggs wrote:SST == shorthand for single step transfer

I suggest reviewing the TSAPI documentation for any DMCC Call Control Service you plan on using in your application.

Pending isnt a work mode but rather it is a type of work mode request... it is used when the agent is still active in a call, to avoid exactly the problem you indicate you have.

No Avaya does not document the internal workings of how it implements functionality.

Are you sure that you can use the functionality to indicate a "Pending work mode" via DMCC? I didn't see any method that seems to do something like that. Do you have any examples? Or do you know the name of the method I should use?

JohnBiggs wrote:SST triggers work on CM. Sending in another request encounters resource busy because CM is working on the SST request.

I suggest using a pending work mode request before sending in the SST request.

I don't know what an sst trigger is. Is there a document I can learn about this? and thus better understand the problem.
I don't remember seeing something like a "Pending work mode" in the DMCC documentation, could you give me more information about it?
This problem, I need to solve programmatically. I cannot modify any configuration in AES or in the PBX.

When an incoming call ends and the _OnConnectionClearedEvent event is fired, in the same event I call the SetAgentState method to configure the agent in "After Call Work" for a few seconds, and thus prevent a new call from the queue from entering. This works perfectly. But when I try to do exactly the same, also with an incoming call, but instead of ending the call it is transferred using the SingleStepTransfer method, the callback indicates a ResourceBusy error and a new call enters from the queue even before the _OnSetAgentStateResponse event is fired.

Why is the behavior different ending a call or transferring?

How should you make sure that when transferring (singleTransfer) an incoming call, the agent goes into AfterCallWork and while that state lasts, no call enters?


DMCC .NET

JohnBiggs wrote:query the agent status. the result would show the single station that the agent is logged in at. There can only be one station where the agent is logged in at.

But the deviceID is a required parameter to query the agent status, and it is precisely the data that I need to find out

JohnBiggs wrote:I believe you can query the agent, and get the device (station) they are logged in on, and then properly fill in the logout request.

I can't find any function in the dashboard that gives me the list of devices where an agent is logged in.

Hi, I can logout an agent from a device (any agent) doint this:

private void SetAgentLogOut()
{
ThirdPartyCallController.SetAgentStateParameters agentParams = new ThirdPartyCallController.SetAgentStateParameters();

if (this.currentDevice != null)
{
agentParams.Device = this.currentDevice.getDeviceIdAsString;
agentParams.RequestedAgentState = ThirdPartyCallController.RequestedAgentState.AM_LOG_OUT;


invokeLogOutID = this.sProv.getThirdPartyCallController.SetAgentState(agentParams, null);
}
}

but, if I remove the Device parameter, and add the AgentID doen't work. ¿Is there any way to logout an Agent from any device?.

Thanks.