All SIP peers treated as insecure=port

[John Runyon]

Asterisk 1:13.18.3~dfsg-1ubuntu4 on 18.04

All SIP peers seem to be being treated as insecure=port, meaning that if you have multiple devices registered from the same IP (for example, two users on the same LAN behind NAT), only one of them will function at a time.
In our case we had 2 phones registered, and only one of them at a time was able to make calls. If the other device attempted to make a call, it would get Declined and Asterisk printed an error that the username provided by the device (in the Digest) did not match the username Asterisk found:

[Nov 21 12:34:48] WARNING[15578][C-000003a7] chan_sip.c: username mismatch, have <1100>, digest has <1110>
[Nov 21 12:34:48] NOTICE[15578][C-000003a7] chan_sip.c: Failed to authenticate device "John Runyon" <sip:1110@asterisk-ip-goes-here>;tag=e8ba7007768f000d1d234cad-a7548314

Both peers were set without 'insecure' and were shown correctly in "sip show peers".

I was unable to build the source package, but after installing 13-current (13.23.1) from tarball provided by the developers (without any config changes), the problem went away.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: asterisk (not installed)
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Thu Nov 22 02:51:40 2018
InstallationDate: Installed on 2018-08-16 (97 days ago)
InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
 LANGUAGE=en_US:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: asterisk
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.init.d.asterisk: [modified]
mtime.conffile..etc.init.d.asterisk: 2018-11-21T14:48:39.513412

[Christian Ehrhardt  (paelzer)]

Hi,
I don't have the devices to test any of that, so I try to help you as good as possible but I'm not entirely sure.
There is a 1:13.22.0~dfsg-2 in the subsequent Ubuntu Cosmic (18.10) version.
There also currently is a 1:13.23.1~dfsg-1 about to become released to the current Disco (19.04) version.

Could you give those a try on your setup so that we know if this is at least fixed in latter versions of Ubuntu?

[Christian Ehrhardt  (paelzer)]

There was a massive change in 13.23 if you see the entries for "insecure" or commit "2a5d408733" in http://downloads.asterisk.org/pub/telephony/asterisk/ChangeLog-13-current

I must admit you as an asterisk user might get more out of all of this, give it a read.
It might explain why 13.23 from upstream works for you.

That said it would be great if you could test both
13.22 from Cosmic
and
13.23 from current Disco-proposed

As it would help to trim down the list of related patches to consider.

[Christian Ehrhardt  (paelzer)]

Finally for someone to (re)try your case it would be really helpful to share all details of your configuration so one can try to recreate (even though if you need any real non SIP phones it might be hard).

[Launchpad Janitor (janitor)]

[Expired for asterisk (Ubuntu) because there has been no activity for 60 days.]