Hi Kaeman, as per the logs you have sent me (please in the future keep users@openser.org on cc so others can use also the results of our time invested work), it looks like you are not handing properly the RTP part.
You have a combination between proxy and non proxy of RTP. If you check your packets you will see that for the case of INVITE from RemoteProxy1-> OpenSER -> RemoteProxy2, you will rewrite the connection IP with the OpenSER IP Address (RTP Sockets) so the RemoteProxy2 will think that he must speak with OpenSER, but for the case of 183 replied back (200 OK, same case) you will not rewrite the connection IP, and the RemoteProxy1 - call originator, will have the feeling that he must send the RTP packets directly to RemoteProxy2. Therefore you must decide the scenario you want: proxy all through your openser (rtpproxy) or proxy nothing and let the parties speak directly to each other and have only signaling passing through your openser server. Since you don't have a NAT case here, I thing it should be pretty easy to do the correct setup. Hope you did get my point. Cheers, DanB On 8/30/07, Kaeman Chris <[EMAIL PROTECTED]> wrote: > > Hi Daniel, > > I agree with you:). thanks for your reply. I see life in me NOW. > > Ok, find the debug with ngrep. I did that grepping the port 5060. Is that > OK? Let me know if you need with any specific keyword. > > Attached you will find the debug file. Thanks!! > > Regards, > KChris. > _______________________________________________ Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
