Ezequiel,
OK ,
maybe this time I can help you out. I had the same problem and downloaded the
2.3.3 fresh from python.org.
This
solved my problem.
I
run on RH9. Maybe in short what I did today to make it all happen. To install
mediaproxy I took the latest source code from ser from cvs. I installed it
this time from the source and did not add the
mediaproxy files from the development ser to my current rpm
install. The difference is that it
will put everything in /usr/local/ path. I changed my ser start
file in init.d to start the correct program.
The
mediaproxy.so is now
present and in the correct directory.
Than
I took the latest Python 2.3.3 configured maked and installed it.
Configured the ser.cfg according the examples and from than on
everything worked well penetrating
nat's.
I
really hate installing from rpm,s and
this caused all my previous problems.
Also
don't really understand well why the install from rpm's is using a different
path. Than you have to wait for a new rpm each time a cvs update is there. But
as I already told you I sure am no linux guru. I just follow the readme's and
the installs.
It
is working great now.
Tjapko.
I cannot run the mediaproxy.py program
from AG-MediaProxy software. The script cannot import optparse
module
Starting SERMediaProxy server:
mediaproxyTraceback (most recent call last):
File
"/etc/ser/mediaproxy/mediaproxy.py", line 21, in ?
from optparse import OptionParser
ImportError: No module named
optparse
Traceback (most recent call last):
File
"/etc/ser/mediaproxy/proxydispatcher.py", line 35, in
?
from optparse import OptionParser
ImportError: No
module named optparse
I have the following rpm packages
installed for python:
python-2.2.1-17
libxml2-python-2.4.23-1
rpm404-python-4.0.4-8x.27
python-tools-2.2.1-17
python-optik-1.3-2
rpm-python-4.1-1.06
mod_python-3.0.0-10
python-devel-2.2.1-17
Thanks
Ezequiel
Colombo