Glen Munro blogs about Lync, Microsoft and Cisco products used in his capacity as a Network Administrator for Prairie South School division.
Look for him on social media sites as "GM_Pentaxfan"
HTA sub routine Sub Speak (text)
'V3.20
'Dim objVoice 'Enabling this section will slow down the HTA program
'Set objVoice = CreateObject("SAPI.SpVoice")
'Set objVoice.Voice = objVoice.GetVoices("Name=microsoft sam").Item(0)
'objVoice.Speak Replace (text, "'d", "ed")
'objVoice.Speak text
'msgbox Text 'Running VBS script allows HTA to continue while message is played.
cmdVoice = "voice.vbs " & chr(34) & text & chr(34)
Objshell.run CmdVoice,0,0
End SubVoice.vbs Script
'V3.20
on error resume next
If wscript.arguments.Item(0) <> "" Then
Text = wscript.arguments.Item(0)
Set objVoice = CreateObject("SAPI.SpVoice")
'Set objVoice.Voice = objVoice.GetVoices("Name=microsoft sam").Item(0)
'objVoice.Speak Replace (text, "'d", "ed")
objVoice.Speak Text
end if
This year it seems that we have had a lot of equipment failures do to power outages.
This has been hard on the older paging equipment in our schools resulting in the need for new equipment.
We approached our audio experts for a solution that was network accessible and would still work with a Cisco CME based phone system if one was installed at that location at a later time.
Their solution was a TOA 8000 system which can be controlled and monitored over the network.
Unlike the previous TOA 9000 and Bogen PCM units that connected using an FXS port, the TOA 8000 requires different hardware.
The FXO port (same hardware that we use to connect to our telco provider phone lines) on the Cisco CME 2921 connects into the NL-8000AL interface unit. The Cisco paging dial peers only required a port change and no changes were made to the Singlewire LPI software configuration we had set up for the Bogen equipment. (see previous post)
We found the TOA 8000 required a setting of a 1 second delay before paging. If the delay was set to zero, the generated DTMF tones could be heard over the speakers on random occasions.
We had been using SingleWire's InformaCast and LPI solution to run our bells schedule.
It integrated well with our Bogen equipment and allowed bells to ring both on the SCCP phones and Bogen paging system using a FXS port.
A few years ago we were installing a new CME into one of our remote sites, and found that the new version of Cisco OS was no longer compatible with InformaCast. Or at least that is what SingleWire was telling us.
We couldn't downgrade the Cisco CME OS because the SRE module running the CUE would not work with older versions of Cisco CME OS.
After a little bit of trial and error, installing the InformaCast software using the HRE install option worked. Bells would now ring even though it reported an error about not being able to talk to the Communications Manager cluster... (see below)
Both the CUCM or CME install options for InformaCast wanted to 'talk' to the CME every time a bell was to ring and since it couldn't 'talk' to the new OS... the bell would not ring.
It's been working great until this year... now we are not sure if the Bogen equipment is starting to fail due to age or if the numerous power outages this summer have caused damage to the Bogen. Either way the DTMF tones from the LPI software are not triggering the Bogen zones. However paging from the Cisco CME using the same DTMF tones worked everytime.
After several tests, solutions were found for 3 out of 5 sites. Adjusting the DTMF length and volume in the LPI device settings resolved the issue. 1 site will be getting new equipment as the Bogen is over 10 years old. The other site will be testing this solution.
The previous config had the LPI software sending the DTMF tones based on the speaker on the single Device (ex 1410). (Sip Address is the Voice Vlan IP of the CME)
The CME already has paging dial peers for the zones, so the LPI software will use those numbers (ex. 1411) when calling the CME via SIP calls. The CME will pass along the DTMF codes and then the bell (aka message) will play. (Sip Address is the Voice Vlan IP of the CME)
dial-peer voice 1411 pots
destination-pattern 1411
port 0/1/0 'FXS port connected to Bogen
prefix ,07#
The problem was that the LPI device software needs at least 1 DTMF code or it will not create the InformaCast speaker.
The solution was rather simple after testing different volumes and time outs.
Change the "DTMF Via" option from "RFC2833" to "SIP INFO".
Now you do not hear the extra DTMF tones before the bell.
The other feature we lost in changing to HRE mode was the ability to play the messages on the phones.
Solution:
Create a paging group for phones (In our case all phones)
ephone-dn 200
number 1498
name Paging All
paging ip 239.1.1.2 port 20482 'Works with SIP and SCCP phones
paging group 201,202,203,204,205,206,207,208,251,303
Create a LPI Paging device that calls the 1498 via SIP.
Now create the speakers in InformaCast and add the Phones speaker to any of the InformaCast Paging Recipient Groups. You may have to increase the "Wait Time" on the messages to allow the CME to send the DTMF tones. The "Example Humoctopus Alert" message is perfect for testing.
Cisco has a Single number reach feature that allows calls to ring more than one number. Think of it as a parallel hunt group but with the option to turn it off and on from the user's phone.
With this setup, the end user's Lync client and Cisco phone will ring a the same time.
Lync (Skype for Business) setup
Create PSTN Gateways
- use the IP address of the CME
Create the Trunks
- Listening on port 5060 and Mediation port 5068.
Enable Enterprise Voice for user's account.
Assign a fake number to the Line URI in the user's account setup
(Example of user with extension 4025 would be Tel:+13065554025)
* You can also create a CME Dial Plan and a CME Voice Policy to allow Lync users to call out on the CME's phone lines from their Lync client.
Cisco CME setup
- If you are using Voice and Data Vlans on your CME, bind it to the CME same Vlan used by the Lync server.
interface GigabitEthernet0/0.1
description Voice
encapsulation dot1Q 1
ip address 192.168.1.1 255.255.255.0
!
interface GigabitEthernet0/0.134
description Data
encapsulation dot1Q 2
ip address 192.168.2.1 255.255.255.0
voice service voip
sip
bind control source-interface GigabitEthernet0/0.1
bind media source-interface GigabitEthernet0/0.1
Create voice translation-rules (these will add the +1306 in front of the number)
Sometimes you want a report of all the variables that computer/device will have when it runs the task sequence.
Here's a script that will report ...
a) device name
b) device assigned variables
c) Collection name with the assigned variables of which the device is a member.
It requires the SCCM console installed and you must provide the computer name in the command line.
The script will report back if the computer name is not valid and kill the powershell process.
For testing, run the script from a command prompt. i.e. powershell .\variables.ps1 computername
In preparing for a Universal Imaging Task sequence, the thought came across my mind, what if I want to see what's going on and the computer is 2 hours away?
Once the task sequence installs Windows, we have it install UltraVNC so after that point it is possible to remotely connect. However what about before when the computer has booted from our PXE server and is running Windows PE.
Here is the quick and dirty version of how we can now VNC into a computer that has started up in Windows PE.
1) Create Standard WIM file using the Windows ADK and then before committing the changes...
1a) Created an 'xtras' folder on the root of the mount folder (I called it 'xtras' because it's always drive x: in our PE environment)
2) UltraVNC program with password protection
2a) Installed on test system running Windows 7 with any settings (i.e. password)
2b) Copied the UltraVNC found in Program Files to mount\xtras
3) Create Computername.vbs and copy into mount\xtras
3a) Basic script that extracts the IP address of the computer using WMI
3b) Disables the WinPE firewall - "wpeutil disablefirewall"
3c) Installs UltraVNC
3d) Popup message with IP address - only on screen for 90secs so that it does not prevent the task sequence from running.
4) Create startup.cmd file in mount\xtras
4a) In that file, it runs wscript.exe %systemdrive%\xtras\computername.vbs
5) Once files have been copied to the mount\xtras folder, you can commit the changes to the WIM and proceed with importing it into SCCM.
6) Create at 'winpeshl.ini' file (See below)
6a) Save to... C:\Program Files\Microsoft Configuration Manager\OSD\bin\x64 or C:\Program Files\Microsoft Configuration Manager\OSD\bin\i386
7) Add Drivers and any extra components that you require
'Extract Computer Details 'Version 3.01 WMI Query 'May 1, 2015 on error resume next Dim oTaskSequence 'Create Objects Set objWMIService = GetObject("winmgmts:\\.\root\CIMV2") 'Local computer WMI Set objShell = CreateObject("WScript.Shell") strQuery = "SELECT * FROM Win32_NetworkAdapterConfiguration WHERE MACAddress > ''" Set colItems = objWMIService.ExecQuery( strQuery, "WQL", 48 ) For Each objItem In colItems for each IP in ObjItem.IPAddress If left(IP,4) = "192." then strIP = IP & vbCRLF & strIP end if next Next StrInfo = "If you require any assistance..." & vbCRLF &_ "Please send this information to the IP department." & vbCRLF &_ vbCRLF & "IP Address: " & strIP cmdFirewall = "wpeutil disablefirewall" objShell.run cmdFirewall,0,1 cmdUltra = "%systemdrive%\xtras\UltraVnc\winvnc.exe -install" 'msgbox cmdUltra ObjShell.run cmdUltra objShell.Popup strInfo, 90, "Message Box Title"
Recently the number of audit failures on our Remote Desktop and IIS servers has increased drastically in the last month.
List of IP addresses found here.
Found this program for our 2012 servers (or any RDP using TLS)
Default config...
After 3 failed login attempts, it would temporarily block the IP for 20 minutes. (Soft Lock)
After 10 login attempts, it would block the IP for 24 hours. (Hard lock)
-There is the option to hard lock the IP address forever.
Issues
1) No option to customized notification emails. -wanted to include
2) Cannot white-list a service provider only IP addresses.
3) No Response to inquiry about their products and licensing.
Since the program creates an event log for when it blocks the IP address, a PowerShell script was created to add firewall rules (permanent rules) and send email notifications out with detailed information.
The original PowerShell script just sent out emails with the server name when an event log with 4001 or 9001 is created in the "CyberArms" event log.
It worked great on our 2012 servers, however 2008 stored the Event log data with extra returns and spaces in the IP addresses. In testing it caused the local network to be blocked via firewall. Good thing it was a virtual machine and could still be access through Virtual Center.
Updated the PowerShell script to distinguish between 2008 and 2012 servers.
Another VBscript was created to manually delete any firewalls from 'trusted' IP addresses using netsh from another computer.
After the first weekend having to check each IP address and manually delete the rules got old and time consuming.
The next revision of the script added NSlookup to a ProviderLookup function in the script.
The ProviderLookup function was created to allow certain IP addresses or provider names (provided by NSLookup) to be unblocked automatically.
Example if NSlookup returned a provider name with "Domain.ca" in it, then we trusted it and the firewall was deleted.
Emails now include the IP address, the provider information and if the rule was deleted.
Steps...
Install CyberArms software
Enable any security agents in CyberArms
Download PowerShell Script "CyberArms Eventlog Script.txt"
- Rename to .PS1 and change "DOMAIN.CA" and email settings.
Create Task Sequence to run the script when event 4001 or 9001 is logged.
Update - April 21, 2015
The ProviderLookup function will now include Country and ISP information extracted from http://ipaddress.com if it cannot find a DNS name for the IP address.
Future options
1) Create the same firewall rule on more that one server via PowerShell Array variable.
2) Create a pause between rule creation and rule deletion, just in case there was malicious intentions.
- probably use a ping command to 127.0.0.1 for 10 minutes then have it delete the rule.
3) Working on cleaning up the ProviderLookup function so that certain ISP names will be allowed.
Back in February I posted about adding contacts to Lync Groups.
However, what happens when you spell the contact address wrong and you just imported that into your 1000+ clients contact list...
Well, you need to find a way to remove the contact from the XML file.
I could have restored the backup files to the user accounts... but didn't think of that until I got this solution working. *
After trying to create an XML script tath use the same script in the previous post, but this time we will replace the offending string with blanks.
Add this to the Configurable Variables section #Delete this line from XML $Variable = @' <Contact Buddy="contact@domain.com" SubscribePresence="1" Groups="1 20" /> '@ $CommonContact = "contact@domain.com" # The one that is spelled wrong.
In the Process-Contacts Function,
Change If ($ContactsToAdd) to If ($ContactsToAdd)
Remove the $ContactsToAdd section and replace it with.
* This does remove the contact from the user's visual list of contacts. However, when the user's contact info is exported, the old contact is still there just not listed in any groups which is why it doesn't appear in the client.
In short, double check spelling and try it on a test account.
To change the script from all users to 1 users change... $AllSipAddresses = Get-CsUser -Identity lyncroom@domain.com -Filter {Enabled -eq $True} | Select SipAddress | %{$_.SipAddress.Replace('sip:','')}
Original Post about adding groups found here on Roland Paix's IT Blog
We purchased a couple of the Intel NUC mini desktops (model NUC5i3RYK) for our custom Lync Room systems.
Deploying with Microsoft System Center Configuration Manager...
Same with any new system... the Window PE boot image needed new drivers for the Ethernet adapter. (In our case the 64 bit driver - e1d64x64.inf)
Created a driver pack for the Intel NUC system, however the drivers were not getting installed into the image by the "Apply Device Drivers" task.
Decided to try the "Apply Driver Package" and picked the Intel NUC package option to see what would happen.
Now the task sequence fails with... This task sequence cannot be run because a package referenced by the task sequence could not be found. For more information, please contact your system administrator or helpdesk operator. Using F8 and cmtrace to open the \windows\temp\SMSTS.log file and found this error message... Failed to resolve selected task sequence dependencies. Code(0x80040104) Found this website and updated the distribution points so that the source version number would not be '1' and now the task sequence is working and drivers are installing.
We know that Config Manager's Task Sequences run with a system account and can only be advertised to Device collections.
What if we wanted only certain people to have permission to re-image their computer?
This script will record the logged in username via wmi as a Task Variable.
If that account is a member of a specific domain group then the 'ValidUser' Task Variable will be set as True.
You can then use that 'ValidUser' Task Variable to allow groups or other commands/applications to run.
To test the sequence with the msgbox dialogs you will need the ServiceUI.exe file from the Microsoft Development kit.
'Find Logged in user 'Version 1.60 on error resume next Dim objNetwork, objDomain, oTaskSequence 'msgbox "Testing" 'Create Objects Set objNetwork = CreateObject("Wscript.Network") Set objDomain = GetObject("LDAP://RootDSE") Set oTaskSequence = CreateObject ("Microsoft.SMS.TSEnvironment") ' Obtain user information. 'strUserName = objNetwork.UserName strcomputer = "." Set objWMI = GetObject("winmgmts:" & "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2") Set colSessions = objWMI.ExecQuery ("Select * from Win32_ComputerSystem",,48) For Each objItem in colSessions if objItem.Username <> "" then strUserName = Replace(Lcase(objItem.UserName),"prairiesouth","") oTaskSequence("UserName") = replace(strUserName,chr(92),"") 'msgbox strUserName else strUserName = objNetwork.UserName end if next If not lcase(strUserName) = "system" then 'Verifies not the System account. strDomain = objDomain.Get("dnsHostName") Set objUser = GetObject("WinNT://" & strDomain & "/" & strUserName) For Each strGroup in objUser.Groups If Lcase(strGroup.Name) = "help desk end users" or Lcase(strGroup.Name) = "information technology department" then strValid = 1 oTaskSequence("UserGroup") = strGroup.Name 'msgbox strGroup.Name exit for end if Next else strValid = 0 end if If strValid = 1 then oTaskSequence("ValidUser") = "True" 'msgbox strValid Else oTaskSequence("ValidUser") = "False" 'msgbox strValid end if
Was looking for a way to Populate our Lync Room systems into end users Lync Contacts as a group rather than a bunch of individual accounts. (More on Lync Room Systems here http://bit.ly/netadmlr)
# Common Contacts - Enable and populate this variable with a set of Lync contacts to distribute to all users instead of distributing all users to all users. Overrides $DontAddUsers.
Change these lines to include 1 and the group number in the $ContactstoAdd | foreach{} section
$NewContact.SetAttribute('Groups','1 20')
If you have a large organization, you will need to create a new policy or edit the Global Presence policy. Once all the Lync users had the Lync Rooms in the list, the "Maximum Followers Reached" error showed up on the Lync Room systems.
A new Presence Policy was created and applied to the Lync Room accounts. The MaxCategorySubcriptions was to 3000 and the error went away.
Since it was only applied to the Lync Room systems it should not drastically increase the server traffic as compared to applying to all our Lync users.
Now that you have collections created based S.M.A.R.T diagnostics or Disk event log entries baselines for failing hard drives... (See previous post)
We can create a custom Task Sequence to notify the user of the problem, when they log onto the computer.
Optionally, you could also deploy this as an available task sequence, for end users to manually check hard drive status.
Here are my suggestions for the task sequence...
Name: Hard Drive Diagnostic
Progress notification text: "Please submit a help desk ticket if the hard drive reports as failing." (or use the standard "Running: <Task sequence name>")
Suppress task sequence notifications - Optional
Maximum run time: 5 minutes
Run on any platform.
Sequence of Tasks... (Keep in mind that the "Name" is what the end user will see on the screen)
Set Task Sequence Variable
Name: Testing hard drive health. Please wait.
Variable: HD Failure
Value: True
Options:Add a WMI query Condition
WMI Namespace: root\wmi
WQL Query: select * from MSStorageDriver_FailurePredictStatus Where PredictFailure = True
Option 2 - Using PowerShell script to read system event log
This option will read the System event log and count any 'disk' source logs that are not Information level.
Note: This will include issues with temporarily attached external hard drives or USB drives.
Name - Event Log Disk Errors
Platforms - All (This will work for servers and virtual machines)
Settings
Name: Report disk errors found in Event Log
Type: Script
Discovery script (See end of post)
Counts the events and writes that value.
Compliance Rules
Name: Disk error count
Rule: Less than1 (That's a number one)
Noncompliance severity: Critical
Now that you have created the Configuration Items, you can add (one or both) to a Configuration Baseline and deploy them to your collections.
Once deployed create collections for the non compliant systems and then use that information in reports for your help desk or create a Task sequence that alerts the end user that the hard drive is may be failing.
Here's the PowerShell script...
- Updated Feb 3, 2015 to exclude '*Device\Harddisk1\DR1*' event logs.
#Version 2.30 Feb 3, 2015 #Designed for SCCM Baseline $AllEvents = 0 #Default Event Logs $Provider = "disk" $HourChange = 24 #Up to you how far back you want to go $TimeNow = [DateTime]::Now $TimeChange = [DateTime]::Now.AddHours(-$HourChange) #Check Event Log for errors $EventLogNames = "System" ForEach ($log in $EventLogNames){ $entry = " " #Search Event Logs
One thing I have found with System Center Configuration Manager is that the client cache folder can take up a lot space on the hard drive. Filled with updates or applications source files that no longer are needed.
Only way is to set the Cache size to smaller value using a vbs script (or powershell) that runs these commands...
set oUIResManager = createobject("UIResource.UIResourceMgr") set oCache=oUIResManager.GetCacheInfo() oCache.TotalSize=4096
However, if you were to install a program like AutoCAD that requires more than 4GB of cache storage, it would likely fail.
The PowerShell script listed at the bottom of this post (based on Kaido Järvemets posting at http://cm12sdk.net) will clean up the "old" content in ccmcache based on the LastReferenced WMI information.
The '$ReferenceAge.Days -gt 30' section deletes anything not referenced in the last 30 days.
The "#Change Cache size" section is optional and only included for reference.
The 'stop-process $pid -Force' command however is required as there have been cases where the PowerShell script fails to exit.
It can be run on a remote computer using the psexec program from Sysinternals.
Example.
copy the file over to hard drive of the remote system.
if ($ReferenceAge.Days -gt 30) { #Write-Host Found $CacheElementID Last referenced $LastDate That is $ReferenceAge ago in $FolderLocation -ForegroundColor Red #Based on http://cm12sdk.net/?p=1526
Write-Host Too old, deleting folder $FolderLocation -ForegroundColor Red $CMObject = New-Object -ComObject "UIResource.UIResourceMgr" $CMCacheObjects = $CMObject.GetCacheInfo() $CMCacheObjects.DeleteCacheElement($CacheElementID) }
#Remove number sign from the next 2 lines to allow for more information #else { #Write-Host $FolderLocation was last referenced $LastDate That is $ReferenceAge days ago -ForegroundColor Green} }
In searching for Caller ID programming on a Cisco CME, I came across the station-id command for FXO, FXS and DID ports.
Since we are not subscribing to our Telco providers incoming call display, this command allows us to assign a name (or number) to calls coming in on the voice-ports.
If we were using the Telco's call display, we would need to use the ephone-dn forwarding setup in the previously mentioned post.
Incoming Call
Now all incoming and outgoing calls are now labeled with the Line 50x and DID 30x. (x referring to the line number)
voice-port 0/0/0 station-id name Line 501 . . .
voice-port 0/1/3 station-id name Line 508
Outgoing Call
Why use 50x and 30x? - Park codes are 10x and if you look at the dial pad L is #5 and D is #3.
Since we can't call out on a DID port, the station-id helps us report troubles to our Telco provider.
The station-id number command would assign a E164 number to that port. However, some people might get confused and think that is the number of the person calling.
We using the FXS port for paging, so we simply call it "Paging".
Call Detail Recording for Nortel (now Avaya) BCM is done with push or pull client software. This setup allows end users to access the FTP share files using Notepad++. (Keep in mind setup is done on Windows based machines.)
Setup the Call Detail Recording Data File Transfer to push the records to your FTP server based on what ever schedule you like.
For multiple sites, create sub folders in the root of your FTP server based on their location. i.e. Reports\School or Reports\Office
Setup an account on the BCM end users or support staff to manually push out the file if it's an urgent request. They just click the "Push Now" button once you have setup the information.
** Keep in mind they will see the IP address and remote user account name for the FTP server.
Now that the files are being pushed to the FTP server, we need a way to get them to the end user.
Since we are using a Windows FTP server, create a share based on the "Reports" folder in the FTP root so that end users can have read access to that folder. Change the security on the subfolders (i.e. School or office) so that only admins and the specific end user accounts have access.
Problem: Opening text files that don't end in .txt or .csv
Now that the end user can browse to the files, then need a program to open the "record.20141024xxx" files. Since the extension is the date of push, it will not open automatically and the extension will always change.
Solution: - Notepad++ and Scheduled Task to the rescue.
Notepad++ will open the "record.20141024xxx" files but if the end user doesn't have Notepad++ or just wants to open the txt file with another program here's a batch file that renames them to "record.20141024xxx.txt"
REM Location Cleanup cd C:\FTP root\Reports\Location
REM copy all date files into one txt file
copy /y record.20* records.*.txt
REM delete the original date file
del record.* /q
Create scheduled task on FTP server to convert the date files to TXT files. Runs 1/2 hour after BCM Push schedule.
For the end users with notepad++
Create a new shortcut for Notepad++ then change the properties of that new shortcut.
Add the share path to the end of the existing the target path.
i.e. "C:\Program Files (x86)\Notepad++\notepad++.exe" "\\server name\Call History Reports\School\"
This will start Notepad++ and open any file that is in that folder.
Staff now press "Ctrl+F" and type in "Digits Dialed" and click "Find All in All opened Documents"
To see more information about that call...
The end user double clicks on the phone number in the "Find result" window.
Notepad++ will jump to that line in that file and show you the Line # and the STN (aka extension number)
Problem: Too many log files can cause Notepad++ to start "Not Responding" especially when using remote network locations.
Solution: Create a scheduled task that runs batch files to merge and overwrite files on the FTP server. (Or monthly depending on your record keeping needs)
Sample Cleanup batch file
- Run every Sunday night
- overwrites the existing weekly.txt file
cd C:\FTP root\Reports\Location
REM merges previous records into a one txt file
copy /y records.20*.txt Weekly.txt
REM delete previous txt files
del records.*.txt /q
Over the years, people or students have accidentally dialed 911 and in some cases the police are dispatched.
Then we (IT department) get the call wanting to know who called 911 or do we log outgoing calls.
Without video surveillance pointed at every phone, it's hard to say who was the one dialing, but the call history on the CME GUI could at least report which extension.
Changed the default logging in the CME configuration to...
To reduce my work load and give the locations a quicker response to the "Who called 911?" question,
I began looking for a way to allow the locations to access the CME web GUI but not have the ability to may any changes to the system.
After following the GUI install from this website and hiding everything in the XML template...
telephony-service
web admin customer name Report password Password
web customize load flash:callreport.xml
The customer account still had the ability to may changes to the configuration.
After searching the internet for how to edit the ccme.html file and finding that the file is not really a file... the next stop was the .js files in the GUI folder.
Knowing nothing about JavaScript, I opened the admin_user.js file in Notepad++ and started looking for some keywords.
Found the Extensions, phones, users and system parameters and was about to cut out the code lines when I noticed the "Block comment" option when I right clicked on the selection.
So I started commenting out line by line and eventually came up with these changes and now any user (even the admin account) that logs into the CME web interface will only be able to access the Call history. - Let face it, when was the last time you configured the CME via Cisco's GUI.
Copied the new admin_user.js file to the tftp server and then downloaded it to the CME.
Changes to the admin_user.js file starting at about line 72 in the version installed on the cme. (Copied the original to admin_userbk.js - Just in case)
Tip - Comment each line as you go and then reload to make sure it is working. - In Notepad++ it's just a right click and "Block Comment" on each line or select more than one line.
/* out += "\"Extensions\", \"javascript:if(!parent.frames[0].checkPageDirty()){parent.frames[0].SetPageCookie(\'page\', \'displayDN()\', true);parent.frames[0].displayDN();}\", 0\n"; */ /* out += ",\"Phones\", \"javascript:if(!parent.frames[0].checkPageDirty()){parent.frames[0].SetPageCookie(\'page\', \'displayEphone()\', true);parent.frames[0].displayEphone();}\", 0\n"; */ // out += ",\"Users\", \"javascript:parent.frames[0].displayUsers();\", 0\n"; /* out += ",\"System Parameters\", \"javascript:if(!parent.frames[0].checkPageDirty()){parent.frames[0].SetPageCookie(\'page\', \'startKeySwitchMenu()\', true);parent.frames[0].startKeySwitchMenu();}\", 0\n"; */ out += ")\n"; out += "mn2 = new Array\n"; out += "(\n"; /* out += "\"Save Router Config\", \"javascript:if(!parent.frames[0].checkPageDirty())parent.frames[0].writeBack();\", 0\n"; */ /* out += ",\"Update System Info\", \"javascript:if(!parent.frames[0].checkPageDirty())parent.frames[0].updateFunc();\", 0\n"; */ /* out += ",\"Create CNF Files\", \"javascript:if(!parent.frames[0].checkPageDirty())parent.frames[0].updateCNF();\", 0\n"; */ out += ")\n"; out += "mn3 = new Array\n"; out += "(\n"; /* if (showControl[SSysMwiSer] != false){ out += "\"Message Waiting Server Setting\", \"javascript:if(!parent.frames[0].checkPageDirty()){parent.frames[0].SetPageCookie(\'page\', \'displayMWI()\', true);parent.frames[0].displayMWI();}\", 0\n"; } */ /* if (!((showAttr[SSysVM] == "Both") && (showControl[SSysVM] == false))){ if (showControl[SSysMwiSer] != false){ out += ","; } out += "\"Pilot Number\", \"javascript:if(!parent.frames[0].checkPageDirty()){parent.frames[0].SetPageCookie(\'page\', \'setVoiceMailNumber(2)\', true);parent.frames[0].setVoiceMailNumber(2);}\", 0\n"; } */ out += ")\n"; out += "mn4 = new Array\n"; out += "(\n"; out += "\"Call History\", \"javascript:if(!parent.frames[0].checkPageDirty()){parent.frames[0].SetPageCookie(\'page\', \'displayCallHistory()\', true);parent.frames[0].displayCallHistory();}\", 0\n"; out += ")\n"; out += "mn5 = new Array\n"; out += "(\n"; /* out += "\"About\", \"javascript:parent.frames[0].showVersion();\", 0\n"; */ /* out += ",\"Configuration\", \"javascript:parent.frames[0].showHelp('help_extension()');\", 0\n"; */
When our first Cisco CME system was installed, we were told that there wasn't a way to report nuisance calls or block outgoing caller id because the incoming phone lines were programmed into trunk groups.
About 4 years and 16 CME systems later, the IT Department is now deploying the CME systems and we are still asked if this is possible. Mostly to report nuisance calls, the odd time to block outgoing caller id.
Today I have found a solution to this question for standard phone lines. This will not work on DID calls as they are only incoming.
In our previous CME configuration, the incoming lines were all forwarded to one DN and appeared as one DN on the main admin phone. This confused some staff as they were used to having 3 or more line buttons on the Nortel, Norstar or Meridian phones.
In smaller locations, with only 2 or 3 phone lines, we could go with the individual DNs showing up on the phone as individual DNs and then forward to one voice mailbox. However, some years the Admin assistants are moved around from location to another location so we want to keep things as consistent as possible in our 30+ locations.
In the new configuration...
The incoming calls will forward to their own separate DN (5xx) via the connection plar command in the voice port configuration.
The 5xx DN will then forward onto the main DN (5400).
Example: A call comes in on Line 1 (FXO 0/0/0), it will show up as a forwarded call from the 501 DN.
Now let's say this was a prank call and they want to report it to our telephone provider.
In the old configuration, it would pick the first available phone line out, which would be Line 4...3...2...1 in the example below. Very often the outgoing call would not pick the same line that the call came in on, so that increase the chances of not working or a false report being filed.
In the new configuration...
The person sees that the call came in on L01 5551212 (501) aka Line 1
Now to report the call to the provider, they dial 9501*57 and the call goes out on Line 1 (FXO port 0/0/0) and *57 is dialed. (Based on dial-peer voice 500 pots)
If the call came in on L03 5551214 (503) aka Line 3, they would dial 9503*57 and the call would be handled by dial-peer 502
The new 5xx dial peers also allows for calling out on the specific line to do troubleshooting with service providers.
Here's the new configuration.
voice-port 0/0/0
trunk-group pstn-outgoing 4
connection plar 501
description FXO Out 5551212 via 501
voice-port 0/0/1
trunk-group pstn-outgoing 3
connection plar 502
description FXO Out 5551213 via 502
voice-port 0/0/2
trunk-group pstn-outgoing 2
connection plar 503
description FXO Out 5551214 via 503
voice-port 0/0/3
trunk-group pstn-outgoing 1
connection plar 504
description FXO Out 5551215 via 504
dial-peer voice 500 pots
description ** Line 1 5551212 **
destination-pattern 9501.T
port 0/0/0
dial-peer voice 501 pots
description ** Line 2 5551213 **
destination-pattern 9502.T
port 0/0/1
dial-peer voice 502 pots
description ** Line 3 5551214 **
destination-pattern 9503.T
port 0/0/2
dial-peer voice 503 pots
description ** Line 4 5551215 **
destination-pattern 9504.T
port 0/0/3
ephone-dn 296
number 501
description Line 1 5551212
name L01 5551212
call-forward all 5400
ephone-dn 297
number 502
description Line 2 5551213
name L01 5551213
call-forward all 5400
ephone-dn 298
number 503
description Line 3 5551214
name L03 5551214
call-forward all 5400
ephone-dn 299
number 504
description Line 4 5551215
name L04 5551215
call-forward all 5400
ephone-dn 300 octo-line
number 5400
pickup-group 1
label 5400
description IT South
name IT South Office
allow watch
call-forward noan 85400 timeout 16
corlist incoming call-International
night-service bell
Needed to recover data off of a laptop and moving the files just wasn't working...
Decided to try Microsoft's SyncToy. We use it on some of our laptops to backup data from the laptop user's documents folder to a server which has it's own backup.
Created folder pairs for syncing between the failed harddrive and new folder on my desktop.
Since the harddrive was failing (faint click sound), paging errors and the odd bad block error showed up in the event log and SyncToy would stall, but not stop responding. (Unlike Windows explorer)
To get it to start copying again, simply unplugged the USB cable from my desktop and plug it in again.
Now most copy jobs would stop completely when you do this, but not SyncToy. It moved on to the next file and try to copy that one.
Granted there would be some files that would be missed based on how long Windows took to re connect the drive however, that is better than no files at all or manually copying over file by file and trying to find out which one was failing.
Once that was done, reran the Windows Chkdsk program on the drive and then ran the SyncToy folder pairs again to recover more files.
Since SyncToy catalogs and compares file changes, this time the Sync took less time. The harddrive still had that faint click of death and still required unplugging and plugging the USB cable. When SyncToy stalled on a bad file, wrote down the file name(s) and then went back into the Folder pair settings and excluded the file(s). This helped recover as much as 90% of the folders contents in some cases.
