The log doesn’t show a failure to authenticate, but rather a request to supply authentication.
The failure is in that the phone doesn’t then try to authenticate, which generally means it hasn’t been told how to do so, i.e. no credential, that it can use, have been configured in it.
Whilst it is unusual for phones not to have credentials, this could happen if the phone, was not configured at all in Asterisk (e.g. no type=endpoint named 20010, and no type=identify for 192.168,10,86, associated with a valid enpdoint).
likely a firewall rule check your router for sip alg and make sure it’s off, and make sure you have proper ports open in your router, some ISP will block port 5060
Hi, I’m going crazy,I changed the IP range of both the server and the phones to see if that was it but no, the phones’ IPs are not in the same range as the server’s IP, the server’s firewall is disabled, I don’t understand why it doesn’t register.is it from asterisk?
Hi, I’m going crazy,I changed the IP range of both the server and the
phones to see if that was it but no, the phones’ IPs are not in the
same range as the server’s IP, the server’s firewall is disabled, I
don’t understand why it doesn’t register.is it from asterisk?
likely a firewall rule check your router for sip alg and make sure
it’s off, and make sure you have proper ports open in your router,
some ISP will block port 5060
hi appears this tcpdump -i any -c5 src 192.168.2.86
tcpdump: data link type LINUX_SLL2
dropped privs to tcpdump
tcpdump: verbose output suppressed, use -v[v]… for full protocol decode
listening on any, link-type LINUX_SLL2 (Linux cooked v2), snapshot length 262144 bytes
16:25:33.412571 eno1 In IP SIP-T46G.localdomain.sip > srv3.localdomain.sip: SIP: REGISTER sip:192.168.2.173:5060 SIP/2.0
16:25:33.423291 eno1 In IP SIP-T46G.localdomain.sip > srv3.localdomain.sip: SIP: REGISTER sip:192.168.2.173:5060 SIP/2.0
16:25:33.444330 eno1 In IP SIP-T46G.localdomain.sip > srv3.localdomain.sip: SIP: REGISTER sip:192.168.2.173:5060 SIP/2.0
16:25:33.455075 eno1 In IP SIP-T46G.localdomain.sip > srv3.localdomain.sip: SIP: REGISTER sip:192.168.2.173:5060 SIP/2.0
16:25:33.476299 eno1 In IP SIP-T46G.localdomain.sip > srv3.localdomain.sip: SIP: REGISTER sip:192.168.2.173:5060 SIP/2.0
5 packets captured
8 packets received by filter
0 packets dropped by kernel
hi appears this tcpdump -i any -c5 src 192.168.2.86
tcpdump: data link type LINUX_SLL2
dropped privs to tcpdump
tcpdump: verbose output suppressed, use -v[v]… for full protocol decode
listening on any, link-type LINUX_SLL2 (Linux cooked v2), snapshot
length 262144 bytes
16:25:33.412571 eno1 In IP SIP-T46G.localdomain.sip >
srv3.localdomain.sip: SIP: REGISTER sip:192.168.2.173:5060 SIP/2.0
16:25:33.423291 eno1 In IP SIP-T46G.localdomain.sip >
srv3.localdomain.sip: SIP: REGISTER sip:192.168.2.173:5060 SIP/2.0
16:25:33.444330 eno1 In IP SIP-T46G.localdomain.sip >
srv3.localdomain.sip: SIP: REGISTER sip:192.168.2.173:5060 SIP/2.0
16:25:33.455075 eno1 In IP SIP-T46G.localdomain.sip >
srv3.localdomain.sip: SIP: REGISTER sip:192.168.2.173:5060 SIP/2.0
16:25:33.476299 eno1 In IP SIP-T46G.localdomain.sip >
srv3.localdomain.sip: SIP: REGISTER sip:192.168.2.173:5060 SIP/2.0
5 packets captured
8 packets received by filter
0 packets dropped by kernel
Run tcpdump or sngrep to see if traffic is comming from your phones Le
07/10/2025 à 15:35, RDouro via Asterisk Community a écrit : [RDouro]
RDouro Profile - RDouro - Asterisk Community October 7 Hi, I’m going
crazy,I changed the IP range of both the server and the phones to see
if that was …