First of all I would recommend you to split your setup in two parts and test them separately. First of all make signalling work (ignore the contents of SDP) and make sure that you are able to send INVITE and receive responses either to local phones or phones/proxies in the public internet.
For that you will have to enable mhomed=yes and make sure that you are record routing all messages that go outside.
You need to make sure that Via and Record-Route of outgoing messages contain thepublic IP (mhomed should take care of it) of your server.
Speak up once you have signalling working and we can continue with RTP proxy setup.
Jan.
On 24-11 00:21, Gregory Sandul wrote:
Hi. Assume I have phones in private network 10.0.0.0/24. There is no NAT server in this network, no default gateway, no way to outside world (except SER). The only server phones "know" about is SER. SER has 2 NIC's one in 10.0.0.0/24 network ip 10.0.0.17 and other in "real" word 201.0.X.X/24. There are some phones (or may be SIP servers) in "real" world. I want to force rtpproxy for outside world and do not for private networks.
I made some test and it fails. If I contact from private network to outside world the Via message contains private SER ip 10.0.0.17 and phone which I need to contact does not know how to contact SER. Also contact in SDP message contains private ser IP 10.0.0.17 because I have forced rtpproxy.
As I understand, it it necessary to modify SDP and SIP messages (contact and Via) in a config script while processing requestst after forcing rtpproxy. Is it possible? May be I missed something, but I have not founded such functions.
Regards, Greg.
Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers