If we were doing that, that was a bug on our part.  Nothing told us to take the call off hold.

On Nov 21, 2016, at 3:33 PM, Jarad Morgan <jaradmorgan@gmail.com> wrote:

Sorry what i meant was on the older FS version the sendonly attribute was not present in the 200 OK message back to Avaya. For example SIP flow on older version. 

Avaya INVITE to FS no SDP

FS 100 trying no SDP to Avaya 

FS 200 OK w SDP to Avaya <-- no sendonly media attribute specified here. 

Avaya ACK w SDP to FS <-- no media attribute so default sendrecv  

Call is taken off hold.. 

Older version and 1.6 are running the same configs. 

I can bug the Avaya guys to fix their stuff but was just hoping to fix in FS if it was easily possible. 

On Mon, Nov 21, 2016 at 3:06 PM Michael Jerris <mike@jerris.com> wrote:

On Nov 21, 2016, at 2:59 PM, Jarad Morgan <jaradmorgan@gmail.com> wrote:

So long story short here is the issue were running into. Sorry for the crappy messaging diagram. 

//when going on hold. 

Avaya INVITE to FS no SDP

FS 100 trying no SDP to Avaya 

FS 200 OK w SDP to Avaya

Avaya ACK w SDP(a=sendonly) to FS

//were now on hold. 

//going off hold where we run into the one way audio. 

Avaya INVITE to FS no SDP

FS 100 trying no SDP to Avaya 

FS 200 OK w SDP (a=sendonly) to Avaya

Avaya ACK w SDP (a=recvonly) to FS

This is not a valid way to go off hold.  The avaya would need to somehow indicate that it is changing the stream to sendrecv, they don’t in what you describe here.

We get a recvonly from Avaya so were in listen mode instead of sendrecv. 

This is a new issue since we upgraded from and older version to 1.6. The previous version of FS we didnt see the a=sendonly in the 200 OK when going off hold so i thought that may be configurable in the newer version to leave those media attributes out of the SDP? 

Not sure what you mean.  We didn’t “see” it?

Thanks!! 

On Mon, Nov 21, 2016 at 2:38 PM Michael Jerris <mike@jerris.com> wrote:

if there is an sdp and it does not specify sendonly, recvonly, or inactive, it means that stream is sendrecv.  This is normal operation of sdp, many things won’t actually include the sendrecv as size of sdp is a bigger and bigger issue these days.  What do you mean about a config setting to leave it out?

> On Nov 21, 2016, at 2:19 PM, Jarad Morgan <jaradmorgan@gmail.com> wrote:
>
> Hello, we are running into some issues with one way audio coming off hold with messaging between Avaya's. Running FS 1.6.10.
>
> Is there a FS config setting to leave out the media type attribute (sendonly,sendrecv) in the 200 OK sent by FS when doing late media negotiation between a Avaya device?
>
> Thanks!!

_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://confluence.freeswitch.org
http://www.cluecon.com

FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org