[OpenSIPS-Users] MediaProxy as bridge between Private and Public Interfaces

[Saúl Ibarra Corretgé]

Hi,

El 03/02/10 6:38, Daniel Worrad escribió:
> Hi All,
>
> I have MediaProxy working in a multi-homed setup where it is acting as a
> relay between an interface on a public IP and one on a private IP (We
> connect to our SIP provider over a private network via the private
> interface using static routes in the route table, and a SNAT out the
> private interface)
>
> The system is functioning and calls are being relayed between public and
> private interfaces, however with every call, I am receiving the
> following in the logs (which is a bit unnerving):
>
> Feb 3 15:19:32 SIPProxy1 media-relay[6806]: Traceback (most recent call
> last):
>
> Feb 3 15:19:32 SIPProxy1 media-relay[6806]: File
> "/usr/local/lib/python2.5/site-packages/twisted/internet/udp.py", line
> 126, in doRead
>
> Feb 3 15:19:32 SIPProxy1 media-relay[6806]:
> self.protocol.datagramReceived(data, addr)
>
> Feb 3 15:19:32 SIPProxy1 media-relay[6806]: File
> "/usr/local/lib/python2.5/site-packages/mediaproxy/mediacontrol.py",
> line 127, in datagramReceived
>
> Feb 3 15:19:32 SIPProxy1 media-relay[6806]: self.cb_func(host, port, data)
>
> Feb 3 15:19:32 SIPProxy1 media-relay[6806]: File
> "/usr/local/lib/python2.5/site-packages/mediaproxy/mediacontrol.py",
> line 203, in got_data
>
> Feb 3 15:19:32 SIPProxy1 media-relay[6806]:
> self.substream.check_create_conntrack()
>
> Feb 3 15:19:32 SIPProxy1 media-relay[6806]: File
> "/usr/local/lib/python2.5/site-packages/mediaproxy/mediacontrol.py",
> line 253, in check_create_conntrack
>
> Feb 3 15:19:32 SIPProxy1 media-relay[6806]: self.forwarding_rule =
> _conntrack.ForwardingRule(self.caller.remote, self.caller.local,
> self.callee.remote, self.callee.local, self.stream.session.mark)
>
> Feb 3 15:19:32 SIPProxy1 media-relay[6806]: Error: No such file or directory
>
> I have tried strace to determine what file may be missing or lacking
> permissions, however there are references to hundreds of files and it is
> proving difficult to track down.
>
> Has anyone seen this before, or could suggest some other way of
> troubleshooting the issue?
>

The reason you are finding it difficult to track down the issue is 
because it's produced by the _conntrack module, which is a Python C 
extension.

At the beginning of your mail you say it's working for you, but do the 
RTP timeouts also work for you?

Please, give me some more information about your system (distro, kernel 
version, MediaProxy version)so we can see what could be happening.


Regards,

-- 
Saúl Ibarra Corretgé
AG Projects