Hey Everyone, I'm not sure if this is an Astlinux issue per se, but I'm confused to as possible causes and was hoping someone might have an idea...
I've been using a particular SIP provider for about 5 years now with zero issues. All of a sudden over the weekend when I tried to make a phone call, I realized something wasn't working. Looking at the Asterisk logs, I saw something like this: [Sep 10 15:19:30] NOTICE[17481]: chan_sip.c:13668 sip_reg_timeout: -- Registration for '12345...@sip.provider.com' timed out, trying again (Attempt #14987) At first I figured it was something simple, so I did all the basic troubleshooting. Tried restarting Asterisk, checking DNS, checking general connectivity to the host, restarting the PBX, etc. Everything looked fine. I opened up a ticket with the provider and while I was waiting for a call back I tried changing the host I was connecting to. The provider recommends connecting to sip.provider.com, which (for me) has always resolved to sip-lv1.provider.com. They also offer sip-la1.provider.com. I assume the general 'sip' is used for load-balancing, geo-location routing, etc. In any case, when I pointed the SIP registration to the other server, I noticed it immediately registered. Just then I got a call back from the provider's support group. We did some testing and he examined some logs on his side, and he said that he was seeing my registration attempts, and their server was sending back the 401 with the nonce and authentication request, but my server would never answer. It simply kept sending the same registration request over and over again. In fact, this went beyond just registration. I had forgotten to change my dialplan so when I tried doing a test call to the old server, it failed as well for the same reason (not responding properly to the 401). As long as I point it to the other server, everything works fine. I am also connected to a different provider which works fine. The only difference in the configuration is the hostname of the peer, and I tried both 'sip' and 'sip-lv1' (both resolve to the same IP) -- neither work anymore. Nothing on my side changed. Configuration has been static for over a year. My public IP might have changed recently (FiOS made a network topology move), but I see the traffic flowing properly, at least network wise, so I don't think that is the cause. I was running Astlinux 1.2.6, but just tried upgrading to 1.2.7 to see if that would help (it didn't). Here is a sanitized for public viewing example of what my packet capture is showing: --==-- REGISTER sip:sip-lv1.provider.com SIP/2.0 Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK79cdf3e6;rport Max-Forwards: 70 From: <sip:usern...@sip-lv1.provider.com>;tag=as32391879 To: <sip:usern...@sip-lv1.provider.com> Call-ID: 0876e62f7f6ca042670b64d16cfe4...@voip.domain.com CSeq: 102 REGISTER User-Agent: Routed/AstlinuxPBX Expires: 120 Contact: <sip:s@1.1.1.1:5060> Content-Length: 0 SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK79cdf3e6;rport=5060 From: <sip:usern...@sip-lv1.provider.com>;tag=as32391879 To: <sip:usern...@sip-lv1.provider.com >;tag=aa681f9fdf30149b00040f579a1d99c4.c445 Call-ID: 0876e62f7f6ca042670b64d16cfe4...@voip.domain.com CSeq: 102 REGISTER WWW-Authenticate: Digest realm="sip.provider.com", nonce="V9hNmlfYTG7oDzmi4HvYzc7Q+IaLBbID", qop="auth" Content-Length: 0 REGISTER sip:sip-lv1.provider.com SIP/2.0 Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK79cdf3e6;rport Max-Forwards: 70 From: <sip:usern...@sip-lv1.provider.com>;tag=as32391879 To: <sip:usern...@sip-lv1.provider.com> Call-ID: 0876e62f7f6ca042670b64d16cfe4...@voip.domain.com CSeq: 102 REGISTER User-Agent: Routed/AstlinuxPBX Expires: 120 Contact: <sip:s@1.1.1.1:5060> Content-Length: 0 SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK79cdf3e6;rport=5060 From: <sip:usern...@sip-lv1.provider.com>;tag=as32391879 To: <sip:usern...@sip-lv1.provider.com >;tag=aa681f9fdf30149b00040f579a1d99c4.c445 Call-ID: 0876e62f7f6ca042670b64d16cfe4...@voip.domain.com CSeq: 102 REGISTER WWW-Authenticate: Digest realm="sip.provider.com", nonce="V9hNmlfYTG7oDzmi4HvYzc7Q+IaLBbID", qop="auth" Content-Length: 0 (repeated over and over) --==-- As you can see, the Astlinux box is simply ignoring the request for authentication. But for the alternate server, which works, it looks fine: --==-- REGISTER sip:sip-la1.provider.com SIP/2.0 Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK1ef0533f;rport Max-Forwards: 70 From: <sip:usern...@sip-la1.provider.com>;tag=as1bf2e5de To: <sip:usern...@sip-la1.provider.com> Call-ID: 21867bc103d1d1926e2329ec3df1a...@voip.domain.com CSeq: 102 REGISTER User-Agent: Routed/AstlinuxPBX Expires: 120 Contact: <sip:s@1.1.1.1:5060> Content-Length: 0 SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK1ef0533f;rport=5060 From: <sip:usern...@sip-la1.provider.com>;tag=as1bf2e5de To: <sip:usern...@sip-la1.provider.com >;tag=aa681f9fdf30149b00040f579a1d99c4.7b31 Call-ID: 21867bc103d1d1926e2329ec3df1a...@voip.domain.com CSeq: 102 REGISTER WWW-Authenticate: Digest realm="sip.provider.com", nonce="V9hNmlfYTG7oDzmi4HvYzc7Q+IaLBbID", qop="auth" Content-Length: 0 REGISTER sip:sip-la1.provider.com SIP/2.0 Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK17fa62b3;rport Max-Forwards: 70 From: <sip:usern...@sip-la1.provider.com>;tag=as1bf2e5de To: <sip:usern...@sip-la1.provider.com> Call-ID: 21867bc103d1d1926e2329ec3df1a...@voip.domain.com CSeq: 103 REGISTER User-Agent: Routed/AstlinuxPBX Authorization: Digest username="USERNAME", realm="sip.provider.com", algorithm=MD5, uri="sip:sip-la1.provider.com", nonce="V9hNmlfYTG7oDzmi4HvYzc7Q+IaLBbID", response="a0bffe6ad0e6f5987f59e8d239c38cd9", qop=auth, cnonce="0f45b71a", nc=00000001 Expires: 120 Contact: <sip:s@1.1.1.1:5060> Content-Length: 0 SIP/2.0 200 OK Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK17fa62b3;rport=5060 From: <sip:usern...@sip-la1.provider.com>;tag=as1bf2e5de To: <sip:usern...@sip-la1.provider.com >;tag=aa681f9fdf30149b00040f579a1d99c4.7473 Call-ID: 21867bc103d1d1926e2329ec3df1a...@voip.domain.com CSeq: 103 REGISTER Contact: <sip:s@1.1.1.1:5060>;q=1;expires=120;received="sip:1.1.1.1:5060" Content-Length: 0 --==-- The only difference between example #1 and #2 is the remote hostname. I don't see any issues in the logs, debug, etc. I am baffled as to why I would only be experiencing this issue on one server, with everything else being equal. Has anyone else had a similar problem or have an idea what else I can do to troubleshoot? Thanks! --James
------------------------------------------------------------------------------
_______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
