This is a bit of a weird one, but hoping it's an easy fix. The phone in this example was working successfully for months, and suddenly started to fail.
I get this message in the CLI when a phone attempts to register where it never registers:
[WARNING] sofia_reg.c:1792 SIP auth challenge (REGISTER) on sofia profile 'internal' for [503@domain] from ip
The phone in this case is a T-48s; however it happens between Yealink models as well as Grandstreams and Polycoms.
All phones that work successfully and those that have failed are programmed in the same way through Devices and the extension being assigned to it. From Yealink RPS we are pointing to the fusion server.
From the nginx access log all phones successfully take their configs.
This seems to happen at random and when I do a SIP trace I get this:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 10.100.106.61:5062;rport=56272;branch=z9hG4bK1252481716;received=ip
From: "502" <sip:502@domain>;tag=2068789286
To: "502" <sip:502@domain>;tag=v3KN1m4rtUmjF
Call-ID: 1814388748@10.100.106.61
CSeq: 1 REGISTER
User-Agent: FreeSWITCH
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE
Supported: timer, path, replaces
WWW-Authenticate: Digest realm="domain", nonce="f04d61de-88e4-43da-80f9-8104914efa27", algorithm=MD5, qop="auth"
Content-Length: 0
Given the 401 I have deleted the device and extension, re-creating both and it's the same.
I've also attempted switch between tcp and udp with and with stun to no avail, as well as manually programming the phones.
Fail2ban does not show the ip blocked, and no other errors are seen in any logs.
Suggestions?
I get this message in the CLI when a phone attempts to register where it never registers:
[WARNING] sofia_reg.c:1792 SIP auth challenge (REGISTER) on sofia profile 'internal' for [503@domain] from ip
The phone in this case is a T-48s; however it happens between Yealink models as well as Grandstreams and Polycoms.
All phones that work successfully and those that have failed are programmed in the same way through Devices and the extension being assigned to it. From Yealink RPS we are pointing to the fusion server.
From the nginx access log all phones successfully take their configs.
This seems to happen at random and when I do a SIP trace I get this:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 10.100.106.61:5062;rport=56272;branch=z9hG4bK1252481716;received=ip
From: "502" <sip:502@domain>;tag=2068789286
To: "502" <sip:502@domain>;tag=v3KN1m4rtUmjF
Call-ID: 1814388748@10.100.106.61
CSeq: 1 REGISTER
User-Agent: FreeSWITCH
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE
Supported: timer, path, replaces
WWW-Authenticate: Digest realm="domain", nonce="f04d61de-88e4-43da-80f9-8104914efa27", algorithm=MD5, qop="auth"
Content-Length: 0
Given the 401 I have deleted the device and extension, re-creating both and it's the same.
I've also attempted switch between tcp and udp with and with stun to no avail, as well as manually programming the phones.
Fail2ban does not show the ip blocked, and no other errors are seen in any logs.
Suggestions?