SIP 401 Errors from a remote location

FreePBX Endpoints
1

I have a group of phones that are failing to register on the server. In the asterisk logs or realtime asterisk, I see absolutely nothing. However, when I turn on TCP dump, I see the registration request hit the server and a 401 Unauthorized being returned but nothing with the asterisk log.

16:35:43.488317 IP 100.64.17.102.60240 > .sip: SIP: SUBSCRIBE sip:[email protected];transport=UDP SIP/2.0
16:35:43.488520 IP .sip > 100.64.17.102.60240: SIP: SIP/2.0 401 Unauthorized

I have checked all extension secrets etc (multiple times) and everything checks out. There are about a dozen phones doing this from one location [100.64.17.102 is their external address]. About 250 other phones are working just fine.

What am I missing?

2

Is not a REGISTER request

use sngrep not tcpdump , it will seperate the SIP conversations

3

The register requests come the same way… and never reach asterisk logs.

16:02:51.969619 IP 100.64.17.102.60240 > : SIP: REGISTER sip:;transport=UDP SIP/2.0
16:02:51.969959 IP .sip > 100.64.17.102.60240: SIP: SIP/2.0 401 Unauthorized

4

The Unauthorized response should trigger a second attempt to REGISTER

Use sngrep :wink:

5

You are right… it keeps trying and trying. I was trying to keep it simple:

16:02:42.549398 IP 172.21.25.75.49186 > .sip: SIP
16:02:51.969619 IP 100.64.17.102.60240 > .sip: SIP: REGISTER sip:;transport=UDP SIP/2.0
16:02:51.969959 IP .sip > 100.64.17.102.60240: SIP: SIP/2.0 401 Unauthorized
16:02:52.469526 IP 100.64.17.102.60240 > .sip: SIP: REGISTER sip:;transport=UDP SIP/2.0
16:02:52.469731 IP .sip > 100.64.17.102.60240: SIP: SIP/2.0 401 Unauthorized
16:02:53.469237 IP 100.64.17.102.60240 > .sip: SIP: REGISTER sip:;transport=UDP SIP/2.0
16:02:53.469446 IP .sip > 100.64.17.102.60240: SIP: SIP/2.0 401 Unauthorized
16:02:55.470364 IP 100.64.17.102.60240 > .sip: SIP: REGISTER sip:;transport=UDP SIP/2.0
16:02:55.470568 IP .sip > 100.64.17.102.60240: SIP: SIP/2.0 401 Unauthorized
16:02:59.469910 IP 100.64.17.102.60240 > .sip: SIP: REGISTER sip:;transport=UDP SIP/2.0
16:02:59.470115 IP .sip > 100.64.17.102.60240: SIP: SIP/2.0 401 Unauthorized

6

Look at the succesful REGISTER ones in sngrep (F7 to filter select just REGISTER) , see if you can DIFF them . . .

My guess is that the far end is rewriting your SIP headers SIP:;* likely wont match

7

Yes… done that. All the successful registrations are coming from non NAT’ed locations. The only ones giving me this grief are from a location where the phone’s

8

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