<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<tt>Hi Carlos,<br>
<br>
OpenSIPS does not have any "teardown" MI command - this looks like
a private extension of the rtpengine. Unfortunately, the rtpengine
team is not so communicative (at least not with our team), so we
were not aware of this extension.<br>
<br>
Of course, we can do the one-way effort to align OpenSIPS to the
rtpengine (again). Still, if we do this, it will be for OpenSIPS
2.3 - new extensions are not backported to the existing stable
releases.<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></pre>
<div class="moz-cite-prefix">On 01/30/2017 12:05 AM, Carlos Oliva
wrote:<br>
</div>
<blockquote
cite="mid:CAPsm+217Gp0OetZB1yzrvLp2_6bD8z8AXfDGfFAypxsjyw_JHA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>Hi List!<br>
<br>
</div>
I'm using Opensips 1.11 and doing some tests to
change my mediaproxy rtprelays to
ngcp-rtpengine. My reasons to try this change
are efficiency and that the mediaproxy project
seems to be a little abandoned by AGProjects
(not really abandoned but has no new features in
years)<br>
<br>
</div>
After the change I started to see some dialogs in
state 3 that ends at timeout (6 hours in my
config)<br>
<br>
</div>
I tried to use the RTPTimeout function in rtpengine
(in mediaproxy it works very well) to try to end
the dialogs which don't have RTP.<br>
<br>
</div>
To try this I used the rtpengine flags
--b2b-url=<a class="moz-txt-link-freetext" href="http://%%:8000/RPC2">http://%%:8000/RPC2</a> --xmlrpc-format=1 to
send Opensips the order to end the related dialog.<br>
<br>
</div>
It doesn't work. Doing some ngrep at xmlrpc interface
seems that rtpengine send some commands to opensips RPC
interface that Opensips does not understand. The command
is: "teardown" and the callid, here is an example:<br>
<br>
POST /RPC2 HTTP/1.1..Host: XXX.XXX.XXX.XXX:8000..Accept:
*/*..Content-Type: text/xml..User-Agent:
Xmlrpc-c/1.33.14 Curl/<a moz-do-not-send="true"
href="http://7.38.0.">7.38.0.</a>.Content-Length:
204....<?xml version="1.0" enco<br>
ding="UTF-8"?>..<methodCall>..<methodName>teardown</methodName>..<params>..<param><value><string><a
moz-do-not-send="true"
href="mailto:822048991-40759-5@BJC.BGI.B.GE"><a class="moz-txt-link-abbreviated" href="mailto:822048991-40759-5@BJC.BGI.B.GE">822048991-40759-5@BJC.BGI.B.GE</a></a></string></value></param>..</params>..</methodCall><br>
<br>
</div>
and the opensips response:<br>
<br>
HTTP/1.1 200 OK..Connection: Keep-Alive..Content-Length:
48..Content-Type: text/xml; charset=utf-8..Date: Sun, 29
Jan 2017 20:31:36 GMT....<html><body>Internal
server error!</body></html><br>
<br>
</div>
Obviously OpenSips does not implement this "teardown"
method.<br>
<br>
</div>
My questions are:<br>
<br>
</div>
<div>Anybody has a good idea of how to deal with this? <br>
</div>
<div><br>
</div>
<div>
<div>Devels: Do you think is a good idea to open a feature
request in github about this? I'll try to backport to 1.11
later.if you accept the request.<br>
</div>
<div>
<div>
<div><br>
<br clear="all">
<div>
<div>
<div>
<div>
<div>
<div>
<div>Thanks and Regards,<br>
<br>
</div>
<div>Carlos Oliva<br>
</div>
<div><br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</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>