[asterisk-bugs] [JIRA] (ASTERISK-25481) Asterisk 13.6.0 with PJSIP 2.4.5 opens unwanted ports

[Peter Pfannenschmid (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-25481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=227989#comment-227989 ] 

Peter Pfannenschmid commented on ASTERISK-25481:
------------------------------------------------

I think I don't need to upload my configuration files: After compiling and installing, do "rm -r /etc/asterisk" (in case there is an old one in place) and then "make samples". Then start Asterisk by doing "asterisk -gc" (this will get you some warnings on the Asterisk console because the sample configuration does not fit well with the module configuration) and observe the following:

>netstat -apnv | grep asterisk
udp 0 0 0.0.0.0:36973 0.0.0.0:* 26419/asterisk

As you can see, the open port 5060 now isn't there any more (this is expected since there is no reasonable PJSIP configuration active with the sample files, notably there is no transport configured), but the unwanted port is still open.



> Asterisk 13.6.0 with PJSIP 2.4.5 opens unwanted ports
> -----------------------------------------------------
>
>                 Key: ASTERISK-25481
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25481
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: pjproject/pjsip
>    Affects Versions: 13.6.0
>         Environment: Debian wheezy x64 (up-to-date), Asterisk 13.6.0, PJSIP 2.4.5
>            Reporter: Peter Pfannenschmid
>            Assignee: Peter Pfannenschmid
>            Severity: Critical
>         Attachments: menuselect.makeopts
>
>
> Asterisk / PJSIP open at least one unwanted UDP port when being started.
> Steps to reproduce:
> 1) Download, configure, compile and make install PJSIP 2.4.5.
> 2) Download Asterisk 13.6.0, configure and make menuselect *LIKE DESCRIBED BELOW*, then make install.
> 3) Fire up Asterisk by asterisk -gc.
> 4) Using netstat, observe something like:
> >netstat -apnv | grep asterisk
> udp    0      0 192.168.20.48:5060      0.0.0.0:*      26419/asterisk  
> udp    0      0 0.0.0.0:38827           0.0.0.0:*      26419/asterisk
> The first line is expected, of course, but the second isn't. The port shown on the second line changes every time Asterisk is restarted.
> Regarding menuselect: I have slimmed my Asterisk installation as much as it was possible taking my needs into account. This means there is no module which should open an additional port. I have attached my menuselect.makeopts file to facilitate reproducing the issue.
> I have tagged this as critical because Asterisk / PJSIP unexpectedly opening a port is quite threatening, letting aside the fact that it does so on all IP addresses, thereby ignoring the configuration of the transport
> Maybe it's a newbie's fault and I have overlooked something, but on the other hand, I got no answer to that on the mailing list, so obviously the reason for that port being open is unknown, and that is critical, isn't it?



--
This message was sent by Atlassian JIRA
(v6.2#6252)