<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<tt>Hi Andreas,<br>
<br>
As I don't know of any mechanism to force a ringing in an ongoing
call by simply using SIP signaling, an alternative is to do inject
the ringing as media stream - you can use rtpproxy to play a
ringing to the A-side between the re-INVITE and its 200 OK. <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 Bootcamp 2017, Houston, US
<a class="moz-txt-link-freetext" href="http://opensips.org/training/OpenSIPS_Bootcamp_2017.html">http://opensips.org/training/OpenSIPS_Bootcamp_2017.html</a>
</pre>
<div class="moz-cite-prefix">On 07/04/2017 08:00 PM, Andreas
Bøckmann wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAN1RbiD403NPsgYNV8a68bVUgMQA8pj8bL1nhAWwo5OFeAWOrg@mail.gmail.com">
<div dir="ltr">Hello Bogdan
<div><br>
</div>
<div>It makes sense; to not send them out that is. The A-side
has sent 200 in reply to re-INVITE and is already "in a call".</div>
<div><br>
</div>
<div>Is it braking RFC3261 to send them to the client and is
there anything said in regards of how the client must/shall
act when receiving 180 after 200?</div>
<div><br>
</div>
<div>It would make sense to me to let the A-party know the
status of "call-progress" during the call (actually both
towards mediaserver and later B-party).<br>
</div>
<div><br>
</div>
<div>How would you suggest solving the case of actually playing
back 180 for the A-side after hearing the first media?<br>
</div>
<div><br>
</div>
<div>Using the prepaid scenario example it's waiting for BYE
from the mediaserver before re-INVITE and connecting the
actual B-party.</div>
<div>This allows me to force the mediafile to finish playing -
something I want it to (not inject media in 183 or similar
during ringing).</div>
<div><br>
</div>
<div><br>
</div>
<div>//Andreas<br>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Jul 4, 2017 at 6:43 PM,
Bogdan-Andrei Iancu <span dir="ltr"><<a
href="mailto:bogdan@opensips.org" target="_blank"
moz-do-not-send="true">bogdan@opensips.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> <tt>Hi Andreas,<br>
<br>
Yes, in bridging mode (when one of the party was already
connected to a previous entity), the provisional replies
are not sent anymore (during the re-INVITE) as make no
sense (for the already connected party).<br>
<br>
In your case, once the A side was connected (via 200 OK)
to the media server, an incoming 180 on the re-INVITE
(while bridging to the B side) will not induce a ringing
tone at all.<br>
<br>
Regards,<br>
</tt>
<pre class="m_-3921406946553429313moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a class="m_-3921406946553429313moz-txt-link-freetext" href="http://www.opensips-solutions.com" target="_blank" moz-do-not-send="true">http://www.opensips-solutions.<wbr>com</a>
OpenSIPS Bootcamp 2017, Houston, US
<a class="m_-3921406946553429313moz-txt-link-freetext" href="http://opensips.org/training/OpenSIPS_Bootcamp_2017.html" target="_blank" moz-do-not-send="true">http://opensips.org/training/<wbr>OpenSIPS_Bootcamp_2017.html</a>
</pre>
<div>
<div class="h5">
<div class="m_-3921406946553429313moz-cite-prefix">On
07/04/2017 02:07 PM, Andreas Bøckmann wrote:<br>
</div>
</div>
</div>
<blockquote type="cite">
<div>
<div class="h5">
<div dir="ltr">Hello
<div><br>
</div>
<div>I am playing around with B2B and running
OpenSIPS proxy and B2B on the same VM.</div>
<div>I am triggering prepaid scenario on initial
INVITEs for authenticated clients.</div>
<div><br>
</div>
<div><a
href="https://www.opensips.org/Documentation/Tutorials-B2BUA#toc13"
target="_blank" moz-do-not-send="true">https://www.opensips.org/<wbr>Documentation/Tutorials-B2BUA#<wbr>toc13</a><br>
</div>
<div><br>
</div>
<div>Now; everything seems to work OK except for
the fact that 180 is not relayed and no ringing
is ever heard on the A-side after listening to
Media and while connecting to B-side.</div>
<div><br>
</div>
<div>It seems to somehow be swallowed by B2B. It's
passed to B2B which seems to not handle 180
while in bridging scenario?</div>
<div><br>
</div>
<div>DBG:tm:local_reply: Passing provisional reply
180 to FIFO application<br>
</div>
<div>....</div>
<div>DBG:b2b_logic:b2b_logic_<wbr>notify_reply:
Received a reply [180] while in BRIDGING
scenario</div>
<div><br>
</div>
<div>Even though A-side is connected (after
listening to media) it would make sense to let
the A-side play ringing while trying to reach
the B-side.<br>
</div>
<div><br>
</div>
<div>Any ideas of how I can solve this?</div>
<div><br>
</div>
<div>The OpenSIPS log for handling 180 can be
found here: <a
class="m_-3921406946553429313moz-txt-link-freetext"
href="https://pastebin.com/fPVgLrCG"
target="_blank" moz-do-not-send="true">https://pastebin.com/<wbr>fPVgLrCG</a></div>
<div><br>
</div>
<div>Thanks a lot for your kind support!</div>
<div><br>
</div>
<div>//Andreas</div>
</div>
<br>
<fieldset
class="m_-3921406946553429313mimeAttachmentHeader"></fieldset>
<br>
</div>
</div>
<pre>______________________________<wbr>_________________
Users mailing list
<a class="m_-3921406946553429313moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org" target="_blank" moz-do-not-send="true">Users@lists.opensips.org</a>
<a class="m_-3921406946553429313moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank" moz-do-not-send="true">http://lists.opensips.org/cgi-<wbr>bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>