NO JOY AAstra`s wont register

[atsak]

I have a few AAstra phones on one system located in a remote office connecting over VPN. There was a brief network interruption last night, and since the VPN came back up, they all return 408 no reply. I checked on the firewall and the traffic traverses it properly (I see it both on the outbound and inbound) but I see nothing in the asterisk console and fail2ban - iptables isn`t running.

Ideas please!!!

 

[islandtech]

A similar thing happened to me with yealink phones. Rebooted the phones and all was well.

 

[atsak]

Oh yes, the phones have been rebooted, factory reset, etc etc.

 

[atsak]

Here's the SIP debug - why is this getting 401 unauthorized?

<--- SIP read from UDP:10.3.0.142:5060 --->
REGISTER sip:10.1.3.1:5060 SIP/2.0
Via: SIP/2.0/UDP 10.3.0.142:5060;branch=z9hG4bK11396d75eb5562272
Max-Forwards: 70
From: "540" <sip:[email protected]:5060>;tag=a939f2d321
To: "540" <sip:[email protected]:5060>
Call-ID: 6c76bfcaa942dd72
CSeq: 22109 REGISTER
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, UPDATE, PRACK, SUBSCRIBE, INFO
Allow-Events: talk, hold, conference, LocalModeStatus
Contact: "540" <sip:[email protected]:5060;transport=udp>;+sip.instance="<urn:uuid:00000000-0000-1000-8000-00085D31E9DE>";expires=300
Supported: path, gruu
User-Agent: Aastra 6731i/3.3.1.4305
Content-Length: 0
 
<------------->
--- (13 headers 0 lines) ---
Sending to 10.3.0.142:5060 (no NAT)
 
<--- Transmitting (no NAT) to 10.3.0.142:5060 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 10.3.0.142:5060;branch=z9hG4bK11396d75eb5562272;received=10.3.0.142
From: "540" <sip:[email protected]:5060>;tag=a939f2d321
To: "540" <sip:[email protected]:5060>;tag=as4c02ed30
Call-ID: 6c76bfcaa942dd72
CSeq: 22109 REGISTER
Server: FPBX-2.11.0(11.14.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="2cd34a4c"
Content-Length: 0

 

[gpuser]

Here's the SIP debug - why is this getting 401 unauthorized?

401 unauthorized is a normal first response from server against a register request. Do you have the next reply from the endpoint?

1. UA sends register request
2. Server responds with realm, nonce, crypto and 401 asking for auth details
3. UA sends auth details mixing them with nonce as per the encryption required.
4. Server sends 200 ok upon receiving correct auth.

So please post packets in steps 3 and 4 from above.

Also, what subnet mask are you using?

What runs the VPN server?

 

[atsak]

So this ended up being a firewall problem. The traffic was passing to the server but was being lost when transiting back due to a stale routing table entry on the Juniper; the phone never got the nonce reply. I could not actually clear the entry, so I had to reboot the firewall. Very strange, it affected only Aastra phones and only 6 of 7 of them.

Thanks for the help.