Summary:	ASTERISK-30470: Cisco SPA3XX and SPA5XX not register with PJSIP TLS and LE certs
Reporter:	Dmitry Shleg (dshleg)	Labels:
Date Opened:	2023-03-16 05:47:54	Date Closed:	2023-03-16 14:32:10
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	pjproject/pjsip
Versions:	18.9.0 18.16.0 18.17.0	Frequency of Occurrence	Constant
Related Issues:
Environment:	Debian 11 Bulleye with latest updates	Attachments:
Description:	I trying to migrate from asterisk 13 chan_sip to asterisk 18 with pjsip channel driver. I has ~300 Cisco SPA devices with 7.6.2e like a SR5 firmware i has three test enviroments(LetsEncrypt certs ): 1. (prod)VM CentOS7 + asterisk 13 ( chan_sip ) - not register problems  chan_sip configured with tlsdontverifyserver=no, tlsclientmethod=tlsv1 2. (test)VM with latest FreePBX distro ( asterisk 18.13 + FreePBX 14)    pjsip driver by default works with param: method=tlsv1_2 and when phone connects to asterisk i got error: SSL SSL_ERROR_SSL (Handshake): Level: 0 err: <336027900> <SSL routines-SSL23_GET_CLIENT_HELLO-unknown protocol after change to method=sslv23, devices registers without problems 3. (test)VM Debian 11 + Asterisk installed from source in any param method(default, sslv23, tlsv1, tlsv1_2) console says: SSL routines-tls_early_post_process_client_hello-unsupported protocol Please describe right direction to fix it.
Comments:	By: Asterisk Team (asteriskteam) 2023-03-16 05:47:57.823-0500 The severity of this issue has been automatically downgraded from "Blocker" to "Major". The "Blocker" severity is reserved for issues which have been determined to block the next release of Asterisk. This severity can only be set by privileged users. If this issue is deemed to block the next release it will be updated accordingly during the triage process. By: Asterisk Team (asteriskteam) 2023-03-16 05:47:58.431-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/]. By: Joshua C. Colp (jcolp) 2023-03-16 05:51:35.435-0500 We appreciate the difficulties you are facing, however this does not appear to be a bug report and your request or comments would be better served in a different forum. The Asterisk community provides support over IRC, mailing lists, and forums as described at http://asterisk.org/community. The Asterisk issue tracker is used specifically to track issues concerning bugs and documentation errors. Please see the Asterisk Issue Guidelines [1] for instruction on the intended use of the Asterisk issue tracker. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines By: Dmitry Shleg (dshleg) 2023-03-16 14:18:54.329-0500 I make new fresh install native asterisk on CentOS Linux release 7.9.2009 (Core) and no problem working with phones on firmware 7.6.2e!! Possible a pjsip build bug  on Debian 11 with 5.10 kernel only! By: Asterisk Team (asteriskteam) 2023-03-16 14:18:54.727-0500 This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable. By: Joshua C. Colp (jcolp) 2023-03-16 14:32:04.722-0500 It is unlikely to be a PJSIP build bug. OpenSSL can be built by the Linux distribution with or without support for older SSL, and it can also be configured at runtime. It is entirely possible and likely that on Debian 11 it's not supporting the older one and thus isn't working. As the comment before said, I would suggest using the community resources to discuss this instead of jumping to it being a bug.