25 Aug
2006
25 Aug
'06
6:20 a.m.
Hi Bogdan,
thanks for your answer!
Bogdan-Andrei Iancu schrieb:
Hi Gerry,
there is a new pseudo variable - fs - forced socket - you can inspect
it after the lookup("") to see what will be the outgoing interface.
Great! I checked it and it works fine even though I wished it would work
anytime, not only after lookup () .
for the static routing, I think it's quite easy to
figure out.
You thought about checking the RURI for local IP addresses?
regarding the rtpproxy, have you tried to use the "i" and "e" flags?
Yes, I have, but
a) it didn't work (but I did not investigate this into extensively), and
b) I'm planning on using more than 2 interfaces (i.e. internal,
external, internal_IPv6, ...)
http://openser.org/docs/modules/1.1.x/nathelper.html#AEN275
regards,
bogdan
Gerry wrote:
Dear openser-users,
I am trying to set-up a configuration where openser + RTPproxy are
relaying messages between disconnected networks (i.e. openser +
RTPproxy having more than one network-interface). With this method, I
could additionally bridge IPv4-only and IPv6-only clients. Therefore
I need to find out, on which interface (or socket, respectively)
openser will send the message out because RTPproxy needs this info
and is too dumb to find out by itself.
I currently have a _very_ complicated solution which utilizes AVPs
and mysql and it fails with NATed clients (detail: because the
"contact" changes, I cannot look it up in the DB again).
So, if you have any solutions or hints I would be VERY happy to
"hear" from you.
Greetings, Gerry.
P.S.: Of course, I would be happy to share my config, but I don't
want to SPAM this list. Therefore, if you are interested, just ask!
But remember: my solution ONLY makes sense, if you're relaying
between disconnected networks!
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users