[OpenSIPS-Users] Media proxy basic setup

Daniel Goepp dan at goepp.net
Fri Oct 16 19:51:12 CEST 2009 

Yes, I do realize that I'm breaking the rules...but that never stopped me
from trying before.  And yes, RTPproxy has the same problem, which is why I
decided to give media proxy a try to see if I could get it working, same
problem though as you note.  I guess next I'm going to have to get in and
hack up some code...would seem a straight forward fix though, just have two
parameters in the config, one to offer and one to bind to.

-dg


On Fri, Oct 16, 2009 at 10:46 AM, Jeff Pyle <jpyle at fidelityvoice.com> wrote:

> I don¹t believe so.  To the best of my understanding, Mediaproxy is not a
> near-end NAT solution, but rather a far-end one.  Perhaps some of the AG
> guys can chime in here.
>
> I took a quick flip through the nathelper module doc and I didn't see
> anything relevant in there for rtpproxy either.
>
> It's definitely far more common to have Opensips + Mediaproxy/Rtpproxy on
> the *outside*.  That doesn't necessarily mean it cannot work on the inside,
> it means I just don't know how.  :)
>
> In this situation I would probably use a ALG on the edge.  I have
> experience
> with Edgemarcs although there are others.  That way it's nice and clean
> courtesy of a device that has a good "view" of both sides.  Not sure if
> this
> is feasible for you or not.
>
>
> - Jeff
>
>
>
> On 10/16/09 1:31 PM, "Daniel Goepp" <dan at goepp.net> wrote:
>
> > I have found the problem, and of course it's just what I though, it is
> because
> > of my setup.  Now I just need to figure out a fix.  The problem is that
> it
> > can't bind to the IP that I want it to use in the offer/answer.  For
> example
> > if I put in:
> >
> > relay_ip = 10.251.27.180
> >
> > Then it doesn't blow up, but it writes the SDP with a private address not
> > accessible.  If I put in:
> >
> > relay_ip = <public_ip>
> >
> > Then it blows up.  So is there a way to get media proxy to bind to one
> > address, and offer another?
> >
> > -dg
> >
> >
> > On Fri, Oct 16, 2009 at 10:25 AM, Jeff Pyle <jpyle at fidelityvoice.com>
> wrote:
> >> Way to let the smoke out.
> >>
> >> What are you using for a port range in config.ini?
> >>
> >>
> >>
> >> - Jeff
> >>
> >>
> >>
> >>
> >> On 10/16/09 1:21 PM, "Daniel Goepp" <dan at goepp.net <http://dan@
> goepp.net> >
> >> wrote:
> >>
> >>> Oh and I believe that since media proxy went a little crazy, opensips
> just
> >>> failed with:
> >>>
> >>> Oct 16 17:15:29 ip-10-251-27-180 /usr/local/sbin/opensips[3093]:
> >>> ERROR:mediaproxy:send_command: did timeout waiting for an answer
> >>>
> >>> -dg
> >>>
> >>>
> >>> On Fri, Oct 16, 2009 at 10:19 AM, Daniel Goepp <dan at goepp.net
> >>> <http://dan@goepp.net> > wrote:
> >>>> That definitely made something happen, as in blow up my relay ;)
> >>>>
> >>>> Dispatcher:
> >>>> debug: Connection to OpenSIPS lost: Connection was closed cleanly.
> >>>> debug: Issuing "update" command to relay at 127.0.0.1
> >>>> debug: Connection to OpenSIPS lost: Connection was closed cleanly.
> >>>> warning: relay failure: Relay at 127.0.0.1 timed out
> >>>> error: No suitable relay found
> >>>> warning: relay failure: Relay at 127.0.0.1 timed out
> >>>> error: No suitable relay found
> >>>> error: Connection with relay at 127.0.0.1 was lost: TCP connection
> timed
> >>>> out.
> >>>>
> >>>> Relay (spewed constantly):
> >>>> warning: Cannot use port pair 59128/59129
> >>>> warning: Cannot use port pair 59130/59131
> >>>> warning: Cannot use port pair 59132/59133
> >>>> warning: Cannot use port pair 59134/59135
> >>>> warning: Cannot use port pair 59136/59137
> >>>> warning: Cannot use port pair 59138/59139
> >>>> warning: Cannot use port pair 59140/59141
> >>>> warning: Cannot use port pair 59142/59143
> >>>>
> >>>> I believe this is likely due to the fact that much like the problem I
> had
> >>>> with opensip, mediaproxy does not like me telling it that it's IP is
> >>>> something other than what it's interface says.  I'm digging in deeper
> now.
> >>>>
> >>>> Thanks
> >>>>
> >>>> -dg
> >>>>
> >>>>
> >>>>
> >>>> On Fri, Oct 16, 2009 at 9:38 AM, Jeff Pyle <jpyle at fidelityvoice.com
> >>>> <http://jpyle@fidelityvoice.com> > wrote:
> >>>>> Dan,
> >>>>>
> >>>>> Are you using the dialog module?  I recommend it.  If so, you¹ll need
> >>>>> somewhere in there before any t_relay():
> >>>>>
> >>>>> create_dialog();
> >>>>> engage_media_proxy();
> >>>>>
> >>>>> This actually switches on Mediaproxy for the call.  It uses the
> dialog
> >>>>> module to track any reinvites, etc.
> >>>>>
> >>>>>
> >>>>> - Jeff
> >>>>>
> >>>>>
> >>>>>
> >>>>> On 10/16/09 12:32 PM, "Daniel Goepp" <dan at goepp.net <http://dan@
> goepp.net>
> >>>>> > wrote:
> >>>>>
> >>>>>> I have finally successfully install and am running media proxy on
> the
> >>>>>> same
> >>>>>> server that I am running opensips.  I have added to the opensips.cfg
> the
> >>>>>> mediaproxy module
> >>>>>>
> >>>>>> loadmodule "mediaproxy.so"
> >>>>>>
> >>>>>> From an example site I tried with these, then commented them out:
> >>>>>> #modparam("mediaproxy", "mediaproxy_socket",
> >>>>>> "/var/run/mediaproxy/dispatcher.sock")
> >>>>>> #modparam("mediaproxy", "mediaproxy_timeout", 500)
> >>>>>> #modparam("mediaproxy", "signaling_ip_avp", "$avp(s:nat_ip)")
> >>>>>> #modparam("mediaproxy", "media_relay_avp", "$avp(s:media_relay)")
> >>>>>>
> >>>>>> The SDP on my calls are not getting re-written with the IP of the
> media.
> >>>>>> With
> >>>>>> RTP proxy I had to put in the force_rtp_proxy call, but I don't see
> >>>>>> anything
> >>>>>> similar with media proxy.  Any ideas on what I might look at next to
> get
> >>>>>> opensips to re-write the SDP?
> >>>>>>
> >>>>>> Here are the startup commands and output:
> >>>>>>
> >>>>>> /usr/local/src# media-dispatcher --no-fork
> >>>>>> Starting MediaProxy Dispatcher 2.3.8
> >>>>>> Twisted is using epollreactor
> >>>>>> mediaproxy.dispatcher.RelayFactory starting on 25060
> >>>>>> mediaproxy.dispatcher.OpenSIPSControlFactory starting on
> >>>>>> "'/var/run/mediaproxy/dispatcher.sock'"
> >>>>>> mediaproxy.dispatcher.ManagementControlFactory starting on 25061
> >>>>>> debug: Connection from relay at 127.0.0.1
> >>>>>> debug: Issuing "sessions" command to relay at 127.0.0.1
> >>>>>>
> >>>>>> /etc/mediaproxy# media-relay --no-fork
> >>>>>> Starting MediaProxy Relay 2.3.8
> >>>>>> Set resource limit for maximum open file descriptors to 11000
> >>>>>> gc: collectable <tuple 0xb7c1152c>
> >>>>>> gc: collectable <StgDict 0xb7a9c6ac>
> >>>>>> gc: collectable <_ctypes.ArrayType 0x8552fc4>
> >>>>>> gc: collectable <getset_descriptor 0xb7bd0a0c>
> >>>>>> gc: collectable <getset_descriptor 0xb7bd09cc>
> >>>>>> gc: collectable <tuple 0xb7f5c61c>
> >>>>>> gc: collectable <tuple 0xb7bd0a2c>
> >>>>>> gc: collectable <StgDict 0xb7a9c91c>
> >>>>>> gc: collectable <_ctypes.ArrayType 0x8554e54>
> >>>>>> gc: collectable <getset_descriptor 0xb7bd08ac>
> >>>>>> gc: collectable <getset_descriptor 0xb7bd048c>
> >>>>>> gc: collectable <tuple 0xb7a632fc>
> >>>>>> gc: collectable <getset_descriptor 0xb7bd060c>
> >>>>>> gc: collectable <getset_descriptor 0xb7bd0c6c>
> >>>>>> /etc/resolv.conf changed, reparsing
> >>>>>> Resolver added ('172.16.0.23', 53) to server list
> >>>>>> <class 'twisted.names.dns.DNSDatagramProtocol'> starting on 21651
> >>>>>> Starting protocol <twisted.names.dns.DNSDatagramProtocol object at
> >>>>>> 0xb7a2254c>
> >>>>>> (Port 21651 Closed)
> >>>>>> Stopping protocol <twisted.names.dns.DNSDatagramProtocol object at
> >>>>>> 0xb7a2254c>
> >>>>>>
> >>>>>> Thanks
> >>>>>>
> >>>>>> -dg
> >>>>>>
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> Users mailing list
> >>>>> Users at lists.opensips.org <http://Users@lists.opensips.org>
> >>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >>>>
> >>>
> >>>
> >>
> >> _______________________________________________
> >> Users mailing list
> >> Users at lists.opensips.org
> >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >>
> >
> >
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.opensips.org/pipermail/users/attachments/20091016/088db13d/attachment.htm

More information about the Users mailing list