Joint Technologies ltd

Ok heres what I did and it works.  FYI.  I have this wokring in 2 locations.

network config at location A

phone – sonicwall TZ170 – internet – SBS2003 – Trixbox

SBS doing the NAT on the TB side.  total pain because you can only forward one port at a time. 

 network config at location b

phone – netgear router- internet – some really old crappy dlink airstream router – trixbox

I did upgrade the firmware on the dlink.

 So my main problem was that you can only forward one port at a time with SBS 2003.  So there was no way I was going to attempt to open 10001-11000 as requested by trixbox.

 so on the TB side of the internet I forwarded 5060 TCP/UDP to TB.  I forwarded 10001-10011 UDP/TCP to TB forward 69 UDP to TB if you want to get your config settings.

Edit RTP.conf

rtpstart=10001
rtpend=10011

Edit sip_nat.conf

externip=your static public IP of the LAN TB is on.
localnet=192.168.16.0/255.255.255.0  the subnet of your internal lan
nat=yes
externrefresh=10

TB is done and will work.

Let me also say that these are small systems so not having many rtp ports is ok for them.  YMMV.  if your router is easier to work with you may want to open as many as possible.

So now on the Phone side.

Set the phone to static IP.  I prefer using dhcp reservations in the router. and leaving the phone set to dhcp.

in the router the phone is connected to

I forwarded 5060 TCP/UDP to the phone.  I forwarded 10001-10011 UDP/TCP to the phone.

Then in the GXP2000 web admin under advanced settings change the local RTP port: to 10001

Set the firmware and config server path to the public IP or hostname of your trixbox so your phone will get its settings.

 If you want the phone in any ring groups you must put them at the top of the list of extensions in the freepbx ringgroups.  Dont ask me why…

I have BLF, the phones ring and everything is great.  Now if I wanted 2 phones at 1 remote location I may have a problem.  then I would use VPN as this SIP nat thing is a total pain.  If I could find a decent IAX hardphone Id get it.
 

I have a client that has been struggling with installing GP clients on a virtual server through terminal services.

Heres what happened.

We found the glitch.  I used a workstation with GP installed but not being used right now to try and find out what is causing these issues.  I first tried to remove GP from this station and it bombed citing the same error that ".NET Framework 2.0 not detected".  I then removed .NET Framework 3.0 with service patch and tried to remove GP again, and it still bombed with same error.  I then removed .NET Framework 2.0 with service patch and it still bombed.  I then installed the .NET 2.0 you sent as a download, and made sure to not update anything as the update icon came on right away.  I left in .NET Framework 1.1 and 1.1 hotfix.

After downloading .NET 2.0 clean, the program then allowed me to remove GP.  I then reinstalled GP with no issues.

So, the 10.0 installation disk we have is only looking for 2.0, and there is hell to pay if you update it.

When working remotely you will often need to access your files from a mapped network drive just like when you are in the office.  MS Small Business server provides this functionality through the Connect to Small Business Server application.  This creates a secure, encrypted connection to your server in the office.

Some times when you connect to small business server you still wont have access to your mapped drives.  This is usually because of an offline files syncronization situation. You can usually diagnose this by looking in your task tray.  See the image below.

A: verify you are connected to Small Business Server
B: This is the offline files icon
C: If you have an ISA firewall you will see that it shows as connected.

If the offline files icon is in your task tray; click it and you will see something like the image below.

click OK

Your computer will then sync up the files that have changed and also re-enable your mapped drives.

Close and reopen my computer and you should have access to your mapped drives.
 

Still not seeing your files?  Contact Us.