Cookies CSS

Friday, August 28, 2015

Setting up IP Phones in AD

You can mass update the IP Phone fields your Active Directory in a couple of easy steps.

Generically, here is what you will need to do.  There are several tools on the internet to assist.  We will attach a couple scripts as well.  Proceed carefully as all the normal AD warning apply.
  1. Export your AD account names to a CSV file with Powershell.
  2. Open in Excel and add a column for the ipPhone field it its missing.
  3. Remove any row entries that do not apply. aka Service accounts etc.
  4. Enter the appropriate DN for each name
  5. Delete any unnecessary columns such as the DisplayName Column.
  6. Delete the header line with column names in it.
  7. Save as a CSV.  example: c:\temp\ADUsersImport.csv
  8. Import the CSV to AD with Powershell.

SAMPLE Export Script (zero risk to anything.)
Change the highlighted text to your choice of export file name.

Get-ADUser -Filter {(Name -notlike "*(Administrator)")}  -Properties SamAccountName,DisplayName,ipPhone| Select-Object SamAccountName,DisplayName,ipPhone | export-csv -path c:\temp\ADUsersExported.csv -NoTypeInformation -Encoding "UTF8"


The exported file will look like this....
C:\TEMP\ADUsersExported.CSV








SAMPLE Excel Spreadsheet












SAMPLE CSV for Import
C:\TEMP\ADUsersImport.CSV








SAMPLE Import Script (Medium risk, make certain your data is clean)

Create a file with the following script named c:\temp\ipphoner.ps1

Import-Module ActiveDirectory 
$CSVPath = "c:\temp\ADUsersImport.csv"
$csvData = Import-CSV $CSVPath -delimiter "," -Header ("sAMAccountName","IPPhone")
foreach ($line in $csvData ) 
{
$accountTable = @{ 
'sAMAccountName'= $line.sAMAccountName 
'IPPhone'= $line.ipPhone 
}
}
ForEach($line in $csvData) 
{ 
$sAMAccountName = $line.sAMAccountName 
$ipphone = $line.ipPhone 
$Blank = ""
if([string]::isNullOrEmpty($sAMAccountName.description))
{ "modifying $($sAMAccountName) and adding $ipphone number " 
$SETIPPHONE = GET-ADUSER $sAMAccountName -PROPERTIES ipphone
$SETIPPHONE.ipphone = $ipphone
Set-ADUser $sAMAccountName -Replace @{ipPhone=$ipphone} }
}


From the Windows Powershell prompt in a C:\Temp run the script.
.\ipphoner.ps1
This should update the iphhone field of all of the users in the CSV.


Thursday, August 27, 2015

Error on (Full) when performing AXL Names Updates

You you receive errors similar to this when doing Names updates















You have enabled the Multi-tenant function.  This is only allowed in conjunction with a multi-tenant CallManager with Active Directory configured.


Troubleshooting Names Updating - AXL

Troubleshooting Names Updating - Active Directory

When you are having trouble with a missing or incorrect username on a DN and are configured for AXL, either Full or Names Only, here are some troubleshooting steps.

AXL information is automatically updated each night at midnight.  If the change was recent, you may get results by running Update AXL Now in Phone System Settings tool -> Device Names

  • Verify that the DN does appear.  In the Console, search for it by number.
  • If it is missing, 
    • Verify that it has not been Excluded from View using the Manage Exclusions menu option.
    • Ensure that the phone that it is configured for, has been added to the Controlled Devices group on CallManager for the BOC-Admin user.
  • If the DN appears but has the wrong name, follow these steps.
    • In BOC Phone System Settings, choose CUCM Settings.
      • Verify that the account information entered for AXL is correct and Test with your DN in the upper box in the middle section.
    • Go to Device Names settings
      • Enter the Extension in the Test box on the lower right quadrant.
        Press Test AXL Lookup.   Check the Windows Application Event log if a response is not displayed.
  • If you get a response and the name is incorrect, you have to correct it in End Users in CallManager.
  • If the response comes back correctly, run the following.
    • Update AXL Now

Troubleshooting Names Updating - Active Directory

When you are having trouble with a missing or incorrect username on a DN and are configured for Active Directory, here are some troubleshooting steps.


  • AD is automatically updated each night at midnight.  If the change was recent, you can get results by running Full LDAP Build followed by Update Names.
  • Verify that the DN does appear.  In the Console, search for it by number.
  • If it is missing, 
    • Verify that it has not been Excluded from View using the Manage Exclusions menu option.
    • Ensure that the phone that it is configured for, has been added to the Controlled Devices group on CallManager for the BOC-Admin user.
  • If the DN appears but has the wrong name, follow these steps.
    • In BOC Phone System Settings, choose Device Names Settings.
    • Verify that the account information entered for AD is correct and not locked out.
    • Enter the Extension in the Test box on the lower right quadrant.  Press Test LDAP Lookup.   Check the Windows Application Event log if a response is not displayed.
    • If you get a response and the name is incorrect, you have to correct it in Active Directory.
    • If the response comes back correctly, run the following.
      • Full LDAP Build
      • Update Names

Wednesday, August 19, 2015

Preparing off box SQL

Create a database using SQL defaults.  Database name MUST be named BOC.
Set the recovery model to SIMPLE.
Create a SQL user and give it DBO rights over that database BOC.
It must be an actual SQL user and not an AD account.
A suggested name is BOC-ADMIN to stay in line with other settings.

When you install the application and give it the connection details, the application will build the rest of the database automatically.

We do not recommend replication on it since the data turns over so quickly which can severely impact both log file and WAN links.

Thursday, August 13, 2015

Off Box SQL installation

We can utilize a SQL Server that is not co-located on the same server as the BOC TAPI2 Connector.
The basic database will need to be created manually prior to the install.
Here are the build out requirements.

  • Create a SQL User.  Normally we recommend the username, BOC-Admin
    We cannot use a Windows account.
  • Create a database using the default seeings named BOC (this name is required) 
    • Collation: SQL_Latin1_General_CP1_CI_AS
    • Recovery Model: Simple
    • Do NOT replicate this database to other servers.
  • Set the new user BOC-Admin to be dbo on the database BOC


Monday, August 3, 2015

Firewall ports for Bridge Operator Console TAPI2 and LICC


We use CTI, AXL, HTTP and HTTPS plus two of our own proprietary ports.

SERVER
Between the BOC TAPI2 Server and CUCM, we will need the following
  • TCP/2748             Cisco TSP
  • TCP/2749             Cisco TSP
  • TCP/8080             AXL
  • TCP/8443             AXL
  • TCP/443               HTTPS
  • TCP/80                 HTTP


If configured for LICC, between the BOC TAPI2 Server and Lync, we will need the following
  • TCP/18675             (can be changed)
  • TCP/18676             (can be changed)
  • TCP/15001             (can be changed)
  • TCP/443                 HTTPS
  • TCP/80                   HTTP


CLIENT

Between the BOC Client and BOC TAPI2 Server, we will need the following
  • TCP/18675             (can be changed)
  • TCP/1433               Microsoft SQL (can also be dynamic)
  • TCP/443                 HTTPS
  • TCP/80                   HTTP

Between the BOC Client and CUCM, if utilizing Hybrid mode, we will need the following
  • TCP/2748             Cisco TSP
  • TCP/2749             Cisco TSP

Thursday, July 9, 2015

Repairing the Cisco TSP installation

Often times, when the Cisco TSP attempts to auto-upgrade, the TSP is left in a non-working state.
Here are a couple common scenarios and methods to repair.
Not all attempts will be successful and may still require a complete uninstall and reinstall.

1. The Cisco TSP Configuration tool is blank.















To correct this, go into Windows Control Panel -> Phone and Modem








Choose the Advanced tab and click Add and choose CiscoTSP001.tsp.
Only add it once or you will duplicate everything.


































When it has been added, close all of the dialog boxes.
You should now see an entry in the Cisco TSP Configuration.


2.  Verify that the TSP has not been switched to Single Sign On.





















If it has been switched, normally, you can just choose the lower radio button and all of your old configuration will be there.  Test it before re-keying any usernames or passwords.






















NOTE: After any changes to the TSP, you will need to either reboot, or restart the Telephony service.








You can use Microsoft Dialer to verify simple connectivity,  if there are Cisco devices listed, you have a basic connection.
It is not a guarantee of function.





















If you are getting an error on the reinstall of the TSP, here are steps to resolve it.

Error: CopyFile CiscoTSP.tsp failed

Problem

CopyFile CiscoTSP.tsp failed

Solution

Complete these steps in order to clean up the TSP registry keys and resolve this issue:
  1. In the Registry Editor, navigate to HKEY_LOCAL_MACHINE > SOFTWARE > Cisco Systems, Inc., and delete the CiscoTSP registry key and all subkeys.
  2. Delete all CiscoTSP*.tsp and CiscoTUISP*.dll files from the winnt\system32 directory. You might need to reboot the system so that the system will allow you to remove these files.
  3. In the Registry Editor, navigate to HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > Windows > CurrentVersion > Uninstall, and delete the {AF198881-AF5B-11D4-9DA2-000039ED6324} and CiscoTSP subkeys.
    Note: Do not delete the entire Uninstall key; delete only the {AF198881-AF5B-11D4-9DA2-000039ED6324} and CiscoTSP keys.

Wednesday, June 3, 2015

Clearing an invalid configuration

In the event that you have an invalid configuration which prevents you from launching the application, you will need to clear this configuration before you can get into settings.
This can result in an Invalid License String error as the client is unable to access the BOC Server to validate its license.

Uninstalling and reinstalling the application will not clear this configuration.
We have a tool you can use to clear the configuration.
You may download it from here.

BOC Cleanup Tool

We recommend exporting the settings from a working console and saving for the configuration of new workstations.

Wednesday, March 25, 2015

Direct Transfer to Voicemail is not working



What happens when you try the direct transfer to VM?
Does it go to the wrong place, or nothing happens at all?

What is your direct transfer to VM dial pattern directly from a phone?

The default direct transfer to Voicemail sequence is *+extension.

So for extension 5501, you would be able to direct transfer to voicemail on the phone by pressing the Transfer Button and then *5501 and then transfer again.

Verify in the BOC client settings that you have the proper Voicemail Prepend set.  
The default is *



Monday, March 23, 2015

Faster BLOC Response group reports

The Lync/Skype4b lcsCDR database is missing some indexes by default that can speed up the reports included with it.  To add those indexes you should run the following.

CREATE NONCLUSTERED INDEX [IX_CdrRGSUsage_MissingIX] ON [dbo].[SessionDetails]
(
 [ReplacesDialogIdTime] ASC,
 [ReplacesDialogIdSeq] ASC,
 [MediaTypes] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]

CREATE NONCLUSTERED INDEX [IX_CdrRGSUsage_MissingIX2] ON [dbo].[SessionDetails]
(
 [CorrelationId] ASC,
 [MediaTypes] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
GO

Monday, March 16, 2015

Configuring Hybrid Mode

In Sockets mode, all communications are passed thru our TAPI2 Connector.
Sockets mode is indicated by the red socket in the lower left corner.
In Sockets mode, there is no Phone/Line count, so zeros here are normal.

Sockets Mode







In Hybrid mode, tasks that can be made faster using our server, go thru the Connector.
Realtime tasks can go directly to the CallManager.

Hybrid mode is indicated by the green leaf in the lower left corner.

Hybrid Mode







To achieve Hybrid mode, you need the Cisco TSP installed.
This should be done logged in as a user with local admin rights.
We have seen inconsistent results trying to use the Windows RunAs procedure rather than a full admin login.
We recommend using the full login route.
You can do this manually using the normal Cisco TSP installation procedure.
This is documented in the BOC TAPI2 Connector install document.
The username will be the one you created for the TAPI2 Connector.
Typically this is BOC-Admin.

However, an much easier way is to use our 1Click TSP Installer.
This is located under the Help Menu in the BOC Console application.
It automates the Cisco TSP installation process.
There is no need for the person doing the installation to have access to the passwords.
The 1Click pulls the username and password from the BOC TAPI2 Connector.
*The TAPI2 server must be up and functional.
We still recommend that this be run as a user with local admin rights.

The 1Click TSP Installer cannot fix a broken non-functional TSP install.
If you already have the TSP installed and it is not working, we recommend uninstalling it before attempting a 1Click install.

Microsoft Dialer is a great test tool to see if the TSP is functioning.
When you run Dialer, pull down the Connect Using menu.
You should see your Cisco extensions listed in there.
If you do not see Cisco devices, the TSP is not installed/configured correctly.

If you are having difficulty with the Cisco TSP and want to force the console into Sockets mode, you can set the value of the following registry key to 1.  The value of 0 is the default for automatic detection of the Cisco TSP.  This is a per user setting.

HKEY_CURRENT_USER\Software\Bridge Communications\Bridge Operator Console 3\ForceSocketMode