Author Message
YOULEHOSON
Joined: Aug 20, 2013
Messages: 0
Offline
hello, guys

i have a problem, so i need a help

CASE:

i did start a monitoring for "MEDIA"

likewise

Avaya.ApplicationEnablement.DMCC.Media.MediaEvents MediaEvents;
MediaEvents = new Avaya.ApplicationEnablement.DMCC.Media.MediaEvents(false);
MediaEvents.MediaStartedEvent = true;
MediaEvents.MediaStoppedEvent = true;
MediaEvents.TonesDetectedEvent = true;
e.getDevice.getPhone.getMedia.StartMonitor(MediaEvents, "Media");

and also regist event hadler like below

realDevice[index_device].getPhone.getMedia.OnMediaStartedEvent += new MediaStartedEventHandler(OnMediaStartedEvent);
realDevice[index_device].getPhone.getMedia.OnMediaStoppedEvent += new MediaStoppedEventHandler(OnMediaStoppedEvent);
realDevice[index_device].getPhone.getMedia.OnToneDetectedEvent += new ToneDetectedEventHandler(OnToneDetectedEvent);


BUT, mediastartevent and tonedetectedevent does not work

ONLY MEDIASTOP event work

same code was normally work at 5.2

but now(6.2) does not work

what can i do for it? please, let me know why mediastart and tonedetected events are not called my eventhandler

same problem is occured for using protocol version PROTOCOL_VERSION_5_2 and PROTOCOL_VERSION_6_2
YOULEHOSON
Joined: Aug 20, 2013
Messages: 0
Offline
and more

DMCC SDK DASHBOARD also same problem appear.


sometime TONES DETECTED EVENT incomming

but sometime does not work


i want to know SDK DLL is problem?

or AES FIRMWARE's problem?
MartinFlynn
Joined: Nov 30, 2009
Messages: 1922
Online
I am not aware of any problems with MediaStartevents in AE Services 6.2 or the .NET SDK. I am using both in my lab and have received MediaStart events for various tests.

When you register the terminal, what media mode do you use? Client or Server?

Martin
YOULEHOSON
Joined: Aug 20, 2013
Messages: 0
Offline
i`m use in client mode and dependant
YOULEHOSON
Joined: Aug 20, 2013
Messages: 0
Offline
i success to get a start media event

but i'm still cannot get a tone detected event

this is raw data captured by wireshark


------------------------------------------------------------
i sent

]0005<?xml version="1.0" encoding="utf-8"?>
<MonitorStart xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3">
<monitorObject>
<deviceObject typeOfNumber="other" mediaClass="notKnown">21002::10.48.226.67:0</deviceObject>
</monitorObject>
<requestedMonitorFilter>
<voice>
<play>false</play>
<record>false</record>
<stop>false</stop>
<suspendPlay>false</suspendPlay>
<suspendRecord>false</suspendRecord>
</voice>
</requestedMonitorFilter>
<extensions>
<privateData>
<private>
<AvayaEvents>
<ToneDetectionEvents>
<toneDetected>true</toneDetected>
</ToneDetectionEvents>
<ToneCollectionEvents>
</ToneCollectionEvents>
<MediaControlEvents>
<mediaStarted>true</mediaStarted>
<mediaStopped>true</mediaStopped>
</MediaControlEvents>
<invertFilter>true</invertFilter>
</AvayaEvents>
</private>
</privateData>
</extensions>
</MonitorStart>

------------------------------------------------------------

i've received

j0005<?xml version="1.0" encoding="UTF-8"?>
<MonitorStartResponse xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"><monitorCrossRefID>117</monitorCrossRefID><actualMonitorFilter><voice><play>false</play><record>false</record><stop>false</stop><suspendPlay>false</suspendPlay><suspendRecord>false</suspendRecord></voice></actualMonitorFilter><extensions><privateData><private><ns1:AvayaEvents xmlns:ns1="http://www.avaya.com/csta" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns1:AvayaEvents"><ns1:invertFilter>true</ns1:invertFilter><ns1:toneDetection><ns1:toneDetected>true</ns1:toneDetected></ns1:toneDetection><ns1:toneCollection/><ns1:mediaControl><ns1:mediaStarted>true</ns1:mediaStarted><ns1:mediaStopped>true</ns1:mediaStopped></ns1:mediaControl></ns1:AvayaEvents></private></privateData></extensions></MonitorStartResponse>

------------------------------------------------------------

i think, i did start monitoring normally
start media and stop media evnets are comming
but, i can't get a TONEDETECTED event

i did like a guide

1. Implement the Media.OnToneDetectedEvent delegate to handle each tone that is
detected.

realDevice[index_device].getPhone.getMedia.OnToneDetectedEvent += new ToneDetectedEventHandler(OnToneDetectedEvent);

void OnToneDetectedEvent(object sender, Media.ToneDetectedEventArgs e)
{
MessageBox.show("tone);
}

2. The Media.MediaEvents must be configured to monitor for the
ToneDetectedEvent issued by the AE Services server using the
Media.StartMonitor request.

Avaya.ApplicationEnablement.DMCC.Media.MediaEvents MediaEvents;
MediaEvents = new Avaya.ApplicationEnablement.DMCC.Media.MediaEvents(false);
MediaEvents.MediaStartedEvent = true;
MediaEvents.MediaStoppedEvent = true;
MediaEvents.TonesDetectedEvent = true;
e.getDevice.getPhone.getMedia.StartMonitor(MediaEvents, "Media");


3. Now each time a tone is detected by the AE Services server, a
ToneDetectedEvent is issued to the application and handled by the registered
delegate.

but i cannot get a event
YOULEHOSON
Joined: Aug 20, 2013
Messages: 0
Offline
i'm using 6.3.0.229 ServiceProvider.dll
JohnBiggs
Joined: Jun 20, 2005
Messages: 1139
Location: Rural, Virginia
Offline
1) does it work in your environment with the DMCC Dashboard?
2) does the /opt/mvap/logs/dmcc-trace.log.0 file show AEServices trying to send tone events to your application (you may want to follow the FAQ related to increasing DMCC tracing to show xml - search for "DMCC XML trace')
3) what are you using as the source point for your DTMF events?
YOULEHOSON
Joined: Aug 20, 2013
Messages: 0
Offline
i think this is some errors on version
if i monitor for 'startmedia', 'stopmedia', 'tonedetected'
only 2 events are works

and if i only monitor for 'tonedetected', it works very well

you can see this works on below
http://youtu.be/bZWYDbVxs0Q

both case occure digit detected on the log like below

Out-of-band digit detected : '1'

and also both case ToneDetectionListener is also registered

2013-08-26 17.45.46,941 :T-109: com.avaya.cmapi.monitor.MonitoringServicesImpl addChangeToneDetectionFilter
FINE: added ToneDetectionListener: 156, id=[21002::10.48.226.67:0] , listener=com.avaya.cmapi.monitor.ToneDetectionListenerImpl@113956e


i cannot understand this phenomenon
could you tell me a way how to fix this phenomenon

1) yes, same problem also occured on DMCC Dashboard

2) each case occure event

3) what is meaning of the source point?
purpose? using for capture signal as record on demand
platform? .net 3.5, vs2010, windows server 2008 standard, 6.3.0.229 dmcc sdk
JohnBiggs
Joined: Jun 20, 2005
Messages: 1139
Location: Rural, Virginia
Offline
3) source point a trunk or station.. in your case you appear to be using a 96xx series telephone.

4) Is this phone a SIP protocol phone, or H.323 protocol phone? the timestamp of 17:45:30 seems to read "CTI: SIP" SIP behavior with DMCC will be drastically different than H.323. A subset of DMCC capabilities are supported with SIP phones.

So from the video if you set tonedetect to true, and mediatart/stop to false, the tonedetect works. If you set tonedetect and mediastart/stop to true, tonedetect now fails. I agree this is very strange.

What version of AE Services are you running?
What version of the DMCC .NET SDK?
Do you see any exceptions (during application initialization or running the call scenario) thrown in AE Services /opt/mvap/logs/dmcc-trace.log.0 when you run with all monitors enabled?

JohnBiggs
Joined: Jun 20, 2005
Messages: 1139
Location: Rural, Virginia
Offline
4) is the MONITORED phone a SIP station? The phone sending DTMF does not worry me (much) in the context of the issue you convey, however the configuration of the destination phone does.

Also what class of registration are you doing, dependant, independant, main? and what media mode, none, server, client, telecommunter?
YOULEHOSON
Joined: Aug 20, 2013
Messages: 0
Offline
3) source point a trunk or station.. in your case you appear to be using a 96xx series telephone.

-> i'm using 9630 phones.

4) Is this phone a SIP protocol phone, or H.323 protocol phone? the timestamp of 17:45:30 seems to read "CTI: SIP" SIP behavior with DMCC will be drastically different than H.323. A subset of DMCC capabilities are supported with SIP phones.

-> engineer says, only use h.323, phones and CM and AES all h.323

What version of AE Services are you running?
-> 6.2
What version of the DMCC .NET SDK?
-> dll is 6.3 .NET SDK and i set protocol to 6.2 when i make a session

Do you see any exceptions (during application initialization or running the call scenario) thrown in AE Services /opt/mvap/logs/dmcc-trace.log.0 when you run with all monitors enabled?
-> i saw some exception, like parse error
but i don't know what they mean

4) is the MONITORED phone a SIP station? The phone sending DTMF does not worry me (much) in the context of the issue you convey, however the configuration of the destination phone does.
-> engineer says, only h.323 stations are here

Also what class of registration are you doing, dependant, independant, main? and what media mode, none, server, client, telecommunter?
-> CLIENT MODE, Dependant
MartinFlynn
Joined: Nov 30, 2009
Messages: 1922
Online
The Developers have been able to reproduce this problem and are investigating it.

In the mean time, the following is a workaround that they say works for them. It may be of some use to you:

1.   Perform a start media monitor where the media start/stop events == false and the tone events == true
2.   Perform a change media monitor where the media start/stop events == true.

Martin
YOULEHOSON
Joined: Aug 20, 2013
Messages: 0
Offline
thank you i'll try it
YOULEHOSON
Joined: Aug 20, 2013
Messages: 0
Offline
i handle this problem successfully

thank you for your help
Go to:   
Mobile view