Sponsor: VoiceMeUp - Corporate & Wholesale VoIP Services

VoIP Mailing List Archives
Mailing list archives for the VoIP community
 SearchSearch 

[Freeswitch-users] Skypiax as a windows service

Goto page 1, 2  Next
 
Post new topic   Reply to topic    VoIP Mailing List Archives Forum Index -> freeSWITCH Users
View previous topic :: View next topic  
Author Message
uv at yuvalhertzog.com
Guest





PostPosted: Mon Apr 13, 2009 6:46 am    Post subject: [Freeswitch-users] Skypiax as a windows service Reply with quote

Great work on Skypiax, Giovanni.

We’ve tested it in our lab for sometime and it works very well.
Unfortunately, when we tried deploying it on a production environment (running Win2K3 server farm), we ran into a barrier:
  1. FS is running as terminal server console application (to be easily maintained remotely by RDP)
  2. This is because Win2K does not allow RDP to access system console (session /userid 0)
  3. Skype does not work on terminal server due to a well known disappearing audio drivers problem, therefore it has to run either as a console or a service (both on session 0).
  4. FS can run well as a windows service
  5. Skypiax seem to load as service, but it can’t find the skype client and exit with the following error:

2009-04-13 20:54:14 [ERR] mod_skypiax.c:990 load_config() rev 13006M[00000000|37 ][ERRORA 990 ][skype_user ][-1, 0, 0] Failed to connect to a SKYPE API for interface_id=1, no SKYPE client running, please (re)start Skype client. Skypiax exiting

This situation prevents me to run skypiax in production.

I understand from the wiki page that windows service is not done yet – so I presume this is a predicted outcome.

Any idea when and if this is planned to be implemented?

Keep up the good work!

Cheers,
UV
Back to top
gmaruzz at celliax.org
Guest





PostPosted: Tue Apr 14, 2009 9:38 am    Post subject: [Freeswitch-users] Skypiax as a windows service Reply with quote

Hi UV,

seems a difficult one this one.

I have no much experience in RDP/terminal server.

If there is no way to have (or fake) audio driver on RDP/terminal
server apps, probably the Skype clients will not works (as you
experienced).

I'm sure, I've read it (Smile ), that Skype clients can be run on a
Windows machine as services, without any user logged in.

That is what I would explore in the future, just adding the How To to
the wiki page.

What you are experiencing seems to be different, seems to be specific
to the RDP/terminal server usage. I'm I understanding you correctly
(that this is specific to RDP)?

Can you send me more info/hints?

In parallel, I'm slowly working on a way to farm out the Skype clients
from the FS servers, so to have the Skype clients running on different
machines on the same LAN. I've a proof of concept working on Linux for
one channel.

You think this would solve your problems (having the Skype clients
running on separate machines other than the machines running FS)?

I'm just back from Easter vacations, please allow a couple days for
the accumulated backlog Wink

Thanks a lot for taking the time to explore Skypiax and report this,
gm


Sincerely,

Giovanni Maruzzelli
=========================================
www.celliax.org
via Pierlombardo 9, 20135 Milano
Italy
gmaruzz at celliax dot org
Cell : +39-347-2665618
Fax : +39-02-87390039




On Mon, Apr 13, 2009 at 1:32 PM, UV <uv@yuvalhertzog.com> wrote:
Quote:
Great work on Skypiax, Giovanni.



We’ve tested it in our lab for sometime and it works very well.

Unfortunately, when we tried deploying it on a production environment
(running Win2K3 server farm), we ran into a barrier:

FS is running as terminal server console application (to be easily
maintained remotely by RDP)
This is because Win2K does not allow RDP to access system console (session
/userid 0)
Skype does not work on terminal server due to a well known disappearing
audio drivers problem, therefore it has to run either as a console or a
service (both on session 0).
FS can run well as a windows service
Skypiax seem to load as service, but it can’t find the skype client and exit
with the following error:

2009-04-13 20:54:14 [ERR] mod_skypiax.c:990 load_config() rev
13006M[00000000|37     ][ERRORA  990  ][skype_user    ][-1, 0, 0] Failed to
connect to a SKYPE API for interface_id=1, no SKYPE client running, please
(re)start Skype client. Skypiax exiting



This situation prevents me to run skypiax in production.



I understand from the wiki page that windows service is not done yet – so I
presume this is a predicted outcome.



Any idea when and if this is planned to be implemented?



Keep up the good work!



Cheers,

UV



_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org



_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
Back to top
uv at yuvalhertzog.com
Guest





PostPosted: Thu Apr 16, 2009 7:01 am    Post subject: [Freeswitch-users] Skypiax as a windows service Reply with quote

Hi Giovanni,

We tried every available fake audio driver (i.e. virtual audio cable) but
with no satisfying results.
As for the Skype as a service - that's not a problem. It's working fine -
but only on Session 0 - which makes it inaccessible for the SkypeAPI from
Skypiax.
The problem is not unique to RDP - but most notable when running the Skypiax
via RDP session.
You'll be able to replicate this problem whenever the Skypiax is not running
in the same session / userID of the Skype.
Decoupling the Skyiax from FS will solve the problem as I assume it'll use
TCP/IP (winsock) to interface with FS - therefore, I can run it still on the
same machine but two separate sessions. However, I think getting the Skypiax
to work as a service will be more beneficial regardless if it's decoupled or
not.

Keep up the good work,

Cheers,
UV


-----Original Message-----
From: freeswitch-users-bounces@lists.freeswitch.org
[mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Giovanni
Maruzzelli
Sent: Wednesday, April 15, 2009 12:28 AM
To: freeswitch-users@lists.freeswitch.org
Subject: Re: [Freeswitch-users] Skypiax as a windows service

Hi UV,

seems a difficult one this one.

I have no much experience in RDP/terminal server.

If there is no way to have (or fake) audio driver on RDP/terminal
server apps, probably the Skype clients will not works (as you
experienced).

I'm sure, I've read it (Smile ), that Skype clients can be run on a
Windows machine as services, without any user logged in.

That is what I would explore in the future, just adding the How To to
the wiki page.

What you are experiencing seems to be different, seems to be specific
to the RDP/terminal server usage. I'm I understanding you correctly
(that this is specific to RDP)?

Can you send me more info/hints?

In parallel, I'm slowly working on a way to farm out the Skype clients
from the FS servers, so to have the Skype clients running on different
machines on the same LAN. I've a proof of concept working on Linux for
one channel.

You think this would solve your problems (having the Skype clients
running on separate machines other than the machines running FS)?

I'm just back from Easter vacations, please allow a couple days for
the accumulated backlog Wink

Thanks a lot for taking the time to explore Skypiax and report this,
gm


Sincerely,

Giovanni Maruzzelli
=========================================
www.celliax.org
via Pierlombardo 9, 20135 Milano
Italy
gmaruzz at celliax dot org
Cell : +39-347-2665618
Fax : +39-02-87390039




On Mon, Apr 13, 2009 at 1:32 PM, UV <uv@yuvalhertzog.com> wrote:
Quote:
Great work on Skypiax, Giovanni.



We’ve tested it in our lab for sometime and it works very well.

Unfortunately, when we tried deploying it on a production environment
(running Win2K3 server farm), we ran into a barrier:

FS is running as terminal server console application (to be easily
maintained remotely by RDP)
This is because Win2K does not allow RDP to access system console (session
/userid 0)
Skype does not work on terminal server due to a well known disappearing
audio drivers problem, therefore it has to run either as a console or a
service (both on session 0).
FS can run well as a windows service
Skypiax seem to load as service, but it can’t find the skype client and
exit
Quote:
with the following error:

2009-04-13 20:54:14 [ERR] mod_skypiax.c:990 load_config() rev
13006M[00000000|37     ][ERRORA  990  ][skype_user    ][-1, 0, 0] Failed
to
Quote:
connect to a SKYPE API for interface_id=1, no SKYPE client running, please
(re)start Skype client. Skypiax exiting



This situation prevents me to run skypiax in production.



I understand from the wiki page that windows service is not done yet – so
I
Quote:
presume this is a predicted outcome.



Any idea when and if this is planned to be implemented?



Keep up the good work!



Cheers,

UV



_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org



_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org


_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
Back to top
gmaruzz at celliax.org
Guest





PostPosted: Thu Apr 16, 2009 10:30 am    Post subject: [Freeswitch-users] Skypiax as a windows service Reply with quote

EG: in the "farm out" scenario there will be FS talking via TCP to a
"farm client" (on local machine or remote). The "farm client" talks
with Skype client instances running on the same machine the "farm
client" is running on.

On Thu, Apr 16, 2009 at 1:47 PM, UV <uv@yuvalhertzog.com> wrote:
Quote:
Decoupling the Skyiax from FS will solve the problem as I assume it'll use
TCP/IP (winsock) to interface with FS - therefore, I can run it still on the
same machine but two separate sessions.

yes, it uses TCP for this. So you would end up with FS (with Skypiax
module) running on RDP while the Skype client instances are running as
services, on the same machine (or in different machines). FS will talk
to Skype client instances via TCP.
Is this acceptable to you?

Other question: why not running FS as a service too? If you run FS as
a service and Skype clients as services, all things would works? Why
you want to use RDP for? (sorry for the silly questions, I just want
to understand better).

Quote:
However, I think getting the Skypiax
to work as a service will be more beneficial regardless if it's decoupled or
not.

What do you mean? I believe that Skypiax (as an FS module) works when
FS is run as service. Your problem seems to me that you cannot run
Skype instances under RDP because they cannot access the sound device.
Is this correct?

gm

_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
Back to top
anthony.minessale at g...
Guest





PostPosted: Thu Apr 16, 2009 5:31 pm    Post subject: [Freeswitch-users] Skypiax as a windows service Reply with quote

are you planning on just signaling on TCP or both audio and signalling
cos realtime audio over TCP kinda stinks.

you may find that just running FS as the farm and calling to it with sip is
more or less the same idea with no work Wink


On Thu, Apr 16, 2009 at 10:09 AM, Giovanni Maruzzelli <gmaruzz@celliax.org (gmaruzz@celliax.org)> wrote:
Quote:
EG: in the "farm out" scenario there will be FS talking via TCP to a
"farm client" (on local machine or remote). The "farm client" talks
with Skype client instances running on the same machine the "farm
client" is running on.

On Thu, Apr 16, 2009 at 1:47 PM, UV <uv@yuvalhertzog.com (uv@yuvalhertzog.com)> wrote:
Quote:
Decoupling the Skyiax from FS will solve the problem as I assume it'll use
TCP/IP (winsock) to interface with FS - therefore, I can run it still on the
same machine but two separate sessions.


yes, it uses TCP for this. So you would end up with FS (with Skypiax
module) running on RDP while the Skype client instances are running as
services, on the same machine (or in different machines). FS will talk
to Skype client instances via TCP.
Is this acceptable to you?

Other question: why not running FS as a service too? If you run FS as
a service and Skype clients as services, all things would works? Why
you want to use RDP for? (sorry for the silly questions, I just want
to understand better).

Quote:
However, I think getting the Skypiax
to work as a service will be more beneficial regardless if it's decoupled or
not.


What do you mean? I believe that Skypiax (as an FS module) works when
FS is run as service. Your problem seems to me that you cannot run
Skype instances under RDP because they cannot access the sound device.
Is this correct?

gm


_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org (Freeswitch-users@lists.freeswitch.org)
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org





--
Anthony Minessale II

FreeSWITCH http://www.freeswitch.org/
ClueCon http://www.cluecon.com/

AIM: anthm
MSN:anthony_minessale@hotmail.com ([email]MSN%3Aanthony_minessale@hotmail.com[/email])
GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com ([email]PAYPAL%3Aanthony.minessale@gmail.com[/email])
IRC: irc.freenode.net #freeswitch

FreeSWITCH Developer Conference
sip:888@conference.freeswitch.org ([email]sip%3A888@conference.freeswitch.org[/email])
iax:guest@conference.freeswitch.org/888
googletalk:conf+888@conference.freeswitch.org ([email]googletalk%3Aconf%2B888@conference.freeswitch.org[/email])
pstn:213-799-1400
Back to top
uv at yuvalhertzog.com
Guest





PostPosted: Thu Apr 16, 2009 6:04 pm    Post subject: [Freeswitch-users] Skypiax as a windows service Reply with quote

Ok, I think I know where's the confusion here. Let me clarify:
1. FS run beautifully as a service - that's why I assumed it should work.
2. Skype client runs as a service very well too.
3. When running FS as a service with Skypiax (hence Skypiax as a service),
Skypiax doesn't seem to find the SkypeAPI.

In the Wiki page
http://wiki.freeswitch.org/wiki/Skypiax#Running_Skypiax_on_Windows_as_a_Serv
ice it's says that Running Skypiax on Windows as a Service is "Not yet
written" therefore I assumed it's a known limitation.

Are you saying it isn't?

Anyway, the farming solution you suggested should solve the problem - I'd
assume.

-----Original Message-----
From: freeswitch-users-bounces@lists.freeswitch.org
[mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Giovanni
Maruzzelli
Sent: Friday, April 17, 2009 1:10 AM
To: freeswitch-users@lists.freeswitch.org
Subject: Re: [Freeswitch-users] Skypiax as a windows service

EG: in the "farm out" scenario there will be FS talking via TCP to a
"farm client" (on local machine or remote). The "farm client" talks
with Skype client instances running on the same machine the "farm
client" is running on.

On Thu, Apr 16, 2009 at 1:47 PM, UV <uv@yuvalhertzog.com> wrote:
Quote:
Decoupling the Skyiax from FS will solve the problem as I assume it'll use
TCP/IP (winsock) to interface with FS - therefore, I can run it still on
the
Quote:
same machine but two separate sessions.

yes, it uses TCP for this. So you would end up with FS (with Skypiax
module) running on RDP while the Skype client instances are running as
services, on the same machine (or in different machines). FS will talk
to Skype client instances via TCP.
Is this acceptable to you?

Other question: why not running FS as a service too? If you run FS as
a service and Skype clients as services, all things would works? Why
you want to use RDP for? (sorry for the silly questions, I just want
to understand better).

Quote:
However, I think getting the Skypiax
to work as a service will be more beneficial regardless if it's decoupled
or
Quote:
not.

What do you mean? I believe that Skypiax (as an FS module) works when
FS is run as service. Your problem seems to me that you cannot run
Skype instances under RDP because they cannot access the sound device.
Is this correct?

gm

_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org


_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
Back to top
gmaruzz at celliax.org
Guest





PostPosted: Fri Apr 17, 2009 1:49 am    Post subject: [Freeswitch-users] Skypiax as a windows service Reply with quote

On Fri, Apr 17, 2009 at 12:30 AM, Anthony Minessale
<anthony.minessale@gmail.com> wrote:
Quote:
are you planning on just signaling on TCP or both audio and signalling
cos realtime audio over TCP kinda stinks.

you may find that just running FS as the farm and calling to it with sip is
more or less the same idea with no work Wink


Hi Anthony,
yes, TCP is not the best for audio. But it's the only way to route
audio from/to the Skype client instance. I mean, it's the only way the
Skype client allows you to access its audio streams.

This is the current situation:
1) mod_skypiax use native signaling (Windows messages, or X events) to
interact with the Skype client through the Skype API.
2) one of the Skype API commands allows for telling to the Skype
client: "please, use this TCP port for audio in, and that TCP port for
audio out, instead of the soundcard".
3) the TCP ports must be on the local IP interface (127.0.0.1)
4) mod_skypiax and the Skype client(s) exchange audio samples through
TCP on the local machine, while signaling is platform native

I would like to have the Skype client instances on another machine,
for security and stability purposes (I'm not trusting consumer grade
Skype client to run on production main FS server).

That's why I was writing the "farming client", for rerouting both the
signaling commands and the audio streams back and forth between two
separate machines.

Now I understand what you wrote: I can use FS itself (with
mod_skypiax) as a "farming client", and connect with the "main" FS via
SIP. So I can achieve the original aim of having a separate machine(s)
with the Skype instances. Obviously, if that's a requirements, I can
optimize the footprint of the "farming client FS" loading only the
modules needed for SIP-Skype interaction.

Thanks a lot Anthony, this cuts the Gordian knot and spare me lots of
pathetic efforts Smile

UV, is this solution practical for you?

Sincerely,

Giovanni Maruzzelli
=========================================
www.celliax.org
via Pierlombardo 9, 20135 Milano
Italy
gmaruzz at celliax dot org
Cell : +39-347-2665618
Fax : +39-02-87390039






Quote:

On Thu, Apr 16, 2009 at 10:09 AM, Giovanni Maruzzelli <gmaruzz@celliax.org>
wrote:
Quote:

EG: in the "farm out" scenario there will be FS talking via TCP to a
"farm client" (on local machine or remote). The "farm client" talks
with Skype client instances running on the same machine the "farm
client" is running on.

On Thu, Apr 16, 2009 at 1:47 PM, UV <uv@yuvalhertzog.com> wrote:
Quote:
Decoupling the Skyiax from FS will solve the problem as I assume it'll
use
TCP/IP (winsock) to interface with FS - therefore, I can run it still on
the
same machine but two separate sessions.

yes, it uses TCP for this. So you would end up with FS (with Skypiax
module) running on RDP while the Skype client instances are running as
services, on the same machine (or in different machines). FS will talk
to Skype client instances via TCP.
Is this acceptable to you?

Other question: why not running FS as a service too? If you run FS as
a service and Skype clients as services, all things would works? Why
you want to use RDP for? (sorry for the silly questions, I just want
to understand better).

Quote:
However, I think getting the Skypiax
to work as a service will be more beneficial regardless if it's
decoupled or
not.

What do you mean? I believe that Skypiax (as an FS module) works when
FS is run as service. Your problem seems to me that you cannot run
Skype instances under RDP because they cannot access the sound device.
Is this correct?

gm

_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org



--
Anthony Minessale II

FreeSWITCH http://www.freeswitch.org/
ClueCon http://www.cluecon.com/

AIM: anthm
MSN:anthony_minessale@hotmail.com
GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com
IRC: irc.freenode.net #freeswitch

FreeSWITCH Developer Conference
sip:888@conference.freeswitch.org
iax:guest@conference.freeswitch.org/888
googletalk:conf+888@conference.freeswitch.org
pstn:213-799-1400

_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org



_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
Back to top
gmaruzz at celliax.org
Guest





PostPosted: Fri Apr 17, 2009 1:51 am    Post subject: [Freeswitch-users] Skypiax as a windows service Reply with quote

On Fri, Apr 17, 2009 at 12:58 AM, UV <uv@yuvalhertzog.com> wrote:
Quote:
Ok, I think I know where's the confusion here. Let me clarify:
1. FS run beautifully as a service - that's why I assumed it should work.
2. Skype client runs as a service very well too.
3. When running FS as a service with Skypiax (hence Skypiax as a service),
Skypiax doesn't seem to find the SkypeAPI.

Why mod_skypiax do not find the API? I know for sure that other
services can access the API on Skype clients running as services. So
mod_skypiax is encountering some specific problem.

I will explore into this one and I'll be back to you.

Quote:

In the Wiki page
http://wiki.freeswitch.org/wiki/Skypiax#Running_Skypiax_on_Windows_as_a_Serv
ice it's says that Running Skypiax on Windows as a Service is "Not yet
written" therefore I assumed it's a known limitation.

Are you saying it isn't?

Was just the documentation "not yet written", I corrected the wiki
page, now reads: "This part of the How To documentation has not yet
been written. Please, feel free to contribute."

Quote:

Anyway, the farming solution you suggested should solve the problem - I'd
assume.

As per the previous Anthony's post, you can use FS itself as a farming solution.

_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
Back to top
uv at yuvalhertzog.com
Guest





PostPosted: Fri Apr 17, 2009 9:08 am    Post subject: [Freeswitch-users] Skypiax as a windows service Reply with quote

You're suggesting running two instances of FS on same machine, have them
communicate first over TCP then UDP via SIP over socket (Skype --> Skypiax
--> FS1 --> FS2) on a production system? Hmmm... nah... Smile

-----Original Message-----
From: freeswitch-users-bounces@lists.freeswitch.org
[mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Giovanni
Maruzzelli
Sent: Friday, April 17, 2009 4:40 PM
To: freeswitch-users@lists.freeswitch.org
Subject: Re: [Freeswitch-users] Skypiax as a windows service

On Fri, Apr 17, 2009 at 12:30 AM, Anthony Minessale
<anthony.minessale@gmail.com> wrote:
Quote:
are you planning on just signaling on TCP or both audio and signalling
cos realtime audio over TCP kinda stinks.

you may find that just running FS as the farm and calling to it with sip
is
Quote:
more or less the same idea with no work Wink


Hi Anthony,
yes, TCP is not the best for audio. But it's the only way to route
audio from/to the Skype client instance. I mean, it's the only way the
Skype client allows you to access its audio streams.

This is the current situation:
1) mod_skypiax use native signaling (Windows messages, or X events) to
interact with the Skype client through the Skype API.
2) one of the Skype API commands allows for telling to the Skype
client: "please, use this TCP port for audio in, and that TCP port for
audio out, instead of the soundcard".
3) the TCP ports must be on the local IP interface (127.0.0.1)
4) mod_skypiax and the Skype client(s) exchange audio samples through
TCP on the local machine, while signaling is platform native

I would like to have the Skype client instances on another machine,
for security and stability purposes (I'm not trusting consumer grade
Skype client to run on production main FS server).

That's why I was writing the "farming client", for rerouting both the
signaling commands and the audio streams back and forth between two
separate machines.

Now I understand what you wrote: I can use FS itself (with
mod_skypiax) as a "farming client", and connect with the "main" FS via
SIP. So I can achieve the original aim of having a separate machine(s)
with the Skype instances. Obviously, if that's a requirements, I can
optimize the footprint of the "farming client FS" loading only the
modules needed for SIP-Skype interaction.

Thanks a lot Anthony, this cuts the Gordian knot and spare me lots of
pathetic efforts Smile

UV, is this solution practical for you?

Sincerely,

Giovanni Maruzzelli
=========================================
www.celliax.org
via Pierlombardo 9, 20135 Milano
Italy
gmaruzz at celliax dot org
Cell : +39-347-2665618
Fax : +39-02-87390039






Quote:

On Thu, Apr 16, 2009 at 10:09 AM, Giovanni Maruzzelli
<gmaruzz@celliax.org>
Quote:
wrote:
Quote:

EG: in the "farm out" scenario there will be FS talking via TCP to a
"farm client" (on local machine or remote). The "farm client" talks
with Skype client instances running on the same machine the "farm
client" is running on.

On Thu, Apr 16, 2009 at 1:47 PM, UV <uv@yuvalhertzog.com> wrote:
Quote:
Decoupling the Skyiax from FS will solve the problem as I assume it'll
use
TCP/IP (winsock) to interface with FS - therefore, I can run it still
on
Quote:
Quote:
Quote:
the
same machine but two separate sessions.

yes, it uses TCP for this. So you would end up with FS (with Skypiax
module) running on RDP while the Skype client instances are running as
services, on the same machine (or in different machines). FS will talk
to Skype client instances via TCP.
Is this acceptable to you?

Other question: why not running FS as a service too? If you run FS as
a service and Skype clients as services, all things would works? Why
you want to use RDP for? (sorry for the silly questions, I just want
to understand better).

Quote:
However, I think getting the Skypiax
to work as a service will be more beneficial regardless if it's
decoupled or
not.

What do you mean? I believe that Skypiax (as an FS module) works when
FS is run as service. Your problem seems to me that you cannot run
Skype instances under RDP because they cannot access the sound device.
Is this correct?

gm

_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org



--
Anthony Minessale II

FreeSWITCH http://www.freeswitch.org/
ClueCon http://www.cluecon.com/

AIM: anthm
MSN:anthony_minessale@hotmail.com
GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com
IRC: irc.freenode.net #freeswitch

FreeSWITCH Developer Conference
sip:888@conference.freeswitch.org
iax:guest@conference.freeswitch.org/888
googletalk:conf+888@conference.freeswitch.org
pstn:213-799-1400

_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org



_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org


_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
Back to top
uv at yuvalhertzog.com
Guest





PostPosted: Fri Apr 17, 2009 9:12 am    Post subject: [Freeswitch-users] Skypiax as a windows service Reply with quote

Give a shout if you get Skypiax working as a service.
I'll be happy to contribute to its wiki about it once you get it working.

-----Original Message-----
From: freeswitch-users-bounces@lists.freeswitch.org
[mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Giovanni
Maruzzelli
Sent: Friday, April 17, 2009 4:50 PM
To: freeswitch-users@lists.freeswitch.org
Subject: Re: [Freeswitch-users] Skypiax as a windows service

On Fri, Apr 17, 2009 at 12:58 AM, UV <uv@yuvalhertzog.com> wrote:
Quote:
Ok, I think I know where's the confusion here. Let me clarify:
1. FS run beautifully as a service - that's why I assumed it should work.
2. Skype client runs as a service very well too.
3. When running FS as a service with Skypiax (hence Skypiax as a service),
Skypiax doesn't seem to find the SkypeAPI.

Why mod_skypiax do not find the API? I know for sure that other
services can access the API on Skype clients running as services. So
mod_skypiax is encountering some specific problem.

I will explore into this one and I'll be back to you.

Quote:

In the Wiki page

http://wiki.freeswitch.org/wiki/Skypiax#Running_Skypiax_on_Windows_as_a_Serv
Quote:
ice it's says that Running Skypiax on Windows as a Service is "Not yet
written" therefore I assumed it's a known limitation.

Are you saying it isn't?

Was just the documentation "not yet written", I corrected the wiki
page, now reads: "This part of the How To documentation has not yet
been written. Please, feel free to contribute."

Quote:

Anyway, the farming solution you suggested should solve the problem - I'd
assume.

As per the previous Anthony's post, you can use FS itself as a farming
solution.

_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org


_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
Back to top
gmaruzz at celliax.org
Guest





PostPosted: Fri Apr 17, 2009 9:14 am    Post subject: [Freeswitch-users] Skypiax as a windows service Reply with quote

On Fri, Apr 17, 2009 at 4:00 PM, UV <uv@yuvalhertzog.com> wrote:
Quote:
You're suggesting running two instances of FS on same machine, have them
communicate first over TCP then UDP via SIP over socket (Skype --> Skypiax
--> FS1 --> FS2) on a production system? Hmmm... nah... Smile


That's exactly what the "farming client" was supposed to attain (and
in my initial idea using TCP instead of UDP). Smile

Using FS is so much better for this purpose, instead of a clumsy
"giovanni's made, TCP based, farming client" you get carrier class
with best throughput/whatever Smile

Yes, this schema will be better employed having the Skype stuff on
different machines than the "main" FS servers.

gm


Quote:
-----Original Message-----
From: freeswitch-users-bounces@lists.freeswitch.org
[mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Giovanni
Maruzzelli
Sent: Friday, April 17, 2009 4:40 PM
To: freeswitch-users@lists.freeswitch.org
Subject: Re: [Freeswitch-users] Skypiax as a windows service

On Fri, Apr 17, 2009 at 12:30 AM, Anthony Minessale
<anthony.minessale@gmail.com> wrote:
Quote:
are you planning on just signaling on TCP or both audio and signalling
cos realtime audio over TCP kinda stinks.

you may find that just running FS as the farm and calling to it with sip
is
Quote:
more or less the same idea with no work Wink


Hi Anthony,
yes, TCP is not the best for audio. But it's the only way to route
audio from/to the Skype client instance. I mean, it's the only way the
Skype client allows you to access its audio streams.

This is the current situation:
1) mod_skypiax use native signaling (Windows messages, or X events) to
interact with the Skype client through the Skype API.
2) one of the Skype API commands allows for telling to the Skype
client: "please, use this TCP port for audio in, and that TCP port for
audio out, instead of the soundcard".
3) the TCP ports must be on the local IP interface (127.0.0.1)
4) mod_skypiax and the Skype client(s) exchange audio samples through
TCP on the local machine, while signaling is platform native

I would like to have the Skype client instances on another machine,
for security and stability purposes (I'm not trusting consumer grade
Skype client to run on production main FS server).

That's why I was writing the "farming client", for rerouting both the
signaling commands and the audio streams back and forth between two
separate machines.

Now I understand what you wrote: I can use FS itself (with
mod_skypiax) as a "farming client", and connect with the "main" FS via
SIP. So I can achieve the original aim of having a separate machine(s)
with the Skype instances. Obviously, if that's a requirements, I can
optimize the footprint of the "farming client FS" loading only the
modules needed for SIP-Skype interaction.

Thanks a lot Anthony, this cuts the Gordian knot and spare me lots of
pathetic efforts Smile

UV, is this solution practical for you?

Sincerely,

Giovanni Maruzzelli
=========================================
www.celliax.org
via Pierlombardo 9, 20135 Milano
Italy
gmaruzz at celliax dot org
Cell : +39-347-2665618
Fax : +39-02-87390039






Quote:

On Thu, Apr 16, 2009 at 10:09 AM, Giovanni Maruzzelli
<gmaruzz@celliax.org>
Quote:
wrote:
Quote:

EG: in the "farm out" scenario there will be FS talking via TCP to a
"farm client" (on local machine or remote). The "farm client" talks
with Skype client instances running on the same machine the "farm
client" is running on.

On Thu, Apr 16, 2009 at 1:47 PM, UV <uv@yuvalhertzog.com> wrote:
Quote:
Decoupling the Skyiax from FS will solve the problem as I assume it'll
use
TCP/IP (winsock) to interface with FS - therefore, I can run it still
on
Quote:
Quote:
Quote:
the
same machine but two separate sessions.

yes, it uses TCP for this. So you would end up with FS (with Skypiax
module) running on RDP while the Skype client instances are running as
services, on the same machine (or in different machines). FS will talk
to Skype client instances via TCP.
Is this acceptable to you?

Other question: why not running FS as a service too? If you run FS as
a service and Skype clients as services, all things would works? Why
you want to use RDP for? (sorry for the silly questions, I just want
to understand better).

Quote:
However, I think getting the Skypiax
to work as a service will be more beneficial regardless if it's
decoupled or
not.

What do you mean? I believe that Skypiax (as an FS module) works when
FS is run as service. Your problem seems to me that you cannot run
Skype instances under RDP because they cannot access the sound device.
Is this correct?

gm

_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org



--
Anthony Minessale II

FreeSWITCH http://www.freeswitch.org/
ClueCon http://www.cluecon.com/

AIM: anthm
MSN:anthony_minessale@hotmail.com
GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com
IRC: irc.freenode.net #freeswitch

FreeSWITCH Developer Conference
sip:888@conference.freeswitch.org
iax:guest@conference.freeswitch.org/888
googletalk:conf+888@conference.freeswitch.org
pstn:213-799-1400

_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org



_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org


_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org


_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
Back to top
gmaruzz at celliax.org
Guest





PostPosted: Fri Apr 17, 2009 9:24 am    Post subject: [Freeswitch-users] Skypiax as a windows service Reply with quote

On Fri, Apr 17, 2009 at 4:02 PM, UV <uv@yuvalhertzog.com> wrote:
Quote:
Give a shout if you get Skypiax working as a service.
I'll be happy to contribute to its wiki about it once you get it working.

Yes, definitely!
gm

_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
Back to top
gmaruzz at celliax.org
Guest





PostPosted: Fri Apr 17, 2009 5:00 pm    Post subject: [Freeswitch-users] Skypiax as a windows service Reply with quote

Quote:
On Fri, Apr 17, 2009 at 4:02 PM, UV <uv@yuvalhertzog.com> wrote:
Quote:
Give a shout if you get Skypiax working as a service.
I'll be happy to contribute to its wiki about it once you get it working.

<shout>got Skypiax working as a service</shout>

I will document this better in the future, but following is the
general idea, from a Vista Home machine:

I assume you have FS configured and working with mod_skypiax (if run
from the command line). I mean, first you have to make sure all is
working as a "normal non-service application", as documented in the
wiki here http://wiki.freeswitch.org/wiki/Skypiax#Skypiax_on_Windows
and in the video here
http://wiki.freeswitch.org/wiki/Skypiax#Windows_Video_How_To

To start the Skype client instances as services, you need to use
instsrv and srvany from "Windows Server 2003 Resource Kit Tools":
http://www.microsoft.com/downloads/details.aspx?FamilyID=9D467A69-57FF-4AE7-96EE-B18C4790CFFD&displaylang=en

Procedure for creating a service is detailed here:
http://support.microsoft.com/kb/137890 (or more shortly here:
http://www.sixxs.net/wiki/Configuring_Windows_Vista#.2816.29__Installing_AICCU_Utility_as_a_Service
)

You create an (empty) service with those tools, then you follow the
procedure steps and as "Parameters" ->"Application" you put the string
"C:\Program Files\Skype\Phone\Skype.exe /secondary /username:skypiax1
/password:xxx"

*use your username and password in the string*

Then, from the "services" applet in Control Center ->administrative
tools, you make sure the service is owned by "local system" and that
"Access desktop" is ticked.

Start the service manually from the "services" applet.
Maybe it will appear a "the service wants to access the desktop". Go
to "show message" to see what Skype wants, and give some
configurations if needed.

Then you install FS as service (freeswitch.exe -install servicename),
start FS as a service (under "local system"), manually (again, from
the "services" applet).
It will appear "the service wants to access the desktop". Go there and
give Skype authorization to be connected by FS, forever.

Stop both services.

Restart both services, manually. First the Skype clients, then after
a while, FS.

Quote:
From another machine, make a Skype call to FS.

If all works as expected, stop both services, make sure (via
"services" applet) the FS service will retry three times to start,
with a minute pause (just to allow for the Skype clients to start and
settle their connection with the network, to be on the safe side).

Make the services to start "automatic".

Reboot the machine, don't log in, make another test call to FS via
Skype, and... shout Smile

PS: instead of having the service to start one only instance of skype,
you can probably make the service to start a .CMD file that will start
many instances, a la startskype.bat

I'll look into this soon.


Sincerely,

Giovanni Maruzzelli
=========================================
www.celliax.org
via Pierlombardo 9, 20135 Milano
Italy
gmaruzz at celliax dot org
Cell : +39-347-2665618
Fax : +39-02-87390039

_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
Back to top
gmaruzz at celliax.org
Guest





PostPosted: Fri Apr 17, 2009 5:20 pm    Post subject: [Freeswitch-users] Skypiax as a windows service Reply with quote

On Fri, Apr 17, 2009 at 11:58 PM, Giovanni Maruzzelli
<gmaruzz@celliax.org> wrote:
Quote:
Then you install FS as service (freeswitch.exe -install servicename),
start FS as a service (under "local system"), manually (again, from
the "services" applet).

make sure the FS service is owned by "local system" and that "Access
desktop" is ticked.


gm

On Fri, Apr 17, 2009 at 11:58 PM, Giovanni Maruzzelli
<gmaruzz@celliax.org> wrote:
Quote:
Quote:
On Fri, Apr 17, 2009 at 4:02 PM, UV <uv@yuvalhertzog.com> wrote:
Quote:
Give a shout if you get Skypiax working as a service.
I'll be happy to contribute to its wiki about it once you get it working.

<shout>got Skypiax working as a service</shout>

I will document this better in the future, but following is the
general idea, from a Vista Home machine:

I assume you have FS configured and working with mod_skypiax (if run
from the command line). I mean, first you have to make sure all is
working as a "normal non-service application", as documented in the
wiki here http://wiki.freeswitch.org/wiki/Skypiax#Skypiax_on_Windows
and in the video here
http://wiki.freeswitch.org/wiki/Skypiax#Windows_Video_How_To

To start the Skype client instances as services, you need to use
instsrv and srvany from "Windows Server 2003 Resource Kit Tools":
http://www.microsoft.com/downloads/details.aspx?FamilyID=9D467A69-57FF-4AE7-96EE-B18C4790CFFD&displaylang=en

Procedure for creating a service is detailed here:
http://support.microsoft.com/kb/137890 (or more shortly here:
http://www.sixxs.net/wiki/Configuring_Windows_Vista#.2816.29__Installing_AICCU_Utility_as_a_Service
)

You create an (empty) service with those tools, then you follow the
procedure steps and as "Parameters" ->"Application" you put the string
"C:\Program Files\Skype\Phone\Skype.exe /secondary /username:skypiax1
/password:xxx"

*use your username and password in the string*

Then, from the "services" applet in Control Center ->administrative
tools, you make sure the service is owned by "local system" and that
"Access desktop" is ticked.

Start the service manually from the "services" applet.
Maybe it will appear a "the service wants to access the desktop". Go
to "show message" to see what Skype wants, and give some
configurations if needed.

Then you install FS as service (freeswitch.exe -install servicename),
start FS as a service (under "local system"), manually (again, from
the "services" applet).
It will appear "the service wants to access the desktop". Go there and
give Skype authorization to be connected by FS, forever.

Stop both services.

Restart both services, manually. First the Skype clients,  then after
a while, FS.

From another machine, make a Skype call to FS.

If all works as expected, stop both services, make sure (via
"services" applet) the FS service will retry three times to start,
with a minute pause (just to allow for the Skype clients to start and
settle their connection with the network, to be on the safe side).

Make the services to start "automatic".

Reboot the machine, don't log in, make another test call to FS via
Skype, and... shout Smile

PS: instead of having the service to start one only instance of skype,
you can probably make the service to start a .CMD file that will start
many instances, a la startskype.bat

I'll look into this soon.


Sincerely,

Giovanni Maruzzelli
=========================================
www.celliax.org
via Pierlombardo 9, 20135 Milano
Italy
gmaruzz at celliax dot org
Cell : +39-347-2665618
Fax : +39-02-87390039


_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
Back to top
gmaruzz at celliax.org
Guest





PostPosted: Sun Apr 19, 2009 7:51 am    Post subject: [Freeswitch-users] Skypiax as a windows service Reply with quote

I tried it on Vista, and it works.

The trick for me (on Vista) is to use the same "local system" account
for both the Skype and the FS services, and *NOT* to use a personal
account. Go figure... Smile

BTW: I tried to use the *.bat you can find in mod_skypiax/configs/
renamed as *.cmd for starting multiple Skype client instances with a
single service, and it works.


Sincerely,

Giovanni Maruzzelli
=========================================
www.celliax.org
via Pierlombardo 9, 20135 Milano
Italy
gmaruzz at celliax dot org
Cell : +39-347-2665618
Fax : +39-02-87390039




On Sun, Apr 19, 2009 at 2:40 PM, UV <uv@yuvalhertzog.com> wrote:
Quote:
The service creation steps you described are identical to what we've done.
The only difference, as having the Skype service running on "local system"
doesn't seem to work on Win2K3 server...
Maybe this works on XP but on Win2K3 it behaves as if it doesn't find the
audio devices.
It does work on a user (such as administrator) account.

We tried it on few servers.
Any insight?

-----Original Message-----
From: freeswitch-users-bounces@lists.freeswitch.org
[mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Giovanni
Maruzzelli
Sent: Saturday, April 18, 2009 8:11 AM
To: freeswitch-users@lists.freeswitch.org
Subject: Re: [Freeswitch-users] Skypiax as a windows service

On Fri, Apr 17, 2009 at 11:58 PM, Giovanni Maruzzelli
<gmaruzz@celliax.org> wrote:
Quote:
Then you install FS as service (freeswitch.exe -install servicename),
start FS as a service (under "local system"), manually (again, from
the "services" applet).

make sure the FS service is owned by "local system" and that "Access
desktop" is ticked.


gm

On Fri, Apr 17, 2009 at 11:58 PM, Giovanni Maruzzelli
<gmaruzz@celliax.org> wrote:
Quote:
Quote:
On Fri, Apr 17, 2009 at 4:02 PM, UV <uv@yuvalhertzog.com> wrote:
Quote:
Give a shout if you get Skypiax working as a service.
I'll be happy to contribute to its wiki about it once you get it
working.
Quote:

<shout>got Skypiax working as a service</shout>

I will document this better in the future, but following is the
general idea, from a Vista Home machine:

I assume you have FS configured and working with mod_skypiax (if run
from the command line). I mean, first you have to make sure all is
working as a "normal non-service application", as documented in the
wiki here http://wiki.freeswitch.org/wiki/Skypiax#Skypiax_on_Windows
and in the video here
http://wiki.freeswitch.org/wiki/Skypiax#Windows_Video_How_To

To start the Skype client instances as services, you need to use
instsrv and srvany from "Windows Server 2003 Resource Kit Tools":

http://www.microsoft.com/downloads/details.aspx?FamilyID=9D467A69-57FF-4AE7-
96EE-B18C4790CFFD&displaylang=en
Quote:

Procedure for creating a service is detailed here:
http://support.microsoft.com/kb/137890 (or more shortly here:

http://www.sixxs.net/wiki/Configuring_Windows_Vista#.2816.29__Installing_AIC
CU_Utility_as_a_Service
Quote:
)

You create an (empty) service with those tools, then you follow the
procedure steps and as "Parameters" ->"Application" you put the string
"C:\Program Files\Skype\Phone\Skype.exe /secondary /username:skypiax1
/password:xxx"

*use your username and password in the string*

Then, from the "services" applet in Control Center ->administrative
tools, you make sure the service is owned by "local system" and that
"Access desktop" is ticked.

Start the service manually from the "services" applet.
Maybe it will appear a "the service wants to access the desktop". Go
to "show message" to see what Skype wants, and give some
configurations if needed.

Then you install FS as service (freeswitch.exe -install servicename),
start FS as a service (under "local system"), manually (again, from
the "services" applet).
It will appear "the service wants to access the desktop". Go there and
give Skype authorization to be connected by FS, forever.

Stop both services.

Restart both services, manually. First the Skype clients,  then after
a while, FS.

From another machine, make a Skype call to FS.

If all works as expected, stop both services, make sure (via
"services" applet) the FS service will retry three times to start,
with a minute pause (just to allow for the Skype clients to start and
settle their connection with the network, to be on the safe side).

Make the services to start "automatic".

Reboot the machine, don't log in, make another test call to FS via
Skype, and... shout Smile

PS: instead of having the service to start one only instance of skype,
you can probably make the service to start a .CMD file that will start
many instances, a la startskype.bat

I'll look into this soon.


Sincerely,

Giovanni Maruzzelli
=========================================
www.celliax.org
via Pierlombardo 9, 20135 Milano
Italy
gmaruzz at celliax dot org
Cell : +39-347-2665618
Fax : +39-02-87390039


_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org


_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org


_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
Back to top
Display posts from previous:   
Post new topic   Reply to topic    VoIP Mailing List Archives Forum Index -> freeSWITCH Users All times are GMT - 5 Hours
Goto page 1, 2  Next
Page 1 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group

VoiceMeUp - Corporate & Wholesale VoIP Services