If you’ve been following the last couple of posts I’ve been doing, you’ll know that I mentioned (here and here) that the default provided shape for performing a transfer, the blindTransfer shape, is OK but has some serious shortcomings. The biggest is that if the called party doesn’t pick-up, the call is dropped. The transfer has already happened, and there’s no way you can recover from this, or “know” that the transfer didn’t succeed.
On the other hand an “attended transfer” will wait until the called party picks up the call, only then transferring the call. Therefore you can add error handling to recover from errors during the transfer, or if no-one answers. read more…
I’ve only just got around to watching this video by Scott Hansleman where he talks about his personal productivity tips, and how he seemingly manages to get more stuff done in a day than anyone else (although, it turns out his days have 28 hours in them, so I guess he gets an advantage 
)
The fact that it has taken me nearly 10 days from spotting the post to watching the video tells me an embarrasing amount about my own triage system, and the video has lots of improvement suggestions for everyone, not just devs. read more…
This is the final post in a series of 4 on using UCMA Workflow (series starts here). If you need more information on this or are looking for a reference guide, I highly recommend Professional Unified Communications by George Durzi & Michael Greenlee, which has an entire chapter (50 pages) devoted to Workflow.
By now you should be fairly happy with the concept of using the UCMA Worfklow SDK to create visual representations of UCMA applications. From the last post you saw how easy it was to create a simple IVR application to route calls to the appropriate department based on user feedback.
In this post I want to show you a different example. It’s got no real use, but it does highlight the many varied things you can do with the workflow. It also demonstrates an important point, which is that you can manipulate the graphic workflow you see at design time in code at run-time, modifying properties and values to fit your needs. It’s an implementation of (what I call) the Numbers Game. read more…
This is post number 3 in a series of 4 on using UCMA Workflow. If you need more information on this or are looking for a reference guide, I highly recommend Professional Unified Communications by George Durzi & Michael Greenlee, which has an entire chapter (50 pages) devoted to Workflow.
In the last two posts I described how to create a UCMA application which uses the Workflow SDK and described some of the more common (and, I think, more useful) shapes you can utilise.
In the next two posts I’d like to walk through some examples. In this post I’ll be creating a simple IVR solution for a small company. After that I’ll describe how to make a Lync version of the numbers game. read more…
A very quick post, as I’ve just come across this and want to jot it down now before I forget it.
In Lync, when you close an active conversation window, you’ll be prompted with this dialog box:
“Closing this window will end all current activities with this contact. Do you want to close this window?”
If you click “Do not show this message again”, then this prompt will be removed permanently.
If that wasn’t really what you meant to do, or you want to restore again in the future, you can do so by making the following Registry modification:
HKEY_CURRENT_USER\\Software\\Microsoft\\Communicator \\yourusername@yourdomain\\DS\\DSFTAndOthersClose
Change the value of this key from 01 00 00 00 to 00 00 00 00 and restart Lync.
