Blogs

Cisco CTI OS .NET Toolkit Release 8.5(2) introduces support for application development using Microsoft Visual Studio .NET 2010 and the .NET 3.5 framework. Existing .NET 2.0 controls do not need to be modified. Additionally, the CTI .NET CIL supports Visual Studio .NET 2010.

Note that Visual Studio 2010 by default uses Framework 4.0 You must change the framework for your CTIOS 8.5(2) .NET Cil project to use the .NET 3.5 framework.

...Read More

 

This main.java sample demonstrates creating a filter mode application to receive skill group statistics.

Here's the source code:

import com.cisco.cti.ctios.cil.CtiOsSession;
import com.cisco.cti.ctios.cil.CtiOs_Enums;
import com.cisco.cti.ctios.util.CtiOs_IKeywordIDs;
import com.cisco.cti.ctios.cil.CtiOs_Enums.SubscriberList;
import com.cisco.cti.ctios.cil.Arguments;
import com.cisco.cti.ctios.util.CtiOs_IKeywordIDs;

...Read More

 



Cisco Developer Network will be presenting a CDN Developer Track at Cisco Live! London the week of January 31, 2011.

We are presenting technical sessions which highlight Application Programming interfaces (APIs) and Software Developer Kits (SDKs) for Cisco technologies such as Unified Communications, IOS, and Access Routing Technologies ¿ including the new Cisco Cius ...Read More

 

It is important if you are implementing a filter mode application that you include End Call events in your filter.
...Read More

 

CTIOS Custom agent desktop developers should be aware of a defect fixed in CTIOS 7.5(7) and later:

Symptom:
Intermittently, after an agent performs a Network Blind Transfer, the desktop client gets stuck in talking state and/or the transfer buttons get grayed out preventing the agent from performing transfer in future.

Conditions:
Any peripheral type where Network Blind Transfers are involved.

Workaround: ...Read More

 

When attempting to login an agent with invalid agentid or password, a custom CTIOS Application may see either:

1. eCTIOSFailureEvent event and eButtonEnablementMaskChange events are fired when eControlFailureConf received by the CIL.

or

2. Only eControlFailureConf event is fired when eControlFailureConf is received by the CIL.


...Read More

 

Cisco Advanced Services offers a WebServices interface to CTIOS. The CTIOS Web Service provides a SOAP XML web method call interface to the CTIOS Server. It's use will require the customer or partner to develop an application that implements the CTIOS Web Service WSDL. This can be done with just about any programming language available which supports HTTP and SOAP XML constructs.

Information about the Advanced Services' CTIOS Web Service is available in the ...Read More

 

Beginning with ICM version 7.5(4), the CTI Server supports sending a Not Ready reason code when in Not Ready state on Unified Contact Center Enterprise systems. This resolves CSCsh47197 cg.ctiserver CTISrvr doesn¿send NR agent state events with different reason codes.
...Read More

 

Be careful when using the JavaCil LogWrapper. Users found that when the year changed from 2008 to 2009 the deleting of old files specified by the number of files to maintain didn't work correctly.

When using the JavaCil LogWrapper class, the format is

LogWrapper(java.lang.String sFileName, long iMaxSize, int iArchives, int iExpires, int iFlushIntervalMs)
...Read More

 

With the release of CTIOS 7.5(3), CTIOS Desktop now supports Windows XP SP 3.

For more information see the release notes
...Read More

 

If you are writing a multi-threaded agent mode app, there should only be one LogWrapper class object for the entire application.
...Read More

 

By default, the CTIOS Agent Desktops use a feature of the CILs to load balance between CTIOS Server A and B as specified in the registry by the CTIOS Desktop install.

Some customers have asked for the feature of being able to select a preferred CTIOS Server Side (for instance if Side A is local and Side B is remote; it would be preferable to have Side A as the preferred side.
...Read More

 

Showing 12 results.
Items per Page 20
of 1

Forums

« Back to CTIOS Toolkit Questions

CTIO 7.5(1) VB Console process - how to supress logging?

Combination View Flat View Tree View
Threads [ Previous | Next ]
toggle
CTIO 7.5(1) VB Console process - how to supress logging?

(sorry, body missing)

I have a console process written in VB that logs the agent in (they are already logged in, of course) and performs actions on incoming calls and then dies when it hears the logout.

There does not seem to be any way of stopping it from writing trace at a fairly detailed level in the console window, and if the trace server is installed, sending this to another file. I can remove the trace server (ctiostracetext.exe) and this prevents the detailed log file from being created in %HOMEPATH%, but I can't seem to stop it writing to the process window.

I have played with the trace masks in HKLM and HKCU - and even tried the advice in manual to create a TraceMask in

HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems\CTI Desktop\Ctios\Logging
see appendix B-2. Is this key correct?
Is there any way to stop the trace in the window. I use the CTIOS trace library and write my own statements to my own log files, which is all I need.

The reason I ask is I have a lot of these processes (around 300) and I'm looking to improve performance.
Regards,
Geoff

.

Wow – I mangled that subject line. I meant to say CTIOS 7.5(10)

Regards,
Geoff
.

Geoff,

There is not a registry setting that tells the COM Cil whether to write to the console or not.
The recommended trace setting for normal operation is 0x40000307.

David

David,

I am struggling to know how these trace masks work.

The one in HKCU is set to 0x40000307 and the one in HKLM is set to 0x0, but even if I change the one in HKCU to 0x0, it still traces to the screen at exactly the same level of tracing.

I see it say something like “Screen Output is ON” – and I hoped there was a way to turn that off. But the setting is not exposed.

What about the comment on B-2 to create this key and install TraceMask there?

HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems\CTI Desktop\Ctios\Logging

Is that the correct key?


Regards,
Geoff

Geoff,

For Windows 7

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cisco Systems, Inc.\CTIOS Tracing

For earlier Windows

HKEY_LOCAL_MACHINE\SOFTWARE\ Cisco Systems, Inc.\CTIOS Tracing


David

David,

Thanks for your reply. I do know about HKEY_LOCAL_MACHINE\SOFTWARE\ Cisco Systems, Inc.\CTIOS Tracing

My question is about the Guides.

Appendix B-2 CTIOS 7.5 Developer's Guide

You can set C++ and COM client trace configuration parameters in the Windows registry at the following key. See Java CIL Logging Utilities, page B-3, for instructions on configuring tracing for the Java CIL. See Logging and Tracing (.NET), page B-5, for instructions on configuring tracing for the .NET CIL.

HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems\CTI Desktop\Ctios\Logging

Appendix B-2 CTIOS 8.5 Developer's Guide

You can set C++ and COM client trace configuration parameters in the Windows registry at the following key. See Java CIL Logging Utilities, page B-3, for instructions on configuring tracing for the Java CIL. See Logging and Tracing (.NET), page B-5, for instructions on configuring tracing for the .NET CIL.

HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems\CTI Desktop\Ctios\Logging

Are you saying that these statements are incorrect?

Regards,
Geoff

The documentation has the wrong registry key it should be HKEY_LOCAL_MACHINE\SOFTWARE\ Cisco Systems, Inc.\CTIOS Tracing . The rest of the statements are correct.

Collateral


No files available