Question:

When I start Call Analyzer or try to load a protocol stack I get the error message "Error code 1"

 

Answer:

This is because the protocol stack is not compiled. Select protocols >> define. Load your protocol stack and select Combine all. If Combine all is dimmed, save your file first.

Question:

I am using abis protocol and abis setup files, but my flow results are not correct and call trace is not working as it should.

 

Answer:

Abis messages are special as they are related to both SDCCH and TCH. First step is to use pre-scan to get references for call trace. Select decode >> prescan references in order to get flow results and call trace to work. In some case you need to deselect auto stop for call trace. Please see abis tutorial for more details.

Question:

When I open a record file I get a lot of error messages instead of decode of the protocol. I have loaded a correct protocol stack and setup file.

 

Answer:

In some cases when you are using non-SS7 protocols such as abis and Gb you need to let Call Analyzer detect what protocol to be used on the different links. To do that select define >> link properties. Here you specify which short and long specifications that you want to use and press auto spec. Call Analyzer will now detect the relevant specifications.

Question:

When I load a protocol file I get the error message: Message "[parameter name] is conflicting", do you still want to load setup file?

 

Answer:

When a new protocol stack is loaded, Call Analyzer tries to use the current setup file. But in this case the setup file contains messages from another protocol (or an older version of the protocol). Now Call Analyzer cannot find the messages from flow definitions in the current protocols. It is urgent that you click NO in order not to damage the setup file, and then manually select the setup file you want to use.

Question:

When I load a setup file I get the error message: Message "[parameter name] is conflicting", do you still want to load setup file?

 

Answer:

If you have the latest protocols and setup files it is because you have loaded a protocol that is different from the protocol used in the setup file. Select NO in order not to damage your setup file and load the correct protocol before you load the setup file.

If you are making your own setup files and your loaded protocol is correct it may be caused by some invalid strings in your setup file. In this case you can select YES and see the log file SetupFileError.txt for details about conflicting messages. It is important not to save the setup file with the same name until you have corrected the conflicts as the conflicting strings are replaced with ??? in you setup file.

Question:

When I load a setup file I get the error message: Message "???  is conflicting", do you still want to load setup file?

 

Answer:

This is because your setup file has been damaged. If you load your setup file with a warning the unknown information elements are replaced with ??? and if you have saved the setup file again you will now have strings in flow definitions with ???. Please download your setup file again.

Question:

When I try to load a setup file I get the error message: File contains illegal characters?

 

Answer:

Your setup file is read-only. Select the setup file and in properties remove the read only indication for the file. This is often caused by copying the file where Windows automatically mark files as read only

 

Question:

When I open a record file with different protocols several of the messages are not decoded correctly?

 

Answer:

Your link properties are not detected correctly. You can correct it by specifying the correct protocols in define >> link properties.

To avoid the problem next time select define >> other and select detect properties after opening record file.

 

Question:

How do I move my Call Analyzer to another PC?

 

Answer:

In the RUN dialog of Windows run the following command from your working directory of Call Analyzer (usually c:\program files\netcare\call analyzer): CallAnalyzer.exe unregister_PCID.

You will now be given a code. Send this code to info@netcare-international.net together with the PCID from your new installation to obtain a new code.