[OpenSIPS-Users] when engage_media_proxy() doesn't
Jeff Pyle
jpyle at fidelityvoice.com
Wed Mar 16 02:20:49 CET 2011
Hello,
Opensips 1.6.4-1-notls with Mediaproxy 2.4.4. Both installed from the
Debian packages onto two very similar machines. All Python packages are
at exactly the same versions on both. Both machines are Debian Lenny with
some packages pulled from testing/squeeze to satisfy things like
python-application, etc, for Mediaproxy.
On one machine, everything is fine. "Everything" means calling
engage_media_proxy() and letting the magic happen. On the other machine,
everything is not fine. engage_media_proxy() just doesn't seem to do
anything. engage_media_proxy() returns 1 in both cases.
There are two relays, both connected to both dispatchers on port 25060.
Verified with netstat. I see no network chatter between the
non-functional machine's dispatcher and either relay during call setup
time; I do on the functional machine.
With Opensips at debug=6 on either machine, engage_media_proxy() doesn't
show anything. Verified with xlogs immediately before and immediately
after the engage call. So that's not helpful for diagnosis.
With log_level = DEBUG in /etc/mediaproxy/config.ini, we have a slight
different between the two machines. I see two "update" lines on the
working system at the time of a call where I see nothing on the
non-working system. These probably correlate to the network chatter I see
on the functional machine.
The non-functional system does not complain in the Opensips logs or the
Media Dispatcher logs of not being able to talk to the other side. Both
machines' Media Dispatcher mention a cleanly closed connection to Opensips
if I shut down Opensips. This leads me to believe that even the
non-functioning still has an opensips-to-dispatcher connection.
Both Opensips configs have a completely default mediaproxy module
configuration. No module parameters defined.
I'm not against trying use_media_proxy() and end_media_session(). My
concern here is the lack of documentation on how to implement it in
loose_route to catch reinvites. Does one need to end_media_session before
use_media_proxy to modify the SDP in the reinvite? Or just call
use_media_proxy? Any special considerations in the onreply_route here?
Or am I missing the boat entirely?
I'm out of stuff to look at on this problem. Any suggestions would be
warmly welcomed.
- Jeff
More information about the Users
mailing list