<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">If we were doing that, that was a bug on our part. Nothing told us to take the call off hold.<div class=""><br class=""></div><div class=""><div class=""><div><blockquote type="cite" class=""><div class="">On Nov 21, 2016, at 3:33 PM, Jarad Morgan <<a href="mailto:jaradmorgan@gmail.com" class="">jaradmorgan@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class=""><div class="">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. </div><div class=""><br class=""></div><div class="">Avaya INVITE to FS no SDP</div><div class="">FS 100 trying no SDP to Avaya </div><div class="">FS 200 OK w SDP to Avaya <span class="Apple-tab-span" style="white-space:pre"> </span><-- no sendonly media attribute specified here. </div><div class="">Avaya ACK w SDP to FS<span class="Apple-tab-span" style="white-space:pre"> </span><-- no media attribute so default sendrecv </div><div class=""><br class=""></div><div class="">Call is taken off hold.. </div><div class=""><br class=""></div><div class="">Older version and 1.6 are running the same configs. </div><div class=""><br class=""></div><div class="">I can bug the Avaya guys to fix their stuff but was just hoping to fix in FS if it was easily possible. </div></div><div class=""><br class=""></div><div class=""><br class=""></div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="">On Mon, Nov 21, 2016 at 3:06 PM Michael Jerris <<a href="mailto:mike@jerris.com" class="">mike@jerris.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg">On Nov 21, 2016, at 2:59 PM, Jarad Morgan <<a href="mailto:jaradmorgan@gmail.com" class="gmail_msg" target="_blank">jaradmorgan@gmail.com</a>> wrote:</div><br class="gmail_msg m_-4734320939673912676Apple-interchange-newline"><div class="gmail_msg"><div dir="ltr" class="gmail_msg"><div class="gmail_msg">So long story short here is the issue were running into. Sorry for the crappy messaging diagram. </div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">//when going on hold. </div><div class="gmail_msg">Avaya INVITE to FS no SDP</div><div class="gmail_msg">FS 100 trying no SDP to Avaya </div><div class="gmail_msg">FS 200 OK w SDP to Avaya</div><div class="gmail_msg">Avaya ACK w SDP(a=sendonly) to FS</div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">//were now on hold. </div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">//going off hold where we run into the one way audio. </div><div class="gmail_msg">Avaya INVITE to FS no SDP</div><div class="gmail_msg">FS 100 trying no SDP to Avaya </div><div class="gmail_msg">FS 200 OK w SDP (a=sendonly) to Avaya</div><div class="gmail_msg">Avaya ACK w SDP (a=recvonly) to FS</div></div></div></blockquote><div class="gmail_msg"><br class="gmail_msg"></div></div></div><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg">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.</div><div class="gmail_msg"></div></div><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><br class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div dir="ltr" class="gmail_msg"><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">We get a recvonly from Avaya so were in listen mode instead of sendrecv. </div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">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? </div></div></div></blockquote><div class="gmail_msg"><br class="gmail_msg"></div></div></div><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg">Not sure what you mean. We didn’t “see” it?</div></div><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><br class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div dir="ltr" class="gmail_msg"><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">Thanks!! </div></div><br class="gmail_msg"><div class="gmail_quote gmail_msg"><div dir="ltr" class="gmail_msg">On Mon, Nov 21, 2016 at 2:38 PM Michael Jerris <<a href="mailto:mike@jerris.com" class="gmail_msg" target="_blank">mike@jerris.com</a>> wrote:<br class="gmail_msg"></div><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">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?<br class="gmail_msg">
<br class="gmail_msg">
> On Nov 21, 2016, at 2:19 PM, Jarad Morgan <<a href="mailto:jaradmorgan@gmail.com" class="gmail_msg" target="_blank">jaradmorgan@gmail.com</a>> wrote:<br class="gmail_msg">
><br class="gmail_msg">
> Hello, we are running into some issues with one way audio coming off hold with messaging between Avaya's. Running FS 1.6.10.<br class="gmail_msg">
><br class="gmail_msg">
> 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?<br class="gmail_msg">
><br class="gmail_msg">
> Thanks!!<br class="gmail_msg"></blockquote></div></div></blockquote></div></div></blockquote></div></div></blockquote></div><br class=""></div></div></body></html>