<div dir="ltr">Beautiful.<div class="gmail_extra"><br clear="all"><div><div dir="ltr"><div><br></div><div>- Jeff</div><div><br></div><div><br></div><div><br></div></div></div><div class="gmail_quote">On Mon, Mar 17, 2014 at 12:30 PM, Ovidiu Sas <span dir="ltr"><<a href="mailto:osas@voipembedded.com" target="_blank">osas@voipembedded.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Track the call with the dialog module in top hiding mode.<br>
It will handle CSeq changes.<br>
Sorry, I want it to send this a while ago but I got distracted.<br>
<span class="HOEnZb"><font color="#888888"><br>
-ovidiu<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
On Mon, Mar 17, 2014 at 11:52 AM, Jeff Pyle <<a href="mailto:jpyle@fidelityvoice.com">jpyle@fidelityvoice.com</a>> wrote:<br>
> Hi Bogdan,<br>
><br>
> Let's say Bob reinvites Alice to T.38 through my proxy. My proxy declines<br>
> the reinvite. That transaction has completed and Bob has incremented his<br>
> CSeq number. Now, if Bob sends another in-dialog request (such as a BYE),<br>
> the CSeq is one higher than Alice is expecting. That's not a problem?<br>
> Alice won't reply with a 400?<br>
><br>
><br>
> - Jeff<br>
><br>
><br>
><br>
> On Mon, Mar 17, 2014 at 11:24 AM, Bogdan-Andrei Iancu <<a href="mailto:bogdan@opensips.org">bogdan@opensips.org</a>><br>
> wrote:<br>
>><br>
>> Hi Jeff,<br>
>><br>
>> This is a false problem - you can simply decline the re-INVITE without<br>
>> breaking anything - each side has its own cseq number, and they are<br>
>> independently increased when a party is generating a new requests.<br>
>><br>
>> So, just decline it and that's it !<br>
>><br>
>> Regards,<br>
>><br>
>> Bogdan-Andrei Iancu<br>
>> OpenSIPS Founder and Developer<br>
>> <a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a><br>
>><br>
>> On 11.03.2014 19:42, Jeff Pyle wrote:<br>
>><br>
>> Hi Alexander,<br>
>><br>
>> To detect the "image" session in the SDP, you are thinking the same way<br>
>> that I am. The problem I see is how to actually reject the re-INVITE. If I<br>
>> were to do something like a sl_send_reply("488", "Not Acceptable Here"),<br>
>> that would work in the moment, but the CSeq values would be increased by one<br>
>> on side compared to the other. That sounds to me like a recipe for problems<br>
>> in future in-dialog transactions (like BYE).<br>
>><br>
>><br>
>><br>
>> - Jeff<br>
>><br>
>><br>
>><br>
>><br>
>> On Tue, Mar 11, 2014 at 12:58 PM, Alexander Mustafin<br>
>> <<a href="mailto:mustafin.aleksandr@gmail.com">mustafin.aleksandr@gmail.com</a>> wrote:<br>
>>><br>
>>> Hi, Jeff.<br>
>>><br>
>>> Maybe stream_exists(regexp) in sipmsgops module will be useful for you.<br>
>>><br>
>>> Best regards,<br>
>>> Alexander Mustafin<br>
>>> <a href="mailto:mustafin.aleksandr@gmail.com">mustafin.aleksandr@gmail.com</a><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>> 11 марта 2014 г., в 20:07, Jeff Pyle <<a href="mailto:jpyle@fidelityvoice.com">jpyle@fidelityvoice.com</a>><br>
>>> написал(а):<br>
>>><br>
>>> Hello,<br>
>>><br>
>>> Is there anything I can do at the proxy level to prevent a dialog from<br>
>>> reinviting to to T.38? I think I could detect the T.38 attributes easily<br>
>>> enough and respond with a 488, although I'm concerned the CSeq values would<br>
>>> be out of sequence for the next transaction that did make it through the<br>
>>> proxy to the far end. That could cause a problem, no?<br>
>>><br>
>>> Is this something that requires a B2BUA? Is it possible from within the<br>
>>> OpenSIPS B2B modules to do SDP inspection of any sort?<br>
>>><br>
>>><br>
>>> - Jeff<br>
>>><br>
>>> _______________________________________________<br>
>>> Users mailing list<br>
>>> <a href="mailto:Users@lists.opensips.org">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>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> Users mailing list<br>
>>> <a href="mailto:Users@lists.opensips.org">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>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> Users mailing list<br>
>> <a href="mailto:Users@lists.opensips.org">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>
>><br>
><br>
><br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@lists.opensips.org">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>
<br>
<br>
<br>
</div></div><div class="im HOEnZb">--<br>
VoIP Embedded, Inc.<br>
<a href="http://www.voipembedded.com" target="_blank">http://www.voipembedded.com</a><br>
<br>
</div><div class="HOEnZb"><div class="h5">_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">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>
</div></div></blockquote></div><br></div></div>