FreeSwitch & Vegastream TLS interoperability problems?
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:
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.
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 <MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <sip%3A888@conference.freeswitch.org> googletalk:conf+888@conference.freeswitch.org<googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:+19193869900
I think my previous response has been lost... I'll use that as a band-aid and ask the manufacturer to fix his software. Thanks, __Yehavi: 2010/3/23 Anthony Minessale <anthony.minessale@gmail.com>
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 <MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch
FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <sip%3A888@conference.freeswitch.org> googletalk:conf+888@conference.freeswitch.org<googletalk%3Aconf%2B888@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
participants (3)
-
Anthony Minessale
-
Brian West
-
Yehavi Bourvine