Hi,
I have been playing around with the mediaproxy over the past few days as well, and seem to
have everything in place that works except the non-nat to nat client calls. Is your
solution working, I know the problem is that the media_session is not starting because the
caller isn't behind nat. If your solution is working, could you please send me the
parts of your ser that determine the receiver is behind nat and starts the media session?
It would be much easier if there was a fuction to check flags on the receiver part of the
usrloc.
Doug
On Thu, January 20, 2005 9:24 am, Hendrik Scholz said:
Hi!
I've been playing around with mediaproxy for quite some time and
it's running pretty well for natted connections. On the downside it's also
redirecting connections
between two external hosts to the mediaproxy.
Using the client_nat_tests() function there should be a way to prevent
this but it seems as if I failed to get it done correctly.
Could someone paste a config that is able to distinguish clients
properly?
How would I handle connections that only have one host behind that
so the INVITE comes from a not-natted connection going to a natted client (and the other
way
round)? I thought about calling use_media_proxy() for all initial INVITES and
call it a second time on the reply route only if client_nat_test("3") found a
NAT.
For my last tests I used the example config from
modules/mediaproxy/config/ser.cfg so I don't have to paste it here.
I'm thinking of marking clients as 'needs NAT' when the register and
client_nat_test("3") is true and when an INVITES comes I check both the source
and destination to
determine whether I need to use the mediaproxy. Makes sense?
Thanks,
Hendrik
--
freenet Cityline GmbH, Hamburger Chaussee 2-4, 24114 Kiel, Germany Phone: +49 (0)431
9020552, Fax:
+49 (0)431 9020559
Internet:
http://www.freenet.de, eMail: hendrik.scholz(a)freenet-ag.de
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers