Maybe somebody could help me. I just need to get 3rd party device and start monitoring it. Here is my code.

void foo()
{
int InvokeId = sp.getThirdPartyCallController.GetThirdPartyDeviceId("CM", "3257", null);
sp.getThirdPartyCallController.OnGetThirdPartyDeviceIdResponse += getThirdPartyCallController_OnGetThirdPartyDeviceIdResponse;
ThirdPartyCallController.ThirdPartyCallControlEvents ev = new ThirdPartyCallController.ThirdPartyCallControlEvents(true);
int i = sp.getThirdPartyCallController.StartMonitor(TPDeviceId, ev, null);
}

void getThirdPartyCallController_OnGetThirdPartyDeviceIdResponse(object sender,
ThirdPartyCallController.GetThirdPartyDeviceIdResponseArgs e)
{
try
{

if (e.getError != "")
{

}
else
{
TPDeviceId = e.getDeviceIdAsString;
}
}
}
catch (Exception) { }
}

Only way i know to get deviceid is to get it while process OnGetThirdPartyDeviceIdResponse event. But it not fires immediately i call GetThirdPartyDeviceId,so in moment i ty to call StartMonitor - param is empty yet.
What i'm doing wrong?

Thanks!

Could?i pass params in MakeCall() as strings in proper format ([extension]:[switchname]:[swithip],[instance]) besides of calling corresponding method for both parties?

But,AFAIK (accoording to manual),MakeCall requires two params: source ThirdPartyDeviceId and called ThirdPartyDeviceId , how can i use it to make call to external number?

Is there some way to place Call outside (for example, to smb cellphone) from device,registered as Third Party Device?

Only way I know to do so, is to register device and and sequentialyl call PressButtonCommand for each digit.

MartinFlynn wrote:
If you are not using call Control events and do use Call Control commands (e.g. Make call, Answer Call) then you should not start a Call Control monitor and you will not need these licenses. If you do need to use call Control (aka third Party) features then you will require more TSAPI licenses.
Martin

I use it to get events like EstablishEvent, OriginatedEvent and so on.That's only reason i have to start it.
Maybe there is another, more suitable, way to obtain information i need

JohnBiggs wrote:
Unless each extension is monitored by a different PC/server, you would be much better served to use a single session. All the monitoring can be done in the context of a single session and that will consume less resources at the application and at the AE Services end of the communication channel.

And how many extensions can be monitored within one single session? It depends on what?

I have application, which based on DMCC Telecommuter.
Every extension need to be monitored by this application, makes four steps :Get session,get deviceId, Start monitors,and (optionnally) register terminal. Most of extensions don't register terminal, so DMCC license should not be used for them.
But few weeks ago i started to receive "generic" messages on StartMonitor commands like
<subscribedResourceAvailability>generic</subscribedResourceAvailability>

Then I check DMCC log, there was a lot of messages like

ch.ecma.csta.errors.SubscribedResourceAvailabilityException: There was a problem allocating the required license. It is possible that the license limit has been exceeded or that there is an off-pbx-telephone station-mapping for the station on CM.

But, according to my WML manager, there are available DMCC licenses (see attachment).

So, whats the source of this error?

Thanks in advance!

I'll try.Thanks a lot.

Just to make sure that I got you right:
All I want is to "listen" current extensions (about 100) for Events Like Call OriginatedEvent, DeilveredEnevt, FailedEvent e.t.c.
Now i'm using Telecommuter Application to do so. And if I want to listen extension - i have to obtain session,deviceId, then start required monitor on (it takes some changes in code, because initially it was a Device monitor),and then register terminnal in dependent mode with no media.
So there is a way to do same things without registration??

Is there some way to make a device to be listened without Register Terminal??
I'm talking about Call Control Monitor.

MartinFlynn wrote:If you have started a Physical device monitor on the extension then I would expect you to receive one or more DisplayUpdated event (plus LampMode events etc.) as soon as you register the terminal.

The events and RegisterTerminalResponse can arrive in any order. So you should not expect to always receive the RegisterTerminalResponse before you receive events.

Martin

Thanks a lot.
But, accodrind to DashBoard,is it possible to start device FP monitor after RegisterTerminal?

Earlier then I send RegisterTerminalRequest XML from my App, RegistertRerminalResponse was only message i receve from AES (at least,it was first). But several days ago something changes: Then i send RegisterTerminalRequest XML, first XML i receive from AES is DisplayUpdateEvent or smth like this
(Yes,i have monitors started before Register Terminal, but it works fine sometimes ago).Help me please.
Which changes it can be?? Sorry fro my English. Appreciate for your help

ChandrashekarSK wrote:Is there any way that I can access the Dialer Database directly through any high level platform like .NET and get the real time data. All we need is the call completion codes and other such details in real time say every 5 mins.

Only way I found is to connect via Net Oracle connection :DB -Avayapdsdb user&passw: avayadba

Hello,EveryOne
Sorry,if i missed a forum,but i can't find a proper thread.

I'm trying to integrate ProactiveContact functionality into our system through API. Generally it works fine,but in case when system crashes and user trying to launch it again, error "E28812: Agent %s already logged in. Access is denied." displayed. Main problem is that i can do nothing, but handle this error ,because ohter methods like Not FurterWork,LogOff,DisconectHeadSet not working because they required agent connection, but i can't do it due those error. How can i get rid of this error??

Does anyone has some examples on C# using ProactiveContact API?

MartinFlynn wrote:7

Examples of Third Party actions are - monitor for Call Control events

This is explained in the Programmers Guide.

Martin

So,i've read "aes api programmer guide", but i found nothing about monitor third party devices by DMCC. Maybe,there are some other manuals, where this information more detailed.