Tag Archives: swyx

Swyx D-Channel Monitor Logfile Location

Hunting down the mystery missing log file in the Swyx D-Channel Monitor.

I had some issues trying to find the log file that the Swyx D-Channel Monitor (v8.00) creates when running on Windows Server 2003.

According to the Swyx KB Article, it can be found in the same place as the executable i.e.¬†C:\Program Files\Swyx ISDN Tools, in the ‘Log’ folder. In my instance, it was not. Using the incredibly useful Procmon, I found that the file was actually created in the following path:

C:\Documents and Settings\All Users\Application Data\Swyx\Traces\

Swyx D-Channel Monitor
Swyx D-Channel Monitor

The filename of the file itself can be found at the bottom of the Swyx D-Channel Monitor window.

I originally wanted to create an executable to scan this file so that I could get alerts if a L1 deactivated message appears, however it would appear than the Swyx D-Channel Monitor locks the file for reading. I suppose I could handle startup & shutdown of the app using Process.Start (.NET) but that’s a bit more effort than I wanted to go to.




Swyx: IpPbx PowerShell – Creating new phonebook entry

The following script will create a new phonebook entry in Swyx. You’ll need the IpPbx PowerShell modules installed first. Oh, and be sure to replace [servername] with, well, the name of your server.

Import-Module IpPbx
Connect-IpPbx [servername]
New-IpPbxPhonebookEntry -Name "NAMEHERE" -Number "NUMBERHEREWITHPAPREFIX" -Description "POWERSHELL IMPORT" | Add-IpPbxPhonebookEntry

Swyx PowerShell: IpPbx Modules – Installation

Swyx PowerShell

Before you can use the IpPbx cmdlets in PowerShell, you need to install the modules first. Grab the IpPbx modules from here, be sure to get the correct version:


Don’t forget to run the following command first:

Set-ExecutionPolicy unrestricted


[quads id=1]

As our ‘My Documents’ folder live on the domain server, we had some issues. The install appeared to go ok, as you can see:

1. Install for Current User only
2. Install for All Users
3. Remove every module version
Select 1-3: 1
Searching for other Module Versions...
Installing for Current User...
Process completed!
Press any key to continue ...

Do not do the above! Because you then get this:

PS C:\Users\xxx\Desktop\IpPbxPowerShellModule_v8.1.0.50 (1)> Import-Module IpPbx
 Add-Type : Could not load file or assembly 'IpPbxBLOB64, Version=, Culture=neutral, PublicKeyToken=null' or one
 of its dependencies. Failed to grant minimum permission requests. (Exception from HRESULT: 0x80131417)
 At \\xxx\Users\xxx\WindowsPowerShell\Modules\IpPbx\IpPbx.psm1:106 char:13
 + add-type <<<< -Path (join-path $ScriptFolder "Binaries\IpPbxBlob64.dll") | out-null 
 + CategoryInfo : NotSpecified: (:) [Add-Type], FileLoadException
 + FullyQualifiedErrorId : System.IO.FileLoadException,Microsoft.PowerShell.Commands.AddTypeCommand

This is because it installed the modules in the folder on the server, and network paths are not trusted.

Instead, install for all users – option 2 (you need to run the PowerShell command prompt as Administrator).

To check the install, run the following command:

get-module -ListAvailable

The result list must contains the following entries:

Script Accelerators
 Manifest IpPbx

If it does, then all should be well.

For more information on Swyx telephony & the Swyx Powershell modules, please check out the following link:



Check out my other posts regarding Swyx here: