siproxd-0.7.0-4577 and Nokia N95 prob

Dear list members

I am running siproxd version 0.7.0-4577 on a pfSense box which is
FreeBSD based. Siproxd works great in conjunction with Ekiga, but when
it comes to my Nokia N95 there seems to fail something which I need help
on... There is no way to get connection with sipgate.de over the proxy 

Any hints on this? 

/sp4rc

$ cat siproxd.conf 
------------------------------------------------
if_inbound = vr1
if_outbound = vr0
sip_listen_port = 5060
daemonize = 0
silence_log = 0
log_calls = 1
user = nobody
chrootjail = /usr/local/siproxd/
registration_file = siproxd_registrations
pid_file = siproxd.pid
rtp_proxy_enable = 1
rtp_port_low = 7070
rtp_port_high = 7079
rtp_timeout = 300
default_expires = 600
debug_level = 0x00000000
------------------------------------------------


$ siproxd -d 1 
------------------------------------------------
20:57:44 register.c:508 sip_agemap, t=1227556664
20:57:46 register.c:508 sip_agemap, t=1227556666
20:57:47 siproxd.c:320 back from sipsock_wait
20:57:47 security.c:48 security_check_raw: size=450
20:57:47 register.c:238 sip_register:
20:57:47 siproxd.c:294 going into sipsock_wait

20:57:49 register.c:508 sip_agemap, t=1227556669
20:57:50 siproxd.c:320 back from sipsock_wait
20:57:50 security.c:48 security_check_raw: size=450
20:57:50 register.c:238 sip_register:
20:57:50 siproxd.c:294 going into sipsock_wait

20:57:52 register.c:508 sip_agemap, t=1227556672
20:57:54 register.c:508 sip_agemap, t=1227556674
20:57:56 register.c:508 sip_agemap, t=1227556676
20:57:56 siproxd.c:320 back from sipsock_wait
20:57:56 security.c:48 security_check_raw: size=450
20:57:56 register.c:238 sip_register:
20:57:56 siproxd.c:294 going into sipsock_wait

20:57:58 register.c:508 sip_agemap, t=1227556678
20:58:00 register.c:508 sip_agemap, t=1227556680
20:58:02 register.c:508 sip_agemap, t=1227556682
20:58:04 register.c:508 sip_agemap, t=1227556684
20:58:06 register.c:508 sip_agemap, t=1227556686
20:58:08 siproxd.c:320 back from sipsock_wait
20:58:08 security.c:48 security_check_raw: size=450
20:58:08 register.c:238 sip_register:
20:58:08 siproxd.c:294 going into sipsock_wait

20:58:10 register.c:508 sip_agemap, t=1227556690
20:58:12 register.c:508 sip_agemap, t=1227556692
20:58:14 register.c:508 sip_agemap, t=1227556694
------------------------------------------------

This is what a tcpdump shows:

$ tcpdump -i ath0 -n -p host 192.168.1.20
------------------------------------------------
20:56:21.224644 IP 217.10.77.22.37890 > 192.168.1.20.49152: UDP, length
172
20:56:21.240860 IP 217.10.77.22.37890 > 192.168.1.20.49152: UDP, length
172
20:56:21.256726 IP 217.10.77.22.37890 > 192.168.1.20.49152: UDP, length
172
20:56:21.256814 IP 192.168.1.20 > 217.10.77.22: ICMP 192.168.1.20 udp
port 49152 unreachable, length 36
20:56:21.259100 IP 192.168.1.20 > 217.10.77.22: ICMP 192.168.1.20 udp
port 49152 unreachable, length 36
20:56:21.261044 IP 192.168.1.20 > 217.10.77.22: ICMP 192.168.1.20 udp
port 49152 unreachable, length 36
20:56:21.272913 IP 217.10.77.22.37890 > 192.168.1.20.49152: UDP, length
172
20:56:21.273566 IP 192.168.1.20.5060 > 217.10.79.9.5060: SIP, length:
621
20:56:21.276265 IP 192.168.1.20 > 217.10.77.22: ICMP 192.168.1.20 udp
port 49152 unreachable, length 36
20:56:21.310743 IP 217.10.79.9.5060 > 192.168.1.20.5060: SIP, length:
435
20:56:32.228930 IP 217.10.79.9.5060 > 192.168.1.20.5060: SIP, length: 4
20:56:45.351943 IP 217.10.79.9.5060 > 192.168.1.20.5060: SIP, length: 4
20:56:50.972278 IP 192.168.1.20.5060 > 217.10.79.9.5060: SIP, length: 4
20:56:50.974190 IP 192.168.1.20.5060 > 217.10.79.2.3478: SIP, length: 20
20:56:51.010056 IP 217.10.79.2.3478 > 192.168.1.20.5060: SIP, length: 88
20:57:41.467983 IP 217.10.79.9.5060 > 192.168.1.20.5060: SIP, length: 4
20:57:46.081619 arp who-has 192.168.1.20 tell 0.0.0.0
20:57:47.431802 arp who-has 192.168.1.1 tell 192.168.1.20
20:57:47.431891 arp reply 192.168.1.1 is-at 00:0b:6b:db:1f:f1
20:57:47.435378 IP 192.168.1.20.38231 > 192.168.1.1.53:  60361+ AAAA?
stun.sipgate.net. (34)
20:57:47.436050 IP 192.168.1.1.53 > 192.168.1.20.38231:  60361 0/0/0
(34)
20:57:47.494034 IP 192.168.1.20.5060 > 217.10.79.2.3478: SIP, length: 20
20:57:47.516204 IP 217.10.79.2.3478 > 192.168.1.20.5060: SIP, length: 88
20:57:47.527910 IP 192.168.1.20.5060 > 192.168.1.1.5060: SIP, length:
450
20:57:50.571125 IP 192.168.1.20.5060 > 192.168.1.1.5060: SIP, length:
450
20:57:56.356536 IP 217.10.79.9.5060 > 192.168.1.20.5060: SIP, length: 4
20:57:56.609895 IP 192.168.1.20.5060 > 192.168.1.1.5060: SIP, length:
450
20:58:08.656036 IP 192.168.1.20.5060 > 192.168.1.1.5060: SIP, length:
450
20:58:09.641543 IP 217.10.79.9.5060 > 192.168.1.20.5060: SIP, length: 4
20:58:13.665192 arp who-has 192.168.1.1 tell 192.168.1.20
20:58:13.665244 arp reply 192.168.1.1 is-at 00:0b:6b:db:1f:f1
20:58:38.468707 IP 217.10.79.9.5060 > 192.168.1.20.5060: SIP, length: 4
20:58:40.745251 IP 192.168.1.20.5060 > 192.168.1.1.5060: SIP, length:
450
20:58:45.752056 arp who-has 192.168.1.1 tell 192.168.1.20
20:58:45.752109 arp reply 192.168.1.1 is-at 00:0b:6b:db:1f:f1
20:58:52.434611 IP 217.10.79.9.5060 > 192.168.1.20.5060: SIP, length: 4
20:58:56.779893 IP 192.168.1.20.5060 > 192.168.1.1.5060: SIP, length:
450
20:59:06.476641 IP 217.10.79.9.5060 > 192.168.1.20.5060: SIP, length: 4
------------------------------------------------



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/