Sorry, I forgot that we need something to initiate the connection. Can you leave that running and then start ekos. You can create a new profile and select the "Remote" setting in the "Mode" section. Leave everything else as the default and save it. Then click the start button (play symbol) under "2. Start & Stop Ekos". Then I'm hopeful that you'll see some output in the terminal where you are running the indiserver command.
The problem is that the name of the CCD that's reported by the DSI is wrong! It says "IXC245AL"...the actual name is "ICX254AL". Unfortunately, the indi driver uses this name to determine what type of DSI it is (even though there's another field that we can read from the camera that describes what type of DSI it is!).
I'm not sure how your camera got to be this way, but I can make a change to the driver to check the both the CCD name and the device name (yours correctly identifies as a "DSI Pro"). It's a simple change and won't take too long.
git clone github.com/bgilsrud/indi-3rdparty.git
git checkout dsi_model_name_fix
mkdir -p build/indi-dsi
cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=Debug ../../indi-dsi/
sudo make install
Then you could try to figure up ekos as you normally do (remember to select your normal profile!) and I'm hoping that it works. If you're able to verify this, then I'll submit the code change upstream.
bruce@bruce-HP-ProBook-6460b:~$ git clone github.com/bgilsrud/indi-3rdparty.git
fatal: repository 'github.com/bgilsrud/indi-3rdparty.git' does not exist
bruce@bruce-HP-ProBook-6460b:~$ cd indi-3rdparty
bash: cd: indi-3rdparty: No such file or directory
The field programmed into your camera's EEPROM is wrong. I've made a change to check the CCD model or the camera model. Checking the camera model seems like the more obvious, direct way to identify the camera...but it's more difficult to guess what it should be since I don't have access to every DSI I, II, III in both mono (Pro) and color. The CCD names for these are less mysterious.