Yealink Forums
t21p and freeswitch tls - Printable Version

+- Yealink Forums (http://forum.yealink.com/forum)
+-- Forum: IP Phone Series (/forumdisplay.php?fid=4)
+--- Forum: Phone specific topic (/forumdisplay.php?fid=12)
+---- Forum: T2xP Series (/forumdisplay.php?fid=21)
+---- Thread: t21p and freeswitch tls (/showthread.php?tid=3842)

Pages: 1 2


t21p and freeswitch tls - sanya - 05-21-2015 08:19 PM

Hi!
I am try to setup sip-t21p with freeswitch using tls.
But, registration does not work.
Syslog at t21p writes:

Code:
Jul 31 00:05:12 SIP [780]: STR <3+error > [000] SIP message does not end with CRLFCRLF
Jul 31 00:05:12 SIP [780]: STR <3+error > [000] Could not parse start line of message.
Jul 31 00:05:12 SIP [780]: SDL <3+error > [000] could not parse message
Jul 31 00:05:12 SIP [780]: STR <3+error > [000] Could not parse start line of message.
Jul 31 00:05:12 SIP [780]: SDL <3+error > [000] could not parse message
Jul 31 00:05:12 SIP [780]: STR <3+error > [000] Could not parse start line of message.
Jul 31 00:05:12 SIP [780]: SDL <3+error > [000] could not parse message
Jul 31 00:05:12 SIP [780]: STR <3+error > [000] Could not parse start line of message.
Jul 31 00:05:12 SIP [780]: SDL <3+error > [000] could not parse message



RE: t21p and freeswitch tls - James_Yealink - 05-21-2015 09:55 PM

Hi Sanya,

Is there working phone with TLS in your side?
It's best that we can get two syslog, one from working phone the other from problematic phone.

The syslog is not level 6, can you set the a new level 6 syslog?
And please make sure that you fill a correct port, generally TLS use a different port from UDP.

Regards,
James


RE: t21p and freeswitch tls - sanya - 05-21-2015 11:42 PM

Sorry, I have just one yealink phone.
syslog level 6 writes:
Code:
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000] Message sent: (to dest=192.168.89.90:5061)
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000]
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000] REGISTER sip:192.168.89.90:5061 SIP/2.0^M
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000] Via: SIP/2.0/TLS 192.168.103.253:43244;branch=z9hG4bK165957143^M
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000] From: "1001" <sip:1001@192.168.89.90:5061>;tag=1491927174^M
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000] To: "1001" <sip:1001@192.168.89.90:5061>^M
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000] Call-ID: 1478982191@192.168.103.253^M
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000] CSeq: 1 REGISTER^M
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000] Contact: <sip:1001@192.168.103.253:43244;transport=TLS>^M
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000] Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE^M
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000] Max-Forwards: 70^M
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000] User-Agent: Yealink SIP-T21P 34.72.193.20^M
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000] Expires: 0^M
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000] Allow-Events: talk,hold,conference,refer,check-sync^M
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000] Content-Length: 0^M
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000] ^M
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000]
Jul 31 00:01:29 SIP [260]: SUA <6+info  > [000] App event:[0x80000005] wParam:(0x0000),lParam:(0x0000) SIP_MSG_BLF_LIST_STATUS_UPDATE  
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000] Received TLS message:
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000]
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000] SIP/2.0 401 Unauthorized^M
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000] Via: SIP/2.0/TLS 192.168.103.253:43244;branch=z9hG4bK165957143;rport=43244^M
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000]
Jul 31 00:01:29 SIP [260]: STR <3+error > [000] SIP message does not end with CRLFCRLF
Jul 31 00:01:29 SIP [260]: SDL <5+notice> [000] Message received from: 192.168.89.90:5061
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000] This is a request
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000] Received TLS message:
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000]
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000] From: "1001" <sip:1001@192.168.89.90:5061>;tag=1491927174^M
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000]
Jul 31 00:01:29 SIP [260]: STR <3+error > [000] Could not parse start line of message.
Jul 31 00:01:29 SIP [260]: SDL <3+error > [000] could not parse message
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000] Received TLS message:
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000]
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000] To: "1001" <sip:1001@192.168.89.90:5061>;tag=D95mcFSZccNHp^M
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000]
Jul 31 00:01:29 SIP [260]: STR <3+error > [000] Could not parse start line of message.
Jul 31 00:01:29 SIP [260]: SDL <3+error > [000] could not parse message
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000] Received TLS message:
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000]
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000] Call-ID: 1478982191@192.168.103.253^M
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000] CSeq: 1 REGISTER^M
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000]
Jul 31 00:01:29 SIP [260]: STR <3+error > [000] Could not parse start line of message.
Jul 31 00:01:29 SIP [260]: SDL <3+error > [000] could not parse message
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000] Received TLS message:
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000]
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000] User-Agent: FreeSWITCH-mod_sofia/1.4.18-3-1~32bit^M
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000] Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE^M
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000] Supported: timer, path, replaces^M
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000] WWW-Authenticate: Digest realm="192.168.89.90", nonce="539901a1-3ef8-457e-8b28-f8267526ac43", algorithm=MD5, qop="auth"^M
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000] Content-Length: 0^M
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000] ^M
Jul 31 00:01:29 SIP [260]: SDL <6+info  > [000]
Jul 31 00:01:29 SIP [260]: STR <3+error > [000] Could not parse start line of message.
Jul 31 00:01:29 SIP [260]: SDL <3+error > [000] could not parse message



RE: t21p and freeswitch tls - James_Yealink - 05-22-2015 02:33 AM

34.72.193.20 is Broadsoft firmware.
Can you upgrade to common firmware, do a reset then check again.

34.72.0.75:
http://support.yealink.com/attachmentDownload/download?path=upload%2Fattachment%2F2015-3-12%2F6%2Ff9d26a82-a5ab-48d4-b3cc-04762b4c86bf%2F34.72.0.75.zip

Regards,
James


RE: t21p and freeswitch tls - sanya - 05-22-2015 03:07 AM

The same:
Code:
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000] Message sent: (to dest=192.168.89.90:5061)
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000]
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000] REGISTER sip:192.168.89.90:5061 SIP/2.0^M
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000] Via: SIP/2.0/TLS 192.168.103.253:20996;branch=z9hG4bK52089866^M
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000] From: "1001" <sip:1001@192.168.89.90:5061>;tag=2014489217^M
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000] To: "1001" <sip:1001@192.168.89.90:5061>^M
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000] Call-ID: 1330404366@192.168.103.253^M
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000] CSeq: 1 REGISTER^M
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000] Contact: <sip:1001@192.168.103.253:20996;transport=TLS>^M
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000] Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE^M
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000] Max-Forwards: 70^M
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000] User-Agent: Yealink SIP-T21P 34.72.0.75^M
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000] Expires: 0^M
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000] Allow-Events: talk,hold,conference,refer,check-sync^M
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000] Content-Length: 0^M
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000] ^M
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000]
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000] Received TLS message:
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000]
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000] SIP/2.0 401 Unauthorized^M
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000] Via: SIP/2.0/TLS 192.168.103.253:20996;branch=z9hG4bK52089866;rport=20996^M
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000]
Jul 29 00:01:27 SIP [781]: STR <3+error > [000] SIP message does not end with CRLFCRLF
Jul 29 00:01:27 SIP [781]: SDL <5+notice> [000] Message received from: 192.168.89.90:5061
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000] This is a request
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000] Received TLS message:
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000]
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000] From: "1001" <sip:1001@192.168.89.90:5061>;tag=2014489217^M
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000]
Jul 29 00:01:27 SIP [781]: STR <3+error > [000] Could not parse start line of message.
Jul 29 00:01:27 SIP [781]: SDL <3+error > [000] could not parse message
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000] Received TLS message:
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000]
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000] To: "1001" <sip:1001@192.168.89.90:5061>;tag=HK1F85yjpy31m^M
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000]
Jul 29 00:01:27 SIP [781]: STR <3+error > [000] Could not parse start line of message.
Jul 29 00:01:27 SIP [781]: SDL <3+error > [000] could not parse message
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000] Received TLS message:
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000]
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000] Call-ID: 1330404366@192.168.103.253^M
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000] CSeq: 1 REGISTER^M
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000]
Jul 29 00:01:27 SIP [781]: STR <3+error > [000] Could not parse start line of message.
Jul 29 00:01:27 SIP [781]: SDL <3+error > [000] could not parse message
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000] Received TLS message:
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000]
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000] User-Agent: FreeSWITCH-mod_sofia/1.4.18-3-1~32bit^M
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000] Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE^M
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000] Supported: timer, path, replaces^M
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000] WWW-Authenticate: Digest realm="192.168.89.90", nonce="822b3669-8071-4c98-b4a3-c644032c3b05", algorithm=MD5, qop="auth"^M
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000] Content-Length: 0^M
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000] ^M
Jul 29 00:01:27 SIP [781]: SDL <6+info  > [000]
Jul 29 00:01:27 SIP [781]: STR <3+error > [000] Could not parse start line of message.
Jul 29 00:01:27 SIP [781]: SDL <3+error > [000] could not parse message



RE: t21p and freeswitch tls - James_Yealink - 05-22-2015 03:17 AM

Can you disable "Only Accept Trusted Certificates" option under Security-> Trusted Certificate and check again.


RE: t21p and freeswitch tls - sanya - 05-22-2015 03:26 AM

It's with already disabled "Only Accept Trusted Certificates".


RE: t21p and freeswitch tls - James_Yealink - 05-22-2015 04:35 AM

I will check with R&D about this problem.
May I know this phone is for testing or for a daily use?

Regards,
James


RE: t21p and freeswitch tls - sanya - 05-22-2015 04:46 AM

At this time its for testing


RE: t21p and freeswitch tls - sanya - 05-24-2015 10:39 PM

Hi!
Have any information about this problem?