Hi Jayesh,
it is not something general accepted, but my personal advice is to try to do the nat traversal on the client side - if it has a robust and correct STUN implementation, use it. use nat traversal only for phones without STUN (or with bogus STUN) and for corner-cases when STUN does not work at all.
doing this, yo will minimize the impact on the server.
regards, bogdan
Jayesh Nambiar wrote:
Hi, We are planning to use Openser in a large scale deployment. We are planning to stick to Linksys ATAs and IP Phones. Now all these phones have good NAT handling capablities. I just wanted to understand if it is better to handle these parameters on the UA side instead of Openser side. Will it cause some overhead to reduce at the Openser side. By using these UAs is it also possible to eliminate the use of Mediaproxy/RTPproxy at the Server side. I have the Openser working fine with Mediaproxy but I just wanted some expert suggestion from the people who are using these kind of UAs.
Thanks,
w/regards, Jayesh.
Here₼s a new way to find what you're looking for - Yahoo! Answers http://us.rd.yahoo.com/mail/in/yanswers/*http://in.answers.yahoo.com/
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users