<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<tt>Hi Andreas,<br>
<br>
First of all you need to be sure about the attempted signaling
from opensips side - do you have a SIP capture from the b2b
machine, showing all the legs ? it is interesting to see the
signaling. <br>
<br>
Best regards,<br>
</tt>
<pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a>
OpenSIPS Summit May 2017 Amsterdam
<a class="moz-txt-link-freetext" href="http://www.opensips.org/events/Summit-2017Amsterdam.html">http://www.opensips.org/events/Summit-2017Amsterdam.html</a>
</pre>
<div class="moz-cite-prefix">On 04/07/2017 07:06 PM, Andreas
Bøckmann wrote:<br>
</div>
<blockquote
cite="mid:CAN1RbiC1coTN+FCifSV5MjDsX=_t-xT1eGgoW-HMY0iCnzB=Vg@mail.gmail.com"
type="cite">
<div dir="ltr">Hello
<div><br>
</div>
<div>I am sending a BYE to some carrier which does not reply
back anything and I am trying to understand what I might be
doing wrong. They are running some Cisco gateway so I expect
them to deal with signaling better than what I do..</div>
<div><br>
</div>
<div>Basically the scenario is identical to <a
moz-do-not-send="true"
href="https://www.opensips.org/Documentation/Tutorials-B2BUA#toc14"><a class="moz-txt-link-freetext" href="https://www.opensips.org/Documentation/Tutorials-B2BUA#toc14">https://www.opensips.org/Documentation/Tutorials-B2BUA#toc14</a></a>
- with the exception I have a proxy in between B2B and PSTN-GW
for routing purposes.</div>
<div><br>
</div>
<div>LegA (to "caller")</div>
<div>LegB (to "mediaserver")</div>
<div>LegC (to "callee")</div>
<div><br>
</div>
<div>After completing playing the media; the call is re-invited
to A and a new call is setup towards C.</div>
<div><br>
</div>
<div>* If I reject the initial call (before media - session 1)
on Cs terminal; everything is OK and A is disconnected.</div>
<div><br>
</div>
<div>* If I hangup on A during "session 2", C is not
disconnected<br>
</div>
<div><br>
</div>
<div>* If I hangup on C during "session 2", A is not
disconnected</div>
<div><br>
</div>
<div>* If I let the call time out during "session 2" (I have a
timer set for max duration) C is disconnected and A is not.</div>
<div><br>
</div>
<div>What causes my head to spin is that I have 3 carriers; two
of them accept the signaling flow "as is" and terminates the
calls correctly in all scenarios. </div>
<div><br>
</div>
<div>The one carrier I want to use has the behavior seen above.</div>
<div><br>
</div>
<div>Does anybody have any suggestion on what I might do on my
side to terminate these calls properly or any suggestions as
to what I am doing wrong?</div>
<div><br>
</div>
<div>Thank!</div>
<div><br>
</div>
<div>Kind regards,</div>
<div><br>
</div>
<div>Andy</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</body>
</html>