These instructions were created for several reasons.

1. The Adapter only Starts at Windows Logon time.
2. The Adapter normally will attempt to connect to ANY Skype Client.
3. The Adapter stops when you are not logged in, but your computer is on.
4. The Adapter does not easily allow secondary Skype Clients.

Imagine, you purchase this adapter so that the phone you connect to it will be available 24/7 no matter what user is logged on to the computer or even if nobody is logged on. Sadly this is NOT what really happens.

These methods show how to create a dedicated Skype Client to be connected to a dedicated Adapter Utility that survives no matter what user is logged on, and during logoff's as well as Logon's as well as when no user is currently logged on your system.

As long as your computer is powered on, your Phone will be able to receive calls and make calls using the same Skype name using these methods.

The Dlink DPH-50U Adapter allows you to connect ANY cord or wireless phone to your computer using a USB port.

Currently it is available at Best Buy as one example for $59.99 + tax in the U.S.

In the event you are short on USB ports you can purchase a Dynex DX-H420P 4 port USB Hub also at Best Buy at $14.99 + tax in the U.S.

You MAY wish to print these instructions if possible

OK, this may get a little long winded but if you would like to be able to use the Dlink DPH-50U Adapter and the phone connected to it always using the same Skype name even if you are logged off and while any user is also logged on your system then here are the instructions.

This will allow the Dlink adapter and the phone connected to it to be used as long as your computer is powered up even without being logged on as any user, this way you can receive calls at all times using the adapter.

Before we start, make a restore point, and also back up your registry!

NOTE: These instructions are for Windows XP systems ONLY!

Logon as an ADMIN account for these procedures.

You will need to download two free programs in order to make both a Skype client as well as the Dlink DPH-50U Adapter Utility a system service.

You can still use another Skype client while logged on your computer, this one however will be dedicated to the Dlink Adapter and the phone connected to it only.

This is very important if you have a SkypeIn number and wish the phone to be available at ALL times, including when the computer is logged off ("But Powered on") and when any user is logged on. It also allows any and all users to continue to use their own Skype clients.

NOTE: Any Windows system can extract files from a .zip file. Once the .zip file is downloaded, simply right click on the .zip file name and choose the Extract All option. There is NO need to purchase a .zip utility.

GenSvc - Which is a wrapper to allow both the Skype client and the Dlink Adapter Utility to run as system services ("Meaning at all times").

http://gocoding.com/projects/gensvc/PRPK5/...1.0.0.1_bin.zip

ServiceControl - Allows you to easily ADD System Services which we will need to do for the Skype client as well as the Dlink Utility. You can download them both from here for now:

http://gocoding.com/projects/servicecontro...control_bin.zip

NOTE: Information changed as of 11/26/07 - You would be better off installing the Skype for business version because it has a smaller footprint. You can keep the normal version if you wish. Here is a link for that http://www.skype.com/download/skype/windows/business.html

If you already have a current version of Skype installed, uninstall it ("You will lose your history if you do this") before installing the Business Version:

1. Go to your Program FilesSkypePhone directory, right click on Skype.exe select copy, right click on any white space area in the Program FilesSkypePhone directory ("same directory") and choose paste.

2. Right click on the copy of Skype.exe you just created and choose rename, rename it to Skype2.exe

3. Unzip the SysService.zip which contains three files, one called GenSvc.exe, one called ServiceControl.exe and another a shortcut to this post in the forum.

Place the GenSvc.exe in your Windows directory which is normally C:\Windows.

4. Place the ServiceControl.exe file on your desktop.

5. Click on the ServiceControl.exe, you will see a list of your current system services, click on Install.

In the "Service Name;" enter "Dlink Skype Client" without the quotes.

In the "Display Name:" enter "Skype Dlink Client" without the quotes.

In "Description:" enter "Skype Client for Dlink" without the quotes.

6. In "Executable:" enter exactly the line below:

C:\Windows\GenSvc.exe "C:\Program Files\Skype\Phone\Skype2.exe" /nosplash /minimized

Check the box "Interact With Desktop"

For the moment change the "Start Type" from Automatic to Manual, we want to make sure the Skype client works properly before we make it an automatic system service.

Click OK

Make sure the "Skype Dlink Client" service name is highlighted.

Click Start

7. Did the Skype Client Start, without a splash screen and minimized?

If so do this step otherwise check the above step and make sure it was followed exactly, something was entered wrong if the Skype client did not start.

Post a message HERE if you need help do not continue.

If your Skype Client Started, and it auto-logged on, sign out.

If you are prompted by the Dlink Utility to connect to Skype choose "Allow" NOT "Allow but ask again in the future".

Now that you are are signed out, make sure the 2 start boxes are checked and enter the Skype name that will always be used for the Dlink adapter and phone connected to the adapter.

If you have a Skype name that has a SkypeIn number most likely you would want that Skype name to be entered with a password and BOTH Start boxes checked.

If you do NOT have a Skype Name with a SkypeIn number pick the Skype Name you use that you wish to ring the phone when contacted, the Skype Name you wish to be connected to Skype no matter what user is logged on your computer or to use even when your computer is logged off ("But Powered ON") to ring the phone.

Sign into Skype after you chosen your Skype name and make sure both Start buttons are checked.

Right click on the Skype Icon on the system toolbar and choose quit.

Using ServiceControl with the "Skype Dlink Client" service highlighted click start.

Did everything go as planned?

Did Skype Startup, have no splash screen, and minimize to the system toolbar, logged in as the Skype Name you want?

If not STOP here and post a message here otherwise:

Using ServiceControl with the "Skype Dlink Client" service highlighted click config and change the "Start Type:" to be Automatic, not Manual, Click on ok, and Exit from ServiceControl.

Reboot your system.

8. Wait to logon you should hear the Skype logged in sound even before you choose a user name to logon as.

Now once you hear that logon sound, you know that Skype client is running in the background as a system service, because you have not even selected a user ID to logon as.

Now logon as the SAME ADMIN id you used for the prior steps.

9. Once your desktop appears you should see Skype running on the System toolbar minimized.

Note: If this ADMIN id normally auto-starts a Skype client, it would be normal to see a second Skype client start when this user logs on. If this is not the case then launch another Skype client the way you do normally, via the Icon or Start button, we need to make sure the Dlink utility is NOT going to try to link to ANY other Skype client except the one we made a system service.

Once you are logged on ("Use another Skype name, not the one that is logged in already as a System Service") at the bottom of that Skype client in the lower left, if you see two arrows between the word "Online" and the Online Icon, click on those two arrows, it will launch a box, if the Dlink utility is listed choose REMOVE.

Make sure you are doing this to the Skype client you just launched via an Icon, and NOT the one started as a system service.

Now sign off of the Skype Client YOU created by clicking on the Skype Icon or via the Start menu. Sign back on using the same Skype name.

If the Dlink Utility prompts to connect to this Skype client, choose the Do NOT ALLOW.

We do this because we don't want the Dlink utility to try to connect to every Skype client, just the one we created as a system service, the Skype2.exe one, this way you or any user logged on your computer will be able to create another Skype client and not be bugged with a connect request from the Dlink utility, you or any other user can be using the normal Skype client and the phone can be used at the same time.

Now, we need to create a system service for the Dlink utility, WHY? because normally the Dlink utility only starts AFTER someone has logged on your computer, so we have the Skype client running even when nobody is logged on your computer but the Dlink utility is not yet a system service, so we can't yet use the phone connected to the Dlink adapter when nobody is logged on to your computer and we can't receive calls until we do when nobody is logged on.

10. We also need to delete the registry key for the NORMAL method of starting the Dlink utility when a user logs on, otherwise, once we create a system service for the Dlink utility, it will try to start TWO copies, which would NOT be good!

11. Click the CTRL-ALT-DEL keys to invoke your task manager, look for a task called "DPH-50U Utility.exe" highlight it, click on end process, it should now be stopped.

12. Start the ServiceControl.exe again, click the "Install Button".

In Service name enter "DPH-50U Utility" without the quotes.

In the Display name Enter "Dlink DPH 50U Utility" without the quotes.

In the description Enter "Dlink Adapter For Skype" without the quotes.

NOTE: Changed as of 11/26/07 A new Driver has been released by Dlink version 1.1, This driver can be found at http://support.dlink.com/products/view.asp...uctid=DPH%2D50U

If you are NOT using the 1.0 version of the Driver installed from the original Dlink CD then use this in the Executable enter exactly:

C:\Windows\GenSvc.exe "C:\Program Files\D-Link\D-Link USB VoIP Adapter\DLinkMonitor.exe"

If you are using the driver installed from the original Dlink CD enter In Executable enter exactly:

C:\Windows\GenSvc.exe "C\:Program Files\D-Link\D-Link USB Phone Adapter\DPH-50U Utility.exe"

Check the box "Interact With Desktop"

For the moment change the "Start Type" from Automatic to Manual, we want to make sure the Dlink Utility works properly before we make it an automatic system service.

Click OK

Make sure the System Service "Dlink DPH 50U Utility" is highlighted.

Click Start

13. Did the Dlink Utility Start? if So do this step otherwise check the above step and make sure it was followed exactly, something was entered wrong.

Post a message HERE if you need help do not continue.

Highlight the "Dlink DPH 50U Utility" Service in ServiceControl and click the "Config" button, change the "Start Type" to Automatic and click ok.

14. Now we need to delete the registry key that normally starts the Dlink Utility when a user logs on since it is now a system service.

You can exit the ServiceControl utility.

Remember you can always use the ServiceControl utility to change or even delete these two system services we created anytime in the future.

The Skype Client service name in the list using the ServiceControl utility is: Skype Dlink Client

The Dlink Utility Service name in the list using the ServiceControl utility is: Dlink DPH 50U Utility

Just click config after one is highlighted and you can change Automatic to Manual, or click Delete to remove.

15. Click the Start Button on your Windows toolbar ("Lower left hand corner") click on run, enter REGEDIT. Go to:

HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\WINDOWS\CurrentVersion\Run

Look for "TLinkAgent" or "DLinkMonitor" ("Name depends on the version of the Dlink DPH-50U Drivers being used") without the quotes, right click on the word TLinkAgent or DLinkMonitor, select delete. Close regedit.

16. Re-Boot your system, do not logon yet.

You should hear the Skype Auto-Logged in sound. When you pick up your phone ("The one Connected to your Dlink adapter") you should have the dial tone, even without being logged in on your system, and no matter what user is logged in, the Skype Name you picked will always be able make and receive calls as well.


NOTE: If you do NOT do Step 17, your Skype Client and USB adapter will NOT survive a user logoff.

17. HIDE the Icon for both this Skype client as well as the Icon for the Adapter Utility:

Using the ServiceControl program look for "Skype Dlink Client" click on config, uncheck the "Interact with Desktop box", click ok.

Using the ServiceControl program look for "Dlink DPH 50U Utility" click on config, uncheck the "Interact with Desktop box", click ok.

Re-boot and now both the Skype Client Icon and the Adapter Icon will be hidden. This is just an extra security step so that users on your computer cannot change the Skye Client settings or the Adapter settings.

You can now even make or receive Skype calls while being at your welcome screen, or login prompt. There is not even a need to login.

Even better, if someone did log on this computer and then logoff, or someone changes users on this computer, and you are using Skype and have a call in progress, or a call is ringing, the call will NOT be terminated as would have been the case normally.

As long as your computer has power, you now have Skype Services 24/7 and the users of this computer can start their own Skype Clients without the need to use "Run As".

You can always re-check the Adapter Utility and re-boot to make adapter changes, this allows some form of security to protect the Adapter configuration. Also, you can run a nomal Skype Client logged on as the same Skype name that interfaces to the Adapter to add contacts, Speed numbers, start chats and so on, and use the name normally, this just gives a security measure.

Note: If calls are made or received when nobody is logged on to the computer, the Skype client will be present when users logon, all they need to do is minimize the client, and they can use their own normal Skype client while logged on with NO impact on your ability to receive or make calls Using the Dlink adapter and phone. Anytime a call is received or made while a user is logged on as well the Skype Client Will appear on the desktop and can be easily minimized.

Some people have explained how to make a Skype Client a Windows System Service, however, when using the Dlink Adapter in order to have a phone connected to this adapter work 24/7 even when nobody is logged into your computer ("It must be powered on") or no matter what user is logged on, this method must be done with the DLink Utility as a system service as well.

NOTE: This same method can be done with the Linksys Skype Phone, I will soon post how to do the same procedures with it.

Hope this helps? any questions, post them!

Enjoy

This concept also works with the USR 9620 as well as the Internet Phone Wizard.

In order to ADD or change Speed Dial numbers for the Skype client that is running as a system service connected to the USB adapter program also running as a system service, you will need to use the ServiceControl program to check the "Interact With Desktop" box, stop the service, start the service, make your changes, stop the service, uncheck the "Interact With Desktop" box and start the service.

While at first this might seem like a painful experience, it does give you some method to protect Speed dial numbers from other users on that computer.

Another side benefit of using 2 copies of the Skype program, is that it allows the USB adapter to use a stable version of Skype while allowing you to use Beta versions of Skpe for other clients. Once you feel comfortable, you can upgrade Skype2.exe to be the same as Skype.exe.

This methodology is ideal for people that have a SkypeIn number for a family phone, and are using a USB adapter or Skype phone connected to a computer shared by many people in that family.

For Business, it allows the use of a USB adapter or Skype phone to be connected to computers in the office, and run in the background so that all your SkypeIn numbers for that business are available for use at all times the computer is powered on, 24/7, and not dependant of any user being logged on those computers, as well as not terminating calls in progress, due to a user logoff/logon.

Bridging calls, if you wish to use this feature which is available from most USB Skype adapters, you do not wish to have a call being bridged from say your cell phone to Skype suddenly terminated because someone decided to logoff or logon as another user on the computer the USB adapter was connected too.

Worse, when someone logs off that computer, and the computer remains logged off, you don't want to loose the use of the USB adapter because of that, which is normally the case.

If at first these methods seem a waste of time, my suggestion would be that you use your USB adapter or Skype phone to make a call, while the call is in progress, logoff the computer the adapter is connected too. Your call will be terminated. Now, have someone call you, while the phone is ringing, logoff the computer your Skype phone or USB adapter is connected too. Your call will be terminated.

In both of the examples above, using these methods, your calls would not be terminated.

Depending on how your computer is set up, this also will automatically recover from a power failure, so once power is restored, since these interfaces now run as system services, once the computer starts, Skype services will be restored without any human intervention or a login required.

Wow! This worked like a charm. Just what I was looking for. Thanks for taking the time to post such detailed instructions.

[quote=smorty71]Wow! This worked like a charm. Just what I was looking for. Thanks for taking the time to post such detailed instructions.[/quote]

You are very welcome :-)

Please post any feedback on what you think for others you seem to be the only person brave enough ("Other than one other person who shall remain nameless ") and bold enough to try this, I think others would like to hear your thoughts :-)

The process you outlined was very simple to follow. If everyone just follows each step as you describe, they should have no problem.

The only issue that I am having with my setup is with the Dlink utility crashing from time to time. It was doing that prior to setting up the service, so it isn't caused by your tips. Once, the Dlink app crashes, the phone is pretty much rendered useless.

Any idea if Dlink might update that app to be more stable?

[quote=smorty71]The process you outlined was very simple to follow. If everyone just follows each step as you describe, they should have no problem.

The only issue that I am having with my setup is with the Dlink utility crashing from time to time. It was doing that prior to setting up the service, so it isn't caused by your tips. Once, the Dlink app crashes, the phone is pretty much rendered useless.

Any idea if Dlink might update that app to be more stable?[/quote]

Actually, The device utility interface and drivers are designed by a company called TLink, and they are same for this device as well as the USR 9620,

What are the errors? How often does it happen? I am having no problems with errors with the 2 I own.

I would post the error on the Dlink site as well just to make sure they don't have a quick solution.

It gives me the standard message in Windows where it asks if I would like to submit the error to MSFT.

It seems to happen quite often after I have been changing settings in the "Tools" menu for Skype.

I'm trying the same instructions out on my CyberPhone W handset, when I click Start, Skype appears unminimized.

Any ideas?

[quote=Tarq]I'm trying the same instructions out on my CyberPhone W handset, when I click Start, Skype appears unminimized.

Any ideas?[/quote]

Well, are we talking about the Skype Client you made a system service?

If so, when you added the Skype Client as a system service did you included the /minimzed switch? The system service line should read:

C:WindowsGenSvc.exe "C:Program FilesSkypePhoneSkype2.exe" /nosplash /minimized

Note: One of the reasons the system service client uses a copy of Skype.exe called Skype2.exe is that it allows you and others using the computer to download and use beta versions of the Skype client, for all your other Skype clients, while leaving the USB adapter always using the most stable version of the Skype client.

If you are talking about the Skype client that runs at startup when you login as a user you will need to modify the registry key:

HKCUSOFTWAREMicrosoftWindowsCurrentVersionRunSkype

and ad the /nosplash /minimized flags to the end of it. It should normally look like this:

"C:Program FilesSkypePhoneSkype.exe" /nosplash /minimized

Note: Always backup your Registry or create a system restore point before making any changes to the Registry.

Sorry I wasn't clear, the Skype client (Skype2.exe).

I have copied/pasted this from what I have entered on the screen:

C:WindowsGenSvc.exe "C:Program FilesSkypePhoneSkype2.exe" /nosplash /minimized

[quote=Tarq]Sorry I wasn't clear, the Skype client (Skype2.exe).

I have copied/pasted this from what I have entered on the screen:

C:WindowsGenSvc.exe "C:Program FilesSkypePhoneSkype2.exe" /nosplash /minimized[/quote]

ok, are you sure this is not another Skype client? not the system service one, because if you already checked the box in the system service Skype client to not interact with the desktop, it would be impossible that this is the system service skype client. Use your task manager [CTRL][ALT][DEL] to see if you have both a Skype.exe and a Skype2.exe running.

If this is not the case then, redo the line in the system service because somehow there is junk in it and the /minimized switch is not being seen.

In other words, if you did have a Skype client that normally started at user logon for this user on your system, not only would the system service Skype client be running, but the other Skype client you normally had would also run as well.

One of the side benefits of following these instructions is that you now can run as many Skype clients as you need without using "Run As" as long as they have different Skype names.

Please post your results and/or findings.

[quote=smorty71]It gives me the standard message in Windows where it asks if I would like to submit the error to MSFT.

It seems to happen quite often after I have been changing settings in the "Tools" menu for Skype.[/quote]

I would report this error to Dlink, I have never seen this error, are you current will all Microsoft updates and updates from the company that sold you the computer, sometimes they post new drivers and such.

What OS are you running, XP Home?

I will report it to Dlink.

BTW, I am up to date and am using WinXP Pro SP2. It is really weird (and frustrating) when it happens.

[quote=ZOverLord][quote=Tarq]Sorry I wasn't clear, the Skype client (Skype2.exe).

I have copied/pasted this from what I have entered on the screen:

C:WindowsGenSvc.exe "C:Program FilesSkypePhoneSkype2.exe" /nosplash /minimized[/quote]

ok, are you sure this is not another Skype client? not the system service one, because if you already checked the box in the system service Skype client to not interact with the desktop, it would be impossible that this is the system service skype client. Use your task manager [CTRL][ALT][DEL] to see if you have both a Skype.exe and a Skype2.exe running.

If this is not the case then, redo the line in the system service because somehow there is junk in it and the /minimized switch is not being seen.

In other words, if you did have a Skype client that normally started at user logon for this user on your system, not only would the system service Skype client be running, but the other Skype client you normally had would also run as well.

One of the side benefits of following these instructions is that you now can run as many Skype clients as you need without using "Run As" as long as they have different Skype names.

Please post your results and/or findings.[/quote]

Thanks for your help so far.

This "client" is Skype.exe from the C:Program FilesSkypePhone folder that I copied and pasted and then renamed Skype2.exe

I then typed C:WindowsGenSvc.exe "C:Program FilesSkypePhoneSkype2.exe" /nosplash /minimized exactly in the Executable box, selected Manual and then ticked Interact with Desktop. When I press Start the Skype window always appears on screen.

[quote=Tarq][quote=ZOverLord][quote=Tarq]Sorry I wasn't clear, the Skype client (Skype2.exe).

I have copied/pasted this from what I have entered on the screen:

C:WindowsGenSvc.exe "C:Program FilesSkypePhoneSkype2.exe" /nosplash /minimized[/quote]

ok, are you sure this is not another Skype client? not the system service one, because if you already checked the box in the system service Skype client to not interact with the desktop, it would be impossible that this is the system service skype client. Use your task manager [CTRL][ALT][DEL] to see if you have both a Skype.exe and a Skype2.exe running.

If this is not the case then, redo the line in the system service because somehow there is junk in it and the /minimized switch is not being seen.

In other words, if you did have a Skype client that normally started at user logon for this user on your system, not only would the system service Skype client be running, but the other Skype client you normally had would also run as well.

One of the side benefits of following these instructions is that you now can run as many Skype clients as you need without using "Run As" as long as they have different Skype names.

Please post your results and/or findings.[/quote]

Thanks for your help so far.

This "client" is Skype.exe from the C:Program FilesSkypePhone folder that I copied and pasted and then renamed Skype2.exe

I then typed C:WindowsGenSvc.exe "C:Program FilesSkypePhoneSkype2.exe" /nosplash /minimized exactly in the Executable box, selected Manual and then ticked Interact with Desktop. When I press Start the Skype window always appears on screen.[/quote]

Just got this working on a CyberPhone W with the help of ZOverlord.

The thing to remember is that the System Service needs to be setup to run SkypeClient.exe NOT VoipVoice.exe as we discovered.

Many thanks for this, makes Skype a lot more useful for SkypeOut / In.

The most useful post I have seen on this forum.

I notice this device ships with a USB 2 cable, would I be at a disadvantage if I used it with my USB 1 hub?

[quote=woodyear99]I notice this device ships with a USB 2 cable, would I be at a disadvantage if I used it with my USB 1 hub?[/quote]

No it works with a hub, I use one of mine with a hub.

Hey ZOverlord thanks for the replies.

So everything seems setup correctly, I used a USB port on my pc for it (I have USB 2 on my mobo) I see the Power and PSTN lights come on and I followed the quick setup guide.

When I lift the handset I hear it click and can get regular dial tone. I am trying to switch over to Skypeout and it's not switching. When I press ## I get a busy signal on my line, I tried changing it to the #* in the software but the same thing is happening. Any idea what I am doing wrong for it not to switch? Taskbar says both skype and adapter are connected...

[quote=woodyear99]Hey ZOverlord thanks for the replies.

So everything seems setup correctly, I used a USB port on my pc for it (I have USB 2 on my mobo) I see the Power and PSTN lights come on and I followed the quick setup guide.

When I lift the handset I hear it click and can get regular dial tone. I am trying to switch over to Skypeout and it's not switching. When I press ## I get a busy signal on my line, I tried changing it to the #* in the software but the same thing is happening. Any idea what I am doing wrong for it not to switch? Taskbar says both skype and adapter are connected... [/quote]

This may sound crazy, but try the ## fast, sometimes if you hesitate between the # <- Delay -> #, your telco will think you have entered bad keys, so you need to beat your telco and do ## very fast. Otherwise your PSTN line Telco will come back with a "Fast Busy" response.

I tired this, no luck. Even plugged in an old corded phone and tried very fast with no luck

I have american phones from Best Buy...

Is there anything else I can try? Tried uninstalling and reinstalling....

[quote=woodyear99]I tired this, no luck. Even plugged in an old corded phone and tried very fast with no luck

I have american phones from Best Buy...

Is there anything else I can try? Tried uninstalling and reinstalling....[/quote]

Not sure what country you are in, it might be a timing issue, where your telco for the PSTN line catches the keys before the Dlink can switch to Skype. What happens when you remove the Telco PSTN line, can you outdial using Skype, I am just trying to get a grip on if the Dlink is really working or not.

I still can't get through if the phone line is not plugged in, oddly enough if I use skype the light switches to the VOIP light but I do not hear anything from the phone even though the adapter is selected as the audio device and I turned up the volume under audio properties...

I would be surprised if this thing is defective, it was brand new and all the lights seem to be working, I even hear it "click" when I make regular phone calls over it....

Without a phone line connected to it, with just a phone, you should hear a click as soon as the adapter utility connects to the Skype client, and see the light show VoIP. Is that what you see? and you should hear some funky dialtone?

It seems more like the adapter utility is not linked to the skype client.

hmm just tried it on the laptop and it seems to be working fine....have to figure out what's going on with the desktop...

could you email me the programs so i can setup my skype that way, thank you. Can you still logon to that account an use it like normal?

I updated the links to download GenSvc and ServiceControl from my site, the other site seems to be offline for the moment.

I am having a problem using the "toll bypass" feature.

I call in to my PSTN line (from my mobile phone) and the DPH-50U picks up as indicated by the intermittent beep, then I enter my PIN followed by '*', then my skype speed-dial # (or full international number, preceeeded by 00, etc.), then '*'. (send character)

I am sure all of this is correct (per user guide) and it does in fact activate the skype Out call (I sit in front of my PC and watch skype come alive and initiate the skype out call correctly)

... but then it cancels immediately. It won't ever hold on for the call to go through...

All other functions of DPH-50U work fine. Outgoing PSTN and VOIP calls via my connected phone (initiating with '##', etc.) work correctly.

Help!? :-? I hope someone else has experienced this... (and fixed it?)

info: WinXP Pro completely up-to-date, latest skype, not much else to say.

I saw that someone mentioned this worked with the Internet Phone Wizard.

Does anyone know, or can anyone post instructions on how to set this up for the Vosky Call Centre?

Thanks

[quote=driggs13]I saw that someone mentioned this worked with the Internet Phone Wizard.

Does anyone know, or can anyone post instructions on how to set this up for the Vosky Call Centre?

Thanks[/quote]

Basically use msconfig, using the "Run" command, look for the startup program the utility uses.

Most likely you would be the first for this adapter model.

I have a PC Phoneline VTA1000 USB phone adapter. I’ve followed everything I think but when I hit the start button for the driver service it sort of runs but it gives me an error stating that it can’t find "N0.WAV". It is one of the sound files that the utility uses to play DTMF tones. (The file is there - in the same directory as the executable along with the busy signal, dialtone and a host of other noises it uses) Should these noises and other files be placed in the windows directory maybe? It seems like a path issue...

Any input would be appreciated.

-Alidor

Hmmm,

In this case you may need to place a copy of GenSvc in the folder where the utility exe is because it seems it is looking for the path from GenSvc ("Since it starts the utility now") so if you point to a copy of GenSvc in the folder of the utility, it may fake it out and force the correct path.

Well, thanks for the quick reply.
I placed a copy of GenSvc.exe in the app folder but no luck.
I tried using this as the path:
C:Program FilesPC Phoneline 1.0GenSvc.exe "C:Program FilesPC Phoneline 1.0PC Phoneline.exe"

I even tried it with extra quotes:
" "C:Program FilesPC Phoneline 1.0PC Phoneline.exe"

Same error - N0.WAV was not found.
Where else could it be looking? I’m hoping this will apply to other setups and devices as well. (it really should work with lots other of adapters)

If you or anyone else think of anything let me know. TIA

-Alidor

Where are the wave files located for this utility, have you tried placing GenSvc in the folder where they are located?

You are the first for this adapter, so it will be trial and error.

The media files are right in the application folder: (along with GenSvc)


C:Program FilesPC Phoneline 1.0>dir /a
Volume in drive C is Local Disk
Volume Serial Number is FC97-0638

Directory of C:Program FilesPC Phoneline 1.0

2006-07-05 22:30 <DIR> .
2006-07-05 22:30 <DIR> ..
2005-05-03 11:32 128 062 busy.wav
2004-06-24 13:05 45 056 CM_HID.dll
2006-04-11 08:09 1 656 connected.wav
2005-04-13 10:24 164 074 dialtone.wav
2005-04-22 21:38 48 164 dialtone2.wav
2006-05-02 17:57 <DIR> drivers
2005-07-21 15:34 49 152 ffevents.dll
2006-06-06 22:09 36 864 GenSvc.exe
2005-05-03 11:31 4 250 keypadtone.wav
2004-10-15 12:37 3 449 license.txt
2004-08-14 14:39 1 660 N#.wav
2004-08-14 14:29 1 780 N0.wav
2004-08-14 14:29 1 762 N1.wav
2004-08-14 14:31 1 712 N2.wav
2004-08-14 14:32 1 762 N3.wav
2004-08-14 14:33 1 746 N4.wav
2004-08-14 14:34 1 678 N5.wav
2004-08-14 14:35 1 746 N6.wav
2004-08-14 14:36 1 712 N7.wav
2004-08-14 14:37 1 746 N8.wav
2004-08-14 14:38 1 746 N9.wav
2005-05-15 21:12 1 712 NA.wav
2004-08-14 14:40 1 746 Nasterisk.wav
2005-05-15 21:13 1 678 NB.wav
2005-05-15 21:13 1 762 NC.wav
2005-05-15 21:14 1 796 ND.wav
2005-04-06 11:49 1 658 offhook.wav
2005-04-06 11:49 2 898 onhook.wav
2006-04-12 07:44 319 488 PC Phoneline.exe
2003-10-10 10:37 683 PC Phoneline.exe.manifest
2005-04-22 11:12 15 886 ring1.wav
2005-04-30 10:10 15 030 ring2.wav
2005-04-22 10:00 16 108 ring3.wav
2005-05-03 11:33 90 660 ringback.wav
2006-07-05 22:37 0 routingnumber.dat
2003-08-05 00:10 5 207 496 rtc.exe
2006-02-07 17:27 53 248 spevents.dll
2004-08-25 13:25 212 992 tjipsys.dll
2006-07-05 21:42 335 032 trace.txt
2006-05-02 17:57 4 266 unins000.dat
2004-02-25 05:00 76 233 unins000.exe
2005-08-09 14:20 53 248 xtevents.dll
2004-04-01 04:17 155 648 YLUSBTEL.dll
42 File(s) 7 069 045 bytes
3 Dir(s) 10 256 093 184 bytes free

C:Program FilesPC Phoneline 1.0>

(S’cuse the mess)
I’ve also tried placing a copy of N0.wav in the windows directory and setting the service path accordingly - C:/WINDOWS/GenSvc.exe etc...

Can’t seem to get my noggin around this one. I’ll keep at it.

-Alidor

Go to control panel, and click on Adminitrative tools -> Event viewer, and look at your event logs to see if you can get anymore error detail on where it is looking for the file.

Hi

Thanks for you very detailed instructions.

I've just finished setting up Skype with Dualphone on Windows 2003 and it works fabulous

[quote=jubozy]Hi

Thanks for you very detailed instructions.

I've just finished setting up Skype with Dualphone on Windows 2003 and it works fabulous [/quote]

Thanks so much :-)

Would you be able to take some time, if needed, and post for others any special things you may have needed to do that were not in the original instructions that may differe between the Dualphone and the Dlink?

It would be a pleasure.....

For Dualphone, I followed your steps up until step no. 9, ignoring your reference to Dlink in step 9.

Step 10 - No need for step 10

Step 11, I stopped the Dual Phone process via the task manager (process Cordless DUALphone Suite.exe)

Step 12 - create a service via ServiceConsole.exe for Dual Phone with the executable being :

C:windowsGenSvc.exe "C:Program FilesCordless USB PhoneCordless DUALphone Suite.exe"

Step 13 - same but refering to Dual Phone service

Step 14 & 15 - not required

Step 16 & 17 - as per your instructions....an presto!!

The only problem I had was trying to get into your site to download the zip file (i got a network error on your site http://testing.onlytherightanswers.com/) but thanks to gOOgle manged to find it.

Good luck!!!!!!!!!!!!!! :wink:

[quote=rolfshervey]I am having a problem using the "toll bypass" feature.

I call in to my PSTN line (from my mobile phone) and the DPH-50U picks up as indicated by the intermittent beep, then I enter my PIN followed by '*', then my skype speed-dial # (or full international number, preceeeded by 00, etc.), then '*'. (send character)

I am sure all of this is correct (per user guide) and it does in fact activate the skype Out call (I sit in front of my PC and watch skype come alive and initiate the skype out call correctly)

... but then it cancels immediately. It won't ever hold on for the call to go through...

All other functions of DPH-50U work fine. Outgoing PSTN and VOIP calls via my connected phone (initiating with '##', etc.) work correctly.

Help!? :-? I hope someone else has experienced this... (and fixed it?)

info: WinXP Pro completely up-to-date, latest skype, not much else to say.[/quote]

Hello!

First advice: try an older version of Skype.

I've installed the adapter and everything was fine UNTIL I've updated my Skype client from beta to version 2.5. Unluckily, I've made several other changing in the same time, and couldn't figure out, why I have the same problems, as you mentioned, plus impossibility to make PSTN->VoIP forwarding and strange tones during call by phone. After lots of tests, I've tried installing back an older version, and now everything is perfect again!

So, my guess is that Skype version 2.5 is not compatible with DPH50U when it comes to toll bypass and forwarding. Now I use version 2.0 and the sun is shining bright again

Is this really an incompatibility with Skype version 2.5?

Hello!

Thanks a lot for your solution!!! It helps me in 3 different scenarios!

Only to prove the versatility of Skype+DPH50U+”Run as a service” I explain it a bit.

I’ve bought 3 adapters to solve the communication between 3 sites where
1 is a HQ with free landline extensions,
2 is a home office with ISDN and a 3/8 PBX
3 is a shop with no landline but WLAN connection to the other ones.

At the HQ I’ve installed one adapter with PSTN->VoIP forwarding and VoIP->PSTN toll bypass. This way I’ve routed an extension to the shop, and can make this number public, as the shops landline number. The shop can access the landline with toll bypass. From my home office, I can dial my company phones via toll bypass and this extension, and having CLIP on our company PBX, people will see who is calling (not bad in a corporate environment :wink: ). The whole stuff is on my office PC, where I log on locally and remotely, without disturbing the phone connection of the shop (Thanks “Run as a service”!).

At the shop I have an adapter with a cordless phone. The installation is on the sole PC we have there, and the shop assistants are logging on and off with their own account, but no problem, since it runs as a service.

At home, I made the adapter a main line (CO) in my PBX connecting the “Phone” of the DPH to the CO2 of the PBX. If I want to make Skype calls, I dial 82 (pre-selection for line 2 in the PBX) and I have a dial tone for Skype. For regular calls I dial 9 or 81. But, I don’t want my family to be disturbed by my private Skype calls. So I have one “Home” account which runs as a service on my PC (always on line) linked to the PBX, and my personal Skype account which is active only when I am logged on.

Maybe sounds like a headache, but it works great, and the users need no more plus training like when having a new mobile phone!

Thanks again for this topic!

You are very welcome!

Once again, this I think shows how easy it is to use Skype with persistance, secured and on shared computers for dedicated Skype communications.

Thanks so much for all the detail you provided, hopefully this will inspire more people to try this when they have these same issues and needs for home and business.

It should be noted that since this thread started, other adpaters have been shown they can support this concept.

I am partial to the Dlink, but if others have other USB adapters, and have these similar needs, take a peek at the posts in this thread, some have given details on what additional steps or modified instructions were required to get their USB adapters running using this concept.

If you don't find your USB adapter instructions already listed here, post and maybe we can help you do the same with yours.

This concept should also apply to most, if not all Skype phones as well.

Hi

Thanks for the info Zoverlord. I am going to do this later today. How much of an impact does running these programs as a service have? Will it slow down users who tend to play games etc on the pc?

[quote=woodyear99]Hi

Thanks for the info Zoverlord. I am going to do this later today. How much of an impact does running these programs as a service have? Will it slow down users who tend to play games etc on the pc?[/quote]

You are very welcome.

No there is no overhead, actually, a little higher priority being a system service, which is good not bad when you are active on a call.

This trick also works on the TelerBOX adaptor.

Would you mind sharing the differences in instructions?

To help others with this device.

Thanks

Hello ZOverLord!

There is no difference. :lol:

They are all using TLink softwares and drivers. I don't have the TelerBOX adaptor but I downloaded the driver. And by looking at the pictures and manual, I can tell that the USR 9620 and the TellerBOX are the same.

The only difference is the name of the executable. TellerBOX is using the "Tommade Teller Box.exe" instead of the "DPH-50U Utility.exe".

Here is the link for the TellerBOX:
http://www.tommade-computers.com/voip.htm


[OUT_OF_TOPIC]
@ZOverLord

I examined the "DLinkMonitor.exe" and the "DPH-50U Utility.exe", and I discovered that D-Link also turned off a lot of features. I am looking for the original driver from Voxelle so I can try it.
[/OUT_OF_TOPIC]

Posted a while ago about setting a service up for the Vosky Call Centre. Have managed to look into the processes that run at startup.

There are two listed in msconfig:

"usbvosky.exe" and "usbdram.exe"

Also there is "voskycallcentre.exe" and "audioproxy.exe".

I can't find the auto start entry for these two anywhere - but they are both in the Call Centre's program folder, and are always running alongside usbvosky and usbdram.

Do I have to set up a service for each exe? I have tried to find out what each process does but Vosky's forum was unhelpful.

Thanks

[quote=driggs13]Posted a while ago about setting a service up for the Vosky Call Centre. Have managed to look into the processes that run at startup.

There are two listed in msconfig:

"usbvosky.exe" and "usbdram.exe"

Also there is "voskycallcentre.exe" and "audioproxy.exe".

I can't find the auto start entry for these two anywhere - but they are both in the Call Centre's program folder, and are always running alongside usbvosky and usbdram.

Do I have to set up a service for each exe? I have tried to find out what each process does but Vosky's forum was unhelpful.

Thanks[/quote]

Look in two places, the startup folders for the current user and ALL users
then use msconfig ("From the RUN option"), select startup, see what is starting at startup, most likely, one program is launching another.

In some cases, when they find their partner program missing, they launch the one missing. Try just adding one of them as a system service, te one you DO see to run at startup, then look in your task manager to see if it launches the other automatically.