[OpenSIPS-Users] opensips 1.6.x and media dispatcher
rrevels at bandwidth.com
Fri Dec 31 14:38:09 CET 2010
I backed off opensips to the same revision I'm using in Production, upgraded opensips to latest 7621 revision, installed a new sandbox Python, copied over the sandbox directory tree from a Production server, and recompiled everything from the ground up numerous times. Not all at once of course. These were different things I tried. : > None of this helped. I don't know what the heck this is but I'm now sure it's something about this particular OS install rather than any SIP application. And that it's a problem for next year.
Thank you for the response. I remembered seeing a new release of Media Proxy within the last couple of months with a comment that a bug was fixed that could cause the software to crash under heavy load. My first thought when I saw this was Whoops! must have been an update to the opensips module too. : >
I think that revision was between the 1.6.3 release tag and the 1.6.4 release by the way.
On Dec 30, 2010, at 3:05 AM, Saúl Ibarra Corretgé wrote:
> On 28/12/10 7:49 PM, Richard Revels wrote:
>> Are there any known issues with media dispatcher 2.4.2 communicating with opensips revision 7377? I am getting errors back to the call to engage_media_proxy on two attempts from within my script. This doesn't seem to occur immediately on start-up most times but does get to the point of 100% failure eventually.
>> Turning up log levels on both opensips and the media dispatcher does not seem to yield any indication of why the function call fails. Connecting to the media dispatcher management port and asking for summary or sessions works fine.
> Which version is revision 7337 close to? There where some changes in the communication protocol when ICE support was added, but that was between 1.6.1 and 1.6.2 releases IIRC.
> Saúl Ibarra Corretgé
> AG Projects
> Users mailing list
> Users at lists.opensips.org
More information about the Users