They are living in the past since the sips thing is all but dead.
There are no clear specs on tls because as usual there were originally 10 ways to do it.


if that contact is always the same you can manually override it with

<param name="force-register-contact" value="sip:80632@10.64.1.6:5061;transport=tls"/>

in the <user> tag in your directory so when they register the substituted value will be placed into the DB.

On Tue, Mar 23, 2010 at 8:57 AM, Brian West <brian@freeswitch.org> wrote:

Every endpoint I have tested that works correctly will append the transport=tls so we have a clue what transport to use to call them back.

/b

On Mar 23, 2010, at 2:19 AM, Yehavi Bourvine wrote:

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.

_______________________________________________
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org

--
Anthony Minessale II

FreeSWITCH http://www.freeswitch.org/
ClueCon http://www.cluecon.com/
Twitter: http://twitter.com/FreeSWITCH_wire

AIM: anthm
MSN:anthony_minessale@hotmail.com
GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com
IRC: irc.freenode.net #freeswitch

FreeSWITCH Developer Conference
sip:888@conference.freeswitch.org
googletalk:conf+888@conference.freeswitch.org
pstn:+19193869900

_______________________________________________
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org