Seems like the NAT traversal is just broken.

just some basic rules:

- Call fix_nated_contact only for request from the clients (although it shouldn't hurt if you call it for all requests) - Whenever a message contains a session description call force_rtp_proxy(). Make sure to provide proper flags regarding the direction of the message. E.g. start rtpproxy listening to internal and external IP and provide the flags "ie" for requests from internal->external and "ei" for requests from external to internal.

regards
klaus

On 04.11.2011 08:51, Sammy Govind wrote:
Thanks Alex for actually finding the thread for me- I'm reading these
thoroughly and let me try these.

Klaus, mhome=1 is a good tip let me try it now: The problem is that when
I set-up the scenario as I mentioned using Private IPs the end user
starts sending the media to the private IP of asterisk (which
is of-course not found anywhere near UAC) - The Asterisk Server on the
other hand sends media to the Public IP of the Client(fixed by the NAT
route and RTPproxy route automatically.)

What I've figured out theoretically is that i need to do the NAT address
fixation in on-reply route from Asterisk servers. By fixing the c=
header in Kamailio for the 200OK back to the client will make the Client
software send media to the Kamailio/RTPproxy port and not on some
private IP.

I hope I made some sense in what I wrote, do let me know if
any clarification is required.

I'm just this one step away from publishing the setup on blog
to benefit the community so any help from experts will be much much
appreciated.

Best Regards,
Sammy

On Fri, Nov 4, 2011 at 12:27 PM, Alex Balashov
<abalas...@evaristesys.com <mailto:abalas...@evaristesys.com>> wrote:

    The fundamental complications that often arise in such a setup are
    summarised in these threads:

    http://lists.sip-router.org/__pipermail/sr-users/2010-__October/065669.html
    <http://lists.sip-router.org/pipermail/sr-users/2010-October/065669.html>

    
http://lists.sip-router.org/__pipermail/sr-users/2011-__September/069975.html
    <http://lists.sip-router.org/pipermail/sr-users/2011-September/069975.html>

    
http://lists.sip-router.org/__pipermail/sr-users/2011-__September/070029.html
    <http://lists.sip-router.org/pipermail/sr-users/2011-September/070029.html>

    --
    Alex Balashov - Principal
    Evariste Systems LLC
    260 Peachtree Street NW
    Suite 2200
    Atlanta, GA 30303
    Tel: +1-678-954-0670 <tel:%2B1-678-954-0670>
    Fax: +1-404-961-1892 <tel:%2B1-404-961-1892>
    Web: http://www.evaristesys.com/


    _________________________________________________
    SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
    sr-users@lists.sip-router.org <mailto:sr-users@lists.sip-router.org>
    http://lists.sip-router.org/__cgi-bin/mailman/listinfo/sr-__users
    <http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>




_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Reply via email to