I am trying to verify that SIP TLS calls work through FreeSwitch running on Windows 7. But the outgoing leg of the call does not get established by FreeSwitch. Setup: 1 PC running Windows 7 and FreeSwitch version 1.4.7 FSClient 1.2.3.5 is installed on two PCs and are configured & registered via TLS to the FreeSwitch server. When I make a call from one FSClient (1003) to the other (1005), I see that the call request gets to the FreeSwitch server: recv 1600 bytes from tls/[10.47.26.44]:14183 at 19:56:53.257366: ------------------------------------------------------------------------ INVITE sip:1005@sszetofs1a.design.mitel.com;transport=tls SIP/2.0 From: "x1003 tls" <sip:1003@sszetofs1a.design.mitel.com
;tag=cKD7B99Z9124m To: <sip:1005@sszetofs1a.design.mitel.com>
------------------------------------------------------------------------ send 353 bytes to tls/[10.47.26.44]:14183 at 19:56:53.257366: ------------------------------------------------------------------------ SIP/2.0 100 Trying Via: SIP/2.0/TLS 10.47.26.44:12347 ;branch=z9hG4bKpKHKUN4jFUerN;rport=14183 From: "x1003 tls" <sip:1003@sszetofs1a.design.mitel.com
;tag=cKD7B99Z9124m To: <sip:1005@sszetofs1a.design.mitel.com>
The call gets challenged and authenticated: SIP/2.0 407 Proxy Authentication Required Via: SIP/2.0/TLS 10.47.26.44:12347 ;branch=z9hG4bKpKHKUN4jFUerN;rport=14183 From: "x1003 tls" <sip:1003@sszetofs1a.design.mitel.com
;tag=cKD7B99Z9124m To: <sip:1005@sszetofs1a.design.mitel.com>;tag=6B6B175KHK8mN
ACK sip:1005@sszetofs1a.design.mitel.com;transport=tls SIP/2.0 Via: SIP/2.0/TLS 10.47.26.44:12347;branch=z9hG4bKpKHKUN4jFUerN Max-Forwards: 70 From: "x1003 tls" <sip:1003@sszetofs1a.design.mitel.com
;tag=cKD7B99Z9124m To: <sip:1005@sszetofs1a.design.mitel.com>;tag=6B6B175KHK8mN
I then see INVITE/100 Trying being exchanged between the caller and FreeSwitch: INVITE sip:1005@sszetofs1a.design.mitel.com;transport=tls SIP/2.0 Via: SIP/2.0/TLS 10.47.26.44:12347;branch=z9hG4bKQvacXgNpc44aH Max-Forwards: 70 From: "x1003 tls" <sip:1003@sszetofs1a.design.mitel.com
;tag=cKD7B99Z9124m To: <sip:1005@sszetofs1a.design.mitel.com>
SIP/2.0 100 Trying Via: SIP/2.0/TLS 10.47.26.44:12347 ;branch=z9hG4bKQvacXgNpc44aH;rport=14183 From: "x1003 tls" <sip:1003@sszetofs1a.design.mitel.com
;tag=cKD7B99Z9124m To: <sip:1005@sszetofs1a.design.mitel.com>
I see a new channel being created to try and reach the terminating party (1005): 2014-08-20 15:56:53.387379 [INFO] mod_dialplan_xml.c:558 Processing x1003 tls <1003>->1005 in context default 2014-08-20 15:56:53.467387 [NOTICE] switch_channel.c:1054 New Channel sofia/internal/sip:gw+3@10.47.26.34:12347 [d416a13a-fb99-4eb4-8645-24104ad5ed97] But that's it ... no SIP messages are sent to 1005 Any thoughts? Are there any parameters I can set within FreeSwitch to make the outbound call leg work? -- *Regards,* *Steve Szeto* *MiContact Center IVR Team* *Software Designer* Tel.: 613-592-5660 Ext. 71698 Email: steven_szeto@mitel.com <steven_szeto@mitel.com_> 350 Legget Drive Kanata, ON Canada K2K 2W7 *www.mitel.com <http://www.mitel.com/_>* -- This e-mail (including any attachments) is for the sole use of the intended recipient(s) and may contain information that is confidential and/or protected by legal privilege. Any unauthorized review, use, copy, disclosure or distribution of this e-mail is strictly prohibited. If you are not the intended recipient, please notify Mitel immediately and destroy all copies of this e-mail. Mitel does not accept any liability for breach of security, error or virus that may result from the transmission of this message.