VoIP Mailing List Archives

[maximilian.dorn at pin...]

Hi everyone,

I am currently working with sip.js and freeswitch which is currently connecting to our freeswitch via the our internal network.
Looking at the registration I am seeing that the contact show fs_nat= yes. Here the registration from the server.

Call-ID: 6ctjv10kv92d3eft9i6lc7
User: 01234678@example.com (01234678@example.com)
Contact: "01234678" <[url=sip:01234678@example.com;transport=ws;fs_nat=yes;fs_path=sip%3A01234678%4010.128.130.129%3A51786%3Btransport%3Dwss]sip:01234678@example.com;transport=ws;fs_nat=yes;fs_path=sip%3A01234678%4010.128.130.129%3A51786%3Btransport%3Dwss[/url]>
Agent: SIP.js/0.15.10
Status: Registered(WSS-NAT)(unknown) EXP(2021-02-11 13:10:07) EXPSECS(658)
Ping-Status: Reachable
Ping-Time: 0.00
Host: example
IP: 10.128.130.129
Port: 51786
Auth-User: unknown
Auth-Realm: example.com
MWI-Account: 01234678@example.com (01234678@example.com)

Nat detection is disabled for the freeswitch and a normal snom phone registering to the server does not show the fs_nat=yes
Does freeswitch always detect nat for webrtc connections? Or is there possibly something wrong in my configuration?

Kind Regards,
Max
------------------------------------------------------------ Phone: +491752242485Fax: Mail: maximilian.dorn@pinguin.ag ------------------------------------------------------------ Phone: +49.30.30 36 63 366Fax: +49.30.30 36 63 367E-Mail: info@pinguin.ag (info@pinguin.ag)www.pinguin.ag ------------------------------------------------------------ Pinguin AGHauptstraße 8 | 10827 Berlin | GermanyUSt-ID: DE240701807Sitz der Gesellschaft: Berlin-Schöneberg, AG Berlin-Charlottenburg, HRB 101380 BVorstand: Roland Becker, Aufsichtsratsvorsitzender: Clemens C. Vogelsberg