Can you please re-submit the patch against original sources, because it is really easier to work with the patch than with modified sources.
Thanks!
-Maxim
dhiraj.2.bhuyan@bt.com wrote:
Hello List,
Attached modified nathelper.c (SER nathelper module) and main.c (for rtpproxy). This will allow you to do the following -
- Multiple RTP proxies on the path.
eg.
UA1 ------- SER/RTPproxy1------SER/RTPproxy2-------UA2
UA1 ---NAT---SER/RTPproxy1------SER/RTPproxy2---NAT----UA2
where UA1 and UA2 are registered to two different SERs. This is useful if you have two different service providers (SER1 and SER2) both providing nathelper/rtpproxy support to their registered clients. No change to the ser.cfg is required. (For the curious - how this works is - when force_rtp_proxy is called, before the media IP:port is replaced by that of the rtpproxy, a check is made if the original IP address is a private address - if yes, nathelper tells rtporoxy to wait for atleast one UDP packet from this end. But if the IP address is a globally routable one, nathelper passes this IP:port to rtpproxy)
- A UA with asymmetric RTP support (sending and receiving on different ports) but with a public IP address can now talk to rtpproxy (to reach a natted UA for example). Note that natted UAs still have to support symmetric RTP.
eg.
SUA1----NAT----SER/RTPproxy-----AUA2
SUA1 is a user agent with symmetric RTP support. AUA2 is a user agent that does asymmetric RTP.
AUA1----SER/RTPproxy-----SER/RTPproxy-----AUA2
where you are forcing rtpproxy on both SERs.
I have tested this with my own test settings. Let me know if you have any questions. Note that this will run only with the CVS version or SER (mine is 2nd Dec CVS download).
Regards,
Dhiraj Bhuyan Network Security Specialist, BT Exact Business Assurance Solutions
Tel: +44 1473 643932 Mob: +44 7962 012145 Email: dhiraj.2.bhuyan@bt.com
Serdev mailing list serdev@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serdev
-
Maxim Sobolev