SVCMAN MonTel Server Console Output.

For a MonTel Server to be able to send information to SVCMAN, a named pipes server need to be enabled on the PC on which the console is being run, and a network interface and protocol capable of supporting named pipes needs to be enabled. This means that the Console must be run on a Windows NT, 2000 Prof or Server, XP or 2003 Prof or Server computer for this to work. In addition, the receiving machine must be able to be a named pipe client, which includes Win95, Win98, WinMe as well as the systems mentioned as servers. A network interface needs to be active, and have the relevant permission to access the computer. (There are configurations where is it possible to monitor remotely, but not on the local computer!). So far this application has only been tested with TCP/IP.

To enable the Named Pipe output of the MonTel Server Console or Service applications the following value has to be set in the PABX.INI file in the [MonTel Server] section: TextOutViaPipe = 1.

If TextOutViaPipe = 0, or but it is otherwise able to listen to a named pipe then it will display the Pipe Status as Not in use.

When SVCMAN is able to access the client side of the pipe it will show that it is listening by displaying the Pipe Listener as active. In this example below it has not detected the server, because the Console Server is not running. However, this could also indicate that the network was also not active (even it the MonTel Server was on the same computer).

While it is attempting to set up the client side of the pipe it will display the Pipe Listener as being in an in-determinate state.

Once it is running and the server console or service are connected by named pipes it will show both the Pipe Listener and the Pipe Status as being active. In this example the Server Console (ServerCN) is running rather than the MonTel Server Service.

SVCMAN MonTel Server Console Output Display.

Once a connection has been achieved SVCMAN will display any new messages on its display, as they would have been displayed on the console screen. In addition it will hold the messages longer than the console would normally do, so it is possible to scroll back and see the last 50 or so Error messages or Call records. You can also resize the windows to view more messages.

Note that you are only able to view messages coming from the Server Console or Service. You cannot stop or start the Console or otherwise interact with it, and you can only Start and Stop the service using the SVCMAN Service Control Manager. See How to use SVCMAN to remotely control the MonTel "Windows NT service" Server (ServerSV) for more information.

One difference is that you will be able to see a message coming from the MonTel Server when it is opening or closing a pipe instance.

There can be up to 5 pipe instances running on the MonTel server, with each instance being able to feed a single SVCMAN running on another computer (or one on the same computer). The server interacts with SVCMAN, and caches messages, so that even the very slowest machine should be able to keep up with the MonTel Server. If a pipe becomes blocked, then after a period of time the MonTel Server will drop the connection.

There is a cost in terms of network traffic, since the connections need to be two way (this is also more secure). Therefore only the minimum numbers of SVCMAN should be active at one time.