If this doesn’t work for your, download the VSphere Client for 5.1 Update 2 which will install on Windows 8 natively.

So we will keep it very simple:

First off, I recommend firmware version 8.3.1. It’s the version we use and it seems to have the least bugs out of all the releases for these phones. Most new features seem to cater to Cisco CallManager features more than they do Asterisk, so let’s forget all about any versions after 8.3.1 for now!

Second, you will need to edit SEP$MAC.cnf.cml ($MAC being the mac address of your phone) and find the line that has this key:

 

<messageWaitingLampPolicy>0</messageWaitingLampPolicy>

You will want to change this to 1. There are more options that allow you to fine-tune this, however, I find this best. 1 will make the envelope blink next to the line that has a new voicemail, and will make that light shine so bright!

Now, we have one more step to make this work properly, which can be done two ways:

• Edit sip_custom.conf and add the following line:

buggymwi=yes

Save the file, reload asterisk.

OR:

• In FreePBX, click on the tools tab, go into SIP Settings (where you change up the NAT settings) and at the very bottom of the page, put in the above setting in the field for extra SIP options. Save, and reload.

You will almost immediately see a change if you already rebooted the phone, if not, well, reboot your phone!

Now go ahead and leave a voicemail and watch the indicator light up!

Some additional notes: You may notice a strange behavior where your dial tone will blip on and off when you start a new call if you have voicemail. This is intended and set as a default in some configs. If you find this annoying, go ahead and open up your SEP$MAC.cnf.xml file and find the following line:

<stutterMsgWaiting>1</stutterMsgWaiting>

and change it to 0. Reboot the phone, and the behavior should go away.

If you have any questions or comments, feel free to leave a few comments.

Further investigation revealed that the message was rejected by their Microsoft Exchange 2007 server’s Anti-Spam feature with message:
550 5.7.1 message rejected as spam by content filtering.

Since we are filtering their e-mail, they no longer need the Anti-Spam services of the Exchange Server, so here is how we disabled it.

1. Launch the Exchange Management Console
2. Expand Organization Configuration
3. Choose Hub Transport
4. Select the Anti-Spam tab
5. Highlight each feature (except recipient filtering), right click on it and then click “Disable.”
   1. We left Recipient filter enabled because it is meant to prevent reverse NDR attacks.
      

      Exchange Server 2007 Management Console
      Organization Configuration>Hub Transport>Anti-Spam

If an application that was deployed via group policy (GPO) is uninstalled using Add/Remove programs (appwiz.cpl), it will not be automatically reinstalled via GPO Group Policy processing on the next restart.

When an application is installed via GPO Group Policy on a client computer, a subkey is created at the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\AppMgmt

In order to force the reinstallation of software that was previously deployed via Group Policy, locate the subkey that contains values describing the software that you’d like to have reinstalled and delete it.

After removing the key from the registry of the client computer, run the command “gpupdate /force” from a run prompt or command line and then restart the computer.

While attempting to convert a couple of Cisco 7941G phones from the SCCP-8-5-4  to SIP, I encountered an “Auth Fail” message after performing a factory reset on the phone.  The “Auth Fail” message was displayed while attempting to download the term41.default.loads file.  If you haven’t reset the phone, you can encounter the error when the phone is attempting to download the SEP{mac}.cnf.xml file.

It turns out that the latest SCCP firmware is unable to authenticate the latest SIP image that I’m trying to install on the phone.  In order to get past this, you’ll need to downgrade the phones current SCCP firmware to sip.8-5-2.  After that, you can upgrade to the another version if you like.

Unzip the 8-5-2 firmware into your tftp directory and overwrite the term41.default.loads and term61.default.loads.  Reset the phone and it will load the term41.default.loads file.  The term41.default.loads file will cause the phone to “upgrade” to the 8-5-2 firmware.  When the phone reboots from the firmware update, it will load the SEP{mac}.cnf.xml.  This is where you want to specify the firmware version that you’d like to end up with.  This time, you won’t get the ”Auth Fail” error.

In this article, we will cover the tuning and optimization of WSUS in SBS 2008 to free up disk space consumption.  Some of the tips below should be repeat every several months to reclaim disk space.  Here is a summary of topics:

1. IIS Logging for WSUS
2. SQL Server Database “SBSMONITORING”
3. SBSMonitoring_log.LDF size reduction
4. (Coming) Updates Synchronization settings in “Windows Server Update Services” manager
5. Reducing the size of Windows\winsxs Folder
6. Cleanup the Licensing Logs for SBS 2008

IIS logging for WSUS is a hidden disk eating culprit, so we’ll address this one first.

These files are typically found in: “%SystemDrive%\inetpub\logs\LogFiles\W3SVC1372222313″  My suggestion is to disable logging for WSUS and delete these log files.  To do so:

1.  Open IIS Manager
2. Navigate to “Sites” and then ”WSUS Administration”
3. Click the ”Logging” icon
4. On the right hand column, click “Disable”
5. Close IIS Manager
6. Open Explorer and navigate to “%SystemDrive%\inetpub\logs\LogFiles\W3SVC1372222313″
7. Delete the contents of this directory to reclaim disk space

Another disk eating culprit is the “SBSMONITORING” SQL Database.

This database will eventually grow to 4GB where it reaches its limit.  You may notice “sqlservr.exe *32″ process takes a lot of processor time when the database grows large and may also notice that Status & Alerts in Windows SBS Console take a long time.

1.  Log on with a user that has administrative privileges.
2. Start SQL Server Management Studio. (Express edition works) in elevated mode by right clicking and then clicking “Run as Administrator”
3. Attach to SBSMONITORING instance (replace SERVERNAME with the name of your server):
   Server Type: Database Engine Server
   Name: SERVERNAME\SBSMONITORING Authentication: Windows Authentication
4. Once connected, from the Menu, click: File -> New -> Query with Current Connection. This creates a new query window.
5. To prevent your database from outgrowing it’s 4GB size limitation, Copy the commands below into the query window, then press F5 to execute:USE SBSMonitoring UPDATE [SBSMonitoring].[dbo].[Settings] SET [Value] = 30 WHERE [Name] = ‘CleanupPeriod’ EXECUTE [SBSMonitoring].[dbo].[CleanupDatabase] CREATE NONCLUSTERED INDEX [_SBS_BLOG_index_WMICollectedData_5_K4_K1_K5_2] ON [dbo].[WMICollectedData] ([WMIPropertyID] ASC,[ID] ASC, [WMIInstanceID] ASC) INCLUDE ( [DateCollected]) WITH (SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, DROP_EXISTING = OFF, ONLINE = OFF) ON [PRIMARY] CREATE NONCLUSTERED INDEX [_SBS_BLOG_index_Reports_5_K2_K3_1_4] ON [dbo].[Reports] ([ConfigurationID] ASC, [DateGenerated] ASC) INCLUDE ([ID], [Data]) WITH (SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, DROP_EXISTING = OFF, ONLINE = OFF) ON [PRIMARY] CREATE NONCLUSTERED INDEX [_SBS_BLOG_index_WMICollectedData_5_K2D_K4_K5] ON [dbo].[WMICollectedData] ([DateCollected] DESC, [WMIPropertyID] ASC, [WMIInstanceID] ASC) WITH (SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, DROP_EXISTING = OFF, ONLINE = OFF) ON [PRIMARY] CREATE INDEX [_SBS_BLOG_index_Alerts_8_7_] ON [SBSMonitoring].[dbo].[Alerts] ([DefinitionID], [ComputerID]) INCLUDE ([DateOccured]) CREATE STATISTICS [_SBS_BLOG_stat_WMICollectedData_5_1_4] ON [dbo].[WMICollectedData]([WMIInstanceID], [ID], [WMIPropertyID]) CREATE STATISTICS [_SBS_BLOG_dta_stat_WMICollectedData_4_1_5_2_3] ON [dbo].[WMICollectedData]([WMIPropertyID], [ID], [WMIInstanceID], [DateCollected], [StatusID]) CREATE STATISTICS [_SBS_BLOG_dta_stat_WMICollectedData_5_1_3_4] ON [dbo].[WMICollectedData]([WMIInstanceID], [ID], [StatusID], [WMIPropertyID]) CREATE STATISTICS [_SBS_BLOG_dta_stat_WMICollectedData_5_4_2] ON [dbo].[WMICollectedData]([WMIInstanceID], [WMIPropertyID], [DateCollected]) CREATE STATISTICS [_SBS_BLOG_stat_WMICollectedData_2_1_5] ON [dbo].[WMICollectedData]([DateCollected], [ID], [WMIInstanceID]) CREATE STATISTICS [_SBS_BLOG_stat_WMICollectedData_1_3_5_2] ON [dbo].[WMICollectedData]([ID], [StatusID], [WMIInstanceID], [DateCollected])

An optional optimization that you may use at your own risk is to add indexes.

Although this has worked well for me, I must say that this is tinkering with the original product design.  Regarding “sqlservr.exe *32 high CPU usage in SBS 2008″
This is the bit that will help optimize the database to take less processing resources by indexing some of the monitoring database tables.  Replace the code in your query window with the code below and press F5:

USE SBSMONITORING
GO
CREATE NONCLUSTERED INDEX [IDX_Alerts_GetAlertsPerID] ON [dbo].[Alerts] (    [DefinitionID] ASC,    [ComputerID] ASC,    [DateOccured] ASC,    [IsSet] ASC,    [ID] ASC )
GO
CREATE NONCLUSTERED INDEX [IDX_WMICollectedData_GetSecurityProductPerComputer] ON [dbo].[WMICollectedData] (    [WMIInstanceID] ASC,    [WMIPropertyID] ASC,    [DateCollected] ASC,   [ID] ASC )
GO

create index IDX_WMIObjectProperties_ObjectID on WMIObjectProperties(ObjectID,ID)
Go

create index IDX_WMIObjectInstances_ObjectID on WMIObjectInstances(ObjectID,ID)

SBSMonitoring_log.LDF size reduction

 The SBSMonitoring_log.LDF file should be 1GB or less, but has been known to grow over 30GB in some instances.  To reduce the size of this space eating monster, do the following:

Open SQL Server Management Studio Express by “RunAs” Administrator
Connect to the “[servername]\SBSMonitoring” database, use Windows Authentication
Expand Databases and then right click on “SBS Monitoring” and choose Tasks, Shrink, file.  In the window that opens, choose “Log” from the “File Type” drop down, click OK. 

Reducing the size of Windows\winsxs Folder

The winsxs folder is a PIG.  Open a command prompt in the administrative context
Run “compcln.exe”
After completion, you may notice up to 1.7GB of recovered space, but you won’t be able to roll back SP2.

Cleanup Licensing Log

The licensing log will take up a lot of space over time.  To reclaim that space:
Open a command prompt in the administrative context
Run: del “%systemroot%\system32\winevt\logs\Microsoft-Windows-Server Infrastructure Licensing*%4Debug.etl.*”

References:

• Index entries found at : http://social.technet.microsoft.com/Forums/en/smallbusinessserver/thread/d195baac-da8b-4387-9079-c55d5e1879b4
• WinSXS cleanup found at:
  http://social.technet.microsoft.com/Forums/en-US/3bcacb59-61f8-457d-bd62-b1230c98aec0/sbs-2008-sp1-winsxs-growing
• Cleanup Licensing Log found at:
  http://blogs.technet.com/b/sbs/archive/2010/03/02/recovering-disk-space-on-the-c-drive-in-small-business-server-2008.aspx

Complete these steps:

1. Cycle the power of the phone by unplugging the power cord and then plugging it back in. If your phone is powered over Ethernet, unplug the network cord and plug it back in.
2. The phone will begin to boot. Immediately press and hold # while the Headset, Mute, and Speaker buttons flash in sequence. Release # after the Speaker button is no longer lit.
3. The line buttons flash in sequence in order to indicate that the phone waits for you to enter the key sequence for the reset.
4. Press 123456789*0# within 60 seconds after the Headset, Mute, and Speaker buttons begin to flash.
   You must complete this key sequence within seconds or the Headset, Mute, and Speaker buttons will stop flashing and the phone will continue its normal boot process and the phone does not reset.
   If you enter an invalid key sequence, the buttons no longer flash, and the phone continues with its normal boot process. The phone does not reset.If you enter this key sequence correctly, the phone displays this prompt:
   upgrading

If you want to complete wipe the phone of its current firmware, hard reset using 3491672850*# instead of 123456789*0#   The extension lights will flash red and then the phone will take the firmware defined in your termXX.default.loads file.

Exchange Unified Messaging

Well folks – my latest one track minded excursion into Open Source was with Elastix. Using version 2.2, there wasn’t a whole lot of effort required until I set myself out to integrate Exchange 2007 Unified Messaging. There are many articles out there with fragments of information and misinformation. I wanted to consolidate the useful tidbits here to supplement the other great write ups out there.  This is not a step-by-step tutorial, but rather a collection of solutions to the challenges I faced during the integration of Asterisk and Exchange Unified Messaging on Exchange Server 2007 using the Elastix 2.2 distribution.

Problem: When an outside caller is transferred to Voicemail, the call is disconnected. Inside callers (other extensions) hear the greeting and can leave a message but outside callers cannot.
Resolution: I had to add “canreinvite=no” in the trunk configuration to Exchange. This setting is required for proper Exchange Unified Messaging integration with Exchange 2007 or 2010.

Problem: Configure Incoming Call to be answered by Exchange Auto Attendant.
Answer: In Elastix OR FreePBX, go to Misc Destinations. Create a destination called “Exchange AA” and use the initiator extension you setup for AA (Auto Attendant) in Exchange Unified Messaging configuration as the extension. Now go to the Inbound Route for the number you’d like to ring to AA and near the bottom of the page, set destination to “Misc Destinations” and then choose “Exchange AA” – submit and apply.

Problem: Voicemail buttons on phones (*97) should call Exchange Voicemail.  You want *97 to use Exchange Unified Messaging Voicemail instead of Asterisk Voicemail.
Answer: Go to Misc Destinations. Create a destination called “Exchange VM” and use the initiator extension you setup for Voicemail in Exchange Unified Messaging as the extension. Go to Feature Codes and disable “My Voicemail” (*97) near the bottom of the page. Go to Misc Applications and add one. Call it “My Voicemail” with feature code “*97″ Feature Status set to enabled. Set destination to “Misc Destinations” and select “Exchange VM”

Problem: Configure Asterisk to use Exchange Unified Messaging Voicemail instead of its own.
Answer: You need to add the following to the extensions_override_elastix.conf file or extensions_override_freepbx.conf file.  Either file is fine (but not both):

[macro-vm]
; ARG1 – extension
; ARG2 – DIRECTDIAL/BUSY
; ARG3 – RETURN makes macro return, otherwise hangup
exten => s,1,Macro(user-callerid,SKIPTTL)
exten => s,n,GotoIf($["foo${DB(${BLKVM_OVERRIDE})}" != "fooTRUE"]?vmx,1)
exten => s,n,Noop(CAME FROM: ${NODEST} – Blocking VM cause of key: ${DB(BLKVM_OVERRIDE)})
exten => s,n,Hangup
exten => vmx,1,GotoIf($["${ARG2}" = "DIRECTDIAL"]?3)
exten => vmx,2,SIPAddHeader(Diversion:<tel:${ARG1}>\;reason=no-answer\;screen=no\;privacy=off)
exten => vmx,3,Dial(SIP/ExchangeUM/222) exten => vmx,4,Hangup

***  in the last line “exten => vmx,3,Dial(SIP/ExchangeUM/222) exten => vmx,4,Hangup” you must replace “ExchangeUM” with the name you gave your trunk to exchange and you must replace “222″ with the initiator extension you assigned for voicemail in your Exchange Config. ***

Problem: When an outside caller is transferred to voicemail, they can leave a voicemail but it is not delivered to the users mailbox. Voicemails from inside callers are delivered but voicemails from outside callers are not.
Answer: You need to have the Hub Transport Service installed as well as the Exchange Unified Messaging role. This is true even if you do receive voicemails from inside callers (other extensions.) This is definitely true if you installed the UM role on a separate Exchange Server than your Mailbox server. Check the Application Event Log on the Exchange Unified Messaging role server and check http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=8.0&EvtID=1082&EvtSrc=MSExchange%20Unified%20Messaging&LCID=1033 , especially if you’re getting error 1082.

Hope you found this article useful.  If you have any questions or require assistance with your computer or network in the Los Angeles, Orange County and Inland Empire area, give us a call at (888) 777-WURX.

Please like our company at http://www.facebook.com/itwurx
Even if it wasn’t useful, like us anyway!

Fortunately the hard drive was not the failure, so I pulled it out, connected it to a USB to SATA adaptor and mounted the hard drive on another computer.   Here are the steps I had to follow in order to transfer worldship to the new computer.

1. Install UPS WorldShip 2012 on the new computer
2. Be sure that WorkShip is closed and open the UPS WorldShip Support Utility (Start, Programs, UPS, UPS WorldShip Support Utility)
3. Double Click on “Data Maintenance”
4. Click “Restore”
   - Note – If you get a message that users are connected to the database, wait a moment and click “Restore” again.  If this still fails after a few times, restart your computer (to definitively kick everybody off) and try again a couple of times.
5. Be sure to “Check this box if the files you wish to restore were backed up by the WorldShip application.”
   Select the disk you mounted via USB.  – Note – I had to mount the disk directly via USB.  I could mount the disk over the network or via a mapped drive.  It had to be connected directly to the computer to work.
6. Now browse to <DriveLetter>\UPS\WSTD\BACKUP
   - Note – If you didn’t install UPS to the default location, you will need to browse to that location to find the WSTD\BACKUP folder
7. You should see some files in the third box.  Select the newest one and click “Restore” button.  The date of the backup will be referenced near the end of the file name.  The restore will ask for a couple of confirmations
8. While the restore is taking place, you may separately browse to the old installation ?:\UPS\WSTD and copy the folders “Archive” and “ImpExp” to the WSTD folder of the new installation.
9. Once you’ve copied those files and the restore process is complete from the Data Maintenance Utility, you can open WorldShip.  You may need to perform updates and re-register this installation with UPS.  You may need a copy of your most recent invoice to complete the registration of the new installation.
10. Contact UPS at 888 553-1118 for further help to transfer worldship to new computer if required.  You will need to have your shipper number handy.

Hope you found this article helpful to transfer worldship to a new computer.  If you have any questions or require assistance with your computer or network in the Los Angeles, Orange County and Inland Empire area, give us a call at (888) 777-WURX.  We provide

Please like our company at http://www.facebook.com/itwurx
Even if it wasn’t useful, like us anyway!

Exchange Setup checks the following Registry key for any pending file renames:
HKLM\SYSTEM\CurrentControlSet\Control\SessionManager\PendingFileRenameOperations
If a program installation, uninstallation  or update needs to rename or replace a file that is currently in use, it must do so during a reboot.  The program setup would add an entry to this key. Here is an example of what an entry might look like:
\??\C:\WINDOWS\system32\FxsTmp\fxsE.tmp
or
\??\C:\Windows\system32\spool\PRTPROCS\x64\1_DKACHC4C.DLL

If after a restart, you recieve the same error, you can delete entries of the previously mentioned registry key and then repeat the Exchange Server 2007 SP2 setup again.   Edit the registry at your own risk.

Hope you found this article useful.  If you have any questions or require assistance with your computer or network in the Los Angeles, Orange County and Inland Empire area, give us a call at (888) 777-WURX.

Please like our company at http://www.facebook.com/itwurx Even if it wasn’t useful, like us anyway!