the way the mrcp integrates into freeswitch, freeswitch would receive the media and relay that to the endpoint.  It wouldn’t be reliable to do it directly to the endpoint without a re-invite, which wouldn’t be practical due to short duration, and needing to re-invite the media back to freeswitch.  It also would remove the ability to do things such as secure media, webrtc, or non rtp endpoints to work with mrcp.

On Mar 13, 2018, at 5:00 PM, Rob Capo <robcapo@gmail.com> wrote:

Hi,

I'm using an MRCPv2 server for TTS in a particular call environment. I have written the MRCPv2 client in a Go application that is talking to FreeSWITCH via ESL.

I've set this application to directly send the audio to remote_media_ip:remote_media_port. However, some VoIP clients seem to filter the UDP data because the c= line specifies the address of the FS server instead of the MRCP server. SDP supports adding a c= line in a media section if it's different than the c= line at the top of the SDP. I'm wondering if FreeSWITCH supports doing this via setting some variable or executing some command.

Thanks,
Rob