• November 01, 2024, 01:35:45 AM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: Configuring ISA Server for DLink DVX2000MS Base Station  (Read 6827 times)

twwebster

  • Guest
Configuring ISA Server for DLink DVX2000MS Base Station
« on: October 01, 2008, 05:51:08 PM »
I need to publish the DVX2000MS Base Station on my ISA Server.  Does anyone know what ports need to be setup for Response Point and the DVX2000MS?

Thanks...
« Last Edit: October 08, 2008, 08:12:11 AM by twwebster »
Logged

mslaga

  • Level 1 Member
  • *
  • Posts: 10
Re: Configuring ISA Server for DLink DVX2000MS Base Station
« Reply #1 on: October 02, 2008, 05:26:10 AM »
What are you trying to accomplish?  Just the Administrator portion?
Logged

twwebster

  • Guest
Re: Configuring ISA Server for DLink DVX2000MS Base Station
« Reply #2 on: October 02, 2008, 07:56:35 PM »
I want to expose my Base Station via the VPN and Protected networks and somehow figure out how to get the RP Assistant to work across VPN or get the Dlink Handsets to work on remote networks.

I know that RP is supposed to be a simplified VOIP solution, but isn't the whole idea of VOIP to be able to setup phones across networks and not just one single network?

The crazy thing is that the Assistant worked on v1 and ever since I have installed SP1, it no longer works.

Is there anyone out there that has this working?  I don't care if it is not supported "technically" by Microsoft or RP...but I need to figure out how...any help would be appreciated!!!

Thanks...
« Last Edit: October 08, 2008, 08:12:31 AM by twwebster »
Logged

mslaga

  • Level 1 Member
  • *
  • Posts: 10
Re: Configuring ISA Server for DLink DVX2000MS Base Station
« Reply #3 on: October 03, 2008, 05:45:40 AM »
RP appears to utilize broadcast packets in most of it's phone and gateway stat gathering. 

I will agree, limiting the RP system to one subnet is extremely restricting.  Especially for certain verticals where remote salespeople could greatly benefit from a remote client.  But the system was designed to fit a particular demographic that fits a pretty large percentage of SMB. 

I have heard of people getting some things to work across a VPN, but spanning multiple subnets is currently a breaking factor with RP, not just DLinks implementation of it.
Logged