tag:blogger.com,1999:blog-42261378581835936432024-03-13T07:06:34.231-04:00sipXcom (formerly sipXecs) News, Tips and EquipmentA blog about using the SIP Open Source sipXcom Unified Communications Server. sipXcom is a fork of sipXecs.Michael Picherhttp://www.blogger.com/profile/12368191261331971014noreply@blogger.comBlogger70125tag:blogger.com,1999:blog-4226137858183593643.post-71900255703691459852015-02-17T04:41:00.004-05:002015-02-17T04:43:06.474-05:00Goodbye SIPfoundry / sipXecs, Hello sipXcom!Based on increasing difficulties working with project leadership at SIPfoundry, eZuce will no longer be supporting the sipXecs project at SIPfoundry. We plan however to continue our support for open source communications projects. It has been a very productive five years and we have supported the community diligently during this time. It has certainly been an amazing journey from where the product was in 2010 at version 4.2 to where it is today with release 14.10. This past year we continued our support with 14.04 and 14.10 releases despite comments by SIPfoundry leadership in recent months.<br />
<br />
Where do we go from here?<br />
<br />
eZuce has created a new organization in Github called sipXcom and forked all of the sipXecs project repositories. All of the sipFoundry licensing of course remains in place for all the existing code so as to honor the copy left requirements from the AGPL3 license. Additional fixes will be freely available in sipXcom repositories.<br />
<br />
The experts who have helped to build sipXecs into the incredible product that it is will be found in the Google Groups sipxcom-users@googlegroups.com (<a href="https://groups.google.com/d/forum/sipxcom-users">https://groups.google.com/d/forum/sipxcom-users</a>) and sipxcom-dev@googlegroups.com (<a href="https://groups.google.com/d/forum/sipxcom-dev">https://groups.google.com/d/forum/sipxcom-dev</a>). We invite the rest of the sipX-users and sipX-dev mailing list users to join us there.<br />
<br />
eZuce employees will not be participating in the sipX-users or sipX-dev mailing lists from this point forward. Unfortunately we'll lose some mailing list history with this move, but the search and indeed the entire mailing list has been a mess for quite a while anyway.<br />
<br />
We'll be publishing update 4 soon for 14.04. And update 1 to 14.10 with a couple fixes that need to get in there. RPM's and ISO's will be available at <a href="http://download.sipxcom.org/">http://download.sipxcom.org</a>. Moving forward from the 15.04 release in April, we'll be publishing monthly releases (15.05, 15.06, 15.07, etc.).<br />
<br />
A new project page will be available at <a href="http://www.sipxcom.org/">http://www.sipxcom.org</a>.<br />
<br />
With so many of us who have so much energy and time invested, its with sad hearts that we leave sipFoundry and sipXecs behind.<br />
<br />
However, we have great optimism for the future with sipXcom and we are very excited about our next generation open source communications project. Please join us.<br />
<br />
Sincerely,<br />
Mike<br />
<div>
<br /></div>
Michael Picherhttp://www.blogger.com/profile/12368191261331971014noreply@blogger.com0tag:blogger.com,1999:blog-4226137858183593643.post-15935868614108654532015-02-17T04:39:00.000-05:002015-02-17T04:43:33.579-05:00Convert .key/.crt to pem for use with AWSI always have to look this up... hence the post here...<br />
<br />
Even though you might have a key file in text form, it won't work with AWS if you need to connect from ssh command line (keys work fine from Putty / WinSCP).<br />
<br />
To convert a key file you also need the crt file.<br />
<br />
Here's how from Mac / Linux command line:<br />
<br />
openssl rsa -in server.key -text > private.pem<br />
openssl x509 -inform PEM -in server.crt > public.pem<br />
<br />
Once you have the pem, don't forget to:<br />
<br />
chmod 600 public.pem<br />
<br />
Otherwise you won't be able to use it to ssh to AWS.Michael Picherhttp://www.blogger.com/profile/12368191261331971014noreply@blogger.com0tag:blogger.com,1999:blog-4226137858183593643.post-43420700911601584692014-12-24T04:39:00.000-05:002014-12-24T04:39:49.269-05:00Logitech K810 Keyboard on FedoraAlright, so just randomness...<div>
<br /></div>
<div>
Replaced my Ubuntu 14.10 installation (weird things with video drivers and performance going downhill... basically, time for a rebuild) with <a href="https://getfedora.org/">Fedora 21 Workstation</a>.</div>
<div>
<br /></div>
<div>
I use a Logitech K810 Bluetooth Keyboard with my laptop (Samsung Series 5 Ultra) when at my desk. And like with Ubuntu it didn't work out of the box (everything else did on Fedora, including suspend! great job Fedora team!).</div>
<div>
<br /></div>
<div>
Reports that this keyboard doesn't work in Linux are hogwash.</div>
<div>
<br /></div>
<div>
Found this article that pertained to Ubuntu: <a href="http://programsketches.org/?p=6">http://programsketches.org/?p=6</a></div>
<div>
<br /></div>
<div>
For my system I did the following:</div>
<div>
<br /></div>
<div>
<div>
<span style="font-family: Courier New, Courier, monospace;">hcitool dev</span></div>
<div>
<br /></div>
<div>
mine is hci0, so next I disable ssmpmode:</div>
<div>
<br /></div>
<div>
<span style="font-family: Courier New, Courier, monospace;">sudo hciconfig hci0 sspmode 0</span></div>
</div>
<div>
<br /></div>
<div>
<div>
To re-enable it, replace the 0 with a 1 in the above command.</div>
<div>
<br /></div>
<div>
Verify that it is disabled:</div>
<div>
<br /></div>
<div>
<span style="font-family: Courier New, Courier, monospace;">hciconfig hci0 sspmode</span></div>
</div>
<div>
<br /></div>
<div>
<div>
This include the text in the output:</div>
<div>
<br /></div>
<div>
<span style="font-family: Courier New, Courier, monospace;">Simple Pairing mode: Disabled</span></div>
</div>
<div>
<br /></div>
<div>
Attempt to pair the keyboard by holding down one of the 3 Bluetooth buttons until it flashes.</div>
<div>
<br /></div>
<div>
<div>
Go to Bluetooth settings in the drop-down menu in the upper right of the screen. Connect to the keyboard and a code will be presented to connect the device. Enter that code on the keyboard and your keyboard should be working.</div>
<div>
<br /></div>
<div>
<br /></div>
</div>
<div>
<br /></div>
<div>
<br /></div>
<div>
<br /></div>
<div>
<br /></div>
<div>
<br /></div>
<div>
<br /></div>
Michael Picherhttp://www.blogger.com/profile/12368191261331971014noreply@blogger.com0tag:blogger.com,1999:blog-4226137858183593643.post-40722003551896487922014-05-02T02:21:00.002-04:002014-05-05T11:41:47.427-04:00WebRTC UpdatesExciting updates from the WebRTC / Chrome Team: https://www.youtube.com/watch?v=DvzDzIXoncg<br />
<br />
Refinement, refinement, refinement. Plus WebRTC on iOS news!<br />
<br />
Interestingly they bring up Jitsi...<br />
<br />
WebRTC Sample repo is now on github: http://github.com/GoogleChrome/webrtc<br />
<br />
<br />
<br />Michael Picherhttp://www.blogger.com/profile/12368191261331971014noreply@blogger.com0tag:blogger.com,1999:blog-4226137858183593643.post-24275269850975601452012-08-15T09:46:00.000-04:002012-08-15T09:46:01.031-04:00Restarting Services in openUC / sipXecs 4.6Restarting services in openUC and sipXecs 4.6 has totally changed. Gone is the use of 'sipxproc -R xxxxx'.<br />
<br />
All services can be started/stopped/restarted from command line with '/etc/init.d/xxxxxx start/stop/restart'.<br />
<br />
The services can be found with 'ls /etc/init.d'.<br />
<br />
For instance, to restart sipxbridge:<br />
/etc/init.d/sipxbridge restart<br />
<br />Michael Picherhttp://www.blogger.com/profile/12368191261331971014noreply@blogger.com1tag:blogger.com,1999:blog-4226137858183593643.post-81986489819351705232012-06-12T10:07:00.000-04:002012-06-12T10:07:10.636-04:00Create a Larger Boot Disk Amazon Linux AMI<b style="font-weight: normal;"><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">I know these last couple posts don't have a lot to do with sipXecs but I thought I'd share a few of the Amazon AWS tips I've been accumulating.</span></b><br />
<b style="font-weight: normal;"><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"><br /></span></b><br />
<b id="internal-source-marker_0.6732922152150422" style="font-weight: normal;"><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Sometimes you just need more than the 8 GB EBS volume that Amazon provides with Amazon Linux. Sure you can just create another volume and attach it somewhere, but sometime it’s just easier to have one big drive.</span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">The following instructions are used to create a 64 bit Amazon Linux AMI with a boot drive up to 1 TB in size.</span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Servers can then be rapidly deployed from your new custom AMI.</span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span></b><br />
<h1 dir="ltr">
<b id="internal-source-marker_0.6732922152150422" style="font-weight: normal;"><span style="font-family: Arial; font-size: 24px; vertical-align: baseline; white-space: pre-wrap;">Create Base System</span></b></h1>
<b id="internal-source-marker_0.6732922152150422" style="font-weight: normal;"><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Starting from</span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">AMI:amzn-ami-pv-2012.03.1.x86_64-ebs (ami-e565ba8c)</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Launch a new instance.</span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">If you’d like, login and update system</span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">SSH to new Instance with key, login as ec2-user</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">sudo sh</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">yum update</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">shutdown -h now</span></div>
<h1 dir="ltr">
<span style="font-family: Arial; font-size: 24px; vertical-align: baseline; white-space: pre-wrap;">Build AMI</span></h1>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">In EC2 console create a snapshot of the root EBS volume.</span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Create an ESB volume from that snapshot with the new desired size. (Please ensure it is in the same Availability Zone as the instance)</span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Detach the root 8 GB EBS volume and attach the newly created EBS volume to /dev/sda1 on the instance.</span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Start the instance and then login.</span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Resize the disk to get the rest of the expanded disk</span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">sudo resize2fs /dev/sda1</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">From the EC2 console, click on the Instance and Create AMI from the running Instance.</span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">There you have it!</span></b>Michael Picherhttp://www.blogger.com/profile/12368191261331971014noreply@blogger.com1tag:blogger.com,1999:blog-4226137858183593643.post-92003445404719285992012-06-09T11:10:00.000-04:002012-06-09T11:10:11.143-04:00Build your own cloud hosted mail service... Zimbra in AWS<b id="internal-source-marker_0.10326352738775313" style="font-weight: normal;"></b><br />
<h1 dir="ltr">
<b id="internal-source-marker_0.10326352738775313" style="font-weight: normal;"><span style="font-family: Arial; vertical-align: baseline; white-space: pre-wrap;">Install Zimbra 7.2 in Amazon Web Services on Amazon Linux (or CentOS 6)</span></b></h1>
<h1 dir="ltr">
<b id="internal-source-marker_0.10326352738775313" style="font-weight: normal;"><span style="font-family: Arial; vertical-align: baseline; white-space: pre-wrap;">Notes</span></b></h1>
<b id="internal-source-marker_0.10326352738775313" style="font-weight: normal;"><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Creating an AWS instance in normal AWS space and stopping and starting a server will have profound repercussions if:</span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">The AMI used is Instance Store - Drive image reset (all data lost)</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">The Instance is not in VPC - Internal IP assigned to server will change</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">VPC = Virtual Private Cloud</span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><h1 dir="ltr">
<span style="font-family: Arial; vertical-align: baseline; white-space: pre-wrap;">Setup VPC</span></h1>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Login to the AWS Console</span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Click on VPC tab.</span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Click on VPC Dashboard</span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Create a VPC with Single Public Subnet Only (default option)</span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">VPC Defaults to 10.0.0.0/16 network space with the server within 10.0.0.0/24.</span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Note which availability zone the VPC subnet was created in (in VPC tab, see subnets on left side menu)</span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">To add a server to the VPC, click on Launch EC2 Instances which will take you back to the EC2 tab. When you create your host following, make sure that it is in the proper availability zone.</span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><h1 dir="ltr">
<span style="font-family: Arial; vertical-align: baseline; white-space: pre-wrap;">Setup VPC Firewall</span></h1>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Allow the following ports to host (create a security group if you don’t have one already).</span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><h2 dir="ltr">
<span style="font-family: Arial; vertical-align: baseline; white-space: pre-wrap;">TCP Ports</span></h2>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">80, 443, 22 (restrict from address to known hosts), 25, 110, 143, 993, 995, 7071</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><h1 dir="ltr">
<span style="font-family: Arial; vertical-align: baseline; white-space: pre-wrap;">Configure DNS</span></h1>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Configure DNS A-Record for your host in your Internet Facing DNS service</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">elastic.ip.addr.ess A mail.yourdomain</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Configure MX Record for your mail domain</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">yourdomain MX 10 mail.yourdomain</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Setup local bind server to resolve ‘yourdomain’ to internal IP addresses.</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">yum install bind</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Modify /etc/named.conf to load a custom zone file:</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">nano -w /etc/named.conf</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Add forwarders section in ‘options’ to forward to AWS DNS servers (typically .2 in your VPC ip range, mine is 172.30.1.2 in my example below and my server is 172.30.1.10). Just put this as the last line in the options { ... } section:</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 108pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">forwarders { 172.30.1.2; }; </span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Add the zone file settings:</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 108pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">zone "yourmaildomain" {</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 108pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"> type master;</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 108pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"> file "yourmaildomain.zone";</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 108pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"> allow-update { none; };</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 108pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">};</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Create zone data file:</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">nano -w /var/named/yourdomain.zone</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Your zone file should look as follows (change yourmaildomain to your email domain, my mail server host name is mail, so fqdn = mail.yourdomain) (also, change the IP to be the IP of your server in the AWS VPC):</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 108pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">$TTL 1800</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 108pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">@ IN SOA ns1.yourdomain. root.yourmaildomain. (</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 108pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"> 2012041902 ; serial#</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 108pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"> 1800 ; refresh, seconds</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 108pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"> 1800 ; retry, seconds</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 108pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"> 1800 ; expire, seconds</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 108pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"> 1800 ) ; minimum TTL, seconds</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 108pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 108pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">; DNS Servers for 'zimbra.yourmaildomain’'</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 108pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 108pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">yourmaildomain. IN NS mail.yourmaildomain.</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 108pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">yourmaildomain. MX 10 mail.yourmaildomain.</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 108pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">mail.yourmaildomain. IN A 172.30.1.10</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Make sure DNS starts on server boot:</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">chkconfig named on</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Reboot server and make sure DNS is started:</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">reboot</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">ssh back in...</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">service named status</span></div>
<h1 dir="ltr">
<span style="font-family: Arial; vertical-align: baseline; white-space: pre-wrap;">Configure Server Name</span></h1>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Edit the hosts file:</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">nano -w /etc/hosts</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Add a line that looks like:</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">ip.addr.ofserver.invpc fqdn.of.server hostnameofserver</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">The fqdn should match what you specified in the external DNS and the hostname is the part of the FQDN before the domain (I used ‘mail’ in the example above)</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Edit the network file:</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">nano -w /etc/sysconfig/network</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Modify HOSTNAME=fqdn.of.server</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><h1 dir="ltr">
<span style="font-family: Arial; vertical-align: baseline; white-space: pre-wrap;">Modify Amazon VPC DHCP</span></h1>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Modify the Amazon VPC setup’s DHCP Server so that the local DNS server is handed out first.</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">VPC Management -> DHCP Options Sets</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Create DHCP Options Set</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Set domain-name = your mail domain</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Set Domain-name-servers = ip.addr.of.host,amazondnsserver</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 108pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">(in my case the above two values were - 172.30.1.10, 172.30.1.2)</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Your VPCs -> Check mark next to the VPC to modify, Change DHCP Options Set to new options set.</span></div>
<h1 dir="ltr">
<span style="font-family: Arial; vertical-align: baseline; white-space: pre-wrap;">Setup Zimbra Host</span></h1>
<span style="font-family: Arial; font-size: 32px; font-weight: bold; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Starting from</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">AMI:amzn-ami-pv-2012.03.1.x86_64-ebs (ami-e565ba8c)</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">(I’m use the East Region so this is mine... ymmv)</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Launch a new instance.</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Create a 20 GB EBS Volume (make sure it is created in the same AWS availability zone as the VPC subnet) and then Attach it to new instance (/dev/sdf)</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Assign an elastic IP to the new server.</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">SSH to new Instance</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">login with ec2-user and certificate</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">ssh -i key.pem ec2-user@elasticip</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Sudo to sh</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">sudo sh</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Mount new drive, format, copy /var folder to it, then mount it back to /var</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">mke2fs -F -j /dev/sdf</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">mkdir /mnt/ec2</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">mount /dev/sdf /mnt/ec2</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">cp -a /var/* /mnt/ec2</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">mount /dev/sdf /var</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">umount /mnt/ec2</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Make system mount this volume every time</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">nano -w /etc/fstab</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Add the following line to the bottom of the file:</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">/dev/sdf /var ext3 defaults 0 0</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Continue with Installation & update Amazon Linux:</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">yum update</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Reboot server to pickup updates.</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">reboot</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">SSH back into system</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">ssh -i key.pem ec2-user@elasticip</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Login as root...</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">sudo sh</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><h1 dir="ltr">
<span style="font-family: Arial; font-size: 24px; vertical-align: baseline; white-space: pre-wrap;">Install Zimbra</span></h1>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">It’s important to make sure DNS is working right before this point...</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">dig yourmaildomain</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">dig yourmaildomain MX</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Make sure this is being resolved locally... LDAP stuff will mess up during install if you don’t do this.</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">SSH back into system</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">ssh -i key.pem ec2-user@elasticip</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Login as root...</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">sudo sh</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Change to root folder</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">cd /root</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Download current Red Hat Enterprise Linux 6 RPM from </span><a href="http://www.zimbra.com/downloads/os-downloads.html"><span style="color: #1155cc; font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">http://www.zimbra.com/downloads/os-downloads.html</span></a><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">wget </span><a href="http://files2.zimbra.com/downloads/7.2.0_GA/zcs-7.2.0_GA_2669.RHEL6_64.20120410002025.tgz"><span style="color: #1155cc; font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">http://files2.zimbra.com/downloads/7.2.0_GA/zcs-7.2.0_GA_2669.RHEL6_64.20120410002025.tgz</span></a><span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Unpack the file</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">tar xzvf zcs-7.2.0_GA_2669.RHEL6_64.20120410002025.tgz</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Change to the directory created</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">cd zcs-7.2.0_GA_2669.RHEL6_64.20120410002025</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Uninstall sendmail</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">yum erase sendmail</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Fix sudoers file</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">nano -w /etc/sudoers</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">comment out ‘Defaults requiretty’</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"># Defaults requiretty</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Fix for libstdc++</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Create symbolic link to the following file :</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 108pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">ln -s /usr/lib64/libstdc++.so.6 /usr/lib/libstdc++.so.6</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Start the Installation</span></div>
<div dir="ltr" style="margin-bottom: 0pt; margin-left: 72pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">./install.sh --platform-override</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Set the admin password (menu option 3, and then menu option 4).</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Enter ‘r’ to return to previous menu.</span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span><br /><div dir="ltr" style="margin-bottom: 0pt; margin-left: 36pt; margin-top: 0pt;">
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;">Enter ‘a’ to apply settings.</span></div>
<div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"><br /></span></div>
<span style="font-family: Arial; font-size: 15px; vertical-align: baseline; white-space: pre-wrap;"></span></b>Michael Picherhttp://www.blogger.com/profile/12368191261331971014noreply@blogger.com0tag:blogger.com,1999:blog-4226137858183593643.post-13704751429177092582011-11-24T05:55:00.005-05:002011-11-24T08:16:05.974-05:00Building CentOS 5.7 images for Amazon EC2I'm new to Amazon's EC2 platform so I've struggled a bit with it as of late. I had been using <a href="http://www.rightscale.com/">Rightscale's </a>excellent AMI's (thanks guys). But I ran into some performance issues with conference bridges and sipXecs (openUC) when running in AWS space. According to the <a href="http://www.freeswitch.org/">Freeswitch </a>mailing list performance should have been better than what I was experiencing (any sort of media services in a virtual environment will at some point experience some quality issues, don't expect otherwise).<div><br /></div><div>To help get to the root of the problem I wanted to find a bare-bones CentOS 5.7 64 bit AMI that was EBS (elastic block storage - storage maintained when server is rebooted) vs. Instance storage (storage that's reset to the base image each time the server is shutdown or rebooted). Well, guess what... there wasn't a public AMI available. This left me with two options, try to adapt somebody else's image or build my own. Not being the trust-in-others type I went for the second option.<div><br /></div><div>I'll spare the trials and tribulations of what I went through and get to exactly how I now build my images...</div></div><div><br /></div><div><b><span class="Apple-style-span">Overview</span></b></div><div><br /></div><div>The basic process I am using is as follows:</div><div><ol><li>Build a CentOS 5.7 64 bit machine to create the image on (this machine is not imaged, just used to build the image on).</li><li>Use modified Rightscale build script to build image and load to AWS</li><li>Register AMI in AWS.</li><li>Convert Instance Store AMI to EBS backed AMI</li></ol></div><div>If anybody has a better process, by all means please let me know...</div><div><br /></div><div><b><span class="Apple-style-span">Build a CentOS 5.7 64 bit machine</span></b></div><div><br /></div><div>So it simplifies the process a bit to build on the same machine type as you want to end up with. I build a box on my Citrix Xen Server with 4 processors, 4 GB of RAM and 60 GB of hard disk (you'll want enough storage because we're going to build a 10 GB image plus have a bunch of files on the disk for a short period).</div><div><br /></div><div>In building the server I select CentOS 5 as my image type, use a CentOS DVD in the system drive but when the install procedure begins select install from http server. Josh Patten had a bit of an explanation about this in a <a href="http://www.sipfoundry.org/web/jpatten/blogs/-/blogs/manually-installing-sipxecs-on-centos-5-6">sipXecs blog post</a>. Also this information on using the <a href="http://www.if-not-true-then-false.com/2010/centos-netinstall-network-installation/">CentOS netinstall feature</a> is handy.</div><div><br /></div><div>I build the box with base packages only (de-select Workstation and any other packages).</div><div><br /></div><div>Once the machine boots, install ruby:</div><div><br /></div><div><span class="Apple-style-span">yum install ruby</span></div><div><br /></div><div><b><span class="Apple-style-span">Rightscale Script</span></b></div><div><br /></div><div>So Rightscale has creating these Amazon AMI's down to a science. It's fully scripted and installs customization tweaks for their cloud platform. Luckily they posted their scripts (although I haven't been able to find the version 4 scripts). The original <a href="http://blog.rightscale.com/2007/10/23/64-bit-centos5-amazon-ec2-image-release/">blog post I found</a> referenced version 1 scripts and I worked on this a bit but I later found version 3 scripts:</div><div><ul><li><span class="Apple-style-span"><span class="Apple-style-span" style="font-size: 12px; line-height: 18px; text-align: -webkit-auto; background-color: rgb(255, 255, 255);"><a href="http://s3.amazonaws.com/rightscale_scripts/Cent5.0V3.0.0Install.sh">http://s3.amazonaws.com/rightscale_scripts/Cent5.0V3.0.0Install.sh</a></span></span></li><li><span class="Apple-style-span"><span class="Apple-style-span" style="font-size: 12px; line-height: 18px; text-align: -webkit-auto; background-color: rgb(255, 255, 255);"><a href="http://s3.amazonaws.com/rightscale_scripts/Cent5.0X86_64V3.0.0Install.sh">http://s3.amazonaws.com/rightscale_scripts/Cent5.0X86_64V3.0.0Install.sh</a></span></span></li></ul></div><div>These of course still loaded all of the Rightscale tweaks but it was a great place to start.</div><div><br /></div><div>The script I ended up with is here: <a href="http://www.box.com/s/rmt719k3ayjf2yzk5sst">http://www.box.com/s/rmt719k3ayjf2yzk5sst</a></div><div><br /></div><div>In the CentOS system you created initially create a folder called /root/ec2:</div><div><br /></div><div>Login to the system as root.</div><div><br /></div><div><span class="Apple-style-span">cd /root</span></div><div><span class="Apple-style-span">mkdir ec2</span></div><div><br /></div><div>Then copy the script into that folder:</div><div><br /></div><div><span class="Apple-style-span">cd /root/ec2</span></div><div><span class="Apple-style-span">wget http://www.box.com/s/rmt719k3ayjf2yzk5sst</span></div><div><br /></div><div>Make the script executable:</div><div><br /></div><div><span class="Apple-style-span">chmod +x Cent5.0X86_64V3.0.0InstallMWP.sh</span></div><div><br /></div><div>Execute the script:</div><div><br /></div><div><span class="Apple-style-span">./Cent5.0X86_64V3.0.0InstallMWP.sh</span></div><div><br /></div><div>Then the following menu will appear:</div><div><br /></div><div><div><span class="Apple-style-span">Hello root, Lets get started installing CentOS 5</span></div><div><span class="Apple-style-span">........................................</span></div><div><span class="Apple-style-span">Please Select an Option or 8 to quit</span></div><div><span class="Apple-style-span">0) Set EC2 Variables</span></div><div><span class="Apple-style-span">1) Create and Mount Image</span></div><div><span class="Apple-style-span">2) Installing Yum and CentOS 5 Base</span></div><div><span class="Apple-style-span">3) Install Additional Packages</span></div><div><span class="Apple-style-span">4) Install RightScale Customizations</span></div><div><span class="Apple-style-span">5) Clean Up FileSystem and Bundle Image</span></div><div><span class="Apple-style-span">6) Upload Image</span></div><div><span class="Apple-style-span">7) Clean Up</span></div><div><span class="Apple-style-span">8) Quit</span></div></div><div><br /></div><div>Now it's a matter of stepping through each of the menu options.</div><div><br /></div><div>Step 0 - Set EC2 Variables</div><div><br /></div><div><div><span class="Apple-style-span">Please Select an Option or 4 to quit</span></div><div><span class="Apple-style-span">1) Set EC2 Variables</span></div><div><span class="Apple-style-span">2) Show EC2 Variables</span></div><div><span class="Apple-style-span">3) Set AWS Bucket, Image Name & Kernel ID</span></div><div><span class="Apple-style-span">4) Back</span></div></div><div><br /></div><div>You'll need to set the following EC2 Variables:</div><div><br /></div><div><div><span class="Apple-style-span">EC2_CERT=/root/ec2/etc/cert-xxxxxxxxxxxxxxxx.pem</span></div><div><span class="Apple-style-span">EC2_HOME=/root/ec2 </span></div><div><span class="Apple-style-span">EC2_PRIVATE_KEY=/root/ec2/etc/pk-xxxxxxxxxxxxxxx.pem</span></div><div><span class="Apple-style-span"><br /></span></div><div><span class="Apple-style-span">The EC2 Cert and Private key are the X.509 Certificates associated with your AWS account (I've assumed you're already signed up). In the upper right of your AWS console, click on your account name drop down and select 'Security Credentials'. On that page under Access Credentials you'll see a tab for X.509 Certficates, click on that and Create a new certificate if you don't have one already then download the cert-xxxxxxxxxxxxxx.pem file and the private key pk-xxxxxxxxxxx.pem file and save to your computer. Then on your CentOS machine, create a /root/ec2/etc folder and copy the files there (I use <a href="http://winscp.net/eng/index.php">winscp </a>because I'm a Windows weenie sometimes).</span></div><div><span class="Apple-style-span"><br /></span></div><div><span class="Apple-style-span">AWS_ACCOUNT_NUMBER= </span></div><div><span class="Apple-style-span"><br /></span></div><div><span class="Apple-style-span">Your AWS Account Number is displayed on the 'Security Credentials' page in the upper right.</span></div><div><span class="Apple-style-span"><br /></span></div><div><span class="Apple-style-span">AWS_ACCESS_KEY_ID= </span></div><div><span class="Apple-style-span">AWS_SECRET_ACCESS_KEY=</span></div><div><span class="Apple-style-span"><br /></span></div><div><span class="Apple-style-span">Your AWS Access Key ID and Secret Access Key are also available on the Security Credentials page under Access Credentials.</span></div><div><span class="Apple-style-span"><br /></span></div><div><span class="Apple-style-span">Now set the AWS Bucket, Image Name and Kernel ID</span></div><div><span class="Apple-style-span"><br /></span></div><div><span class="Apple-style-span">AWS_BUCKET=</span></div><div><span class="Apple-style-span"><br /></span></div><div><span class="Apple-style-span">The AWS Bucket is an S3 bucket that you must create in your AWS console prior to running this script. It is simply the bucket name.</span></div><div><span class="Apple-style-span"><br /></span></div><div><span class="Apple-style-span">IMAGE_NAME=</span></div><div><span class="Apple-style-span"><br /></span></div><div><span class="Apple-style-span">The Image Name is simply what you'd like to name this image. I avoided any noon alpha-numeric characters.</span></div><div><span class="Apple-style-span"><br /></span></div><div><span class="Apple-style-span">KERNEL_ID=</span></div></div><div><br /></div><div>The Kernel ID is the Amazon Kernel ID you'd like to use. Amazon only allows certain kernels on their infrastructure.</div><div><br /></div><div><div>The Current Amazon Kernel ID's for CentOS 5 (2.6.18) as of this writing are:</div><div><br /></div><div>US region32-bit:</div><div>aki-f5c1219c</div><div>ari-dbc121b2</div><div><br /></div><div>64-bit:</div><div>aki-e5c1218c</div><div>ari-e3c1218a</div><div><br /></div><div>EU region</div><div>32-bit:</div><div>aki-966a41e2</div><div>ari-906a41e4</div><div><br /></div><div>64-bit:</div><div>aki-aa6a41de</div><div>ari-946a41e0</div></div><div><br /></div><div>I used aki-e5c1218c for my system.</div><div><br /></div><div>Once you have all of the variables and bucket info setup, simply run down through menu options 1 - 8 to complete the process.</div><div><br /></div><div><b><span class="Apple-style-span">Register AMI in AWS</span></b></div><div><br /></div><div>Ok, now with the Image fully loaded to your S3 bucket, now we can register the AMI in your AWS console. In the EC2 tab of the console, click on 'AMIs' under the Images section of the left side menu.</div><div><br /></div><div>Now click on the 'Register New AMI' button. A Register Image dialog box will appear asking for the AMI Manifest Path. In the box enter your bucketname/imagename.manifest.xml</div><div><br /></div><div>So if your bucket name was centos and your image name was centos5764 you would enter:</div><div><br /></div><div><span class="Apple-style-span">centos/centos5764.manifest.xml</span></div><div><br /></div><div>Next, click the 'Register' button and your new AMI will be displayed as an AMI owned by you. It will be an Instance store at this point however.</div><div><br /></div><div><b><span class="Apple-style-span">Convert Instance Store AMI to EBS backed AMI</span></b></div><div><br /></div><div>There are a number of web sites the explain how to create an EBS backed AMI from an Instance Store AMI. The process is basically to create a new EBS Volume, mount it in a running version of your instance store system, copy the instance store drive to the EBS volume.</div><div><br /></div><div>I found a handy web site for doing this. The guys at <a href="https://cloudyscripts.com/">CloudyScripts </a>created a bunch of tools for working with cloud systems. The tool for making this conversion is here: <a href="https://cloudyscripts.com/tool/show/2">https://cloudyscripts.com/tool/show/2</a></div><div><br /></div><div>You'll want to create a separate Access Key (on the AWS Security Credentials Page) for your AWS account that you can disable / delete and a temporary account key pair (in your EC2 management console, left side menu at the bottom) that the service can use to log in to the AMI while it is working. Also, in the security group that you specify in the tool, you'll need to temporarily allow SSH access inbound from anywhere (0.0.0.0/0).</div><div><br /></div><div><b><span class="Apple-style-span">Conclusion</span></b></div><div><br /></div><div>Hopefully I haven't left anything out. I went through quite a few days of pain to figure all of this out and end up with something that was very reusable by me. I hope others will find it useful!</div><div><br /></div>Michael Picherhttp://www.blogger.com/profile/12368191261331971014noreply@blogger.com0tag:blogger.com,1999:blog-4226137858183593643.post-10472016310341950912011-03-22T16:45:00.005-04:002011-04-30T06:28:01.480-04:00Installing sipXecs / openUC from USB Memory StickJim Canfield of EMStar Solutions posted this in the sipx-users mailing list and I thought I'd share it...<br /><blockquote><br />1. Download<>the Fedora *liveusb-creator-x-x.zip* and extract to your PC<br />2. Download<>the *sipxecs-4.2.1-100820-x86_64.iso*<br />3. Navigate to the *liveusb-creator-x-x* folder and click * liveusb-creator.exe* to launch the tool<br /><br /><br />1. Under *Use existing Live CD*, browse to where you saved the *<br />sipxecs-4.2.1-100820-x86_64.iso* and select it<br />2. Set the *Target Device* to point to your USB flash drive<br />3. Click *Create Live USB* to begin the creation process<br /><br />ISSUES:<br /><br />- SEE COMMENTS BELOW - sipxecs setup script is looking specifically for device CDROM during the install. I suggest using the CentOS netinstall method described in the comments section if you don't have a CDROM (or DVD for new 4.4 install).<br /><br />- Depending on your bios, you may have to edit you grub.conf after install because the install will assume the USB drive is (hd0,0) and the primary hard drive is (hd1,0). To fix, simply edit on boot fail the first time, then edit grub.conf manually once booted. Press ENTER on the fail message, at the menu screen press 'e' and then 'e' again to edit the 'root(hd1,0)' line and change to 'root (hd0,0)', Press ENTER and then press 'b' to boot. After you boot, to edit grub.conf 'nano -w /etc/grub.conf' and change all references to 'root (hd1,0)' to 'root (hd0,0)'.<br /><br />- Windows 7 users must "run as administrator"<br /><br /></blockquote>Michael Picherhttp://www.blogger.com/profile/12368191261331971014noreply@blogger.com4tag:blogger.com,1999:blog-4226137858183593643.post-76695761198216250732011-03-19T08:33:00.001-04:002011-03-19T08:33:34.668-04:00Java memory problems...Java virtual machine running out of memory in sipXecs / openUC?<br /><br />This will manafest itself as Configuration pages not loading and other<br />Java related errors...<br /><br /><br />Edit /usr/bin/sipxconfig.sh and change a command that looks like this:<br /><br /> exec $JavaCmd \<br /> $SystemProps \<br /> $JavaOpts \<br /> $TrustStoreOpts \<br /> $KeyStoreOpts \<br /> -classpath "$Classpath" \<br /> ....<br /><br />to one that looks like this:<br /><br /> exec $JavaCmd \<br /> -XX:MaxPermSize=128M \<br /> -Xmx1024m \<br /> $SystemProps \<br /> $JavaOpts \<br /> $TrustStoreOpts \<br /> $KeyStoreOpts \<br /> -classpath "$Classpath" \<br /> .....<br /><br />That should increase the fixed memory allocated in the JVM...Michael Picherhttp://www.blogger.com/profile/12368191261331971014noreply@blogger.com0tag:blogger.com,1999:blog-4226137858183593643.post-19914686086430768172011-02-08T16:41:00.002-05:002011-02-08T16:48:50.421-05:00Exchange 2010 / Lync/rant<br /><br />How did Microsoft manage to make Exchange 2010 such a pig?<br /><br />Can you tell I'm a little frustrated? I'm trying to with with Exchange 2010 Unified Messaging to test out interoperability with sipXecs/openUC. I've been at this now for well over 2 days worth of time between installing and trying to get systems upgraded.<br /><br />I'm trying to install Exchange 2010 SP1 at this point and the requirements are killing me. First off, stupid IE won't download anything on the 2008 R2 server so I have chrome installed on that box which works but you can't directly click on the pre-reqs in Microsoft's setup tool. The links don't come up correctly in Chrome. Ok, so I type them all in and get to the last one... Microsoft Speech Server Runtime. The freaking thing won't install because something else is in place. Well, MS in their wisdom upgraded another component that replaced this piece but the server needs this one installed in order to do the upgrade.<br /><br />What happened to the nice simple days of Exchange 5.5? Man they've gone down hill with this product since then. At least 5.5 was manageable (even if the database puked once in a while, it was easy to fix).<br /><br />I'm sure Lync will be much better to work with.... gack! No praise coming from this camp.<br /><br />/rantMichael Picherhttp://www.blogger.com/profile/12368191261331971014noreply@blogger.com0tag:blogger.com,1999:blog-4226137858183593643.post-1214202536459235672011-01-20T14:11:00.002-05:002011-01-20T14:12:44.295-05:00Disaster Recovery & sipXecsWrote a blog post on Disaster Recovery & sipXecs over at sipFoundry.org web site...<br /><br /><a href="http://www.sipfoundry.org/web/mpicher/blogs/-/blogs/disaster-recovery-%26-sipxecs?_33_redirect=http%3A%2F%2Fwww.sipfoundry.org%2Fhome%3Bjsessionid%3D2C03761BBE0B86EFDB9FDB21BEF06DE8%3Fp_p_id%3D115%26p_p_lifecycle%3D0%26p_p_state%3Dnormal%26p_p_mode%3Dview%26p_p_col_id%3Dcolumn-2%26p_p_col_pos%3D3%26p_p_col_count%3D5">Disaster Recovery & sipXecs</a>Michael Picherhttp://www.blogger.com/profile/12368191261331971014noreply@blogger.com0tag:blogger.com,1999:blog-4226137858183593643.post-5229169517559430302010-05-12T07:48:00.002-04:002010-05-12T07:56:40.954-04:00Capture Traffic on your sipXecs ServerJust a quick note on capturing traffic directly on the sipXecs PBX.<div><br /></div><div>Personally, I'm a network guy and I like to use Wireshark to evaluate network traffic. Sure SipViewer shows you what the PBX is seeing for SIP traffic, but I want it all...</div><div><br /></div><div>To capture directly on the sipXecs server, use the following command:</div><div></div><span><span><br />sipXecs: tcpdump -n -s 0 -i any -w filename.cap</span></span><div><span><span><br /></span></span></div><div><span><span>Then you'll be able to use winscp to copy the file to your PC and open it with wireshark.</span></span></div><div><span><span><br /></span></span></div><div><span><span><br /></span></span><div><span class="Apple-style-span" style="font-family:Calibri, sans-serif;font-size:130%;"><span class="Apple-style-span" style="font-size: 15px;"><br /></span></span></div></div>Michael Picherhttp://www.blogger.com/profile/12368191261331971014noreply@blogger.com0tag:blogger.com,1999:blog-4226137858183593643.post-32962769649337919342010-05-01T07:04:00.002-04:002010-05-01T07:28:39.059-04:00sipXecs... the alternate build...It's kind of like an alternate movie ending, or director's cut...<div><br /></div><div>Douglas Hubler (aka, Lazyboy, aka, lazieburd) (<a href="http://lazieburd.blogspot.com/">Douglas' Blog</a>) a long time sipXecs contributor and former Pingtel employee is offering up an alternative sipXecs build to the community build offered by Avaya.</div><div><br /></div><div>Douglas has added back in some code that had 'disappeared' before 4.2.0 was released. Also, he is setting up build shop on the open suse build service which makes it easier to build for many other distributions. There are also some more builds for other distros than supported by the Avaya builds.</div><div><br /></div><div>Basically the process to start using the new builds is to change your sipxecs.repo file and do a 'yum update'.</div><div><br /></div><div>Backup your system and get the backup off of the PBX (the update does an in-place upgrade, but you can never be too safe).</div><div><br /></div><div>Login to your sipXecs box as root and edit your sipxecs.repo file ('nano -w /etc/yum.repos.d/sipxecs.repo').</div><div><br /></div><div>Comment out the existing sipXecs yum info with '#' in front of each line.</div><div><br /></div><div>Add the following lines to the bottom of the repo:</div><div><br /></div><div><div><span class="Apple-style-span" style="font-size: x-small;">[home_sipfoundry]</span></div><div><span class="Apple-style-span" style="font-size: x-small;">name=SIPfoundry sipXecs IP PBX Unified Communications Solution (CentOS_5)</span></div><div><span class="Apple-style-span" style="font-size: x-small;">type=rpm-md</span></div><div><span class="Apple-style-span" style="font-size: x-small;">baseurl=http://download.opensuse.org/repositories/home:/sipfoundry/CentOS_5/</span></div><div><span class="Apple-style-span" style="font-size: x-small;">gpgcheck=0</span></div><div><span class="Apple-style-span" style="font-size: x-small;">gpgkey=http://download.opensuse.org/repositories/home:/sipfoundry/CentOS_5/repodata/repomd.xml.key</span></div><div><span class="Apple-style-span" style="font-size: x-small;">enabled=1</span></div></div><div><br /></div><div>The above is for a CentOS_5 distro... (ie., the sipXecs install from ISO). Check out http://download.opensuse.org/repositories/home:/sipfoundry for other builds. Builds are currently available in 32 bit and 64 bit for:</div><div><br /></div><div><ul><li>CentOS 5</li><li>Fedora 10, 11, 12</li><li>RHEL 5</li><li>Suse Enterprise Linux 10 & 11</li><li>openSuse 11.1 and 11.2</li></ul></div><div><br /></div><div>Once you have your .repo file setup properly, run a 'yum clean' and then a 'yum update' from the command line.</div><div><br /></div><div>I rebooted my sipXecs box after the yum completed.</div><div><br /></div><div>Big thanks to Douglas for the hard work he's putting in!</div><div><br /></div><div><br /></div>Michael Picherhttp://www.blogger.com/profile/12368191261331971014noreply@blogger.com2tag:blogger.com,1999:blog-4226137858183593643.post-59045075138207613042010-04-25T13:16:00.003-04:002010-04-25T13:25:33.713-04:00A little off-topic... ok, a lot off topic...Just finished re-writing a configuration I built for a Proxy server.<div><br /></div><div>Proxy servers are a great way to tighten up your network security. Point all your users at the proxy server in their browser settings and allow only the proxy server to go out to the Internet in your inside interface firewall rules.</div><div><br /></div><div>This example is built on CentOS 5.4 and utilizes squid, dansguardian, clamav and webmin. Daily downloads of malware and various blacklists are included.</div><div><br /></div><div>Here's the build doc: <a href="http://www.box.net/shared/dgaczasvlc">SetupProxyServer.pdf</a></div><div><br /></div><div>Very low overhead for this box. I built it on a single processor virtual machine with 512 MB RAM and a 10 GB virtual drive.</div><div><br /></div><div>Some things I'd like to add include logging of userid to make logging a little nicer than just by IP address.</div>Michael Picherhttp://www.blogger.com/profile/12368191261331971014noreply@blogger.com0tag:blogger.com,1999:blog-4226137858183593643.post-63178454456753735842010-04-16T06:45:00.001-04:002010-04-16T06:46:48.891-04:00sipXecs 4.0.4 to 4.2.0 upgrade notes and impressions<span style="font-weight: bold;">Upgrade Notes:</span><br /><br />Installed 4.0.4 fresh from ISO (dev build 4.1.7 on my test system was trashed).<br />Added a user / tested.<br />Fixed sipxecs.repo file replacing all '5.2' mirror references with '5'. (see previous blog post)<br />Ran YUM update from command line (265 items to be installed / upgraded, 374 MB worth).<br />Rebooted server.<br />A little patience was required on my relatively slow lab machine (800 MHz, Xeon w/1GB of RAM)... web services came up after a couple minutes.<br /><br /><span style="font-weight: bold;">Impressions:</span><br /><br />New login screen is a little bland w/o graphic image.<br /><br />Background job listed as failed on first login (problem listed as File replication: sipxpage.properties).<br />Created a paging group and re-sent the server profile and paging seemed to come up properly.<br /><br />New GUI is better? different? I wish the tabs were starting from the left instead of centered.<br /><br />Domain aliases of system IP address and host name are added automatically.<br /><br />New user portal is nicer. Can't seem to import GMail contacts.<br /><br />Branch concept in place... need to test.<br /><br />Still no live attendant option as part of Auto Attendant.<br /><br />Special Mode Auto Attendant configuration prominently available on Auto Attendants page.<br /><br />GUI is much more sluggish on my dog of a test system (800 MHz, Xeon w/1GB of RAM)... time to upgrade I guess :-)<br /><br />NTP server config in GUI is a nice add.<br /><br />Alarm SNMP MIB now available on Alarm Configuration screen.<br /><br />Alarm groups are now available for different notifications to different users (now including SMS and SNMP notification methods)<br /><br />Much more but that's all I have time for at the moment...Michael Picherhttp://www.blogger.com/profile/12368191261331971014noreply@blogger.com2tag:blogger.com,1999:blog-4226137858183593643.post-22391392439779626152010-04-16T04:37:00.002-04:002010-04-16T04:52:49.568-04:00Upgrading from sipXecs 4.0.4 to 4.2.0One note that went across the mailing list (in case you missed it...).<div><br /></div><div><p class="MsoPlainText"><b></b></p><blockquote><p class="MsoPlainText"><b>Important Note on Upgrading:</b></p> <p class="MsoPlainText"><o:p> </o:p></p> <p class="MsoPlainText"><span style="mso-spacerun:yes"> </span>There is a bug in 4.0.4 that breaks upgrading from the web user</p> <p class="MsoPlainText"><span style="mso-spacerun:yes"> </span>interface.<span style="mso-spacerun:yes"> </span>Specifically, it disables to use of the CentOS</p> <p class="MsoPlainText"><span style="mso-spacerun:yes"> </span>repositories during the upgrade, which causes some prerequisites</p> <p class="MsoPlainText"><span style="mso-spacerun:yes"> </span>to be unavailable, which makes the upgrade fail.<span style="mso-spacerun:yes"> </span>The bug has</p> <p class="MsoPlainText"><span style="mso-spacerun:yes"> </span>been fixed in 4.2 (and a bunch of other improvements to the</p> <p class="MsoPlainText"><span style="mso-spacerun:yes"> </span>upgrade interface have been made too).</p><p class="MsoPlainText"><br /></p> <p class="MsoPlainText"><span style="mso-spacerun:yes"> </span></p> <p class="MsoPlainText"><span style="mso-spacerun:yes"> </span>The best way to avoid the problem is to just do the upgrade from</p> <p class="MsoPlainText"><span style="mso-spacerun:yes"> </span>the command line.<span style="mso-spacerun:yes"> </span>Modify your yum repository configuration to</p> <p class="MsoPlainText"><span style="mso-spacerun:yes"> </span>point to the repo where the 4.2 version is, and run 'yum</p> <p class="MsoPlainText"><span style="mso-spacerun:yes"> </span>update', and when it's done, reboot.</p><p class="MsoPlainText"></p></blockquote><p class="MsoPlainText"><br /></p> <p class="MsoPlainText"><o:p> </o:p></p><p class="MsoPlainText"><o:p>I'm working on testing a 4.0.4 to 4.2.0 upgrade now.</o:p></p><p class="MsoPlainText"><o:p><br /></o:p></p></div>Michael Picherhttp://www.blogger.com/profile/12368191261331971014noreply@blogger.com0tag:blogger.com,1999:blog-4226137858183593643.post-85687732841723039062010-04-15T20:38:00.001-04:002010-04-15T20:40:03.571-04:00sipXecs Version 4.2 just released!Al Campbell posted today on the sipfoundry web site that version 4.2 is officially released!<div><br /></div><div><a href="http://www.sipfoundry.org/component/content/article/54-sipxecs42.html">http://www.sipfoundry.org/component/content/article/54-sipxecs42.html</a></div><div><br /></div><div><br /></div>Michael Picherhttp://www.blogger.com/profile/12368191261331971014noreply@blogger.com0tag:blogger.com,1999:blog-4226137858183593643.post-61200781074750741012010-03-30T04:41:00.002-04:002010-03-30T04:43:16.008-04:00Using sipviewer on your PC for Windows guys<p>Get the following applications loaded to your PC:</p> <ul> <li>Putty (<a href="http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html</a>)</li> <li>WinSCP (<a href="http://winscp.net/eng/download.php">http://winscp.net/eng/download.php</a>)</li> <li>Java (<a href="http://www.java.com/">http://www.java.com</a>)</li> <li>sipviewer (<a href="http://sipxecssw.org/temp/sipXecs/sipviewer-install.jar">http://sipxecssw.org/temp/sipXecs/sipviewer-install.jar</a>)</li> </ul> <p>Run Putty and WinSCP programs and login to your sipXecs server with each. Open sipviewer on your local machine.</p> <p>With Putty go to /var/log/sipxpbx.</p> <ul> <li>cd /var/log/sipxpbx</li> </ul> <p>Navigate to the same folder in WinSCP.</p> <p>In the Putty window, run the following command if you want to clear your log files:</p> <ul> <li>logrotate -f /etc/logrotate.d/sipxchange</li> </ul> <p>Try placing the call that you are attempting to diagnose.</p> <p>From Putty run the following command to create a single log file with all of the sipXecs log files merged into one file:</p> <ul> <li>merge-logs</li> </ul> <p>In WinSCP, refresh the right window directory display. In that directory will be the new file named merged.xml that was just created.</p> <p>With WinSCP copy the merged.xml file to your local hard drive and open it with sipviewer. You should be able to see a diagram of what your call did (according to sipXecs).</p> <p>For more information on sipviewer see the Wiki <a href="http://wiki.sipfoundry.org/display/xecsuserV4r0/Display+SIP+message+flow+using+Sipviewer">page: http://wiki.sipfoundry.org/display/xecsuserV4r0/Display+SIP+message+flow+using+Sipviewer</a></p>Michael Picherhttp://www.blogger.com/profile/12368191261331971014noreply@blogger.com0tag:blogger.com,1999:blog-4226137858183593643.post-40762709713746278972009-12-29T07:17:00.005-05:002009-12-29T08:48:53.931-05:00Mount USB Key for sipXecs BackupsOk, so you don't want to bother setting up an FTP server to store backups of your sipXecs system. Here's how to mount a USB Key to your backup folder.<br /><br />Most USB keys will setup SCSI drive device (in my case it was /dev/sda1). Plug in a USB key and check out the /var/log/messages file to see what device was created.<br /><br />You'll want to get a little program installed on your system called 'scsiadd'. This allows you to remove USB scsi devices from the system without causing them damage. It's available here: <a href="http://llg.cubic.org/tools/">http://llg.cubic.org/tools/</a><br /><br />The following assumes you are logged into the system as root...<br /><br /><span style="font-weight: bold;font-size:130%;" >Add required packages:</span><br /><span style="font-family: courier new;">yum install lsscsi</span><br /><br /><span style="font-weight: bold;font-size:130%;" >If you don't have development tools on your sipXecs system yet, add them:</span><br /><span style="font-family: courier new;">yum install gcc gcc-c++ kernel-devel</span><br /><br /><span style="font-weight: bold;font-size:130%;" >Download, build and install scsiadd:</span><br /><span style="font-family: courier new;">cd $HOME</span><br /><span style="font-family: courier new;">mkdir scsiadd</span><br /><span style="font-family: courier new;">cd scsiadd</span><br /> <span style="font-family: courier new;">wget http://llg.cubic.org/tools/scsiadd-1.97.tar.gz</span><br /><span style="font-family: courier new;">tar -xf scsiadd-1.97.tar.gz</span><br /><span style="font-family: courier new;">cd scsiadd-1.97</span><br /><span style="font-family: courier new;">./configure</span><br /><span style="font-family: courier new;">make install</span><br /><br /><span style="font-size:130%;"><br /><span style="font-weight: bold;">Command line options:</span></span><br /><span style="font-family: courier new;">scsiadd 1.97 - add and remove devices from the scsi subsystem</span><br /><span style="font-family: courier new;">---------------------------------------------------------------</span><br /><span style="font-family: courier new;">syntax: scsiadd {-a|-r} <id></span><br /><span style="font-family: courier new;"> scsiadd {-a|-r} <id> <lun></span><br /><span style="font-family: courier new;"> scsiadd {-a|-r} <host> <id> <lun></span><br /><span style="font-family: courier new;"> scsiadd {-a|-r} <host> <channel> <id> <lun></span><br /><span style="font-family: courier new;"> scsiadd [-i maxid] -s <host></span><br /><span style="font-family: courier new;"> scsiadd [-i maxid] -s <host> <channel></span><br /><span style="font-family: courier new;"> scsiadd -p</span><br /><span style="font-family: courier new;">parameters not given are assumed 0</span><br /><span style="font-family: courier new;">-a: add a device (default if no command given)</span><br /><span style="font-family: courier new;">-r: remove device</span><br /><span style="font-family: courier new;">-s: scan for devices</span><br /><span style="font-family: courier new;">-p: print scsi status</span><br /><span style="font-family: courier new;">-h: print this help message</span><br /><span style="font-family: courier new;">-i: maximum SCSI ID which is scanned</span><br /><br />Here's a good blog article on using scsiadd: <a href="http://blog.shadypixel.com/safely-removing-external-drives-in-linux/">http://blog.shadypixel.com/safely-removing-external-drives-in-linux/</a><br /><br />Essentially, to remove a scsi device while the system is running, first find the device with lsscsi and then use scsiadd -r to remove it...<br /><br /><span style="font-family: courier new;">[root@sipx scsiadd-1.97]# lsscsi</span><br /><span style="font-family: courier new;">[3:0:0:0] disk CBM USB 2.0 5.00 /dev/sdb</span><br /><span style="font-family: courier new;">[root@sipx scsiadd-1.97]# scsiadd -r 3</span><br /><span style="font-family: courier new;">could not remove device 0 0 3 0 : No such device or address</span><br /><span style="font-family: courier new;">[root@sipx scsiadd-1.97]# scsiadd -r 3 0 0 0</span><br /><span style="font-family: courier new;">[root@sipx scsiadd-1.97]#</span><br /><br /><span style="font-weight: bold;font-size:130%;" >Ok, now let's get to making the USB work:</span><br /><br />Convert your USB drive from FAT16 or whatever it is to ext3:<br /><br /><span style="font-family: courier new;">mkfs.ext3 /dev/sda1</span><br /><br />Modify /etc/fstab:<br /><br /><span style="font-family: courier new;">nano -w /etc/fstab</span><br /><br />Add the following line at the bottom:<br /><br /><span style="font-family: courier new;">/dev/sda1 /var/sipxdata/backup vfat auto,user,rw,sync 0 0</span><br /><br />Test your fstab file now:<br /><br /><span style="font-family: courier new;">mount -a</span><br /><br />And check to see that it is mounted:<br /><br /><span style="font-family: courier new;">mount</span><br /><br />Change ownership on backup folder:<br /><br /><span style="font-family: courier new;">chown -R sipxchange:sipxchange /var/sipxdata/backup</span><br /><br />Perform a test backup from the GUI.Michael Picherhttp://www.blogger.com/profile/12368191261331971014noreply@blogger.com4tag:blogger.com,1999:blog-4226137858183593643.post-86408604098964419162009-12-28T21:53:00.000-05:002009-12-28T21:57:05.107-05:00How to fix the yum repos file for sipXecs 4.0.4Edit the /etc/yum.repos.d/sipxecs.repo<br /><br />nano -w /etc/yum.repos.d/sipxecs.repo<br /><br />on all the lines that begin with mirrorlist and baseurl change the 5.2 to be just 5.<br /><br />Here's the resulting sipxecs.repo file.<br /><br />[centos-5.2-base]<br />name=CentOS-5.2 - Base<br />mirrorlist=http://mirrorlist.centos.org/?release=5&arch=$basearch&repo=os<br />#baseurl=http://mirror.centos.org/centos/5/os/$basearch/<br />gpgcheck=1<br />gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5<br /><br />#released updates<br />[centos-5.2-updates]<br />name=CentOS-5.2 - Updates<br />mirrorlist=http://mirrorlist.centos.org/?release=5&arch=$basearch&repo=updates<br />#baseurl=http://mirror.centos.org/centos/5/updates/$basearch/<br />gpgcheck=1<br />gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5<br /><br />#packages used/produced in the build but not released<br />[centos-5.2-addons]<br />name=CentOS-5.2 - Addons<br />mirrorlist=http://mirrorlist.centos.org/?release=5&arch=$basearch&repo=addons<br />#baseurl=http://mirror.centos.org/centos/5/addons/$basearch/<br />gpgcheck=1<br />gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5<br /><br />#additional packages that may be useful<br />[centos-5.2-extras]<br />name=CentOS-5.2 - Extras<br />mirrorlist=http://mirrorlist.centos.org/?release=5&arch=$basearch&repo=extras<br />#baseurl=http://mirror.centos.org/centos/5/extras/$basearch/<br />gpgcheck=1<br />gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5<br /><br />#additional packages that extend functionality of existing packages<br />[centos-5.2-centosplus]<br />name=CentOS-5.2 - Plus<br />mirrorlist=http://mirrorlist.centos.org/?release=5&arch=$basearch&repo=centosplus<br />#baseurl=http://mirror.centos.org/centos/5/centosplus/$basearch/<br />gpgcheck=1<br />enabled=0<br />gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5<br /><br />[sipxecs-stable]<br />name=SIPfoundry sipXecs pbx - latest stable version<br />baseurl=http://sipxecs.sipfoundry.org/pub/sipXecs/LatestStable/CentOS/5/$basearch/RPM<br />gpgcheck=0Michael Picherhttp://www.blogger.com/profile/12368191261331971014noreply@blogger.com1tag:blogger.com,1999:blog-4226137858183593643.post-28737703375762279832009-10-05T07:41:00.002-04:002009-10-05T07:43:03.450-04:00DNS concepts for sipXecsPublished a new whitepaper on dealing with DNS and sipXecs.<br /><br /><a href="http://sipx-wiki.calivia.com/images/0/0b/SipXecsDNSConcepts.pdf">http://sipx-wiki.calivia.com/images/0/0b/SipXecsDNSConcepts.pdf</a><br /><br />Let me know if there are any glaring problems. I'll likely add other scenarios as time goes along. If you have a specific need please let me know.Michael Picherhttp://www.blogger.com/profile/12368191261331971014noreply@blogger.com1tag:blogger.com,1999:blog-4226137858183593643.post-43017523762860318962009-09-28T07:44:00.002-04:002009-09-28T07:47:24.173-04:00More Document UpdatesI updated the "<a href="http://www.opensourcesip.org:8080/clearspacex/docs/DOC-1110">Installing OpenSBC on Vyatta 5</a>" document again. Added a firewall rule change and also tweaked the formatting and text a little bit to clarify a few of the finer points.<br /><br />While I was at it I also freshened up the "<a href="http://www.opensourcesip.org:8080/clearspacex/docs/DOC-1080">DNS Setup Concepts for Session Border Controllers</a>" document also published at <a href="http://www.opensourcesip.org">www.OpenSourceSIP.org</a>.Michael Picherhttp://www.blogger.com/profile/12368191261331971014noreply@blogger.com0tag:blogger.com,1999:blog-4226137858183593643.post-89886558837624929162009-09-25T18:04:00.002-04:002009-09-25T18:06:29.282-04:00Updated document on Installing OpenSBC on Vyatta 5Sorry for the delay all but a project finally forced my hand on this. Here's a link to the updated document for installing OpenSBC on Vyatta 5.0.<br /><br /><a href="http://www.opensourcesip.org:8080/clearspacex/docs/DOC-1110">Install OpenSBC on Vyatta 5.0</a><br /><br />The original document was built with Vyatta 5.0 beta and there were some changes with the final release of Vyatta 5.0.Michael Picherhttp://www.blogger.com/profile/12368191261331971014noreply@blogger.com0tag:blogger.com,1999:blog-4226137858183593643.post-23355661648901687802009-09-22T06:14:00.001-04:002009-09-22T06:16:01.943-04:00An Interview with... Me!Packt Publishing just released an interview they did with me.<br /><a href="http://authors.packtpub.com/content/interview-michael-picher"><br />http://authors.packtpub.com/content/interview-michael-picher</a>Michael Picherhttp://www.blogger.com/profile/12368191261331971014noreply@blogger.com0