[Freeswitch-users] RTP NAT issue

[Carlo Dimaggio]

Ok, I'll try the parameter NDLB. Is it suitable in an hosted environment 
(thousand of extensions)?


Anyway, the problem is that I can't use STUN (phone side configuration) 
because I have two needs:

1) Phone A (192.168.0.100) calls Phone B (192.168.0.101), in this case 
the RTP flow should be sent directly between two endpoints. If I use 
STUN the SDP "A" contains the public IP and not the private IP (that 
must be used for device reachability).

2) Phone A (192.168.0.100) calls Freeswitch (Public IP), in this case 
the RTP flow shoud be sent to Freeswitch Public IP and Freeswitch shoud 
send the RTP to the Phone A NAT IP. Here the STUN is the best solution.

What is the best practice in this scenario?

Regards,


Il 06/06/12 18.28, Brian Foster ha scritto:
>
> The issue is more likely the phone, as the phone is responsible for 
> handing FS the correct IP. There is however a way to force this on the 
> FS side but may break other devices. Please take a look at NDLB (No 
> Device Left Behind) parameters for Sofia on the wiki.
>
> Brian Foster
> Endigo Computer LLC
>
> Sent from a mobile device.
>
> On Jun 6, 2012 12:15 PM, "Carlo Dimaggio" <jaasmailing at gmail.com 
> <mailto:jaasmailing at gmail.com>> wrote:
>
>     Hi all,
>
>     I have a problem with RTP and NAT.
>     The scenario is Hosted PBX and Natted phones (yealink):
>
>     Phones (192.168.0.x) - NAT -> FS (public IP)
>
>     When I call FS (for example an IVR) from a Phone, FS send the RTP
>     to the private address (192.168.0.x) instead to the public NAT IP.
>     The registration is ok:
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20120606/4c69fc83/attachment.html