Python's nest

Trials and errors given me following list of ports to be open in guest wi-fi firewall in order for WhatsApp calls to work.

Until then it was giving error “Call couldn’t be placed due to wi-fi network that prevents WhatsApp calls”.

TCP: 4244,5222,5223,5228,5242

UDP: 3478,45395

Vmware Player is as simple as a pie, whether it’s good or bad.
What is definitely bad about it is it’s lack of management tools, but it’s how it was supposed to be, otherwise you wouldn’t pay for more advanced versions, right?
To ensure your virtual machine of choice is started together with Windows but not hanging in front of your eyes act as follows:

1. Add pref.vmplayer.exit.vmAction = “disconnect” to the C:\Users\%USERNAME%\AppData\Roaming\VMware\preferences.ini – this step is not a must but will keep your VM alive if you decide to kill vmplayer.exe process later on.
2. Schedule a task for it with trigger – “at startup” (Tick “Run with highest privileges” if you’re using raw device as I do). Action will be “Start a program”, Program/script – “C:\Program Files (x86)\VMware\VMware Player\vmplayer.exe” and “Add arguments (optional)” field must contain full path to your VM .vmx file (do not forget quotes if path contains spaces)

That’s it.
PS. Of course it all has sense if VM is reachable over IP in some manner.

Now, when 6.2 is available, those of us not having support subscription will have to install updates manually, it’s not that difficult, you just need to always start from pool master and never put it in maintenance mode prior to update.

1. Get update from Citrix site and upload it to pool master using scp
2. Connect to pool master via ssh or XenCenter console and upload update to pool database using following command:xe patch-upload filename=filename.xsupdate – it will show uuid of newly uploaded xotfix
3. Apply update using following command: xe patch-apply uuid=<UUID of the hotfix> host-uuid=<UUID of the pool master> (you can copy pool master uuid from XenCenter or from output of xe host-list)
4. Reboot pool master and continue with remaining servers in pool.

After SIP firmware update to version 9.3 on my Cisco 7945G and 7965G phones they all stopped to register with Asterisk. They did load config from tftp and then just stayed with “Registering” on screens forever.
What caused it is dropped UDP support in new version of SIP firmware and one required update to SEP{MAC}.xml config files, so, make following changes and may the force be with you:

sip.conf:
tcpenable=yes

SEP{MAC}.xml  (in each <line button=”N”> section):

<proxy>USECALLMANAGER</proxy>

Configuring appropriate default calendar permissions globally in an Exchange environment can be accomplished for Exchange 2000, 2003 or 2007 with a handy tool called PFDAVadmin found here.

The Exchange 2007 commandlet Set-MailboxCalendarSettings only works for resource mailboxes and won’t accomplish what PFDAVadmin can for calendar client permissions. The only commandlet currently that mirrors this capability simply retrieves client permissions on public folders Get-PublicFolderClientPermission

With PFDAVadmin, you have two options:

• script
• GUI

Read the rest of this entry »

My Citrix XenServer pool is powered through network enabled APC Smart-UPS (6000 RT)

There are at least two ways of monitoring UPS state in order to shutdown pool members and VMs running in the pool when juice is over:

– apcupsd (installation used to be somewhat tricky before XenServer 5.6 and included some unsupported movements)

– getting values from UPS via SNMP and acting accordingly to them – the way which I went, and you’re welcome to see detailed route description.

Read the rest of this entry »

Until it’s in official repository let’s use one provided by Brian Mercer:

put these in sources.list

deb http://ppa.launchpad.net/brianmercer/php/ubuntu lucid main
deb-src http://ppa.launchpad.net/brianmercer/php/ubuntu lucid main

And at then run this:

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 8D0DC64F
sudo aptitude update
sudo aptitude install php5-fpm

done!

Ever had problems trying to get two network cards directly connect via that standard crossover cable at 1000Mbit/s speed? If yes – it’s most likely because your cable was made using 100BaseT standard – only orange and green pairs were crossed. For gigabit it’s a bit more tricky.

1000BaseT Crossover cable pinout:

This morning XenCenter started to disconnect from pool almost immediately after it was started. Short backtrack revealed that only recent time adjustment on pool members could cause that. To fix this bad behavior of XenCenter I had to issue xe-toolstack-restart command via ssh on pool master.

if you are running Squid on or behind you Linux gateway here’s HowTo transparently run all outgoing HTTP through it

Read the rest of this entry »