I was on the remote labs earlier today and I was trying to capture media for both MR as well as SSC recording methods. For MR I was using extensions 40016 till 40020 as both monitored devices and recording devices. For SSC I had configured 40016, 40017 and 40018 as MD and 40019 and 40020 as RD's. For the RD I had configured mediainfo as my capturer VPN IP and ports 4502 and 4504 for SSC and for MR 4502, 4504,4506,4508 and 4510. I was using Avaya X Communicator as my agent soft phones to dial calls from one extension to another.

I was also doing a wireshark capture on the VPN adapter. Wireshark screen shots for both SSC and MR is given in the attached document.

Briefly, for MR, I see RTP being sent to port 2788 and UDP packets being sent to my configured ports 4502 and 4506. I am able to capture media.

For SSC I only see RTP on port 2788 and no udp to my configured ports and I am not able to record media.

Is there any reason why RTP is sent on a non-configured port and not getting udp packets for SSC recording method ?

Thanks in advance.

I would assume that 2788 is the port being used by One-X Communicator.

On the question about not getting media for the SSC recorders. I suggest that you check to make sure that:

1. The application actually asked for the recorder to be SSCed into the call
2. The request succeeded
3. The application received a MediaStart event.

You may find it useful to enable the DMCC tracing on eAE Services. To do this, follow the instructions in the Devconnect Product FAQ "What is the procedure for enabling and accessing the AE Services logs for TSAPI (trace, tracing, g3trace, csta_trace)?". It is in the "FAQ: AE Services TSAPI -> General" section.

A forum posting is not the best place to get assistance on this question I suggest opening a Remote Lab support ticket (Support & Forums -> DevConnect Remote Lab Support). Please include AE Services DMCC trace information with XML (finest) tracing enabled for the problem SSC test case and the registration of the recorder. I would also have looked at the SAT: status station form to see where CM was sending the audio stream to the recorder while the call was active. I would also look for denial events that occurred when the recorder was added to the call (SAT: clear events ; display events and then type= denial).

Sorry for the delay in my reply as I was waiting to get another remote lab access.

Answers to Martin's questions are -

1. The application actually asked for the recorder to be SSCed into the call
YES

2. The request succeeded
YES

3. The application received a MediaStart event.
YES

Attached is a word document that has the screen shot of the SAT as advised by John and the DMCC trace excerpt for the period. I do not see any error corresponding to the media. The RTP port numbers in the DMCC logs are the same as that I receive on media start.

What could be wrong ?

Thanks

I would do a packet trace on the recorder to investigate the RTP packet transfer

Hi John

I had done a capture, but did not get any packets.

I went back to the logs of the 24th and found some additional messages in the log for this failure. Does this message provide any clue to you of what could be wrong -

<132>Oct 24 20:34:31 aeserver DmccMain[20474] -06:00 2017 568 1 com.avaya.aes | :NIO-ChannelServicer Thread: com.avaya.mvcs.h323.MsgStream WARNING - could not decode Q931 message: Failure decoding com.avaya.mvcs.h323.Q931Msg:#012Q.931 Message#012{#012 Call Reference Value: 0#012 Message Type: #012 h323_uu_pdu:#012 {#012 h323_message_body: #012 {#012 nullChoice:#012 }#012 #012 }#012 #012}#012


This message immediately follows my RTP forwarding messages. I have added this log excerpt of the 24th in the attached word file.

Thanks again for your kind help.

I see that the DMCC application is on 192.168.163.72 so it would make sense that 192.168.163.70 could be where the recording ports are hosted.

However the print for registering your RTP address is showing a truncated IP. Please double check that you are transmitting the proper IP.

Here is one example of what I see:

<135>Oct 24 20:34:31 aeserver DmccMain[20474] -06:00 2017 568 1 com.avaya.aes | :NIO-ChannelServicer Thread: com.avaya.mvcs.h323.Q931Messages FINE - ******* Reverse RTP: channel[2], MediaChannel TypeID=IPv4, RTPAddr=92.168.163.70[u], RTPPort=4502

Hi John

Thanks for identifying the issue. I am sorry that I did not look hard enough to locate the error.

Thanks again for your time. Everything working OK now after correcting the IP.

Best regards,

I have overlooked the obvious myself, no worries. I'm glad it is working. :wink: