<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; "><div>Yikes. Good to know; thanks.</div><div><br></div><div>Here's the issue. Today I use media relay in limited cases, only when I have to have it for internal network reasons. Long story, but if I don't use it, QoS doesn't happen right. Anyway, it's about 1% of total traffic. No big deal.</div><div><br></div><div>I've had no issues with the dialog module over the last 2 years or so. (Counting blessings…) As such, I use the engage_media_proxy() command. It works — most of the time. Unless an upstream carrier lets some media "leak" through outside of the ports indicated in the SDP that hasn't arrived yet. The relay locks onto the wrong ports, and we get one-way or no-way audio.</div><div><br></div><div>This happens in one particular carrier's case when they route-advance on SS7 behind the scenes as a function of their Sonus GSX. They can't tell me why any media comes through at all on the first (disregarded) route. But, the SDPs they send do have the correct ports for the second (utilized) route. This SDP comes after the leaky media. Mediaproxy, being primarily a NAT traversal mechanism, listens more to what's really happening on the network rather than what's happening in the SDP.</div><div><br></div><div>And now the part I haven't researched fully. I'm hoping to be able to "reset" the media relay with an end_media_session() then use_media_relay() in an onreply_route to force a port re-detection in the relay when the 180 w/ SDP comes through (after the incorrect media dribble has completed), and ultimately the 200 OK. I may break more than I fix with this. Time will tell.</div><div><br></div><div>If this or something like it works, I'll be able to use the relays more. Which is something I'd like to do – mostly for accounting.</div><div><br></div><div><br></div><div>- Jeff</div><div><br></div><span id="OLK_SRC_BODY_SECTION"><div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span style="font-weight:bold">From: </span> Duane Larson <<a href="mailto:duane.larson@gmail.com">duane.larson@gmail.com</a>><br><span style="font-weight:bold">Reply-To: </span> OpenSIPS users mailling list <<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>><br><span style="font-weight:bold">Date: </span> Thu, 20 Jan 2011 14:54:13 -0500<br><span style="font-weight:bold">To: </span> OpenSIPS users mailling list <<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>><br><span style="font-weight:bold">Subject: </span> Re: [OpenSIPS-Users] multiple use_media_proxy() calls<br></div><div><br></div>accidentally called twice in a script that is...<br><br><div class="gmail_quote">On Thu, Jan 20, 2011 at 1:53 PM, Duane Larson <span dir="ltr"><<a href="mailto:duane.larson@gmail.com">duane.larson@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">I think I have accidentally called use_media_proxy() in scripts and it has spit out syslog errors. I think it caused one way audio issues for me.<br><br><div class="gmail_quote"><div><div></div><div class="h5">On Thu, Jan 20, 2011 at 1:31 PM, Jeff Pyle <span dir="ltr"><<a href="mailto:jpyle@fidelityvoice.com" target="_blank">jpyle@fidelityvoice.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div><div></div><div class="h5"><div style="word-wrap: break-word; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri,sans-serif;"><div>Hello,</div><div><br></div><div>What would happen if use_media_proxy() were called on a transaction (or dialog) where it had already been used? The documented result codes don't cover this case.</div><div><br></div><div>Would it simply start a new session with the dispatcher and close any previous ones, modifying the SDP again? Or error out perhaps?</div><div><br></div><div><br></div><div><br></div><div>Regards,</div><div>Jeff</div></div><br></div></div>_______________________________________________<br>
Users mailing list<br><a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br><a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br><br></blockquote></div><br><br clear="all"><br>-- <br>--<br>*--*--*--*--*--*<br>Duane<br>*--*--*--*--*--*<br><font color="#888888">--<br></font></blockquote></div><br><br clear="all"><br>-- <br>--<br>*--*--*--*--*--*<br>Duane<br>*--*--*--*--*--*<br>--<br></span></body></html>