You have to figure it somehow with adjusting the python code of media-dispatcher. We have developed special "/etc/init.d/kamailio grace" command, which waits for the moment, when there are no calls, so it can be restarted. It queries mediaproxy every second.

In future we will not use mediaproxy anymore - it is not supported in latest version either. rtpproxy gives us better performance results.

On Tue, Feb 12, 2013 at 2:44 PM, Eduardo Lejarreta lejarreta.e@sarenet.eswrote:

Good evening.

Launching "mediaproxy-dispatcher" and "mediaproxy-relay" on the foreground and with "DEBUG" we can see:

mediaproxy-dispatcher log: ------------------------------------------------------------------> Kamctl restart debug: Connection to OpenSIPS lost: Connection was closed cleanly. debug: Connection to OpenSIPS lost: Connection was closed cleanly. debug: Connection to OpenSIPS lost: Connection was closed cleanly. debug: Issuing "remove" command to relay at A.B.C.D debug: Got statistics: {xxxxxxxxxxxxxxxxxxx} debug: Connection to OpenSIPS lost: Connection was closed cleanly.

mediaproxy-relay log: ------------------------------------------------------------------> Kamctl restart debug: removing session xxxxxxxxxxxxxxxxxxx (Port 50000 Closed) (Port 50001 Closed) (Port 50002 Closed) (Port 50003 Closed)

So "mediaproxy-dispatcher" doesn't receive any command from Kamailio, he just detects " Connection was closed cleanly" and then issues a "remove" command to "mediaproxy-relay".

Does anybody know any way to avoid this?

Thanks and regards.

Eduardo Lejarreta.

---

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users