DrayTek UK Users' Community Forum

Help, Advice and Solutions from DrayTek Users

SIP account registration failing with Sky ADSL Broadband

  • rp8049
  • Topic Author
  • Offline
  • New Member
  • New Member
More
05 May 2011 16:45 #1 by rp8049
At my old address, I was running Virgin cable broadband with my 2820Vn and my SIP account for Draytel always registered with no problems and VOIP was working perfectly. I've just moved, and can't get Virgin, so have switched to Sky ADSL and now the SIP account won't register for love nor money. I'm pretty sure that the problem isn't that Sky is blocking the ports for VOIP as I've downloaded X-Lite software and that will connect to my Draytel account no problems.

Has anyone else had any issues with a Draytek 2820Vn not being able to register SIP accounts using Sky ADSL? I've tried setting the SIP account to register specifically via WAN1, and also to "Auto", but nothing seems to solve the issue, it just doesn't want to register. I've updated to the latest 3.3.5 firmware (was running the 3.3.4 firmware from last October), but that also has not helped solve the situation.

I'm about to try some other SIP accounts from different providers to check if the problem is specifically related to Draytel, but I can't imagine that it is.

Any help/advice much appreciated!

Please Log in or Create an account to join the conversation.

  • rp8049
  • Topic Author
  • Offline
  • New Member
  • New Member
More
05 May 2011 17:35 #2 by rp8049
I've checked the voip logs, and gotten the following (with relevant private info altered of course!):

-->Send Message to 217.14.132.183:5060 <17:26:15>
REGISTER sip:draytel.org SIP/2.0
Via: SIP/2.0/UDP **.*.**.***:5060;branch=z9hG4bK-tcm-26863;rport
From: my account <sip:12345678@draytel.org>;tag=gqc-18555
To: <sip:12345678@draytel.org>
Call-ID: eCg-13862@**.*.**.***
CSeq: 123 REGISTER
Contact: <sip:12345678@**.*.**.***>
Max-Forwards: 70
Expires: 3600
User-Agent: DrayTek UA-1.2.3 Vigor2820 Series 3.3.5.2_232201
Content-Length: 0


<--Receive Message from 217.14.132.183:5060 <17:26:15>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP **.*.**.***:5060;branch=z9hG4bK-tcm-26863;rport=5060
From: my account <sip:12345678@draytel.org>;tag=gqc-18555
To: <sip:12345678@draytel.org>
Call-ID: eCg-13862@**.*.**.***
CSeq: 123 REGISTER
Server: OpenSIPS (1.5.1-notls (x86_64/linux))
Content-Length: 0


<--Receive Message from 217.14.132.183:5060 <17:26:15>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP **.*.**.***:5060;branch=z9hG4bK-tcm-26863;rport=5060
From: my account <sip:12345678@draytel.org>;tag=gqc-18555
To: <sip:12345678@draytel.org>;tag=dea7ace6b651c43aa467a5e170703289.2532
Call-ID: eCg-13862@**.*.**.***
CSeq: 123 REGISTER
WWW-Authenticate: Digest realm="draytel.org", nonce="4dc2cfd0eb626ea44d7397c5520fb1fe6c328cf5"
Server: OpenSIPS (1.5.1-notls (x86_64/linux))
Content-Length: 0


-->Send Message to 217.10.79.23:5060 <17:27:23>
REGISTER sip:sipgate.co.uk SIP/2.0
Via: SIP/2.0/UDP **.*.**.***:5060;branch=z9hG4bK-mkc-10512;rport
From: my account <sip:87654321@sipgate.co.uk>;tag=bgf-18724
To: <sip:87654321@sipgate.co.uk>
Call-ID: PWS-9173@**.*.**.***
CSeq: 124 REGISTER
Contact: <sip:87654321@**.*.**.***>
Max-Forwards: 70
Expires: 3600
User-Agent: DrayTek UA-1.2.3 Vigor2820 Series 3.3.5.2_232201
Content-Length: 0


<--Receive Message from 217.10.79.23:5060 <17:27:23>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP **.*.**.***:5060;branch=z9hG4bK-mkc-10512;rport=5060
From: my account <sip:87654321@sipgate.co.uk>;tag=bgf-18724
To: <sip:87654321@sipgate.co.uk>;tag=e6312186bd5c2eb4571f6550243cfacc.244a
Call-ID: PWS-9173@**.*.**.***
CSeq: 124 REGISTER
WWW-Authenticate: Digest realm="sipgate.co.uk", nonce="4dc2d123a081f90d5aef4ce9c7ef93b5ef130237"
Content-Length: 0

So it's able to contact the sip servers, but then not authenticating, either for my draytel account, or for another sipgate account I set up a while ago to check issues weren't with one account!

I can log into these accounts fine with the same username/password etc... using x-lite, so something is wrong on the draytek end?!

Please Log in or Create an account to join the conversation.

  • rp8049
  • Topic Author
  • Offline
  • New Member
  • New Member
More
05 May 2011 17:55 #3 by rp8049
Ok, finally managed to solve the problem - it seems that inputing the MAC of the sky router into the setup for WAN1 has solved the problem. Slightly strange since the internet connection etc... was already there, but hey ho, for whatever reason, it's now working!

Panic over!

Please Log in or Create an account to join the conversation.