LinuxMCE - User contributions [en]

Postfix configured with Gmail SMTP

2012-02-16T18:36:56Z

Sedgington: The /usr/pluto/bin directory already contains Configure_Postfix_interactive.sh do not follow the steps for installing as the file it links to will not untar. Just run the script

[[Category:Tutorials]]

== Configure Postfix to send mail using Gmail SMTP servers ==

For those who want to send email from LinuxMCE, you can configure postfix to forward mail through your gmail account.

'''Please NOTE: The /usr/pluto/bin directory already contains Configure_Postfix_interactive.sh
Do NOT follow the steps for installing as the file in the link will not untar once downloaded.

Just run the script in /usr/pluto/bin directory.'''

== This has been rolled into the web admin now and should not be done manually! ==

=== Confirmed working with 810 ===

== Automatic Install and Configure Postfix ==

I have created scripts that can be ingegrated ino linuxmce, or run in interactive mode.

Go to the console of your core as root.

Get the scripts:
wget http://donpaul.info/configure_postfix.tar

Untar the scripts:
cd /usr/pluto/bin ; tar -xvf /root/configure_postfix.tar

Run the interactive script:
/usr/pluto/bin/Configure_Postfix_interactive.sh

== Manual Install and Configure Postfix ==

If you prefer to do things yourself...

'''* make sure you replace "Full Name" with your name, and "user@gmail.com" with your actual gmail address. *'''

Install postfix

apt-get install postfix

Create the CA:

/usr/lib/ssl/misc/CA.pl -newca

CA certificate filename (or enter to create)

Making CA certificate ...
Generating a 1024 bit RSA private key
.............++++++
..++++++
writing new private key to './demoCA/private/cakey.pem'
Enter PEM pass phrase:
Verifying - Enter PEM pass phrase:
-----
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [AU]:US
State or Province Name (full name) [Some-State]:North Carolina
Locality Name (eg, city) []:
Organization Name (eg, company) [Internet Widgits Pty Ltd]:LinuxMCE
Organizational Unit Name (eg, section) []:
Common Name (eg, YOUR name) []:Full Name
Email Address []:email@gmail.com

Please enter the following 'extra' attributes
to be sent with your certificate request
A challenge password []:
An optional company name []:
Using configuration from /usr/lib/ssl/openssl.cnf
Enter pass phrase for ./demoCA/private/cakey.pem:
Check that the request matches the signature
Signature ok
Certificate Details:
Serial Number:
9d:29:da:d3:76:20:17:10
Validity
Not Before: Mar 31 01:01:29 2009 GMT
Not After : Mar 30 01:01:29 2012 GMT
Subject:
countryName = US
stateOrProvinceName = North Carolina
organizationName = LinuxMCE
commonName = Full Name
emailAddress = usrer@gmail.com
X509v3 extensions:
X509v3 Subject Key Identifier:
A0:79:00:CA:90:00:E4:81:12:00:2A:73:00:00:CA:BD:54:08:03:7B
X509v3 Authority Key Identifier:
keyid:A0:79:00:CA:90:00:E4:81:12:00:2A:73:00:00:CA:BD:54:08:03:7B
DirName:/C=US/ST=North Carolina/O=LinuxMCE/CN=Full name/emailAddress=user@gmail.com
serial:90:20:0A:03:06:00:17:10

X509v3 Basic Constraints:
CA:TRUE
Certificate is to be certified until Mar 30 01:01:29 2012 GMT (1095 days)

Write out database with 1 new entries
Data Base Updated</nowiki>

Extend the key for 10 years

openssl x509 -in demoCA/cacert.pem -days 3650 -out cacert.pem -signkey demoCA/private/cakey.pem

Copy the extended key

cp cacert.pem demoCA

Generate private key

openssl req -new -nodes -subj '/CN=dcerouter/C=US/ST=North Carolina/O=LinuxMCE/CN=Full Name/emailAddress=user@gmail.com' -keyout key.pem -out req.pem -days 3650

Sign private key

openssl ca -out cert.pem -infiles req.pem

Copy to the postfix directory

cp demoCA/cacert.pem /etc/postfix
cp key.pem /etc/postfix
cp cert.pem /etc/postfix
chmod 644 /etc/postfix/cert.pem
chmod 644 /etc/postfix/cacert.pem
chmod 400 /etc/postfix/key.pem

Install the CA Certificates

apt-get install ca-certificates

Add Equifax certificate

cat /etc/ssl/certs/Equifax_Secure_CA.pem >> cacert.pem

Create transport file:

# Contents of /etc/postfix/transport
#
# This sends mail to Gmail
* smtp:[smtp.gmail.com]:587
#local mail delivered local
dcerouter relay:[dcerouter]

Create generic file
touch /etc/postfix/generic

Create sasl_passwd file:

# Contents of /etc/postfix/sasl_passwd
#
[smtp.gmail.com]:587 user@gmail.com:password

Be sure to hash the files:

postmap sasl_passwd
postmap transport
postmap generic

Add these lines to the bottom of /etc/postfix/main.cf

## TLS Settings
smtp_tls_loglevel = 1
smtp_enforce_tls = yes
smtp_tls_CAfile = /etc/postfix/cacert.pem
smtp_tls_cert_file = /etc/postfix/cert.pem
smtp_tls_key_file = /etc/postfix/key.pem
smtp_tls_session_cache_database = btree:/var/run/smtp_tls_session_cache
smtp_use_tls = yes
smtpd_tls_CAfile = /etc/postfix/cacert.pem
smtpd_tls_cert_file = /etc/postfix/cert.pem
smtpd_tls_key_file = /etc/postfix/key.pem
smtpd_tls_received_header = yes
smtpd_tls_session_cache_database = btree:/var/run/smtpd_tls_session_cache
smtpd_use_tls = yes
tls_random_source = dev:/dev/urandom

## SASL Settings
# This is going in to THIS server
smtpd_sasl_auth_enable = no
# We need this
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtpd_sasl_local_domain = $myhostname
smtp_sasl_security_options = noanonymous
#smtp_sasl_security_options =
smtp_sasl_tls_security_options = noanonymous
smtpd_sasl_application_name = smtpd

## Gmail Relay
relayhost = [smtp.gmail.com]:587

# Disable DNS Lookups
disable_dns_lookups = yes
#
# Great New feature Address Mapping
# for example may mchirico@localhost to mchirico@gmail.com
smtp_generic_maps = hash:/etc/postfix/generic
#
#
transport_maps = hash:/etc/postfix/transport

restart postfix

/etc/init.d/postfix restart

install mailx

apt-get install mailx

test forward

mailx -s "testing from linuxmce" youremail@domain.com < /etc/hosts

View log

tail /var/log/mail.log

You should see your message "Sent"

Changing Xine Player Audio Settings

2011-11-13T20:20:18Z

Sedgington: /* Troubleshooting audio setup */

LinuxMCE Xine Player audio settings are configured at [[LinuxMCE Admin Website]], at the [[Media Directors]] section. The format of corresponding Device Data item is a string, containing 0 or more character flags (see possible values below):

'''C''' = S/PDIF Coaxial, Xine option 'audio.alsa_front_device' will be set to 'asym_spdif'

'''O''' = S/PDIF TosLink/Optical, Xine option 'audio.alsa_front_device' will be set to 'asym_spdif'

'''S''' = Analog Stereo, Xine option 'audio.alsa_front_device' will be set to 'plughw:0'

'''L''' = Analog Multi-channel, Xine option 'audio.alsa_front_device' will be set to 'plughw:0'

::(this probably refers to 4.0 and 5.1 using analog jacks for 2-channel pairs)

'''3''' = AC3/DTS PassThrough, Xine option 'audio.output.speaker_arrangement' will be set to 'Pass Through'

::(if '''3''' is not present, 'audio.output.speaker_arrangement' will be set to 'Stereo 2.0')

'''M''' = Manual, if the flag is present, the whole configuration string will be ignored and defaults from /etc/pluto/xine.conf won't be overridden

== Troubleshooting audio setup ==
1. Sometimes A/V wizard won't work and here's simple help to try settings :

Play sample music on default output (analog out on most MDs)
mpg321 /usr/pluto/sound/avwizard_volume_test.mp3

in 8.10 this file can be found here (you must first apt-get install mpg321):

mpg321 /home/public/data/avwizard-sounds/avwizard_volume_test.mp3

Play sample music on spdif output (not sure how this is different for optical or coax spdif)
mpg321 -a asym_spdif /usr/pluto/sound/avwizard_volume_test.mp3
[[Category:Tutorials]]
[[Category:Troubleshooting]]

Changing Xine Player Audio Settings

2011-11-13T20:19:37Z

Sedgington: gave proper link for file to test in 8.10

LinuxMCE Xine Player audio settings are configured at [[LinuxMCE Admin Website]], at the [[Media Directors]] section. The format of corresponding Device Data item is a string, containing 0 or more character flags (see possible values below):

'''C''' = S/PDIF Coaxial, Xine option 'audio.alsa_front_device' will be set to 'asym_spdif'

'''O''' = S/PDIF TosLink/Optical, Xine option 'audio.alsa_front_device' will be set to 'asym_spdif'

'''S''' = Analog Stereo, Xine option 'audio.alsa_front_device' will be set to 'plughw:0'

'''L''' = Analog Multi-channel, Xine option 'audio.alsa_front_device' will be set to 'plughw:0'

::(this probably refers to 4.0 and 5.1 using analog jacks for 2-channel pairs)

'''3''' = AC3/DTS PassThrough, Xine option 'audio.output.speaker_arrangement' will be set to 'Pass Through'

::(if '''3''' is not present, 'audio.output.speaker_arrangement' will be set to 'Stereo 2.0')

'''M''' = Manual, if the flag is present, the whole configuration string will be ignored and defaults from /etc/pluto/xine.conf won't be overridden

== Troubleshooting audio setup ==
1. Sometimes A/V wizard won't work and here's simple help to try settings :

Play sample music on default output (analog out on most MDs)
mpg321 /usr/pluto/sound/avwizard_volume_test.mp3

in 8.10 this file can be found here (you must first apt-get install mpg3210:

mpg321 /home/public/data/avwizard-sounds/avwizard_volume_test.mp3

Play sample music on spdif output (not sure how this is different for optical or coax spdif)
mpg321 -a asym_spdif /usr/pluto/sound/avwizard_volume_test.mp3
[[Category:Tutorials]]
[[Category:Troubleshooting]]

LG 42LB5D

2010-03-25T16:29:04Z

Sedgington:

[[Category: Video]]
[[Category: Displays]]

{| align="right"
| __TOC__
|}
==Features==
===Basics===
* 42" (diagonal) [[16:9|widescreen]] [[LCD]] television
* Good build quality on the whole, though some edges on the plastic casing were left "sharp" (I'm OCD about fit and finish)
* Not that heavy for its size (one person can lift it, in or out of packing carton)
Special features and nice touches:
* [[RS232 port]] at the back to allow external control (by LinuxMCE for example)
* Power LED is red on standby, and switches to green when set is on (thank goodness, blue-LED fever is abating! :-)
* Brightness can be instantly adjusted via two remote buttons -- the only thing better would be a photosensor that adjusts things automatically for ambient light (but that's what hacking is all about ;-)
===Picture fidelity===
* Crisp picture when provided with full quality source (e.g. true HD)
* Crisp picture with some ghosting when using the RGB-PC input with a standard (though longer than average) VGA video cable -- I will try to add a photo of the effect; the lowest-tech connections ([[S-Video]], RF, and the like) for PC video are NOT recommended!
* A touch blurry with low-end sources ([[S-Video]], RF) like older game systems, but still a fairly good overall picture; I have yet to test other signal methods with my game systems (requires special cables I don't yet have).
===Usability===
* The [[OSD]] UI and remote are excellent. Both the menus and the buttons are laid out sensibly, and the system incorporates a great idea for settings that are cyclic (most are): the first time you press a button (e.g. [[aspect ratio]]), it brings up an [[OSD]] reminder of the current setting; subsequent presses will cycle through the available options. It's simple, and effective at preventing accidental setting changes by a single inadvertent button press on the remote.
Resolutions:
* 1024x768
* 1280x768
* 1360x768

== Adding new template ==
Here is a description of adding a Template for LG LCD TV with serial connections for control. According to the manual the following models should work:
LCD TV MODELS 37LB5D / 42LB5D / 47LB5D 52LB5D/ 32LB4D / 37LB4D / 42LB4D
I have the 42LB5D, so I know that this one works.

=== Specify device data and parameters ===

On the LinuxMCE admin website go to: Advanced > Configuration > Device Templates

Select: Manufacturer 'LG', Device Category 'TVs/Plasmas/LCD's/Projectors' and press 'Add device template'

Description : XXLB4/5D
Implements DCE : yes
Command line : Generic_Serial_Device
Device Category AV TVs/Plasmas/Projection... #77
Manufacturer LG

Also have added following parameters (You need to add them one by one under the header 'Device data'):

Device data
Current Data Comments Default Value
#37 COM Port on PC(string) The serial port
#76 COM Port ParityBit/Stop(string) Parity/Stop bits (factory defaults) N81
#78 COM Port BaudRate(string) Baud rate (factory default) B9600
#157 Discrete Volume(bool) Indicates if the volume on... 1

Settings are factory defaults and shouldn't be changed (9600 baud rate, 8 bits, 1 stop bit). Make sure that the check box for Allowed to Modify is checked, so that you can change to the appropriate COM port later.

=== 'Edit Ruby code' (on template page) ===

==== 'Add/remove commands' ====
First, I clicked on 'Add/remove commands' and clicked on commands that are supported by device...

* Ruby Internal Commands
* Standard TV

==== 'Add Ruby snippets to commands'====
Edited corresponding Ruby snippets for each command. Basically those are just simple strings that get send on rs232 to take proper action on device according to received command from LinuxMCE... Use the extended editor for the multiline entries (otherwise ruby won't understand it and gives lot's of errors)
<pre>
#193 Off
log('Sending OFF Command')
<$"ka 01 00\r"$>
#192 On
log('Sending ON Command')
<$"ka 01 01\r"$>
Inputs
#419 Antenna

#316 AV 1
log('Switching Input to AV1')
<$"kb 01 02\r"$>
#317 AV 2
log('Switching Input to AV2')
<$"kb 01 03\r"$>
#712 Component 1
log('Switching Input to Component 1')
<$"kb 01 04\r"$>
#713 Component 2
log('Switching Input to Component 2')
<$"kb 01 05\r"$>
#426 External 3
log('Switching Input to HDMI 3')
<$"kb 01 09\r"$>
#361 HDMI
log('Switching Input to HDMI 1')
<$"kb 01 07\r"$>
#767 HDMI 2
log('Switching Input to HDMI 2')
<$"kb 01 08\r"$>
#376 Input 3
log('Switching Input to HDMI 3')
<$"kb 01 09\r"$>
#154 RGB
log('Switching Input to RGB/PC')
<$"kb 01 06\r"$>
#166 Tuner
log('Switching Input to Analog Tuner')
<$"kb 01 01\r"$>
#873 Tuner - Digital
log('Switching Input to Digital Tuner')
<$"kb 01 00\r"$>
Aspect Ratios
#879 16:9
log('Switching Aspect Ratio to 16:9')
<$"kc 01 02\r"$>
#877 4:3
log('Switching Aspect Ratio to 4:3')
<$"kc 01 01\r"$>
Disk Handle
#48 Eject Disk

DSP Modes
#116 DSP Mode
log('Switching DSP Modes: Toggled Only')
<$"mc 01 52\r"$>
General
#190 Enter/Go
log('Sending Enter/Go Command')
<$"mc 01 44\r"$>
Internal
#373 Private Method Listing
def log(line)
$log = File.open("/var/log/pluto/" + device_.devid_.to_s + "_Generic_Serial_Device.log", "a")
$log.puts "(***):" + line.to_s
$log.close
end
#351 Process IDLE

#350 Process Incoming Data
buff = ''
loop do
buff=conn_.Recv(30,200)
if buff.empty?
log('Nothing Received')
break
end
log('Received: ' + Regexp.escape(buff.to_s))
if buff.include?("OK")
log(Regexp.escape(buff.to_s) + ': Command Processed Successfully')
elsif buff.include?("NG")
log(Regexp.escape(buff.to_s) +': Command Processed Unsuccessfully')
end
end
#355 Process Initialize
for iRetry in 0...4
print "Initializing unit\n"
conn_.Send("ke 01 01\r") # Send UnMute Command
buf = conn_.Recv(30,200) # Expected Return # ke 01 01\r\ne 00 OK01x\r\n
if !buf.nil? && buf.include?("OK")
print "Initialized ok\n"
print "Setting volume to 30%\n"
cmd_313(15)
SetDeviceDataInDB( device_.devid_, 158, "15" )
# 158 = DEVICEDATA_Volume_Level_CONST
return
end
print "Failed to initialize. Wait 1 secs and try again\n"
sleep(1)
end
#DisableDevice( device_.devid_, true )
#print "The device would not respond. Disabling it.\n"
#384 Process Receive Command For Child

#356 Process Release

Misc
#548 Menu
log('Sending Menu Command')
<$"mc 01 43\r"$>
#676 Video Mute
log('Sending Video Mute Command')
<$"kd 01 00\r"$>
Numbers
#364 -/--/---

#204 0
log('Sending 0 ')
<$"mc 01 10\r"$>
#205 1
log('Sending 1 ')
<$"mc 01 11\r"$>
#206 2
log('Sending 2 ')
<$"mc 01 12\r"$>
#207 3
log('Sending 3 ')
<$"mc 01 13\r"$>
#208 4
log('Sending 4 ')
<$"mc 01 14\r"$>
#209 5
log('Sending 5 ')
<$"mc 01 15\r"$>
#210 6
log('Sending 6 ')
<$"mc 01 16\r"$>
#211 7
log('Sending 7 ')
<$"mc 01 17\r"$>
#212 8
log('Sending 8 ')
<$"mc 01 18\r"$>
#213 9
log('Sending 9 ')
<$"mc 01 19\r"$>
#363 Back / Clear Entry
log('Sending Back/Clear Command ')
<$"mc 01 1A\r"$>
On-Screen Menu Navig
#240 Back / Prior Menu
log('Sending Exit Command ')
<$"mc 01 5B\r"$>
#225 Display

#368 Help

#86 Menu (Show Menu)
log('Sending Menu Command ')
<$"mc 01 43\r"$>
#201 Move Down
log('Sending Move Down Command ')
<$"mc 01 41\r"$>
#202 Move Left
log('Sending Move Left Command ')
<$"mc 01 07\r"$>
#203 Move Right
log('Sending Move RighCommand ')
<$"mc 01 06\r"$>
#200 Move Up
log('Sending Move Up Command ')
<$"mc 01 40\r"$>
Simple Control
#92 Pause
log('Sending Pause Command ')
<$"mc 01 BA\r"$>
#139 Play
log('Sending Play Command ')
<$"mc 01 B0\r"$>
#102 Record
#log('Sending Record Command ')
#<$"mc 01 BD\r"$>
#64 Skip Back - Channel/Track Lower
log('Sending Channel Down Command ')
<$"mc 01 01\r"$>
#63 Skip Fwd - Channel/Track Greater
log('Sending Channel Up Command ')
<$"mc 01 00\r"$>
#95 Stop
log('Sending Stop Command ')
<$"mc 01 B1\r"$>
Sound & Volume
#97 Mute
if @mute
<$"ke 01 00\r"$>
else
<$"ke 01 01\r"$>
end
@mute=!@mute
#313 Set Volume
@volume=level.to_i()
ilevel = @volume.to_i
log( 'setting volume to '+ ilevel.to_s)
log('Sending the Following Command: kf 01 '+ilevel.to_s(16)+'\r')
<$"kf 01 "+ilevel.to_s(16)+"\r"$>
SetDeviceDataInDB( device_.devid_, 158, ilevel .to_s)
# 158 = DEVICEDATA_Volume_Level_CONST # "volume and corresponding device data set\n"
#90 Vol Down
log('lowering volume from ' + @volume.to_s)
cmd_313(@volume-1)
#89 Vol Up
log('Increasing volume from ' + @volume.to_s)
cmd_313(@volume+1)
Speed Ctrl
#125 Scan Back/Rewind
log('Sending Rewind Command ')
<$"mc 01 8F\r"$>
#93 Scan Fwd/Fast Fwd
log('Sending Fast Fwd Command ')
<$"mc 01 8E\r"$>
#98 Slow Scan Back

#99 Slow Scan Forward

TV
#136 Previous Channel
log('Sending Previous Channel Command ')
<$"mc 01 B2\r"$>
</pre>

== Adding device ==

This is a simple process that you can now add via the [[LinuxMCE Admin Website]] at '''Wizard > [[AV Devices|A/V Equipment]]'''
=== Add device based on created template ===
Just search for the device template that you created and select it from the list
=== Specify COM port for it ===
Just tell LinuxMCE which com port to use.
=== Assing it to new room ===
Tell LinuxMCE which room to assign this device
=== Specifiy Audio pipe connections to inputs on receiver ===
Tell LinuxMCE how you have thing attached to the LG TV and how the LG TV is attached to the computer.

''I have it attached via RGB port and I have my cable box attached to AV1 and my HDTV connected to Tuner-Digital input.''

==Making Plug&Play==
This is not needed to use the TV, but I post as an option.
Location: /usr/pluto/pnp

vi /usr/pluto/pnp/20_LGLCD.sh
add the following and then make the file executable.

<pre> #!/bin/bash
#Play and Play script for LG TV's Models Numbers:LGXXLB4/5D
#Set ID needs to be set to 01
#Serial feedback is very slow so it requires several seconds to get feedback
#Device Template Number:1905 on my local Machine.
#Serail Command for Power On ka 01 01
#Serial Command for Power OFF ka 01 00
#Returns two different strings depending on whether or not the TV is On or Off, so we will try to turn it ON then resend the ON command as it returns proper string (ka 01 01\r\na 00 OK01x\r\n)
echo "LG TV Detection script queue $2"
/usr/pluto/bin/TestSerialPort -p $3 -P N81 -b 9600 -t "ka 01 01\r"
sleep 5s
/usr/pluto/bin/TestSerialPort -p $3 -P N81 -b 9600 -t "ka 01 01\r" -i 5 -s "OK01x\r"
if [[ "$?" -ne 0 ]]; then
echo "It's not a LG TV"
/usr/pluto/bin/MessageSend dcerouter -r 0 $1 1 806 224 $2 13 "$4" 44 0
else
echo "It is a LG TV"
/usr/pluto/bin/MessageSend dcerouter -r 0 $1 1 806 224 $2 13 "$4" 44 1905
fi</pre>

the plugin will run the script with 4 parameters: the device id of the plugin, the unique id for this event (the PK_PnpQueue), a path where the device is located (ip address for ethernet devices, serial port for rs232 devices, etc.), and the name of the pnp detection script.

The detection script should attempt to determine what device template is on the path using any appropriate means. If it finds a match, it should fire a message using the paramters it received, such as this:

/usr/pluto/bin/MessageSend dcerouter -r 0 $1 806 224 $2 13 "$4" 44 1905(this is the template id for the devicetemplate you created above)

=====================================

==
'''== Adapting these instructions for other LG rs232 TVs == =='''

This seems to be a good template for LG TVs with serial ports. Some of the command need to be changed for later models <$xb 01 90\r$> instead of <$kb 01 07\r$> for inputing HDMI 1 for example, but generally a good guide for adapting it to your TV.

The major problem is undocumented above but is critical to making this work: You need to look up the device id number of your LG TV from the Wizard \ Devices \ AV Equipment in the upper left hand corner and replace the number "158" in all the scripts above with this number (for example, in my case 310). This allows the script to process successfully.

Otherwise it will cause a compile error in 7.10 in the "follow log" on the "advanced" link of the A/V device and will not allow your template to run. The compile error will state that it found a "kend" and was expecting "$end".

The code that breaks it is:

----------------------------
#355 Process Initialize
for iRetry in 0...4
print "Initializing unit\n"
conn_.Send("ke 01 01\r") # Send UnMute Command
buf = conn_.Recv(30,200) # Expected Return # ke 01 01\r\ne 00 OK01x\r\n
if !buf.nil? && buf.include?("OK")
print "Initialized ok\n"
print "Setting volume to 30%\n"
cmd_313(15)
SetDeviceDataInDB( device_.devid_, 158, "15" )
# 158 = DEVICEDATA_Volume_Level_CONST
return
end
print "Failed to initialize. Wait 1 secs and try again\n"
sleep(1)
end

-------------------------------
which is also necessary for the volume set, volume up and volume down commands the way they are written.
Carefully replacing "158" with the LG TV device ID number on your setup in the extended editor will make all these commands functional.

Please note that the description for the plug and play implementation discussed above has not been tested with this fix.

AMP Configuration Guide

2009-01-29T00:08:06Z

Sedgington:

[[Category :Tutorials]]
[[category :Programmer's Guide]]
<h1>How to configure Asterisk with AMP (Asterisk management portal)</h1>
AMP is a separate web based configuration tool for Asterisk. Note that as of March 2006, it has been renamed to [http://www.freepbx.org Freepbx]. More information can be found on the [http://www.voip-info.org/wiki/view/freePBX VoIP Wiki], and the [http://www.freepbx.org FreePBX website].
Here is a quick intro as it relates to LinuxMCE. Note the AMP integration is not fully complete. In time this process will become more seamless.
Step 1: Add your phones
The phones in your home will be stored in 2 places: Once in LinuxMCE's database as LinuxMCE devices. This is where the orbiters retrieve the list of phones in the house to display on the screens, and also the phones you can position on the floorplan.

Secondly, AMP also maintains its own list of phone extensions that it uses to configure Asterisk. Normally LinuxMCE's list and AMP's list will stay in sync automatically. You can verify this by checking Wizard, Devices, Phones to see LinuxMCE's list.

Go to Wizard, Devices, Phone Setup, and take a look at extension list in the right. The 'Extension' in AMP's list should equal the 'PhoneNumber' in LinuxMCE's list, and in LinuxMCE's list if you click the 'ADV' button, you will see LinuxMCE's IP address, which should correspond to AMP's.

LinuxMCE has its own plug & play back end. If you have IP based phones, just plug them in. If we have that model in our plug & play database it should appear automatically in AMP's phone extension table and also in LinuxMCE's Device list. Otherwise you must add the phones manually to both lists. For each phone specify the IP address of the phone and a give each phone a unique phone extension (the 'Phone Number' on LinuxMCE's list).

Check that device is listed as child of 'Asterisk' device.by checking devices list on left of web admin
Goto AMP's config site from the LinuxMCE Web Admin site: Advanced/Configuration/Phones Setup then extensions on the left list and then click on your phone from the list on the right...
<ul><li>if your phone is plug&play it should be listed
on the right, select it and just check if all data are ok.</li>
<li>otherwise (specify phone type(SIP/IAX2),
Extention, Password and later IP address.
</ul>

Don't forget to regenerate screens on orbiters and quick reload
for dcerouter.
If you added more than one phone, try to call between them
It's a good idea to setup a default phone in section

Step 2: Add your phone lines and VOIP providers
Next step is to setup external lines...Please follow your VOIP
provider's instructions.

AMP Configuration Guide

2009-01-29T00:07:11Z

Sedgington:

[[Category :Tutorials]]
[[category :Programmer's Guide]]
<h1>How to configure Asterisk with AMP (Asterisk management portal)</h1>
AMP is a separate web based configuration tool for Asterisk. Note that as of March 2006, it has been renamed to [http://www.freepbx.org Freepbx]. More information can be found on the [http://www.voip-info.org/wiki/view/freePBX VoIP Wiki], and the [http://www.freepbx.org FreePBX website].
Here is a quick intro as it relates to LinuxMCE. Note the AMP integration is not fully complete. In time this process will become more seamless.
Step 1: Add your phones
The phones in your home will be stored in 2 places: Once in LinuxMCE's database as LinuxMCE devices. This is where the orbiters retrieve the list of phones in the house to display on the screens, and also the phones you can position on the floorplan.

Secondly, AMP also maintains its own list of phone extensions that it uses to configure Asterisk. Normally LinuxMCE's list and AMP's list will stay in sync automatically. You can verify this by checking Wizard, Devices, Phones to see LinuxMCE's list.

Go to Wizard, Devices, Phone Setup, and take a look at extension list in the right. The 'Extension' in AMP's list should equal the 'PhoneNumber' in LinuxMCE's list, and in LinuxMCE's list if you click the 'ADV' button, you will see LinuxMCE's IP address, which should correspond to AMP's.

LinuxMCE has its own plug & play back end. If you have IP based phones, just plug them in. If we have that model in our plug & play database it should appear automatically in AMP's phone extension table and also in LinuxMCE's Device list. Otherwise you must add the phones manually to both lists. For each phone specify the IP address of the phone and a give each phone a unique phone extension (the 'Phone Number' on LinuxMCE's list).

Check that device is listed as child of 'Asterisk' device.by checking devices list on left of web admin
Goto AMP's config site from the LinuxMCE Web Admin site: Advanced/Configuration/Phones Setup then extensions on the left list and then click on your phone from the list on the right...
<ul><li>if your phone is plug&play it should be listed
on the right, select it and just check if all data are ok.</li>
<li>otherwise (specify phone type(SIP/IAX2),
Extention, Password and later IP address.
</ul>

Don't forget to regenerate screens on orbiters and quick reload
for dcerouter.
If you added more than one phone, try to call between them
It's a good idea to setup a default phone in section

Step 2: Add your phone lines and VOIP providers
Next step is to setup external lines...Please follow your VOIP
provider's instructions.

AMP Configuration Guide

2009-01-29T00:06:21Z

Sedgington:

[[Category :Tutorials]]
[[category :Programmer's Guide]]
<h1>How to configure Asterisk with AMP (Asterisk management portal)</h1>
AMP is a separate web based configuration tool for Asterisk. Note that as of March 2006, it has been renamed to [http://www.freepbx.org Freepbx]. More information can be found on the [http://www.voip-info.org/wiki/view/freePBX VoIP Wiki], and the [http://www.freepbx.org FreePBX website].
Here is a quick intro as it relates to LinuxMCE. Note the AMP integration is not fully complete. In time this process will become more seamless.
Step 1: Add your phones
The phones in your home will be stored in 2 places: Once in LinuxMCE's database as LinuxMCE devices. This is where the orbiters retrieve the list of phones in the house to display on the screens, and also the phones you can position on the floorplan.

Secondly, AMP also maintains its own list of phone extensions that it uses to configure Asterisk. Normally LinuxMCE's list and AMP's list will stay in sync automatically. You can verify this by checking Wizard, Devices, Phones to see LinuxMCE's list.

Go to Wizard, Devices, Phone Setup, and take a look at extension list in the right. The 'Extension' in AMP's list should equal the 'PhoneNumber' in LinuxMCE's list, and in LinuxMCE's list if you click the 'ADV' button, you will see LinuxMCE's IP address, which should correspond to AMP's.

LinuxMCE has its own plug & play back end. If you have IP based phones, just plug them in. If we have that model in our plug & play database it should appear automatically in AMP's phone extension table and also in LinuxMCE's Device list. Otherwise you must add the phones manually to both lists. For each phone specify the IP address of the phone and a give each phone a unique phone extension (the 'Phone Number' on LinuxMCE's list).

Check that device is listed as child of 'Asterisk' device.by checking devices list on left of web admin
Goto AMP's config site from the LinuxMCE Web Admin site: Advanced/Configuration/Phones Setup then extensions on the left list and then click on your phone from the list on the right...
<ul><li>if your phone is plug&play it should be listed
on the right, select it and just check if all data are ok.</li>
<li>otherwise (specify phone type(SIP/IAX2),
Extention, Password and later IP address.
</ul>

Don't forget to regenerate screens on orbiters and quick reload
for dcerouter.
If you added more than one phone, try to call between them
It's a good idea to setup a default phone in section

Step 2: Add your phone lines and VOIP providers
Next step is to setup external lines...Please follow your VOIP
provider's instructions.

AMP Configuration Guide

2009-01-29T00:05:04Z

Sedgington:

[[Category :Tutorials]]
[[category :Programmer's Guide]]
<h1>How to configure Asterisk with AMP (Asterisk management portal)</h1>
AMP is a separate web based configuration tool for Asterisk. Note that as of March 2006, it has been renamed to [http://www.freepbx.org Freepbx]. More information can be found on the [http://www.voip-info.org/wiki/view/freePBX VoIP Wiki], and the [http://www.freepbx.org FreePBX website].
Here is a quick intro as it relates to LinuxMCE. Note the AMP integration is not fully complete. In time this process will become more seamless.
Step 1: Add your phones
The phones in your home will be stored in 2 places: Once in LinuxMCE's database as LinuxMCE devices. This is where the orbiters retrieve the list of phones in the house to display on the screens, and also the phones you can position on the floorplan.

Secondly, AMP also maintains its own list of phone extensions that it uses to configure Asterisk. Normally LinuxMCE's list and AMP's list will stay in sync automatically. You can verify this by checking Wizard, Devices, Phones to see LinuxMCE's list.

Go to Wizard, Devices, Phone Setup, and take a look at extension list in the right. The 'Extension' in AMP's list should equal the 'PhoneNumber' in LinuxMCE's list, and in LinuxMCE's list if you click the 'ADV' button, you will see LinuxMCE's IP address, which should correspond to AMP's.

LinuxMCE has its own plug & play back end. If you have IP based phones, just plug them in. If we have that model in our plug & play database it should appear automatically in AMP's phone extension table and also in LinuxMCE's Device list. Otherwise you must add the phones manually to both lists. For each phone specify the IP address of the phone and a give each phone a unique phone extension (the 'Phone Number' on LinuxMCE's list).

Check that device is listed as child of 'Asterisk' device.by checking devices list on left of web admin
Goto AMP's config site from the LinuxMCE Web Admin site: Advanced/Configuration/Phones Setup then extensions on the left list and then click on your phone from the list on the right...
<ul><li>if your phone is plug&play it should be listed
on the right, select it and just check if all data are ok.</li>
<li>otherwise (specify phone type(SIP/IAX2),
Extention, Password and later IP address.
</ul>

Don't forget to regenerate screens on orbiters and quick reload
for dcerouter.
If you added more than one phone, try to call between them
It's a good idea to setup a default phone in section

Step 2: Add your phone lines and VOIP providers
Next step is to setup external lines...Please follow your VOIP
provider's instructions.

AMP Configuration Guide

2009-01-28T23:57:12Z

Sedgington:

[[Category :Tutorials]]
[[category :Programmer's Guide]]
<h1>How to configure Asterisk with AMP (Asterisk management portal)</h1>
AMP is a separate web based configuration tool for Asterisk. Note that as of March 2006, it has been renamed to [http://www.freepbx.org Freepbx]. More information can be found on the [http://www.voip-info.org/wiki/view/freePBX VoIP Wiki], and the [http://www.freepbx.org FreePBX website].
Here is a quick intro as it relates to LinuxMCE. Note the AMP integration is not fully complete. In time this process will become more seamless.
Step 1: Add your phones
The phones in your home will be stored in 2 places: Once in LinuxMCE's database as LinuxMCE devices. This is where the orbiters retrieve the list of phones in the house to display on the screens, and also the phones you can position on the floorplan. Secondly, AMP also maintains its own list of phone extensions that it uses to configure Asterisk. Normally LinuxMCE's list and AMP's list will stay in sync automatically. You can verify this by checking Wizard, Devices, Phones to see LinuxMCE's list.
It should look like this include/images/amp/amp-00.jpg" target="_blank"><img src="include/images/amp/t-amp-00.jpg

Go to Wizard, Devices, Phone Setup, you will see click 'Setup', then and you'll be be able to an extension (usefull if your phone is not plug-and-play), but take a look at extension list in the right. The 'Extension' in AMP's list should equal the 'PhoneNumber' in LinuxMCE's list, and in LinuxMCE's list if you click the 'ADV' button, you will see LinuxMCE's IP address, which should correspond to AMP's.

LinuxMCE has its own plug & play back end. If you have IP based phones, just plug them in. If we have that model in our plug & play database it should appear automatically in AMP's phone extension table and also in LinuxMCE's Device list. Otherwise you must add the phones manually to both lists. For each phone specify the IP address of the phone and a give each phone a unique phone extension (the 'Phone Number' on LinuxMCE's list).

Check that device is listed as child of 'Asterisk' device.
Goto AMP's config site include/images/amp/amp-05.jpg" target="_blank section...
<ul><li>if your phone is plug&play it should be listed
on the right, select it and just check if all data are ok.</li>
<li>otherwise include/images/amp/amp-04.jpg" target="_blank (specify phone type(SIP/IAX2),
Extention, Password and later IP address.
</ul>

Don't forget to regenerate screens on orbiters and quick reload
for dcerouter.
If you added more than one phone, try to call between them
It's a good idea to setup a default phone in section

Step 2: Add your phone lines and VOIP providers
Next step is to setup external lines...Please follow your VOIP
provider's instructions.

AMP Configuration Guide

2009-01-28T23:44:36Z

Sedgington:

[[Category :Tutorials]]
[[category :Programmer's Guide]]
<h1>How to configure Asterisk with AMP (Asterisk management portal)</h1>
AMP is a separate web based configuration tool for Asterisk. Note that as of March 2006, it has been renamed to [http://www.freepbx.org Freepbx]. More information can be found on the [http://www.voip-info.org/wiki/view/freePBX VoIP Wiki], and the [http://www.freepbx.org FreePBX website].
Here is a quick intro as it relates to LinuxMCE. Note the AMP integration is not fully complete. In time this process will become more seamless.
Step 1: Add your phones
The phones in your home will be stored in 2 places: Once in LinuxMCE's database as LinuxMCE devices. This is where the orbiters retrieve the list of phones in the house to display on the screens, and also the phones you can position on the floorplan. Secondly, AMP also maintains its own list of phone extensions that it uses to configure Asterisk. Normally LinuxMCE's list and AMP's list will stay in sync automatically. You can verify this by checking Wizard, Devices, Phones to see LinuxMCE's list.
It should look like this include/images/amp/amp-00.jpg" target="_blank"><img src="include/images/amp/t-amp-00.jpg

Go to Wizard, Devices, Phone Setup</a>, you will see <a href="include/images/amp/amp-02.jpg" target="_blank
click 'Setup', then include/images/amp/amp-03.jpg" target="_blank
and you'll be be able to include/images/amp/amp-04.jpg" target="_blank an extension (usefull if your phone is not plug-and-play), but take a look at extension list in the right. The 'Extension' in AMP's list should equal the 'PhoneNumber' in LinuxMCE's list, and in LinuxMCE's list if you click the 'ADV' button, you will see LinuxMCE's IP address, which should correspond to AMP's.
include/images/amp/amp-05.jpg" target="_blank"><img src="include/images/amp/t-amp-05.jpg"></a><a href="include/images/amp/amp-05a.jpg" target="_blank"><img src="include/images/amp/t-amp-05a.jpg

LinuxMCE has its own plug & play back end. If you have IP based phones, just plug them in. If we have that model in our plug & play database it should appear automatically in AMP's phone extension table and also in LinuxMCE's Device list. Otherwise you must add the phones manually to both lists. For each phone specify the IP address of the phone and a give each phone a unique phone extension (the 'Phone Number' on LinuxMCE's list).

Check that device is listed as child of 'Asterisk' device.
Goto AMP's config site include/images/amp/amp-05.jpg" target="_blank section...
<ul><li>if your phone is plug&play it should be listed
on the right, select it and just check if all data are ok.</li>
<li>otherwise include/images/amp/amp-04.jpg" target="_blank (specify phone type(SIP/IAX2),
Extention, Password and later IP address.
</ul>

Don't forget to regenerate screens on orbiters and quick reload
for dcerouter.
If you added more than one phone, try to call between them
It's a good idea to setup a default phone in include/images/amp/amp-15.jpg" target="_blank section

Step 2: Add your phone lines and VOIP providers
Next step is to setup external lines...Please follow your VOIP
provider's instructions.

Broadvoice

2009-01-28T18:21:39Z

Sedgington:

For the uninitiated to Asterisk, Broadvoice is a good place to start to test the system with a few caveats:

1. Sip username is not the same as account username. For Sip setup, you use your Broadvoice assigned phone number whenever LinuxMCE asks you what your username is.

2. Sip password is not the same as your account password. You must contact support to get this. When using the LinuxMCE wizard for Broadvoice setup be sure to enter this case-sensitive password exactly as it will prevent you from registering Asterisk with Broadvoice if you do not. The consequence will be a series of ambiguous messages in the asterisk log that will give you little hint that this is the problem. In fact, once the wrong credentials are presented several times the server will lock you out. The work around is to use the /etc/hosts file to enter the ip address of a different proxy server than you had been attempting to register with aliased as sip.broadvoice.com. This should let you register immediately.

3. Make sure you get all the information entered the first time correctly when you set up the Broadvoice account with the LinuxMCE Wizard. If you do not, you may run into a series of Asterisk related conundrums that will require real expertise to figure out. I eventually gave up on them, reinstalled LinuxMCE from the DVD as a fresh install and then it worked perfectly.

4.Broadvoice support does not have Asterisk experience and can not be counted on to give you all the information you may need--although their web site does give you an idea of what steps you might need to take. But beware that you really don't need to follow these steps on the web site if you get the username and password right in the LinuxMCE wizard. In my case, it took 4 separate calls to support to figure out why my Asterisk server would not register: first they told me to use my phone number instead of my account name. Then they told me to turn off the Broadvoice-supplied Grandstream HT-502 as two devices could not be registered at the same time. Then they told me I needed a separate Sip password and finally they told me that I was being locked out because I had put in the incorrect password and attempted to register too many times. Generally, support was friendly, just not up on what needed to be done.

Given this background, you should be able to get your asterisk server up and running quickly. Adding an ip phone--in my case Linksys SPA 942--has not been the plug and play that is advertised elsewhere in this wiki, but if you follow the information on adding a phone as a device and then go on the web for tutorials on how to set up the phone of your choice, it should be relatively painless to get it working. The big key here was to realize that your extension is also your password and the ip address the phone connects to is the LinuxMCE server internal address: 192.168.80.1 if you go for the default setup. Asterisk codes also conflict with the factory codes in the Linksys SPA 942 so they need to be removed on the device, but this was easily discovered on the web.

Broadvoice

2009-01-28T18:13:40Z

Sedgington: Setting up Broadvoice to work with LinuxMCE/Asterisk

For the uninitiated to Asterisk, Broadvoice is a good place to start to test the system with a few caveats:

1. Sip username is not the same as account username. For Sip setup, you use your Broadvoice assigned phone number whenever LinuxMCE asks you what your username is.

2. Sip password is not the same as your account password. You must contact support to get this. When using the LinuxMCE wizard for Broadvoice setup be sure to enter this case-sensitive password exactly as it will prevent you from registering Asterisk with Broadvoice if you do not. The consequence will be a series of ambiguous messages in the asterisk log that will give you little hint that this is the problem. In fact, once the wrong credentials are presented several times the server will lock you out. The work around is to use the /etc/hosts file to enter the ip address of a different proxy server than you had been attempting to register with aliased as sip.broadvoice.com. This should let you register immediately.

3. Make sure you get all the information entered the first time correctly when you set up the Broadvoice account with the LinuxMCE Wizard. If you do not, you may run into a series of Asterisk related conundrums that will require real expertise to figure out. I eventually gave up on them, reinstalled LinuxMCE from the DVD as a fresh install and then it worked perfectly.

4.Broadvoice support does not have Asterisk experience and can not be counted on to give you all the information you may need--although their web site does give you an idea of what steps you might need to take. For example, it took 3 separate calls to support to figure out whymy Asterisk server would not register: first they told me to use my phone number instead of my account name. Then they told me to turn off the Broadvoice-supplied Grandstream HT-502 as two devices could not be registered at the same time. Then they told me my Sip password and finally they told me that I was being locked out because I had put in the incorrect password. Generally, support was friendly, just not up on what needed to be done.

Given this background, you should be able to get your asterisk server up and running quickly. Adding ip phone--in my case Linksys SPA 942--has not been the plug and play that is advertised, but if you follow the information on adding a phone as a device and then go on the web for tutorials on how to set up the phone of your choice, it should be relatively painless to get it working. The big key here was to realize that your extension is also your password and the ip address the phone connects to is the LinuxMCE server internal address: 192.168.80.1 if you go for the default setup.