Hello,

We have a Vegastream ATA adapter working fine with FreeSwitch as long as we do not enable TLS. Once TLS is enabled, I see the following behavior:

The adapter creates a TLS tunnel with Freeswitch and registers itself. However, I see one difference in the registration between this adapter and other adapters/phones:

The VegaStream adapter is registered as:

Contact: "user" <sips:80632@10.64.1.6:5061>
Status: Registered(TLS)(unknown) EXP(2010-03-23 08:50:26)
Other TLS phones register as:
Contact: "user" <sips:80631@10.64.0.8:5061;transport=tls>
Status: Registered(TLS)(unknown) EXP(2010-03-23 08:37:35)
What I see is the difference in the "contact" field in which the transport=tls clause is missing.

When a user on the ATA dials out, the request is sent via TLS and all is fine.
When someone calls an ATA extension, Freeswitch sends the request to the ATA via SIP/UDP and not via SIP/TLS

I've contacted the manufacturer who claims that according to RFC5630 it should send the request via TLS as it is registered as TLS. I have a feeling that the erronous behaviour is because they do not append "transport=tls" to the contact field, although they claim it is not required.

Who is right and who is wrong?

Thanks! __Yehavi: