[YMCS/YDMP Free Trial Program]Yealink would like to offer Free Trial Program of Yealink device management service for our current eligible customers. You can see the details below.
https://www.yealink.com/ydmp-freetrial-2020


Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
t21p and freeswitch tls
Author Message
sanya Offline
Junior Member
**

Posts: 7
Joined: May 2015
Reputation: 0
Post: #1
t21p and freeswitch tls
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
05-21-2015 08:19 PM
Find all posts by this user    like0    dislike0 Quote this message in a reply
James_Yealink Offline
Administrator
*******

Posts: 1,159
Joined: Aug 2014
Reputation: 8
Post: #2
RE: t21p and freeswitch tls
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
05-21-2015 09:55 PM
Find all posts by this user    like0    dislike0 Quote this message in a reply
sanya Offline
Junior Member
**

Posts: 7
Joined: May 2015
Reputation: 0
Post: #3
RE: t21p and freeswitch tls
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
05-21-2015 11:42 PM
Find all posts by this user    like0    dislike0 Quote this message in a reply
James_Yealink Offline
Administrator
*******

Posts: 1,159
Joined: Aug 2014
Reputation: 8
Post: #4
RE: t21p and freeswitch tls
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/attachmentDow...2.0.75.zip

Regards,
James
05-22-2015 02:33 AM
Find all posts by this user    like0    dislike0 Quote this message in a reply
sanya Offline
Junior Member
**

Posts: 7
Joined: May 2015
Reputation: 0
Post: #5
RE: t21p and freeswitch tls
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
05-22-2015 03:07 AM
Find all posts by this user    like0    dislike0 Quote this message in a reply
James_Yealink Offline
Administrator
*******

Posts: 1,159
Joined: Aug 2014
Reputation: 8
Post: #6
RE: t21p and freeswitch tls
Can you disable "Only Accept Trusted Certificates" option under Security-> Trusted Certificate and check again.
05-22-2015 03:17 AM
Find all posts by this user    like0    dislike0 Quote this message in a reply
sanya Offline
Junior Member
**

Posts: 7
Joined: May 2015
Reputation: 0
Post: #7
RE: t21p and freeswitch tls
It's with already disabled "Only Accept Trusted Certificates".
05-22-2015 03:26 AM
Find all posts by this user    like0    dislike0 Quote this message in a reply
James_Yealink Offline
Administrator
*******

Posts: 1,159
Joined: Aug 2014
Reputation: 8
Post: #8
RE: t21p and freeswitch tls
I will check with R&D about this problem.
May I know this phone is for testing or for a daily use?

Regards,
James
05-22-2015 04:35 AM
Find all posts by this user    like0    dislike0 Quote this message in a reply
sanya Offline
Junior Member
**

Posts: 7
Joined: May 2015
Reputation: 0
Post: #9
RE: t21p and freeswitch tls
At this time its for testing
05-22-2015 04:46 AM
Find all posts by this user    like0    dislike0 Quote this message in a reply
sanya Offline
Junior Member
**

Posts: 7
Joined: May 2015
Reputation: 0
Post: #10
RE: t21p and freeswitch tls
Hi!
Have any information about this problem?
05-24-2015 10:39 PM
Find all posts by this user    like0    dislike0 Quote this message in a reply
Post Reply 


Possibly Related Threads...
Thread: Author Replies: Views: Last Post
  T21P E2 firmware upgrade janp 0 2,130 01-27-2024 02:43 AM
Last Post: janp
  T21P TLS - Trusted CA TheCourier 0 1,135 07-17-2023 04:34 PM
Last Post: TheCourier
  T21P E2 - Custom Ringtone Darleen 3 5,301 07-26-2022 10:40 PM
Last Post: complex1
  T21P Low headset volume rmatuda 14 46,756 11-02-2021 08:39 PM
Last Post: overlay
  Firmware upgrade fails on T21P E2 p.pasquino@technology4you.it 0 5,731 11-02-2021 04:42 PM
Last Post: p.pasquino@technology4you.it
  T21P Stuck on "Initializing" - Recovery Mode Fails` YCMJamie 5 14,510 08-24-2021 07:04 PM
Last Post: YCMJamie
  T21P E2 default Programmable Key label in V84 erictam 6 17,173 10-28-2020 10:32 PM
Last Post: GwenH
  Recovery files T21P agalindo 1 9,459 06-16-2020 01:49 PM
Last Post: complex1
  T21P Register Failed agatospk 6 18,761 01-31-2020 06:08 AM
Last Post: agatospk
  T21P recover files davidpablo 8 29,988 01-30-2020 02:02 PM
Last Post: Yisroel_MongoTEL

Forum Jump:


User(s) browsing this thread:

Contact Us   Yealink   Return to Top   Return to Content   Lite (Archive) Mode   RSS Syndication