20140622-173955-63595162.jpgSince the introduction of Apples “kill switch” preventing iPhones from being wiped or services being disabled while “find my phone” service is configured, iPhone theft has dropped dramatically. Giving owners the ability to render their phones stolen at the push of a button, turns a high value device into something a little harder to sell on.

Microsoft and Google have both recently announced they’re planning on following suit, and introducing similar systems into their own handset models.

Google recently launched their very own find my phone type system, which proved to be a little buggy at times. It’s believed that this system will gain the additional functionality of being able to disable phones on users request. Something Apple have been doing for sometime now.

This will be closely followed by a tightly bing maps integrated system by the guys over at Microsoft.

It would be great to fully stamp out phone theft, or at least make phones seem less desirable to thieves. Although this is properly unlikely to stop opportunist thieves it may stamp out some crime.



In a recent tweet Mark Russinovich has confirmed Microsoft are working on bringing a “start menu” to the Windows blue screen of death (BSOD)

20140524-215139-78699712.jpg

It’s not yet clear as to when this will be released to end users.. But it’s certainly going to be a game changer, and will make diagnosing BSOD issues a whole load easier!

Well done Microsoft – a true step in the right direction..



LCS 2014

Here it is!

The very first public BETA release of my latest project.. I decided to build this application to add a little ‘Je ne sais quoin’ to the Microsoft Lync client status selection. I am a big fan of the Microsoft Lync product, and unified communications.. However, as those close to me will know – I am a big fan of automation. Which is when the idea for this app was born..

So.. What does it do.. Well, check out the details below! Please remember this is an extremely early public release BETA. It’s in its early stages, and I still have BIG plans for this app.

Continue reading »



Today I was asked if it would be possible to ‘Automate’ the repeated dialling of a SIP contact, this was in order to try and replicate and resolve an issue with a headset and lync.

So I cam up with this, and thought I should share it in case others find it useful.

The code below commences dialling after the command button is pushed, and each time the other party hangs up the App starts dialling again. Simple but effective.

If you use the code, or figure out a better way of doing it drop me a message using the comments section below.



da57591e-7377-46d3-959c-005816e755c4So todays challenge was around handling the ModalityState change on the Lync 2013 client. The ModalityState change event happens during certain stages of Lync calls, and client actions. The ModalityState is part of the Microsoft.Lync.Model.Conversation namespace. We are using it to configure certain custom Lync Status’ dependant of the current state of the client.

To capture and handle these events, you need to create and event handler for the conversation manager namespace and for ModalityStateChangedEventArgs. The code below is written in VB.Net but could easily be transferred to C# etc.

In my example, I am only interested in the AudioVideo modality state changes.

Imports Microsoft.Lync.Model
Imports Microsoft.Lync.Model.Conversation
Imports Lync = Microsoft.Lync.Model.Conversation

Public Class frmMain
    Private _LyncClient As LyncClient
    Public WithEvents _ConversationMgr As Microsoft.Lync.Model.Conversation.ConversationManager
    Public WithEvents _conv As Conversation

    Private Sub MainWindow_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
        Try
            _LyncClient = LyncClient.GetClient()
            _ConversationMgr = _LyncClient.ConversationManager
            DisplayCurrentState()
        Catch generatedExceptionName As ClientNotFoundException
            MessageBox.Show("client is not running")
        End Try
    End Sub

    Private Sub _ConversationMgr_ConversationAdded(ByVal sender As Object, ByVal e As Microsoft.Lync.Model.Conversation.ConversationManagerEventArgs) Handles _ConversationMgr.ConversationAdded
        AddHandler e.Conversation.Modalities(ModalityTypes.AudioVideo).ModalityStateChanged, AddressOf AVModalityStateChanged
    End Sub

    Private Sub AVModalityStateChanged(ByVal sender As Object, ByVal e As ModalityStateChangedEventArgs)
        Select Case e.NewState
            Case ModalityState.ConnectingToCaller
                'Insert your code here
            Case ModalityState.Connecting
                'Insert your code here
            Case ModalityState.Joining
                'Insert your code here
            Case ModalityState.Transferring
                'Insert your code here
            Case ModalityState.Disconnected
                'Insert your code here
            Case ModalityState.Disconnecting
                'Insert your code here
            Case ModalityState.Forwarding
                'Insert your code here
            Case ModalityState.OnHold
                'Insert your code here
            Case ModalityState.Suspended
                'Insert your code here
        End Select
    End Sub

So as you can see, it’s quite a simple concept – which holds lots of potential!




Page 1 of 512345