« Back to CTIOS Toolkit Questions

RE: New Message from Bill Webb in Computer Telephony Integration Object Ser

Combination View Flat View Tree View
Threads [ Previous | Next ]
Hi Folks -
 
I have a customer that wants to be able to copy and paste the ANI, DNIS, and Dialed Number fields from CTIOS Desktop, and this seems to not be possible without making those fields "editable" by adding that flag in the registry.
 
While this workaround does work, is there any risk to doing this, like for instance if the Agent changes or completely deletes any of those fields? I figured they are somewhat "protected", but I want to be sure...
 
Thanks in advance!
 
 - Bill

Bill,

You could customize the CTIOS Soft Phone to pop up a dialog where the salient fields can be copied from, thus protecting the peripheral variables. Pretty easy coding for a VB.NET person – took me an afternoon to get nice and pretty.

Once you work with the Grid ActiveX control, you are bound by its policies. I think the agents can change those values and the ActiveX will save the new value to the Peripheral Variable.

Regards,
Geoff

Yeah, I'd love to (and would prefer to) go that route, but customer doesn't have budget for any custom dev. I'm trying to give them as much "customization" as possible without going through the recompile.

Another factor there is that they are using Outbound, and it seems like the sample VB project from the toolkit doesn't compile out of the box - anyone else experience this? Considering that issue, it becomes more than an afternoon's worth of work! ;-)

- Bill

I hear you about “no custom dev”.

I’ve never had any issues with the sample Outbound Soft Phone not compiling in VB.NET. What exact version are you using?

Regards,
Geoff

In fairness, I've actually been playing around with VB Express 2010, but it actually works fine with the other samples. The Outbound one, for some reason, just opens up with tons of errors and won't run with the debugger. The compiled sample (the exe in that directory works just fine, but it looks like the source code and sample VB Project are also slightly different than the compiled sample.

Not sure, but I was curious if anyone else had that experience with 8.5(3).

- Bill

For the curious, here's what I've uncovered so far in my informal testing with 8.5(3):

1. You can add the "editable" attribute to ANI, DNIS, and DialedNumber, which makes these fields editable just like the call variable fields. This allows them to be selected for standard Windows copy/paste functions.

2. Even if these fields are overwritten/deleted, they will show as modified in the desktop for the duration of the call (not sure about transfers), but the TCD record will still have them stored with original values (which is a very good thing)!

Still curious to get others' feedback on this, since it is, in the words of a colleague, "an unnatural act". I would certainly recommend the development route, but in a pinch, this seems like it will work fine with a couple caveats.

- Bill

Bill/Geoff,
I am looking to modify some CTIOs code. The code I have is CSharp, is there another version of the sample code with VB also. I am looking at version 8.0.1


From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
Sent: Friday, April 27, 2012 1:10 PM
To: cdicuser@developer.cisco.com
Subject: New Message from Bill Webb in Computer Telephony Integration Object Server (CTIOS) Toolkit - CTIOS Toolkit Questions: RE: Impact of making ANI, DNIS, Dialed Number fields "editable" in registry

Bill Webb has created a new message in the forum "CTIOS Toolkit Questions":

--------------------------------------------------------------
For the curious, here's what I've uncovered so far in my informal testing with 8.5(3):

1. You can add the "editable" attribute to ANI, DNIS, and DialedNumber, which makes these fields editable just like the call variable fields. This allows them to be selected for standard Windows copy/paste functions.

2. Even if these fields are overwritten/deleted, they will show as modified in the desktop for the duration of the call (not sure about transfers), but the TCD record will still have them stored with original values (which is a very good thing)!

Still curious to get others' feedback on this, since it is, in the words of a colleague, "an unnatural act". I would certainly recommend the development route, but in a pinch, this seems like it will work fine with a couple caveats.

- Bill
--
To respond to this post, please click the following link:

<http://developer.cisco.com/web/ctios/forums/-/message_boards/view_message/5529077>

or simply reply to this email.

>>>is there another version of the sample code with VB also

There certainly is – there are a number of VB.NET samples. Supervisor, Agent, Outbound. The full code is there and the applications built are precisely the same as what are distributed as Cisco apps. Remember that these use the ActiveX objects for the heavy lifting.

Regards,
Geoff

That’s certainly weird behaviour. They must go with the call to the next user though, or what would be the point!

It’s looking good for you, though - and thanks for your testing and updating the Community.

Regards,
Geoff

David Lender (467)
Shannon McCoy (91)
Arthur Shats (57)
Christopher Nagel (47)
GEOFFREY THOMPSON (38)