<div dir="ltr">Hi Bogdan,<div><br></div><div>thanks for the reply.</div><div><br></div><div>The prepaid example will play the pre-call announcement in a 200 OK. The thing is, after the 200OK you cannot have any other early media such as a personalized ring back tone or any other network announcement.</div><div>In fact, I am trying to implement a B2B forking UA and multiple early media is in my scope. Can I do that with opensips? Can the prepaid example by used to do that?</div><div><br></div><div>Regards</div><div>Ano</div><div><br><br><div class="gmail_quote"><div dir="ltr">On Fri, Oct 5, 2018 at 6:58 PM Bogdan-Andrei Iancu <<a href="mailto:bogdan@opensips.org">bogdan@opensips.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF"><tt>Hi Ano,<br><br>But the prepaid example already has an pre-call announcement - so what are you trying to change ?<br><br>Regards,<br></tt><pre class="gmail-m_212344995235594624moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a class="gmail-m_212344995235594624moz-txt-link-freetext" href="http://www.opensips-solutions.com/" target="_blank">http://www.opensips-solutions.com</a>
OpenSIPS Bootcamp 2018
<a class="gmail-m_212344995235594624moz-txt-link-freetext" href="http://opensips.org/training/OpenSIPS_Bootcamp_2018/" target="_blank">http://opensips.org/training/OpenSIPS_Bootcamp_2018/</a>
</pre><div class="gmail-m_212344995235594624moz-cite-prefix">On 10/05/2018 09:32 AM, Ano Nemo wrote:<br></div><blockquote type="cite"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div class="gmail-m_212344995235594624m_1852765546755814507gmail-gE gmail-m_212344995235594624m_1852765546755814507gmail-iv gmail-m_212344995235594624m_1852765546755814507gmail-gt" style="padding:20px 0px 0px;font-size:12.8px;font-family:Roboto,RobotoDraft,Helvetica,Arial,sans-serif">Hi all,</div><div class="gmail-m_212344995235594624m_1852765546755814507gmail-" style="font-family:Roboto,RobotoDraft,Helvetica,Arial,sans-serif"><div id="gmail-m_212344995235594624m_1852765546755814507gmail-:t3" class="gmail-m_212344995235594624m_1852765546755814507gmail-ii gmail-m_212344995235594624m_1852765546755814507gmail-gt gmail-m_212344995235594624m_1852765546755814507gmail-adO" style="font-size:12.8px;direction:ltr;margin:8px 0px 0px;padding:0px"><div id="gmail-m_212344995235594624m_1852765546755814507gmail-:t4" class="gmail-m_212344995235594624m_1852765546755814507gmail-a3s gmail-m_212344995235594624m_1852765546755814507gmail-aXjCH" style="overflow:hidden;font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:small;line-height:1.5;font-family:Arial,Helvetica,sans-serif"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><br></div><div>I am trying to implement pre-alerting announcement by modifying the prepaid B2B UA scenario.</div><div><br></div><div>If I am not mistaken the default prepaid B2B UA scenario looks as below:</div><div><div><br></div><div><font face="monospace, monospace"><br></font></div><div><font face="monospace, monospace"> A Party OpenSIPS MS B Party</font></div><div><font face="monospace, monospace">1. ----Dialog1:INV+SDP(offer)---></font></div><div><font face="monospace, monospace">2. ----Dialog2:INV+SDP(offer)----></font></div><div><font face="monospace, monospace">3. <----Dialog2:200+SDP(answer)--- </font></div><div><font face="monospace, monospace">------------------------------- Bridging -------------------------------------</font></div><div><font face="monospace, monospace">4. <----Dialog1:200+SDP(answer)--- </font></div><div><font face="monospace, monospace">5. ----Dialog1:ACK---------------></font></div><div><font face="monospace, monospace">6. ----Dialog1:ACK--------------> </font></div><div><font face="monospace, monospace">------------------------------- Announcement ---------------------------------</font></div><div><font face="monospace, monospace">7. <----Dialog2:BYE--------------- </font></div><div><font face="monospace, monospace">8. -------------------Dialog3:INV+SDP(offer)--></font></div><div><font face="monospace, monospace">9. <------------------Dialog3:180 -------------</font></div><div><font face="monospace, monospace">10 <------------------Dialog3:200 -------------</font></div><div><font face="monospace, monospace">11 -------------------ACK--------------------> </font></div><div><font face="monospace, monospace">------------------------------- Bridging -------------------------------------</font></div></div><div><br></div><div><br></div><div>I am having problems with this behavior because in the prepaid scenario, the opensips B2B UA will create a leg to B party only after it has received a BYE from the MS. This means that there has to be a 200 OK before that which needs to reach the A party and establish media.</div><div>The behavior I am aiming for is for the MS to deliver an provisional response with SDP (183) to A Party and play the announcement. However, after an 183, I cannot terminate the call from the MS with a BYE and also, I do not want to generate a 200 OK. But I could generate an error on the MS (say an 4xx error).</div><div>So, the question is, can the scenario xml rules be formulated to make the B2B UA act on negative response? Is the below possible?</div><div><br></div><div><pre style="white-space:pre-wrap;font-size:0.9em;font-family:"Lucida Console","Andale Mono","Courier New",Courier;margin-top:0px;margin-bottom:0px"><span style="color:rgb(102,102,0)"><</span><span style="color:rgb(0,0,136)">rules</span><span style="color:rgb(102,102,0)">></span>
</pre><pre style="white-space:pre-wrap;font-size:0.9em;font-family:"Lucida Console","Andale Mono","Courier New",Courier;margin-top:0px;margin-bottom:0px"> <span style="color:rgb(102,102,0)"><</span><span style="color:rgb(0,0,136)">reply</span><span style="color:rgb(102,102,0)">></span>
<span style="color:rgb(102,102,0)"><</span><font color="#000088">negative</font><span style="color:rgb(102,102,0)">> or</span> <<font color="#000088">410</font><span style="font-size:0.9em;color:rgb(102,102,0)">></span><span style="color:rgb(102,102,0)">
</span>
<span style="color:rgb(102,102,0)"><</span><span style="color:rgb(0,0,136)">rule</span> <span style="color:rgb(102,0,102)">id</span><span style="color:rgb(102,102,0)">=</span> ”<span style="color:rgb(102,0,102)">1</span>”<span style="color:rgb(102,102,0)">></span>
...
<span style="color:rgb(102,102,0)"></</span><span style="color:rgb(0,0,136)">rule</span><span style="color:rgb(102,102,0)">></span>
<pre style="white-space:pre-wrap;font-size:0.9em;font-family:"Lucida Console","Andale Mono","Courier New",Courier;margin-top:0px;margin-bottom:0px"> <span style="color:rgb(102,102,0)"></</span><font color="#000088">negative</font><span style="color:rgb(102,102,0)">> or</span> </<font color="#000088">410</font><span style="font-size:0.9em;color:rgb(102,102,0)">></span></pre> <span style="color:rgb(102,102,0)"></</span><span style="color:rgb(0,0,136)">reply</span><span style="color:rgb(102,102,0)">></span>
<span style="color:rgb(102,102,0)"></</span><span style="color:rgb(0,0,136)">rules</span><span style="color:rgb(102,102,0)">></span></pre></div><div><br></div><div>If not, is there any other way to do this?</div><div><br></div><div>Regards,</div><div>Ano</div></div></div></div></div></div></div></div></div></div><br><fieldset class="gmail-m_212344995235594624mimeAttachmentHeader"></fieldset><br><pre>_______________________________________________
Users mailing list
<a class="gmail-m_212344995235594624moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>
<a class="gmail-m_212344995235594624moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre></blockquote></div></blockquote></div><br class="gmail-Apple-interchange-newline"></div></div>