As an additional clarification, my tls-bind-params do mention transport=tls.
I'm trying to make sense of why FS would be using the clear SIP port instead of the TLS one in any packets over a TLS session.

Any idea?

Thanks
On Feb 9, 2015, at 8:08 AM, Emrah <lists@kavun.ch> wrote:

Hi all,
My experience with FS and TLS has been rather mixed so far. It's been a little inconsistent in keeping NAT sessions up and users discoverable.
One thing I've noticed is that FS advertises the wrong information in option packets. The following is what I receive over my TLS session which is working on port 443.
1.2.3.4:443 -(SIP over TLS)-> 10.0.0.99:51132
Via: SIP/2.0/TLS 1.2.3.4:443;branch=z9hG4bK6Kv171Q3U5rrD
Route: <sip:53178246@5.6.7.8:51132>;transport=tls
Max-Forwards: 70
From: <sip:mod_sofia@1.2.3.4:5060>;tag=Q6XDFHeUUrcHD
Call-ID: 0a052f23-34a8-4158-8c88-fd2a70ffb561_c2RhaSoOYBR6jfJe4ndLoTTKJMrO2gMv
CSeq: 71498568 OPTIONS
User-Agent: FreeSWITCH
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE
Supported: timer, path, replaces
Allow-Events: talk, hold, conference, presence, as-feature-event, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer
Content-Length: 0

Do you see the From and Contact line? How can I rewrite this? Port 5060 has nothing to do there.

Thanks and all the best,
Emrah