December 7, 2011 – 6:58 pm | 16 Comments

3CX is pleased to announce a new release of 3CX Phone System 10, build 22686. Service Pack 5 fixes numerous 3CX Wallboard issues and also adds a new and important caller ID feature. To download …

Read the full story »
Releases

3CX Product Releases

VoIP How To

Technical tips to run your VoIP PBX more efficiently

Events

3CX Trainings and Webinars around the world

Docs & FAQ

3CX Documentation how to and FAQ

Phone configuration

3CX, Aastra, Cisco, Yealink, Grandstream, Polycom configs

Home » Docs & FAQ

Troubleshooting Cassini Web server Issues

Submitted by on November 9, 2009 – 4:18 pmNo Comment

When using 3CX with Cassini, you may encounter situations where the Web Interface or the Web Service stops running and you have to restart the 3CX services to get it running again, or where the 3CX Webserver service fails to start. To be able to resolve this issue you need to do the following

  • Go to Start / Run and type %allusersprofile%
  • Locate a folder named Ultidev, double click on this folder and open the folder named Cassini.
  • Inside the Cassini folder you will see an xml file named CassiniMetabase.xml.  Delete this file
  • Download the attached file below and place it in this location.
Note: The physical path tag must be changed to the path that matches the location of the Http folder on your 3CX PBX Machine.
The below extract gives an example of a PBX installed in the default location on a Vista / Server 2008 / Windows 7 operating systems. For Windows XP and Server 2003 machines, the Physical Path tag needs to be modified accordingly.
Example (contents of the attached CassiniMetabase.xml)
<?xml version=”1.0″ encoding=”utf-8″?>
<CassiningMetabase xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” xmlns:xsd=”http://www.w3.org/2001/XMLSchema”>
<Application FrameworkVersion=”2.0″ KeepRunning=”true”>
<PhysicalPath>C:\ProgramData\3CX\Data\Http\Interface\myPhone</PhysicalPath>
<Port>5000</Port>
<Name />
<Description />
<DefaultDocument>index.aspx</DefaultDocument>
<ApplicationID>7abee8ec-5ffa-23f4-b881-6441d5b7c1e9</ApplicationID>
</Application>
<Application FrameworkVersion=”2.0″ KeepRunning=”true”>
<PhysicalPath>C:\ProgramData\3CX\Data\Http\Interface</PhysicalPath>
<Port>5481</Port>
<Name />
<Description />
<DefaultDocument>index.aspx</DefaultDocument>
<ApplicationID>7abee8ec-5ffa-45f4-b881-6441d5b7c1e9</ApplicationID>
</Application>
<Application FrameworkVersion=”2.0″ KeepRunning=”true”>
<PhysicalPath>C:\ProgramData\3CX\Data\Http\Interface\ivr</PhysicalPath>
<Port>5484</Port>
<Name />
<Description />
<DefaultDocument>ivr_start.aspx</DefaultDocument>
<ApplicationID>7abee8ec-6cca-45f4-b881-6441d5b7c1e9</ApplicationID>
</Application>
</CassiningMetabase>
  • Go to Services.msc and start the Ultidev Cassini Web server.
  • Confirm that the service is started and that it remains started. (Press F5 to confirm that it remains started. If after 1 minute it is still started, then the issue is fixed)
  • Also check event viewer / application for any events posted by Cassini.
This concludes one of the most common issues regarding Cassini service that fails to work properly
You can download a sample Cassini Metabase file from here.  This shows an example of how the cassini metabase xml is structured.

Comments are closed.