10 Sep
2005
10 Sep
'05
10:39 a.m.
How can I avoid relay wiht this block
Harry
--- Zeus Ng <zeus.ng(a)isquare.com.au> a écrit :
Harry,
You are detecting nat only within this block.
if (!is_uri_host_local() || !is_from_local() ) {
nat detection ...
}
This means any request that is not originate from
our domain or not for our
domain, detect nat. Now, when someone outside send
an INVITE to you, it will
pass this block, no nat detection, as it is for your
domain. Besides, you
are setting up a open relay. Anyone can use your
server to call someone
else.
We usually send a 404 response within that block.
I suggest you move the nat detection to the very
beginning, just after
checking max forward and message size.
Zeus
-----Original Message-----
From: harry gaillac [mailto:gaillacharry@yahoo.fr]
Sent: Friday, 9 September 2005 6:47 PM
To: Zeus Ng
Subject: RE: [Serusers] RFC3621
Hello,
Thanks for reply.
here are my ser.cfg and two ethereal files .
You can see I use the latest mediaproxy (1.4.2)
look at internal_sip_call file line 15-18 the
callee
send the public ip in SDP in reply.
Look at incoming_call file line 9-10 the calle send
its private ip in SDP in reply.
This is my problem !!
Regards
Harry
___________________________________________________________________________
Nothing is wrong with the reply. SER just
forwards
what the UA report its
IP.
I guest you are using a dual home server to run
SER
and does not have
routing logic to handle internal/external RTP
communication. You need to
bridge the RTP with either rtpproxy or mediaproxy.
I
know the theory but
haven't tried myself. The rtpproxy has some
example
config for you to start.
Appel audio GRATUIT partout dans le monde avec le
nouveau Yahoo! Messenger
Téléchargez cette version sur
http://fr.messenger.yahoo.com
___________________________________________________________________________
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger
Téléchargez cette version sur http://fr.messenger.yahoo.com