<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle24
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-CA" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">I have gone over the release notes for 2.4.2 to 2.4.6. I will upgrade and retest.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Louis<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> Users <users-bounces@lists.opensips.org>
<b>On Behalf Of </b>Ben Newlin<br>
<b>Sent:</b> July 31, 2019 10:34 AM<br>
<b>To:</b> OpenSIPS users mailling list <users@lists.opensips.org><br>
<b>Subject:</b> Re: [OpenSIPS-Users] Functional Difference B2B_Bridge between OpenSIP 1.8 and 2.4.2<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-bottom:3.0pt"><strong><span lang="EN-US" style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:red;border:solid gray 3.0pt;padding:0cm;background:lightgrey">WARNING: External Email: Exercise Caution</span></strong><span lang="EN-US" style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
<br>
</span><span lang="EN-US"><o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US">I’m not sure about the B2B behavior, but is there a reason you are not migrating to 2.4.6, which is the latest supported 2.4 release? It’s possible this problem has already been reported and fixed.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US" style="color:black">Ben Newlin </span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:12.0pt;color:black">From:
</span></b><span lang="EN-US" style="font-size:12.0pt;color:black">Users <<a href="mailto:users-bounces@lists.opensips.org">users-bounces@lists.opensips.org</a>> on behalf of Louis Rochon <<a href="mailto:Louis.Rochon@comtechtel.com">Louis.Rochon@comtechtel.com</a>><br>
<b>Reply-To: </b>OpenSIPS users mailling list <<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>><br>
<b>Date: </b>Wednesday, July 31, 2019 at 10:29 AM<br>
<b>To: </b>"<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>" <<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>><br>
<b>Subject: </b>[OpenSIPS-Users] Functional Difference B2B_Bridge between OpenSIP 1.8 and 2.4.2<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<p class="MsoPlainText"><span lang="EN-US">Trying to upgrade my platform to OpenSIPS 2.4.2 (yea, about time, I know).<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">We use this to move established calls from one server to another:<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">/usr/local/sbin/opensipsctl fifo b2b_bridge <tupleID>
<a href="sip:555@1.2.3.4">sip:555@1.2.3.4</a> 0<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">This works fine with OpenSIPS 1.8. The above causes this:<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">1. Invite (reinvite) to caller with no sdp.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">2. RX of 200 OK with SDP from caller<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">3. Invite with SDP to 1.2.3.4<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">4. RX of 200 OK with SDP from 1.2.3.4<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">5. OpenSIPS send ACK WITH SDP to caller.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">Call moved. All good.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">With OpenSIPS 2.4.2:<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">1. Invite (reinvite) to caller with no sdp.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">2. RX of 200 OK with SDP from caller<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">3. Invite with SDP to 1.2.3.4<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">4. RX of 200 OK with SDP from 1.2.3.4<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">5. OpenSIPS send ACK WITHOUT SDP to caller.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">With 2.4.2, I get one way audio, very likely because of the lack of SDP in the ACK in point 5.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">My research does not lead me anywhere on how why this behaviour changed between 1.8 and 2.4.2. I can't find any flags to set to get b2b_bridge command to have to old behaviour.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">Help!<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">regards,<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">Louis<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">NOTICE TO RECIPIENT: This email, including attachments, may contain information which is confidential, proprietary, attorney-client privileged and / or controlled under U.S. export laws and regulations and may be restricted
from disclosure by applicable State and Federal law. Nothing in this email shall create any legal binding agreement between the parties unless expressly stated herein and provided by an authorized representative of Comtech Telecommunications Corp. or its subsidiaries.
If you are not the intended recipient of this message, be advised that any dissemination, distribution, or use of the contents of this message is strictly prohibited. If you received this message in error, please notify us immediately by return email and permanently
delete all copies of the original email and any attached documentation from any computer or other media.
<o:p></o:p></span></p>
</div>
</div>
</body>
</html>