Message |
[+]
DMCC APIs
» RTCP packet analysis, 29/10/2018 07:40:02
» Go to message
|
|
When monitoring client media using the DMCC dashboard, the RTCP packet messages are appearing, is there a way to develop an application to analyze these packets and translate it to a useful data like Delay, Jitter and packet loss?
|
|
[+]
DMCC APIs
» TSAPI advance license types, 30/08/2018 06:00:05
» Go to message
|
|
i finally got the info found in the document
Avaya Aura® Application Enablement
Services Overview and Specification
The TSAPI advanced license is intended for applications that launch calls (predictive dialing
applications) or route calls. The TSAPI advanced license is based on the number of
Communication Manager servers you want to license and the size of the Communication Manager
platform: Small (S84xx), Medium (S85xx), and Large (S87xx and S8800).
|
|
[+]
DMCC APIs
» TSAPI advance license types, 29/08/2018 09:10:43
» Go to message
|
|
AVP stands for avaya virtual appliance not voice portal.
|
|
[+]
DMCC APIs
» TSAPI advance license types, 29/08/2018 08:30:20
» Go to message
|
|
I already tried that with my partner but his reply is not clear can you differentiate between them?
|
|
[+]
DMCC APIs
» TSAPI advance license types, 27/08/2018 07:07:40
» Go to message
|
|
I need to know the difference between AES TSAPI advance license for small, medium and large switches?
What scale do i need for AVP duplex CM license?and for small AVP S8300 server?
|
|
[+]
DMCC APIs
» MakePredictiveCall snippet, 09/07/2018 03:13:54
» Go to message
|
|
Thanks Martin for your support
|
|
[+]
DMCC APIs
» MakePredictiveCall snippet, 09/07/2018 02:14:06
» Go to message
|
|
Thanks Martin for your response i'm using DMCC .Net SDK, i finally got it to work using the following, do you know what exact TSAPI advanced license is required?
ThirdPartyCallController.MakePredictiveCallParameters param;
param = new ThirdPartyCallController.MakePredictiveCallParameters();
param.CallingDevice = DeviceId;
param.CalledDirectoryNumber = DestinationDeviceId;
param.DestRoute = "";
InvokeId = serviceProvider.getThirdPartyCallController.MakePredictiveCall(param ,null);
|
|
[+]
DMCC APIs
» MakePredictiveCall snippet, 08/07/2018 08:11:51
» Go to message
|
|
Hi,
I can't find the make predictive call snippet in order to know its method syntax.
Please share it or make any example for using it with its parameters.
|
|
[+]
DMCC APIs
» DMCC Failed event call not answered, 14/06/2018 07:40:13
» Go to message
|
|
Sad to hear this but anyway thanks a lot for your support guys.
|
|
[+]
DMCC APIs
» DMCC Failed event call not answered, 14/06/2018 07:33:06
» Go to message
|
|
Do you think If using TSAPI API i'll have the same issue or i can get better results?
|
|
[+]
DMCC APIs
» DMCC Failed event call not answered, 14/06/2018 07:28:28
» Go to message
|
|
Correct, but by testing this Network Reached event only triggers when the call is not answered so i will assume that if this event occurred it means that the call is not answered.
|
|
[+]
DMCC APIs
» DMCC Failed event call not answered, 14/06/2018 02:15:22
» Go to message
|
|
I'm going to us this event for not answered calls
void getThirdPartyCallController_OnNetworkReachedEvent(object sender, ThirdPartyCallController.NetworkReachedEventArgs e)
{
if (e.getProgDescription.ToString().Equals("Undefined") & e.getLocalConnectionInfo.Equals("connected"))
{
}
}
and this one if Mobile not available
private void getThirdPartyCallController_OnOriginatedEvent(object sender, ThirdPartyCallController.OriginatedEventArgs e)
{
if(e.getEventCause.ToString().Equals("newCall") & e.getLocalConnectionInfo.Equals("initiated"))
{
}
}
|
|
[+]
DMCC APIs
» DMCC Failed event call not answered, 13/06/2018 02:22:30
» Go to message
|
|
I tried this using the dashboard where the monitored station is 2231 kindly find below the XML messages from the dashboard
-----------------------
Incoming XML 9999
<?xml version="1.0" encoding="UTF-8"?>
<LampModeEvent xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3">
<monitorCrossRefID>430</monitorCrossRefID>
<device>
<deviceIdentifier typeOfNumber="other" mediaClass="voice" bitRate="constant">2231:EFG:10.255.252.40:0</deviceIdentifier>
</device>
<lamp>262</lamp>
<lampMode>2</lampMode>
<lampBrightness>unspecified</lampBrightness>
<lampColor>3</lampColor>
</LampModeEvent>
-----------------------
Incoming XML 9999
<?xml version="1.0" encoding="UTF-8"?>
<DisplayUpdatedEvent xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3">
<monitorCrossRefID>430</monitorCrossRefID>
<device>
<deviceIdentifier typeOfNumber="other" mediaClass="voice" bitRate="constant">2231:EFG:10.255.252.40:0</deviceIdentifier>
</device>
<logicalRows>1</logicalRows>
<logicalColumns>48</logicalColumns>
<contentsOfDisplay>
</contentsOfDisplay>
</DisplayUpdatedEvent>
-----------------------
Incoming XML 9999
<?xml version="1.0" encoding="UTF-8"?>
<DisplayUpdatedEvent xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3">
<monitorCrossRefID>430</monitorCrossRefID>
<device>
<deviceIdentifier typeOfNumber="other" mediaClass="voice" bitRate="constant">2231:EFG:10.255.252.40:0</deviceIdentifier>
</device>
<logicalRows>1</logicalRows>
<logicalColumns>48</logicalColumns>
<contentsOfDisplay>a=901095939008 </contentsOfDisplay>
</DisplayUpdatedEvent>
-----------------------
Incoming XML 9999
<?xml version="1.0" encoding="UTF-8"?>
<NetworkReachedEvent xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3">
<monitorCrossRefID>432</monitorCrossRefID>
<outboundConnection>
<callID>6553</callID>
<deviceID typeOfNumber="dynamic" mediaClass="notKnown" bitRate="constant">T6553#2:EFG::0</deviceID>
</outboundConnection>
<networkInterfaceUsed>
<notKnown />
</networkInterfaceUsed>
<callingDevice>
<notKnown />
</callingDevice>
<calledDevice>
<deviceIdentifier typeOfNumber="implicitPublic" mediaClass="notKnown" bitRate="constant">1095939008:EFG::0</deviceIdentifier>
</calledDevice>
<lastRedirectionDevice>
<notKnown />
</lastRedirectionDevice>
<localConnectionInfo>connected</localConnectionInfo>
<cause>normal</cause>
<extensions>
<privateData>
<private>
<NetworkReachedEventPrivateData xmlns:ns1="http://www.avaya.com/csta" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="NetworkReachedEventPrivateData">
<progressLocation>user</progressLocation>
<progressDescription>inband</progressDescription>
</NetworkReachedEventPrivateData>
</private>
</privateData>
</extensions>
</NetworkReachedEvent>
Received Lamp Update Event for 2231:EFG:10.255.252.40:0
Monitor Id: 430 lamp Id: 262 Color: Green Mode: Off
Display Update Event: 2231:EFG:10.255.252.40:0Monitor ID: 430 ""
Display Update Event: 2231:EFG:10.255.252.40:0Monitor ID: 430 "a=901095939008 "
Network Reached Event: 432
Called Device:
Cause: normal
Local Connection Info: connected
Network Interface Used:
Progress Description: Undefined
Progress Location: User
Outbound Connection Id:
Call Id: 6553
Device Id: T6553#2:EFG::0
-------- Device History Start-------------------------
Device History List Items: Size=0
-------- Device History End
|
|
[+]
DMCC APIs
» DMCC Failed event call not answered, 12/06/2018 02:30:56
» Go to message
|
|
What are you doing in your application to monitor for no-answer events?
ThirdPartyCallController.ThirdPartyCallControlEvents CallControlEvents;
CallControlEvents = new ThirdPartyCallController.ThirdPartyCallControlEvents(false);
CallControlEvents.FailedEvent = true;
InvokeId = serviceProvider.getThirdPartyCallController.StartMonitor(DeviceId, CallControlEvents, null);
serviceProvider.getThirdPartyCallController.OnFailedEvent += new FailedEventHandler(getThirdPartyCallController_OnFailedEvent);
void getThirdPartyCallController_OnFailedEvent(object sender, ThirdPartyCallController.FailedEventArgs e)
{
MessageBox.Show("" + e.getEventCause + "");
}
Specifically what do you consider a no-answer event to be?
Outgoing call over the PRI trunk to my cell phone with no answer
What event are you seeing in the SIP call flow?
CALLNOTANSWERED
Are these inbound or outbound calls you are monitoring?
Outbound calls
What device in the call flow are you monitoring?
H.323 9600 series IP phone with CM 7.0 and AES 5 or 7.0 or 7.1.2
|
|
[+]
DMCC APIs
» How can i get a busy event for an outbound call using web services in AES and DMCC, 11/06/2018 07:42:15
» Go to message
|
|
i got busy event when cancelling on cell phone by using the getThirdPartyCallController_OnFailedEvent
ThirdPartyCallController.ThirdPartyCallControlEvents CallControlEvents;
CallControlEvents = new ThirdPartyCallController.ThirdPartyCallControlEvents(false);
CallControlEvents.FailedEvent = true;
|
|