It seems there is an account name / password problem.

[j_friedrich]

Hi.

"It seems there is an account name / password problem."

Come on guys. We are following the the Skype gateway tutorial to the letter and we are getting these issues... We have looked at the account generation and everything else. The new gateway has some options that are even addressed in the online faq. Help us out and update your step by step instructions. We are looking to implement this and are looking for a little help. Sorry for the frustration. We just want to get this up and running.

Thanks for everyone's time.

Jason

 

[ricorocks1]

I have the problem with account name / password problem. I have changed the permsisions so that the group can log on locally, but no success. When I check the security log, it seems that the account is not using the domain to log on:

User Name: 3cxskypeacc01
Domain: [Computer name is here rather than the domain]

Is that right? Can it be changed to use the domain?

 

[dab]

IMHO it's not possible to use domain accounts. why not use local accounts? ok, I know "bestpractise" and company wide regulations are a point, but even if our pbx is windows based, for me the question is "is it a good idea to place the system in the domain?", for the moment if the system isn't more integrated in Active Directory there is no real need to do this. Where is your pbx placed in your network layout? DMZ? Active Directory members in the DMZ?

 

[ricorocks1]

Thanks for your reply Daniel, but I don't think you can add local users to SBS 2003 (I'm willing to be proved wrong!). The Skype Gateway created the user in the AD as expected, but then tries to log on using a local account which isn't there. I only installed all this yesterday to see if the program works for me, so I'm a still getting my head round it all.
Is there any way to change the username in the Skype Gateway. I can't see any obvious ways.

 

[dab]

Ok, I see your problem. But I think it's impossible to install it according to: http://www.3cx.com/voip-gateways/skype.html

3CX Gateway for Skype can not be installed on a domain controller

Do you have a different machine? This can be done ...

 

[ricorocks1]

Ok. Sorry for not reading that before.

As I say, only had a quick play, but from what I've seen the product looks good. And the responses on the forum are quick! I'll fish out an old box and see what I can do with a new install!

Thanks again.

 

[danrajkumar]

I'm having the same problem after having tried all the suggestions in this thread. I'm using Win Server 2008.
The 3CX Skype Gateway seems to be unable to create users on the domain. Event after manually creating a few users they fail to login.

After checking the security logs I see the logon process is Advapi - not sure what that means but I get bad username / password errors.

The tracelog says the same.

I know all the details configured in the gateway are correctly set.
Any help you be appreciated.

 

[vinet]

As noted, the 3CX Skype Gateway Monitor cannot be installed on a Domain Controller.

I've tried all sorts of workarounds; including everything above, but to no avail.

I ended up using the Server2008 embedded Hyper-V to virtualize a WinXP machine, installed Skype, .NET Framework 2.0/3.5, and finally the 3CX Skype Gateway Monitor, and it worked.

This workaround works. Be sure to give the virtualized guest a little extra processor priority & sufficient RAM to run, or you'll find quite a bit of lag I tried 512MB RAM, and that just didn't seem to do it. 1GB was better; 1.5GB was smooth.



FYI: Our SBS2011 domain controller is running on a Core i5-560 /w 8GB physical RAM memory, couple of IMSM RAID mirrors.

 

[vinet]

====>>>> EDIT <<<<====

This doesn't work via Hyper-V as proposed!

When connected to your virtual guest OS (WinXP in this scenario) you get a 'Virtual RDP Audio Controller' installed. However, when you log OUT the controller disappears and the poor virtual machine's Skype no longer has an audio controller. :x

I would like to try it again using a virtual environment other than Hyper-V that _supports_ audio, like VMWare or VirtualBox, but unfortunately we use this particular system to support our Terminal Server via Hyper-V, and you can't have more than one virtual system running concurrently ... or at least not without a whole lot of headache.

So I'm off to refurbish an old desktop as a Skype gateway instead ... I will post results.

Sorry for any false hopes

 

[hainesk967]

I use Windows Server 2008 and Skype 5.3.32 just fine. However I don't use the Skype gateway with 3CX, I just use SIPtoSIS on my home computer and set it up to connect to my server as a PSTN gateway and it works great since my server doesn't have a sound card. If you have any questions on how to do that let me know.