cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
Walkthrough Wednesdays
387
Views
5
Helpful
7
Replies
Highlighted
Enthusiast

Persistent CTI Driver Error

Anyone know the cause of this error? I've looked just about everywhere, but can't find any info on cause or troubleshooting approach.

I've been assuming that some scripted Float variable is being passed to the Desktop, and the ctidriver doesn't like it. But I haven't been able to identify nor prove this theory.

Any ideas?

CCallReachedNetworkEvent::DecodeMessage-WARNING: Unsupported float len 0

CCallReachedNetworkEvent::DecodeMessage-WARNING: Unsupported float len 50

CCallReachedNetworkEvent::DecodeMessage-WARNING: Unsupported float len 48

CCallReachedNetworkEvent::DecodeMessage-WARNING: Unsupported float len 108

.

.

.

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Cisco Employee

Please reference CSCsb30704

"CCallReachedNetworkEvent::DecodeMessage-WARNING:"

It was opened as a minor severity. Unlikely we would include it in a Service Release since it is not service impacting, but at least you have something to reference.

View solution in original post

7 REPLIES 7
Highlighted
Cisco Employee

What version of IPCC are you running?

This is a warning message which should not be causing any problem.

The CCallReachedNetworkEvent is an event coming from the PG indicating that an agent initiated call has extended beyond the CCM cluster either via gateway or a Intercluster trunk. (This event is what the PG uses to differentiate an internal call from an external outbound call).

There was a defect related to this which was fixed in CTI OS 5.0 (CSCdz55612), but if you are already on 5.0 or greater, there may be a bit more work to do.

David

Highlighted

Thanks, David, for responding and for the bug.

Don't think it's causing a problem. But I'm not certain.

We've seen some instabilities on one instance of this particular duplexed pair. Misconfigured odbc, QuickEdit enabled on console windows, etc, that were recently corrected and we're now testing the stability.

Having seen it in other, stable deployments, we too believe this error is cosmetic. But it has been one that we haven't been able fix, describe the cause of, or write off as meaningless.

We're running 5.0sr5, and soon will be applying sr10.

CTI versions are:

ctios server [5.1.05108]

ctidriver [5.1 05108]

Mike

Highlighted
Cisco Employee

Please reference CSCsb30704

"CCallReachedNetworkEvent::DecodeMessage-WARNING:"

It was opened as a minor severity. Unlikely we would include it in a Service Release since it is not service impacting, but at least you have something to reference.

View solution in original post

Highlighted

Even if not fixed, that kind of info is exactly what I'm looking for!

Just checked the Bugtool. Seems CSCsb30704 is not yet available for public/partner/customer consumption.

Can you post or email the its details?

Highlighted

Here is the Release-note. It gets reviewed before its released to CCO bug toolkit. It might change a bit before its released.

Symptom:

CTI Driver process logs show an error for an unsupported floater tag.

The following can be seen in the process window traces.

CCallReachedNetworkEvent::DecodeMessage-WARNING: Unsupported float len 0

CCallReachedNetworkEvent::DecodeMessage-WARNING: Unsupported float len 50

CCallReachedNetworkEvent::DecodeMessage-WARNING: Unsupported float len 48

CCallReachedNetworkEvent::DecodeMessage-WARNING: Unsupported float len 108

Conditions:

Running with CTI OS Server when PG sends network reached events.

Workaround:

None necessary.

Further Problem Description:

This is a cosmetic issue.

Highlighted

Thanks Dave!! That's a huge help!

Highlighted

Also, here are some generic platform performance metrics that I can recommend that you run to monitor the system for future instability to rule out performance related issues.

Use Performance Monitor (perfmon).

Platform measurements

(Process) Handle count - Total

(Process) Thread count - Total,

(System) Processes,

(System) Processor Queue Length,

(Processor) % Processor Time - Total

(Memory) Comitted Bytes

(Memory) Available Bytes

(Memory) Page/secs

(Memory) Page Faults/sec

(Physical Disk) Avg Disk Queue Length

(Physical Disk) % Idle Time

(Network Interface) Bytes total

(Network Interface) output queue length

Process Specific

(Process) Private Bytes -

(Process) %Processor Time -

(Process) IO Write Bytes/Sec -

Every minute, log to disk using Binary format for short term capture, or Circular binary format and leave running.

In this case, might be a good idea to monitor process specific metrics mentioned above for CTI OS Server and CTI Driver processes.

Content for Community-Ad