[OpenSIPS-Users] Mediaproxy gives "ASN1 parser: Element was not found"
Jeff Pyle
jpyle at fidelityvoice.com
Tue Oct 28 21:49:13 CET 2008
Hello,
I upgrading my OpenSER 1.3.2 + Mediaproxy 1.9.1 configuration to
OpenSIPs 1.4 + Mediaproxy 2.1.0. When I start either media-dispatcher
or media-relay with --no-fork, I get the following errors:
# media-relay --no-fork
Starting MediaProxy Relay 2.1.0
Set resource limit for maximum open file descriptors to 1384
failed to create MediaProxy Relay: ASN1 parser: Element was not found.
Traceback (most recent call last):
--- <exception caught here> ---
File "/usr/bin/media-relay", line 54, in <module>
relay = MediaRelay()
File "/usr/lib/python2.5/site-packages/mediaproxy/relay.py", line
291, in __init__
self.cred = X509Credentials(cert_name='relay')
File "/usr/lib/python2.5/site-packages/mediaproxy/tls.py", line
132, in __init__
twisted.X509Credentials.__init__(self, self.X509cert,
self.X509key, [self.X509ca], [self.X509crl])
File "/usr/lib/python2.5/site-packages/mediaproxy/tls.py", line 99,
in __get__
return descriptor.get()
File "/usr/lib/python2.5/site-packages/mediaproxy/tls.py", line 82,
in get
self.object = self.klass(f.read())
File "<string>", line 1, in __init__
File "/usr/lib/python2.5/site-packages/gnutls/validators.py", line
273, in check_args
return func(*func_args)
File "/usr/lib/python2.5/site-packages/gnutls/crypto.py", line 82,
in __init__
gnutls_x509_crt_init(byref(self._c_object))
File "/usr/lib/python2.5/site-packages/gnutls/library/errors.py",
line 64, in _check_status
raise GNUTLSError(ErrorMessage(retcode))
gnutls.errors.GNUTLSError: ASN1 parser: Element was not found.
The dispatcher's errors are very similar.
This on a Fedora 7 box. Its RPM version of gnutls is old, at 1.6.3.
I see the Mediaproxy docs state that 2.4.1 is required. I installed
2.4.2 from source into /usr/local/lib.
I attempted to reinstall python-gnutls, but I'm quickly discovering
that I have no idea how to manage python whatsoever.
I'm not sure if I still have a version problem or what here. Any
suggestions would be greatly appreciated.
Thanks,
Jeff
More information about the Users
mailing list