[OpenSIPS-Users] AG Project - Media Proxy
dan at ag-projects.com
Thu Aug 2 11:06:58 EDT 2018
The log suggests that the mediaproxy dispatcher is not replying in time, yet it is not dead/frozen.
The timeout is 500ms and can be set through the mediaproxy_timeout module parameter (see the mediaproxy module README for more info).
I suggest you increase the timeout until you don't see the problem again, but keep in mind that whatever value you use, that is how long the opensips worker process can be blocked waiting for a reply, during which time it cannot do anything else (communication with the dispatcher is not asynchronous).
Better would be to identify what causes the dispatcher to lag like that (maybe over time you got an increasing number of call setups which resulted in a higher load that makes the dispatcher take more than 500ms to reply sometimes). In that case it would be better to consider some horizontal scaling and use some clustering solution to distribute the load.
P.S. subsequent calls work, because opensips reconnects automatically to the dispatcher as needed.
On 24 Jul 2018, at 14:56, Alex Tatham wrote:
> Hello everyone,
> We have been using AG Projects Media Proxy for several years. Recently we’ve been experiencing intermittent problems with calls not being initiated and we’ve traced this to the media proxy component.
> The frequency of the issue is around 1 in 2000 calls.
> The following error is logged by the SIP proxy “ERROR: mediaproxy [mediaproxy.c:1528]: send_command(): did timeout waiting for an answer”.
> The following error corresponds in the dispatcher component of the Media Proxy software “Connection to OpenSIPS lost: Connection was closed cleanly.”.
> The problem is temporary and subsequent calls are successful without any intervention.
> I can’t find any information on the WWW about either of these messages.
> The mediaproxy components are running the latest debian packages as is the corresponding module. I do have some older servers running a much older version of mediaproxy that don’t have this fault but I’ve got to update because of a bug with the relay component on that build.
> Does anyone have any suggestions.
> Thanks, Alex
> Alex Tatham
> Technical Director
> T: 01233 220 943
> E: alex.tatham at dmcplc.co.uk
> W: www.dmctechnologies.co.uk
> DMC Technologies formerly HP Technology
> Unit 5, Invicta Business Centre
> Orbital Park
> Kent |
> TN24 0HB
> DMC Technologies is a trading name of Hobbs Parker 2000 Limited
> Registered Office: Romney House, Orbital Park, Monument Way, Ashford TN24 0HB
> Registered in England No.04027755
> Users mailing list
> Users at lists.opensips.org
More information about the Users