Link to home
Start Free TrialLog in
Avatar of Andy Brown
Andy BrownFlag for United Kingdom of Great Britain and Northern Ireland

asked on

Dialing through a Remote Server

I have an Access database that allows users to dial a telephone number via either; TAPI, Com port or Command line prompt (Skype etc).  However, we are just about to start moving it onto a remote server (running Microsoft Server 2008 R2).

The server is stored in a high-speed data centre, so bandwidth shouldn't be a problem (hopefully).

Ideally, I would like my users to be able to plug a headset into their laptop and be able to dial from anywhere - but I could really do with some guidance as to the best way forward (and possibly who to use).
Avatar of Jim Dettman (EE MVE)
Jim Dettman (EE MVE)
Flag of United States of America image

Just to be clear; they are using remote desktop and loggiing into the server?

If not, assuming your app is split into a front end/backend and the backend will be on the server,
your going to have problems high band width or not if your using JET for a datastore (a MDB file).  

JET DBs cannot operate over a WAN unless it's a high end setup (speed >40Mb/sec and latency <10ms).

 You need to detail out a little more what the setup is and why the server plays a role in the dialing.

Jim.
Avatar of Andy Brown

ASKER

Hi Jim,

The front-end and back-end are both on the remote server and each user logs on  using MS Remote Desktop connection.  I've used this configuration for some time and it works really well (assuming everyone has enough bandwidth).

I've spoken with the proposed data-centre who host our servers and they believe the bandwidth will be fine (at their end), but that the bottleneck will understandably be on the external users connection.  However, assuming everyone has enough bandwidth - in theory it should be fine.

Hope that helps.
Yes, that certainly clears things up, but I guess the question is then, what's the question?   It's early here and maybe I'm being a bit dense, but your app is running on the server, so it's the server that would be dialing out.

As you point out, the headset data will be going between the server and the users PC, but RDP does a fair job of that.

Jim.
Thanks Jim

Assuming that technicaly it works (which we think it will).  I now need to find a UK based low-cost call provider who can supply something with a command line prompt (such as Skype (who are too expensive)).

Do you/anyone have any recommendations?
<<Assuming that technicaly it works (which we think it will).>>

Actually, I'm not positive on that after thinking about it; RDP I know for sure handles audio out, but I'm not sure about audio in.

<< I now need to find a UK based low-cost call provider who can supply something with a command line prompt (such as Skype (who are too expensive)).>>

 Sorry, can't help there; I'm in the US and not familer with any UK providers.  Let's see who else jumps in.  In the meantime, I'll double check if RDP handles audio in as well as out.

Jim.
Jim - you're a star - thank you as always.
Well that's a bummer; RDP only handles audio out (speakers).  A mic won't work.

Jim.
ASKER CERTIFIED SOLUTION
Avatar of Andy Brown
Andy Brown
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Wow...news to me.  I knew Microsoft had overhauled RDP for 2008, but I never heard about the items in the link you posted.

 Make sure you accept your own comment as answer.

Jim.
Thanks Jim.
I found the answer myself