You will find all commands available to you in Advanced -> DCE -> Commands in the web admin. In that list is also the device that implements it (the device the command must be sent to).

In your case you might find what you are looking for with "Spawn Application" in the App_Server device (note that there is one App_Server per computer).

br,
sambuca

I have experienced that ipsec has stopped a few times - I haven't looked any more at it.

I'm sorry, but I don't know much about xl2tpd in this regard.

br,
sambuca

From auth.log I can see that the ipsec connection has been established. But I see no record of the connection part of xl2tpd/pppd in syslog. Are you sure you have copied enough of the log?

br,
sambuca

There are events for sunset and sunrise, you can use those instead.

Also see http://wiki.linuxmce.org/index.php/Event_criteria#Time_of_Day.

br,
sambuca

pw44, from the logs it seem like the ipsec connection has been established succesfully, but there are no record of any xl2tpd activity. Are xl2tdp running?

br,
sambuca

Mine is

virtual_private=%4:192.168.80.0/24

and it is working, so I don't think that is your problem.

I found I couldn't get a connection to work however until I replaced the !VPNpass1 against my user with a plain text password.  Hope this helps someone make sense of the issues.

What do you mean, "!VPNPass1" seems pretty plain text to me..?

br,
sambuca

It is the "Can connect to VPN" setting, yes.

br,
sambuca

Just for reference, this is the wiki page that describes VPN in LMCE (http://wiki.linuxmce.org/index.php/VPN). I'm sure most of you have read it already, though.

There are some gotchas in there as well, for instance this

Note: Currently you need to re-enable the user and change his username after any change to the Network settings page as the files are rewritten

Also, messing around with forwarding network ports without understanding how VPN works can be a big security problem:

Do NOT forward port 1701 (L2TP), this would have allowed direct access to the L2TP server, bypassing IPSEC entirely and sending all your data unencrypted. The whole idea is that the IPSEC connection encrypts your data from end to end, and on the server end, this data will be passed on to port 1701 internally.

It *is* easier to get a connection when not going through IPSEC, but some devices will happily connect to the L2TP server if the IPSEC fails for some reason.

That said, my biggest hurdle getting VPN set up was to configure other network routers in the path (my broadband router) properly. This was mostly a try-and-fail history until I got the correct setting. Any setting related to IPSEC should be tried in all their possible settings (I had to turn one IPSEC setting off to get mine working). It seems to me that IPSEC is the cause of most problems with this VPN, so that is where I would do my investigations.

And in one case I was unable to get VPN working from one particular network because of the router at that site (or possibly other network limitation at that site).

If you have any concrete questions I can try to answer them.

best regards,
sambuca

You perhaps need to do a sqlCVS update. In the web admin -> Advanced -> sqlCVS -> Update. Check all (at least under DCE), and click next. (You need to have allowed popup windows for this to work.)

See if that helps.

br,
sambuca

I use the SPA3102 in 1004 as a phone line (PSTN -> IP adapter). I configured it using the phone lines page in the web admin. You have to select the SPA protocol. What took the most work was to set up the SPA itself.

And for the provider setups, if the setups had been integrated into LinuxMCE, they would probably have been considered when changing the Asterisk setup for 1004. Because they were only in a wiki page, they most probably were not.

br,
sambuca

Yes, posde did a fix today. The event template was wrong, so it did not match the doorbell device correctly.

br,
sambuca

Hi

I think we use Asterisk 1.8 at the moment (in 1004 at least), so in that case the module might be available. But it is probably not loaded by default. Maybe it is as simple as a configuration change?

You might run into some LMCE specific issues, it depends on your device I suppose and what setting it requires.

Creating a device template is always the recommended option. This way you don't have to create it again if you reinstall or otherwise break you system. And other people can also benefit from it.

br,
sambuca

pw44, I tested the link and it does not work. Don't know why, but there is probably something different about that m3u URL than other m3u URLs. Might be some server settings that is different (content-type) or difference in the file itself. I'm really just blurting out ideas here... 

While it is bad that this URL doesn't work, I'm not sure if we will do anything to support it, as this is a xine-lib thing. It depends on what the problem is and if we can do simple changes to fix it. If you could identify any differences between a working URL and a non-working URL, we might be able to consider a fix for it.

br,
sambuca

Yes, m3u files are supported in the radio scenario. I have m3u links that works in my setup. So I'm guessing this is a problem with your particular url.

For information, we use xine-libs support for playlist urls.

br,
sambuca

LMCE now uses the realtime db feature of Asterisk to do the setup, so there are no files to edit.

You should be able to set up phones and lines using the "Wizard" pages (not the advanced pages). Look for "Wizard - Devices - Phones" and ".. - Phone Lines".

best regards,
sambuca