Multiple registers in the CLI

Dear Ones!
I was wondering if you could help me with the following behavior:

Why does peer appear multiple times?

Asterisk 13.38.3

8010338/8010338 (Unspecified) D Yes Yes 0 OK (10 ms) Cached RT
8010338/8010338 (Unspecified) D Yes Yes 0 OK (10 ms) Cached RT
8010338/8010338 (Unspecified) D Yes Yes 0 OK (10 ms) Cached RT
8010338/8010338 (Unspecified) D Yes Yes 0 OK (10 ms) Cached RT
8010338/8010338 (Unspecified) D Yes Yes 0 OK (10 ms) Cached RT
8010338/8010338 (Unspecified) D Yes Yes 0 OK (10 ms) Cached RT
8010338/8010338 177.44.191.130 D Yes Yes 5060 OK (10 ms) Cached RT
8010338/8010338 177.44.191.130 D Yes Yes 5060 OK (20 ms) Cached RT
8010338/8010338 (Unspecified) D Yes Yes 0 OK (10 ms) Cached RT
8010338/8010338 (Unspecified) D Yes Yes 0 OK (10 ms) Cached RT
8010338/8010338 177.44.191.130 D Yes Yes 5060 OK (10 ms) Cached RT
8010338/8010338 (Unspecified) D Yes Yes 0 OK (10 ms) Cached RT
8010338/8010338 177.44.191.130 D Yes Yes 5060 OK (10 ms) Cached RT
8010338/8010338 (Unspecified) D Yes Yes 0 OK (10 ms) Cached RT
8010338/8010338 177.44.191.130 D Yes Yes 5060 OK (10 ms) Cached RT
8010338/8010338 177.44.191.130 D Yes Yes 5060 OK (10 ms) Cached RT
8010338/8010338 177.44.191.130 D Yes Yes 5060 OK (10 ms) Cached RT
8010338/8010338 (Unspecified) D Yes Yes 0 OK (10 ms) Cached RT
8010338/8010338 (Unspecified) D Yes Yes 0 OK (11 ms) Cached RT
8010338/8010338 (Unspecified) D Yes Yes 0 OK (10 ms) Cached RT
8010338/8010338 177.44.191.130 D Yes Yes 5060 OK (10 ms) Cached RT
8010338/8010338 (Unspecified) D Yes Yes 0 OK (12 ms) Cached RT
8010338/8010338 177.44.191.130 D Yes Yes 5060 OK (10 ms) Cached RT
8010338/8010338 (Unspecified) D Yes Yes 0 OK (10 ms) Cached RT
8010338/8010338 177.44.191.130 D Yes Yes 5060 OK (13 ms) Cached RT
8010338/8010338 (Unspecified) D Yes Yes 0 OK (10 ms) Cached RT
8010338/8010338 (Unspecified) D Yes Yes 0 OK (10 ms) Cached RT
8010338/8010338 177.44.191.130 D Yes Yes 5060 OK (10 ms) Cached RT
8010338/8010338 177.44.191.130 D Yes Yes 5060 OK (10 ms) Cached RT
8010338/8010338 (Unspecified) D Yes Yes 0 OK (10 ms) Cached RT
8010338/8010338 (Unspecified) D Yes Yes 0 OK (10 ms) Cached RT

If you can reproduce this problem with a supported version of Asterisk (18+)
then you may get some assistance here.

Also, explaining some detail about your network setup, and also telling us
what type of device is doing the registering, would help.

Antony.

1 Like

Hi Antony!

Unfortunately I can’t reproduce the scenario in version 18+, since my system only uses version 13.38.

Regarding the network and topology, it is another Asterisk also in this version that is registered in this peer.

configuration:

image

Both machines have NAT service

Remembering that we also have the registration string. But it is set in this field in another field.

I believe it is not something related to the network or the peer that is registered, but it seems to be a bug in asterisk

Entirely possible it is.

1 Like

If you use an end of life version, or a deprecated channel driver, you need to accept that, if things go wrong, you will need to do your own source level debugging and fixing.

It’s unlikely that anything like this will ever get fixed on chan_sip, and unlikely that anyone will even look into it on a driver with core support, unless you either reproduce it on Asterisk 18 or later, or you provide an analysis of the underlying cause and a rationale for why it is still a problem in current versions. Even then, you are likely to have to do the back port to Asterisk 13, yourself.

If it is a bug and no-one has found it already, it is not affecting enough people to get any priority.

1 Like

Thank Guys!

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.