Fusion/FreeSwitch SIP profile "internal" config

[Samael28]

Hi!
By default FusionPBX configures internal profile in a bit strange way. Idea is, in some cases phones behind NAT can't register on Fusion.
Case is:
Phone (port 5060) -> NAT (change port to 1023) -> Fusion.
In this case in REGISTER message phone has address like <private_IP>:5060. But Fusion receives this message from port 1023 (due to port change in router).
But Fusion keep replying on port 5060. Problem can be solved changing transport to TCP or not happen if source port on router is more than 1024.
For some reason Fusion (Freeswitch with Fusion config) not wants to reply back to port less or equal than 1024 in UDP case.
Adding NDLB-force-rport does not helps.
Asterisk in same cases work fine with nat=force_rport. There is no SIP ALG on router.
Anyone encountered this?

 

[DigitalDaz]

What phone is this? Can you not do rport on the phone?

 

[Samael28]

Yealink T-19. And why to do rport on the phone? My idea is to make Freeswitch to reply back to correct port.
UPD: Missed, happens only with UDP and when router set port less or eq than 1024. With TCP and UDP source ports more than 1024 - all is ok.

 

[DigitalDaz]

The general consensus is that it is always better to do it on the phone when possible, especially being as we can easily provision the yealinks to do so. Also because clients have differing remote networks a one size fits all at the server end often won't work.