[SR-Users] Help need on NAT_Traversal

[JinKevin]

Many thanks Klaus,

with "fix_nated_contact", "fix_nated_register" and the "fix_nated_sdp", I have resovled the NAT Traversal.

 

Thanks,

Kevin 
> Date: Mon, 14 Jun 2010 08:31:47 +0200
> From: klaus.mailinglists at pernau.at
> To: kevin.jzh at hotmail.com
> CC: sr-users at lists.sip-router.org
> Subject: Re: [SR-Users] Help need on NAT_Traversal
> 
> Everything you want to do is possible with the default configuration.
> 
> Just enable all configuration parts with "fix_nated_contact" and
> fix_nated_register".
> This will enable NAT traversal for SIP. Depeing if you want to relay
> media or not just enable/disable the "force_rtpproxy" calls.
> 
> regards
> 
> klaus
> 
> Am 12.06.2010 04:58, schrieb JinKevin:
> > Hi All,
> > 
> > I'm building a video conference system with the kamailio and the video 
> > AS. The network is as below:
> > 
> > UAC(behind NAT) ------ kamailio(public IP) ------ AS (public IP)
> > 
> > I have setup the basic kamailio and the SIP signaling can reach the AS 
> > and the call can be established. Now the time to setup the NAT traveral 
> > since the UACs are behind the NAT.
> > 
> > Since it's video scenario, I don't want the kamailio as the RTPproxy so 
> > try to use the NAT_Traversal module.
> > 
> > From the module doc, NAT_Traversal needs the Dialog module as well. 
> > Have no idea on how to load these two modules and the route config 
> > required although have readed the module docs. Wondering if someone can 
> > help on the config for this scenario?
> > 
> > All call with $rU=="0216666" is forwarded to the video AS as the 
> > route[CONF].
> > 
> > Thanks in advance!
> > 
> > Thanks,
> > Kevin
> > 
> > Below is the current config of the kamailio server:
> > 
 		 	   		  
_________________________________________________________________
一张照片的自白――Windows Live照片的可爱视频介绍
http://windowslivesky.spaces.live.com/blog/cns!5892B6048E2498BD!889.entry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20100616/e4da0576/attachment.htm>