[OpenSIPS-Users] rtpengine xmlrpc integration with opensips. Teardown xmlrpc method

Carlos Oliva carlos.oliva at numintec.com
Sun Jan 29 17:05:33 EST 2017


Hi List!

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)

After the change I started to see some dialogs in state 3 that ends at
timeout (6 hours in my config)

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.

To try this I used the rtpengine flags --b2b-url=http://%%:8000/RPC2
--xmlrpc-format=1 to send Opensips the order to end the related dialog.

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:

POST /RPC2 HTTP/1.1..Host: XXX.XXX.XXX.XXX:8000..Accept: */*..Content-Type:
text/xml..User-Agent: Xmlrpc-c/1.33.14 Curl/7.38.0..Content-Length:
204....<?xml version="1.0" enco

ding="UTF-8"?>..<methodCall>..<methodName>teardown</methodName>..<params>..<param><value><string>
822048991-40759-5 at BJC.BGI.B.GE
</string></value></param>..</params>..</methodCall>

and the opensips response:

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>

Obviously OpenSips does not implement this "teardown" method.

My questions are:

Anybody has a good idea of how to deal with this?

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.


Thanks and Regards,

Carlos Oliva
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20170129/c5e99953/attachment.html>


More information about the Users mailing list