# Bell Server

### Overview

This document outlines the setup and management of the BellCommander service on the VM-BellServer-25. The documentation includes information about user accounts, scheduled tasks, scripts used for service management, data file locations, and system details.

<p class="callout danger"><span style="color: rgb(186, 55, 42);"><span style="text-decoration: underline;">**Make sure to close the bell commander software when finished.** </span>  
It has a memory leak and it will cause issues if left open when not needed. The bell service runs in the background whether the bell commander window is open or not.</span></p>

## <span style="color: rgb(186, 55, 42);">If the Bells are not working:</span>

#### Restart Bell Service ( **Try This First** )

1. There is an icon on the desktop called **Restart Bell Service** double click it to run it  
      
    [![image.png](https://bookstack.archfox.org/uploads/images/gallery/2025-11/scaled-1680-/UZr18Bt6bATlhLLh-image.png)](https://bookstack.archfox.org/uploads/images/gallery/2025-11/UZr18Bt6bATlhLLh-image.png)
2. Click **Yes** when it asks to run as admin
3. The service should now be restarted. If the bells continue to not work **Restart the Computer.**

<p class="callout warning">If the bells service does not restart or fix itself run the Hard Kill Script which will hard kill the bell service and restart it</p>

#### **Further Troubleshooting:**

Further Trouble shooting is at the End of this Document   
[Further Troubleshooting Link](https://bookstack.archfox.org/books/rpsd/page/bell-server#bkmrk-troubleshooting "Further Troubleshooting Link")

---

## System Details

<div class="document-content-inner" id="bkmrk-type%3A-rockport-datac"><div><div class="section-container-wrapper"><div class="section-container editor-container" data-section-id="32631650" draggable="false"><div draggable="false"><div class="content"><div class="text-section-body"><div class="react-rich-text-editor"><div class="alloy cke_editable read-only">- **Server Type:** Rockport Datacenter VM on the RPSD VM Host
- **Name**: `VM-BellServer-25`
- **Static IP Address:** `10.4.0.49`
- **Remote Access:** Accessible by RDP or Ncentral
- **OS:** Windows Server 2025

</div></div></div></div></div></div></div></div></div>#### Account Information

This is a domain account used to log in to the Bell-Computer where the BellCommander service is hosted.

<div class="document-content-inner" id="bkmrk-domain-account-usern"><div><div class="section-container-wrapper"><div class="section-container editor-container" data-section-id="32631650" draggable="false"><div draggable="false"><div class="content"><div class="text-section-body"><div class="react-rich-text-editor"><div class="alloy cke_editable read-only">- **Domain Account Username:**  
    `belluser`
- **Password:** In IT glue under Domain Accounts

</div></div></div></div></div></div></div></div></div>- **Group Membership:** The `belluser` account is a part of the local admin group.

#### Service Management

BellCommanderApplicationService is an important service that must be running in order for the software to communicate with the VOIP extension.

The Executable is located at `C:\Program Files (x86)\BellCommander\bcappservice.exe`

A task has been set up to ensure that the BellCommanderApplicationService remains operational by restarting it daily.

<div class="document-content-inner" id="bkmrk-task-schedule%3A-time%3A"><div><div class="section-container-wrapper"><div class="section-container editor-container" data-section-id="32631650" draggable="false"><div draggable="false"><div class="content"><div class="text-section-body"><div class="react-rich-text-editor"><div class="alloy cke_editable read-only">- **Task Schedule:**
    - *Time:* Daily at 7:00 AM
    - *Script Location:* `C:\Users\belluser\Scripts\`
    - *Functionality:* This script is responsible for restarting the BellCommanderApplicationService.

</div></div></div></div></div></div></div></div></div>Use this Command to Register the service in a admin powershell:

```
New-Service -Name "BellCommanderApplicationService" -BinaryPathName "C:\Program Files\BellCommander\bcappservice.exe" -DisplayName "Bell Commander Service" -Description "Bell Commander Service" -StartupType Automatic
```

#### Data File Locations

**Directory:**

<div class="document-content-inner" id="bkmrk-path%3A-c%3A%5Cprogram-fil"><div><div class="section-container-wrapper"><div class="section-container editor-container" data-section-id="32631650" draggable="false"><div draggable="false"><div class="content"><div class="text-section-body"><div class="react-rich-text-editor"><div class="alloy cke_editable read-only">- *Path:* `C:\Program Files (x86)\BellCommander`
- *Contents:* Houses all data files related to the BellCommander service. These files are critical for the operation of the BellComander application that contains data files like songs, sounds, and bell schedule databases.

</div></div></div></div></div></div><div class="section-container editor-container" data-section-id="32631650" draggable="false">  
</div></div></div></div>---

## Troubleshooting

#### Verify the Service is Running:

1. Open the BellCommander Application  
      
    [![image.png](https://bookstack.archfox.org/uploads/images/gallery/2025-11/scaled-1680-/xXNKppbmVGt32sLf-image.png)](https://bookstack.archfox.org/uploads/images/gallery/2025-11/xXNKppbmVGt32sLf-image.png)
2. Check that the Application is Connected the Service. If this **Does not say Connected** it means the service is **Not Running** and the Bells will **Not Work**. Run the script above to **Restart the Bell Service**.  
    <div drawio-diagram="158"><img src="https://bookstack.archfox.org/uploads/images/drawio/2025-11/Eoh7hvvDXvN3Ckd4-drawing-1-1763068546.png" alt=""/></div>
3. If after Running the script, it still does not connect, then **Restart the Computer**

#### Invalid path:

Sometimes the bells have an invalid music file path in the **Day Scheduler**. When the bell tries to ring it that invalid path it will hang the service and not send any further bells. The bell service will not be able to be restarted if this occurs and will just give a message of "Service already Restarting" when trying to run the restart script.

Fix this by finding the faulty entry and correcting it to a valid song file.

---

#### Send a Test Bell:

1. Click Devices  
      
    [![image.png](https://bookstack.archfox.org/uploads/images/gallery/2025-11/scaled-1680-/eFro0cSp8BRfdaOJ-image.png)](https://bookstack.archfox.org/uploads/images/gallery/2025-11/eFro0cSp8BRfdaOJ-image.png)
2. Select from the Dropdown **Sip Destinations** [![image.png](https://bookstack.archfox.org/uploads/images/gallery/2025-11/scaled-1680-/0CJs8TcqscgSXe99-image.png)](https://bookstack.archfox.org/uploads/images/gallery/2025-11/0CJs8TcqscgSXe99-image.png)
3. Click a SIP Extension group to ring  
      
    [![image.png](https://bookstack.archfox.org/uploads/images/gallery/2025-11/scaled-1680-/nuA3FD71SvGpsLJe-image.png)](https://bookstack.archfox.org/uploads/images/gallery/2025-11/nuA3FD71SvGpsLJe-image.png)
4. Click Browse to pick the sound file to send to the bells  
      
    [![image.png](https://bookstack.archfox.org/uploads/images/gallery/2025-11/scaled-1680-/4rMaRAJ7K2EG3U4N-image.png)](https://bookstack.archfox.org/uploads/images/gallery/2025-11/4rMaRAJ7K2EG3U4N-image.png)
5. Choose the test.wav file at:  
    `C:\Program Files (x86)\BellCommander\sounds\test.wav`  
      
    [![image.png](https://bookstack.archfox.org/uploads/images/gallery/2025-11/scaled-1680-/5j61rEld2jXbeYuz-image.png)](https://bookstack.archfox.org/uploads/images/gallery/2025-11/5j61rEld2jXbeYuz-image.png)
6. Click **Send Test** to test the bells  
      
    [![image.png](https://bookstack.archfox.org/uploads/images/gallery/2025-11/scaled-1680-/WQT6ZWTGqzG2rECr-image.png)](https://bookstack.archfox.org/uploads/images/gallery/2025-11/WQT6ZWTGqzG2rECr-image.png)