Hi all,
We´re testing the CLIENT mode media control and INDEPENDENT dependency mode for SIP endpoints through Dashboard tool.
Our environment is Avaya SM 6.1, Avaya CM 6.2 and AES 6.2 and Avaya OneX Communicator 6.1.9
Registration process and event registration request works with sucess.
When you make a call (OUTBOUND) from registered DMCC station (10021) to other station (10019), you can see the RTP and you can see all requested events in Dashboard.

When registered station (10021) receives a call (INBOUND), you cannot see RTP data and you cannot see any requested events neither in Dashboard. However, the call between the phones are established with sucess.

See below the DMCC trace from an OUTBOUND call.
I cannot see similar evidences in logs for INBOUND calls

2013-10-01 12.41.48,612 :T-35: com.avaya.mvcs.station.h323.q931.Q931CcmsDivider receivePacket
FINEST: [stplabaesv1:180.205.8.231:10021:0] Q931 MESSAGE: {03,00,00,69,08,02,00,00,62,7E,00,5D,05,26,80,06,00,08,91,4A,00,05,63,E0,70,00,11,00,00,00,00,00,00,00,10,00,00,00,00,00,B4,05,04,7A,34,02,13,00,00,00,0C,60,13,80,0B,0F,00,01,00,B4,CD,08,E4,08,19,00,1E,40,00,64,06,04,01,00,4C,60,13,80,12,15,00,01,00,B4,CD,08,E4,08,18,00,B4,CD,08,E4,08,19,00,01,00,01,00,10,80,01,00}
2013-10-01 12.41.48,612 :T-35: com.avaya.mvcs.h323.MsgStream extractH245TransportAddress
FINEST: Extracted choice from MsgStream -- id:0 name:ipAddress
2013-10-01 12.41.48,612 :T-35: com.avaya.mvcs.h323.MsgStream extractH245TransportAddress
FINEST: extracted IPv4Addr in MsgStream: 180.205.8.228
2013-10-01 12.41.48,612 :T-35: com.avaya.mvcs.h323.MsgStream extractH245TransportAddress
FINEST: extracted IPv4Addr.port in MsgStream: 2073
2013-10-01 12.41.48,612 :T-35: com.avaya.mvcs.h323.MsgStream extractH245TransportAddress
FINEST: Extracted choice from MsgStream -- id:0 name:ipAddress
2013-10-01 12.41.48,612 :T-35: com.avaya.mvcs.h323.MsgStream extractH245TransportAddress
FINEST: extracted IPv4Addr in MsgStream: 180.205.8.228
2013-10-01 12.41.48,612 :T-35: com.avaya.mvcs.h323.MsgStream extractH245TransportAddress
FINEST: extracted IPv4Addr.port in MsgStream: 2072
2013-10-01 12.41.48,612 :T-35: com.avaya.mvcs.h323.MsgStream extractH245TransportAddress
FINEST: Extracted choice from MsgStream -- id:0 name:ipAddress
2013-10-01 12.41.48,612 :T-35: com.avaya.mvcs.h323.MsgStream extractH245TransportAddress
FINEST: extracted IPv4Addr in MsgStream: 180.205.8.228
2013-10-01 12.41.48,612 :T-35: com.avaya.mvcs.h323.MsgStream extractH245TransportAddress
FINEST: extracted IPv4Addr.port in MsgStream: 2073
2013-10-01 12.41.48,617 :T-35: com.avaya.mvcs.station.h323.q931.Q931CcmsDivider receivePacket
FINEST: Q.931 Message
{
Call Reference Value: 0
Message Type: FACILITY
h323_uu_pdu:
{
h323_message_body:
{
facility:
{
protocolIdentifier:
{ 0.0.8.2250.0.5 }
reason: undefinedReason
callIdentifier: 00 00 00 00 00 00 10 00 00 00 00 00 B4 05 04 7A
fastStart:
[{
forwardLogicalChannelNumber: 1
forwardLogicalChannelParameters:
{
dataType:
{
audioData:
{
g711Ulaw64k: 20
}

}

multiplexParameters:
{
h2250LogicalChannelParameters:
{
sessionID: 1
mediaGuaranteedDelivery: false
mediaControlChannel:
{
ip: 180.205.8.228
port: 2073
}

mediaControlGuaranteedDelivery: false
silenceSuppression: false
}

}

}

}
, {
forwardLogicalChannelNumber: 101
forwardLogicalChannelParameters:
{
dataType:
{
nullData:
{
}
}

multiplexParameters:
{
none:
}

}

reverseLogicalChannelParameters:
{
dataType:
{
audioData:
{
g711Ulaw64k: 20
}

}

multiplexParameters:
{
h2250LogicalChannelParameters:
{
sessionID: 1
mediaChannel:
{
ip: 180.205.8.228
port: 2072
}

mediaControlChannel:
{
ip: 180.205.8.228
port: 2073
}

silenceSuppression: false
}

}

}

}
]
}

}

h245Tunneling: false
}

}

Any suggestion or idea, please?

Thanks in advance and regards.

Hi Raul,

I haven't forgotten about you. I have not used MR on a SIP station before and I am having problems setting it up.

My latest situation is that for inbound & outbound calls, I do get MediaStartEvents and an RTP stream. My problem is that the stream is always silence.

Martin

Hi Martin,
Still stuck in same scenario. I can playback saved file with success when it´s an outbound call (see below received xml file)
I don´t receive MediaStartEvents when it´s an incoming call.
I´ll try to get some traces from station side to see the differents.

Incoming XML 9999
<?xml version="1.0" encoding="UTF-8"?>
<MediaStartEvent xmlns="http://www.avaya.com/csta">
<monitorCrossRefID xmlns:ns1="http://www.ecma-international.org/standards/ecma-323/csta/ed3">2</monitorCrossRefID>
<connection>
<deviceID xmlns:ns2="http://www.ecma-international.org/standards/ecma-323/csta/ed3" typeOfNumber="other" mediaClass="voice" bitRate="constant">10021:stplabaesv1:0.0.0.0:0</deviceID>
</connection>
<rtpAddress>
<address>180.205.8.228</address>
<port>2056</port>
</rtpAddress>
<rtcpAddress>
<address>180.205.8.228</address>
<port>2057</port>
</rtcpAddress>
<codec>g711U</codec>
<packetSize>20</packetSize>
<encryption>
<protocol>none</protocol>
<transmitKey>
</transmitKey>
<receiveKey>
</receiveKey>
<payloadType>-1</payloadType>
</encryption>
</MediaStartEvent>

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

Received Lamp Update Event for 10021:stplabaesv1:0.0.0.0:0
Monitor Id: 1 lamp Id: 263 Color: Green Mode: Steady
Media Started Event: 10021:stplabaesv1:0.0.0.0:0 Monitor ID: 2 RTP IP Address: 180.205.8.228 RTP IP Port: 2056 RTCP IP Address: 180.205.8.228 RTCP IP Port:2057
Packet Size:20 Codec:g711U
Encryption Information
Protocol: none
Payload Type: -1
Receive Key:

Hi Raul,

I tried on a different system and I had no problems. I got the MediaStart events and the media correctly. I was using real phones rather than One-X Communicator but I would not expect that to make a difference.

Martin