[Home]

Summary:ASTERISK-27245: Access to AMI always raise a tls exception even if tls is disable
Reporter:Fabio Masini (faxioman)Labels:
Date Opened:2017-09-02 10:22:39Date Closed:2017-09-11 06:03:59
Priority:MinorRegression?
Status:Closed/CompleteComponents:
Versions:13.9.1 Frequency of
Occurrence		Constant
Related
Issues:
Environment:LEDE 17.01.2Attachments:
Description:Trying to access the manager with a simple telnet command:

```
telnet 192.168.10.26 5038
```
results in:

```
Trying 192.168.10.26...
Connected to 192.168.10.26.
Escape character is '^]'.
Connection closed by foreign host.
```

and in the asterisk console this warning (verbosity is vvv):

```
tcptls.c:684 handle_tcptls_connection: FILE * open failed!
```
The error message is really, really, really cryptic, and the manager page is not working. I'm not enabling tls in manager, this is my conf:

```
[general]
enabled = yes
webenabled = yes

port = 5038
bindaddr = 0.0.0.0

[admin]
secret = ****
permit=0.0.0.0/0.0.0.0

read = system,call,log,verbose,agent,user,config,dtmf,reporting,cdr,dialplan
write = system,call,agent,user,config,command,reporting,originate,message
```
Comments:By: Asterisk Team (asteriskteam) 2017-09-02 10:22:40.298-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.

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].
By: Joshua C. Colp (jcolp) 2017-09-11 06:03:59.804-0500

The code in question is common TCP/TLS code. It handles both TCP and TLS, thus the "tcptls" name. Since you are connecting using TCP it is being used. I'd suggest upgrading to the latest version of Asterisk 13, and then using one of the community methods[1] to try to figure out why your AMI connection is not working. If after that it is determined this is a bug then it can be reopened.

[1] https://community.asterisk.org/