Recurrent issues with VOIP

[GoogleCodeExporter]

What steps will reproduce the problem?

1. Register VOIP on my ISP 
2. Wait for the lease to expire
3. Bang! The problem appears. The only way to sort this, is by re-registering 
the voip service.

What is the expected output? What do you see instead?
- It was supposed to keep the voip service registration working after it 
expired.

What version of the product are you using? On what operating system?

- Draytek 2130 v1.5.2_RC4 (v2130_r2764) 

Please provide any additional information below.

Every time my voip service is re-registered, although the registration is 
accepted by my ISP, the draytek 2130 keeps asking for a registration which 
after 5 registration requests, my ISP blocks the voip service for around 3600 
seconds or such...

Here are the details from extracted from the sip_trace:

----------------------------------------------------------------------

at May 12 16:43:33 2012
=== Send Message ==> to 213.30.59.133:5060
REGISTER sip:ims.vodafone.pt SIP/2.0
Via: SIP/2.0/UDP 10.168.14.127:5060;branch=z9hG4bK-ije-1273708123;rport
From: 211932360 <sip:+************@ims.vodafone.pt>;tag=ije-1273708122
To: <sip:+************@ims.vodafone.pt>
Call-ID: jtO-1105833162@10.168.14.127
CSeq: 116 REGISTER
Contact: <sip:+************@10.168.14.127>
Max-Forwards: 15
Expires: 3600
User-Agent: DrayTek UA-1.2.3 draytek2130 v1.5.2_RC4
Content-Length: 0

Sat May 12 16:43:33 2012
<== Receive Message === from 213.30.59.133:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 
10.168.14.127:5060;received=10.168.14.127;branch=z9hG4bK-ije-1273708123;rport
From: 211932360 <sip:+************@ims.vodafone.pt>;tag=ije-1273708122
To: <sip:+************@ims.vodafone.pt>;tag=1e2758630393620570a44e57e41b77b1
Call-ID: jtO-1105833162@10.168.14.127
CSeq: 116 REGISTER
Content-Length: 0
Contact: <sip:+************@10.168.14.127>;expires=3600
P-Associated-URI: <sip:+************@ims.vodafone.pt>
P-Associated-URI: <tel:+************>
P-Charging-Vector: icid-value=1e2758630393620570a44e57e416c47f
P-Charging-Function-Addresses: 
ccf="aaa://ALF1MM.ims.vodafone.pt:3868;transport=tcp"

Sat May 12 16:43:37 2012
=== Send Message ==> to 213.30.59.133:5060
REGISTER sip:ims.vodafone.pt SIP/2.0
Via: SIP/2.0/UDP 10.168.14.127:5060;branch=z9hG4bK-CfV-1303436486;rport
From: 211932360 <sip:+************@ims.vodafone.pt>;tag=CfV-1303436485
To: <sip:+************@ims.vodafone.pt>
Call-ID: jtO-1105833162@10.168.14.127
CSeq: 115 REGISTER
Contact: <sip:+************@10.168.14.127>
Max-Forwards: 15
Expires: 3600
User-Agent: DrayTek UA-1.2.3 draytek2130 v1.5.2_RC4
Content-Length: 0

Sat May 12 16:43:41 2012
=== Send Message ==> to 213.30.59.133:5060
REGISTER sip:ims.vodafone.pt SIP/2.0
Via: SIP/2.0/UDP 10.168.14.127:5060;branch=z9hG4bK-CfV-1303436486;rport
From: 211932360 <sip:+************@ims.vodafone.pt>;tag=CfV-1303436485
To: <sip:+************@ims.vodafone.pt>
Call-ID: jtO-1105833162@10.168.14.127
CSeq: 115 REGISTER
Contact: <sip:+************@10.168.14.127>
Max-Forwards: 15
Expires: 3600
User-Agent: DrayTek UA-1.2.3 draytek2130 v1.5.2_RC4
Content-Length: 0

Sat May 12 16:43:45 2012
=== Send Message ==> to 213.30.59.133:5060
REGISTER sip:ims.vodafone.pt SIP/2.0
Via: SIP/2.0/UDP 10.168.14.127:5060;branch=z9hG4bK-CfV-1303436486;rport
From: 211932360 <sip:+************@ims.vodafone.pt>;tag=CfV-1303436485
To: <sip:+************@ims.vodafone.pt>
Call-ID: jtO-1105833162@10.168.14.127
CSeq: 115 REGISTER
Contact: <sip:+************@10.168.14.127>
Max-Forwards: 15
Expires: 3600
User-Agent: DrayTek UA-1.2.3 draytek2130 v1.5.2_RC4
Content-Length: 0

Sat May 12 16:43:50 2012
=== Send Message ==> to 213.30.59.133:5060
REGISTER sip:ims.vodafone.pt SIP/2.0
Via: SIP/2.0/UDP 10.168.14.127:5060;branch=z9hG4bK-CfV-1303436486;rport
From: 211932360 <sip:+************@ims.vodafone.pt>;tag=CfV-1303436485
To: <sip:+************@ims.vodafone.pt>
Call-ID: jtO-1105833162@10.168.14.127
CSeq: 115 REGISTER
Contact: <sip:+************@10.168.14.127>
Max-Forwards: 15
Expires: 3600
User-Agent: DrayTek UA-1.2.3 draytek2130 v1.5.2_RC4
Content-Length: 0

Sat May 12 16:43:58 2012
<== Receive Message === from 213.30.59.133:5060
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 
10.168.14.127:5060;received=10.168.14.127;branch=z9hG4bK-CfV-1303436486;rport
From: 211932360 <sip:+************@ims.vodafone.pt>;tag=CfV-1303436485
To: <sip:+************@ims.vodafone.pt>;tag=1e275863032ccb43b0a44e58464c8ea4
Call-ID: jtO-1105833162@10.168.14.127
CSeq: 115 REGISTER
Content-Length: 0
WWW-Authenticate: Digest 

realm="ims.vodafone.pt",domain="sip:ttcnserver@ims.vodafone.pt",nonce="d2cc87998
0843aee33b06e3eff716680",stale=false,qop="auth",algorithm=MD5
P-Charging-Vector: icid-value=1e275863032ccb43b0a44e582ada9557

----------------------------------------------------------------------

Explanation:

1. The voip service on the draytek at 16:43:33 sends a "REGISTER" request, to 
which my ISP answers at 16:43:33 (on the same second), with a "SIP/2.0 200 OK"

2. ...but for some dumb reason, the draytek keep sending afterwards, the same 
"REGISTER" requests, every 4 seconds...

3. ...until that (and after five received "REGISTER" requests on the ISP side), 
the ISP sees all this requests as a threat (probably an IDS) and starts sending 
a "SIP/2.0 401 Unauthorized" to my draytek...

4. ...and my voip phone service dies, meaning, the 1st registration ends and 
any attempt done to do a call will result in: 

----------------------------------------------------------------------
Sat May 12 16:55:13 2012
<== Receive Message === from 213.30.59.133:5060
SIP/2.0 403 Calling User Not Registered
Via: SIP/2.0/UDP 
10.168.14.127:5060;received=10.168.14.127;branch=z9hG4bK-Iam-366766899;rport
From: 211932360 <sip:+************@ims.vodafone.pt>;tag=Iam-366766897
To: <sip:00************@ims.vodafone.pt>;tag=02365eb5036c123890a44e629205553f
Call-ID: Iam-366766898@10.168.14.127
CSeq: 3 INVITE
Content-Length: 0
P-Charging-Vector: icid-value=02365eb5036c123890a44e6292052976
----------------------------------------------------------------------

Please see what is going on because i've been through dozens of beta (and 
official) firmwares and i'm really tired of all this voip issues that have been 
haunting me since day 1.

Original issue reported on code.google.com by Keepe...@gmail.com on 12 May 2012 at 5:38

[GoogleCodeExporter]

It seems CSeq is out of order
CSeq: 116 REGISTER arrive before 115 ?

You can also get more debug info by running daryvoip in foreground

# killall drayvoip ; drayvoip -l 7

Original comment by jht...@gmail.com on 25 Jun 2012 at 3:02

[GoogleCodeExporter]

This issue was sorted out during the last 1.5.2 builds.

This issue can now be closed.

Original comment by Keepe...@gmail.com on 13 Oct 2012 at 12:44