Thanks! This solved my problem! Matthias
> -----Original Message----- > From: Guilherme Oliveira [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 19, 2006 5:12 PM > To: [email protected] > Subject: Re: [pfSense Support] Problem with VoIP > > In "Firewall: NAT: Outbou" check "Static-port". > I think :-/ > > On 4/19/06, Matthias Kessler > <[EMAIL PROTECTED]> wrote: > > Hello everyone, > > > > I installed BETA 3 with the 2 additional patches today on > my PC with > > the bootable CD. Now my VoIP-Box (Fritzbox 5012) can't > register with > > the SIP-Server anymore. Before I've used m0n0wall 1.22 and > there were > > no problems with this. > > > > I found some strange things: > > > > First the Fritzbox is connecting the STUN server correctly and gets > > the response with the IP-Address and the port for > registering himself > > with the SIP-server. You can see this in the firewall log and I > > additionally captured the traffic on the WAN and the LAN > interface. Everything seems to be OK. > > > > After that the SIP client wants to register himself at the > SIP server > > (this one has a different IP address!) and makes a second > connection. > > And now there is the problem: the SIP server wants to > connect to the > > port from the first STUN connection. This gets either > blocked by the > > firewall (this I can resolve because the source port is > always 5060) > > or doesn't get redirected to the Fritzbox (logical! It's > coming from a different IP address!). > > > > Is there any chance, to give the outgoing connection from my SIP > > client > > (Fritzbox) always the same source port on the WAN > interface? (Best it > > would not chance the source port and leave it as 5060) or I want to > > define "if fritzbox:5060 connects to the internet it gets > WAN-IP:50600 > > or something like this. > > > > Can anybody help me with this? Sould I give any additional > information? > > > > Thank you very much, > > Matthias > > > > P.S. > > > > - First connection LAN interface: > > > > 16:11:28.599595 IP 192.168.0.100.5060 > 212.227.15.200.3478: SIP, > > length: 28 > > 16:11:28.652117 IP 212.227.15.200.3478 > 192.168.0.100.5060: SIP, > > length: 56 > > > > - First connection WAN interface: > > > > 16:11:28.599855 PPPoE [ses 0x128e] IP 84.156.35.12.53758 > > > 212.227.15.200.3478: UDP, length 28 > > 16:11:28.651995 PPPoE [ses 0x128e] IP 212.227.15.200.3478 > > > 84.156.35.12.53758: UDP, length 56 > > > > ================================== > > > > - Second connection LAN interface: > > > > 16:11:28.786448 IP 192.168.0.100.5060 > > 212.227.15.197.5060: SIP, length: > > 608 > > 16:11:28.792426 IP 192.168.0.100.5060 > > 212.227.15.197.5060: SIP, length: > > 608 > > > > - Second connection WAN interface: > > > > 16:11:28.787105 PPPoE [ses 0x128e] IP 84.156.35.12.62460 > > > 212.227.15.197.5060: SIP, length: 608 > > 16:11:28.793055 PPPoE [ses 0x128e] IP 84.156.35.12.62460 > > > 212.227.15.197.5060: SIP, length: 608 > > 16:11:28.857601 PPPoE [ses 0x128e] IP 212.227.15.197.5060 > > > 84.156.35.12.53758: SIP, length: 465 > > 16:11:28.872782 PPPoE [ses 0x128e] IP 212.227.15.197.5060 > > > 84.156.35.12.53758: SIP, length: 465 > > > > ================================== > > > > # pfctl -ss > > > > self udp 192.168.0.100:5060 -> 84.156.35.12:53758 -> > > 212.227.15.200:3478 MULTIPLE:SINGLE self udp 192.168.0.100:5060 -> > > 84.156.35.12:62460 -> 212.227.15.197:5060 SINGLE:NO_TRAFFIC > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] For > additional > > commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] For > additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
