Upper Registration to sipgate.de with AVM Fritzbox

laslo · Brekeke Member Joined: 20 Jan 2009 Posts: 10

1. Brekeke Product Name and version:
2.2.6.2/276

2. Java version:
1.6.0_07

3. OS type and the version:
FreeBSD 7.0-RELEASE

4. UA (phone), gateway or other hardware/software involved:
Fritzbox 7170

5. Select your network pattern from http://www.brekeke-sip.com/bbs/network/networkpatterns.html :
Pattern 4

6. Your problem:
Hi,
we have different UA behind NAT Routers connected to BSS, which works as Proxy (Upper Registration) to sipgate.de. With Grandstream Devices (for example: HT286) we have no problem. If Fritzbox is the UA it cant connect to sipgate.de with the Failure Code: 403 Registration Failed becaus of Forbidden (translated from german). Here is the log from BSS.:

Quote:
listener: debug: remote=192.168.209.70:5060 at Wed Jan 21 17:26:38 CET 2009
==============================================
REGISTER sip:10.116.0.200 SIP/2.0
Via: SIP/2.0/UDP 192.168.209.70:5060;branch=z9hG4bK2C031CE9E14F8685
Route: <sip:10.116.0.200:5080;lr>
From: <sip:2284755@10.116.0.200>;tag=2788842811
To: <sip:2284755@10.116.0.200>
Call-ID: C600108D69201975@192.168.178.1
CSeq: 1 REGISTER
Max-Forwards: 70
User-Agent: AVM FRITZ!Box Fon WLAN 7170 29.04.22 (Sep 6 2006)
Supported: 100rel,replaces
Allow-Events: telephone-event,refer
Allow: INVITE,ACK,OPTIONS,CANCEL,BYE,UPDATE,PRACK,INFO,SUBSCRIBE,NOTIFY,REFER,MESSAGE
Accept: application/sdp, multipart/mixed
Accept-Encoding: identity
Content-Length: 0

==============================================
register.8: processing: rule=register
register.8: recv: at Wed Jan 21 17:26:39 CET 2009
==============================================
REGISTER sip:10.116.0.200 SIP/2.0
Via: SIP/2.0/UDP 192.168.209.70:5060;branch=z9hG4bK2C031CE9E14F8685;rport=5060
Route: <sip:10.116.0.200:5080;lr>
From: <sip:2284755@10.116.0.200>;tag=2788842811
To: <sip:2284755@10.116.0.200>
Call-ID: C600108D69201975@192.168.178.1
CSeq: 1 REGISTER
Max-Forwards: 70
User-Agent: AVM FRITZ!Box Fon WLAN 7170 29.04.22 (Sep 6 2006)
Supported: 100rel,replaces
Allow-Events: telephone-event,refer
Allow: INVITE,ACK,OPTIONS,CANCEL,BYE,UPDATE,PRACK,INFO,SUBSCRIBE,NOTIFY,REFER,MESSAGE
Accept: application/sdp, multipart/mixed
Accept-Encoding: identity
Content-Length: 0

==============================================

register.8: target=local upper(217.10.79.9:5060)
register.8: upper: send to server: to=217.10.79.9:5060(UDP) at Wed Jan 21 17:26:39 CET 2009
==============================================
REGISTER sip:sipgate.de SIP/2.0
Via: SIP/2.0/UDP 91.17.49.48:5080;rport;branch=z9hG4bKd28ebfa89af51814319d8
Route: <sip:10.116.0.200:5080;lr>
From: <sip:2284755@sipgate.de>;tag=2788842811
To: <sip:2284755@sipgate.de>
Call-ID: 549f0a11-f05e6384-6322347b-be297e67@91.17.49.48
CSeq: 1 REGISTER
Max-Forwards: 69
User-Agent: AVM FRITZ!Box Fon WLAN 7170 29.04.22 (Sep 6 2006)
Supported: 100rel,replaces
Allow-Events: telephone-event,refer
Allow: INVITE,ACK,OPTIONS,CANCEL,BYE,UPDATE,PRACK,INFO,SUBSCRIBE,NOTIFY,REFER,MESSAGE
Accept: application/sdp, multipart/mixed
Accept-Encoding: identity
Content-Length: 0

==============================================

listener: debug: remote=192.168.209.70:5060 at Wed Jan 21 17:26:39 CET 2009
==============================================
REGISTER sip:10.116.0.200 SIP/2.0
Via: SIP/2.0/UDP 192.168.209.70:5060;branch=z9hG4bK2C031CE9E14F8685
Route: <sip:10.116.0.200:5080;lr>
From: <sip:2284755@10.116.0.200>;tag=2788842811
To: <sip:2284755@10.116.0.200>
Call-ID: C600108D69201975@192.168.178.1
CSeq: 1 REGISTER
Max-Forwards: 70
User-Agent: AVM FRITZ!Box Fon WLAN 7170 29.04.22 (Sep 6 2006)
Supported: 100rel,replaces
Allow-Events: telephone-event,refer
Allow: INVITE,ACK,OPTIONS,CANCEL,BYE,UPDATE,PRACK,INFO,SUBSCRIBE,NOTIFY,REFER,MESSAGE
Accept: application/sdp, multipart/mixed
Accept-Encoding: identity
Content-Length: 0

==============================================
listener: debug: remote=217.10.79.9:5060 at Wed Jan 21 17:26:39 CET 2009
==============================================
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 91.17.49.48:5080;rport=61618;branch=z9hG4bKd28ebfa89af51814319d8
From: <sip:2284755@sipgate.de>;tag=2788842811
To: <sip:2284755@sipgate.de>;tag=e6312186bd5c2eb4571f6550243cfacc.90ab
Call-ID: 549f0a11-f05e6384-6322347b-be297e67@91.17.49.48
CSeq: 1 REGISTER
Content-Length: 0

==============================================
register.8: upper: recv res from server: at Wed Jan 21 17:26:39 CET 2009
==============================================
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 91.17.49.48:5080;rport=61618;branch=z9hG4bKd28ebfa89af51814319d8
From: <sip:2284755@sipgate.de>;tag=2788842811
To: <sip:2284755@sipgate.de>;tag=e6312186bd5c2eb4571f6550243cfacc.90ab
Call-ID: 549f0a11-f05e6384-6322347b-be297e67@91.17.49.48
CSeq: 1 REGISTER
Content-Length: 0

==============================================

register.8: upper: recv res=403 from server
register.8: upper: failed: send response=403: error
register.8: close
management.8: close: register: from=sip:2284755@10.116.0.200

listener: debug: remote=192.168.209.70:5060 at Wed Jan 21 17:26:39 CET 2009
==============================================
REGISTER sip:10.116.0.200 SIP/2.0
Via: SIP/2.0/UDP 192.168.209.70:5060;branch=z9hG4bKB5FEBC1F73835C46
Route: <sip:10.116.0.200:5080;lr>
From: <sip:2284755@10.116.0.200>;tag=2788842811
To: <sip:2284755@10.116.0.200>
Call-ID: C600108D69201975@192.168.178.1
CSeq: 2 REGISTER
Contact: <sip:2284755@192.168.209.70;uniq=603EC99E55A6AFF7FEAB24D956D92>
Expires: 1800
Max-Forwards: 70
User-Agent: AVM FRITZ!Box Fon WLAN 7170 29.04.22 (Sep 6 2006)
Supported: 100rel,replaces
Allow-Events: telephone-event,refer
Allow: INVITE,ACK,OPTIONS,CANCEL,BYE,UPDATE,PRACK,INFO,SUBSCRIBE,NOTIFY,REFER,MESSAGE
Accept: application/sdp, multipart/mixed
Accept-Encoding: identity
Content-Length: 0

==============================================
register.9: processing: rule=register
register.9: recv: at Wed Jan 21 17:26:39 CET 2009
==============================================
REGISTER sip:10.116.0.200 SIP/2.0
Via: SIP/2.0/UDP 192.168.209.70:5060;branch=z9hG4bKB5FEBC1F73835C46;rport=5060
Route: <sip:10.116.0.200:5080;lr>
From: <sip:2284755@10.116.0.200>;tag=2788842811
To: <sip:2284755@10.116.0.200>
Call-ID: C600108D69201975@192.168.178.1
CSeq: 2 REGISTER
Contact: <sip:2284755@192.168.209.70;uniq=603EC99E55A6AFF7FEAB24D956D92>
Expires: 1800
Max-Forwards: 70
User-Agent: AVM FRITZ!Box Fon WLAN 7170 29.04.22 (Sep 6 2006)
Supported: 100rel,replaces
Allow-Events: telephone-event,refer
Allow: INVITE,ACK,OPTIONS,CANCEL,BYE,UPDATE,PRACK,INFO,SUBSCRIBE,NOTIFY,REFER,MESSAGE
Accept: application/sdp, multipart/mixed
Accept-Encoding: identity
Content-Length: 0

==============================================

register.9: target=local upper(217.10.79.9:5060)
register.9: upper: send to server: to=217.10.79.9:5060(UDP) at Wed Jan 21 17:26:39 CET 2009
==============================================
REGISTER sip:sipgate.de SIP/2.0
Via: SIP/2.0/UDP 91.17.49.48:5080;rport;branch=z9hG4bKab730838f749c914319d8
Route: <sip:10.116.0.200:5080;lr>
From: <sip:2284755@sipgate.de>;tag=2788842811
To: <sip:2284755@sipgate.de>
Call-ID: 549f0a11-f05e6384-6322347b-be297e67@91.17.49.48
CSeq: 2 REGISTER
Contact: <sip:2284755@91.17.49.48:5080>
Expires: 1800
Max-Forwards: 69
User-Agent: AVM FRITZ!Box Fon WLAN 7170 29.04.22 (Sep 6 2006)
Supported: 100rel,replaces
Allow-Events: telephone-event,refer
Allow: INVITE,ACK,OPTIONS,CANCEL,BYE,UPDATE,PRACK,INFO,SUBSCRIBE,NOTIFY,REFER,MESSAGE
Accept: application/sdp, multipart/mixed
Accept-Encoding: identity
Content-Length: 0

If the BSS is not involved there is no problem with regstration.

thx,
laslo

Tata · Brekeke Master Guru Joined: 27 Jan 2008 Posts: 223

Are you using BSS on FreeBSD ?
Which Java VM are you using?

laslo · Brekeke Member Joined: 20 Jan 2009 Posts: 10

Hi,
yes iam using Brekeke SIP Server on FreeBSD.

java-ver: 1.6.0_07

james · Brekeke Master Guru Joined: 10 Dec 2007 Posts: 501

Hi laslo,

It seems Fritzbox includes "Route: <sip:10.116.0.200:5080;lr>" header in the REGISTER request. It will be a cause.

Remove it by the DialPlan.

Matching Patterns

$request = ^REGISTER
Route = .+

Deploy Patterns

Route = 
$action = register

laslo · Brekeke Member Joined: 20 Jan 2009 Posts: 10

Hi james,

thanks for the fast reply. I add the rule "Fritzbox" to the Dialplan as you say and it work now. I will test tomorrow, because i cant call my customers at 00:06 here in Germany Smile

.

I test the BSS with 3x Customers (2x ATA286, 1x Fritzbox 7170) and it worked. But in some cases the first 2-3 seconds from the call is lost. Are there any options to avoid that. In this conext i must they that the BSS is installed on a squid proxy for testing. A new machine is already orderd (P4 2,4 GHz, 1 GB Ram), will this suitable for 15 - 30 customers. In Peak times maybe 3-5 calles runs concurrent.

Here is a extract from the log file. I hope it is ok to post log files in this length here in the forum.

james · Brekeke Master Guru Joined: 10 Dec 2007 Posts: 501

Hi laslo,

>> But in some cases the first 2-3 seconds from the call is lost.

Was it a call with a analogue line?
It may be a negotiating period...
(You may tune it in settings of a device...)

If you use a VoIP phone or softphone, such a issue will not happen.

laslo · Brekeke Member Joined: 20 Jan 2009 Posts: 10

>>Was it a call with a analogue line?
sorry i am not sure what you mean exactly. The Test Customers have analogue telefon devices on their ata´s. They always call over the internet, because they have no analogue line.

>>It may be a negotiating period...
>>(You may tune it in settings of a device...)
on what device the cononfiuration/setting is needed? on the ata device or analogue telefon device?

thanks,

laslo

james · Brekeke Master Guru Joined: 10 Dec 2007 Posts: 501

>> on what device the cononfiuration/setting is needed? on the ata device or analogue telefon device?

It depends on devices...

Did you try the softphone (X-Lite) ?
I think you will not experience the problem from a softphone because the problem will be related with an ATA and Fritzbox ..

laslo · Brekeke Member Joined: 20 Jan 2009 Posts: 10

>>It depends on devices...

>>Did you try the softphone (X-Lite) ?
>>I think you will not experience the problem from a softphone >>because the problem will be related with an ATA and Fritzbox ..

thanks for reply. i found the problem, it was related to one WLAN P2P Link in our backbone.

best regards,

laslo

james · Brekeke Master Guru Joined: 10 Dec 2007 Posts: 501

Did you solve the issue?
If so, that is nice.