yesterday I commented about the announcement  that
Microsoft will publish managed API FOR their SIP protocol
stack - UCMA 1.0.

I'm looking forward to see what can be done with it,
but first signs are discouraging.

This will be published as SDK, so I assume it will not
be included in .NET 3.5... If true, I don't like it.
Building SIP client applications will be easier but
deployment (downloading dependancies) will be a
problem.

SIP protocol and managed API for it should be part of OS.

Similarly, Microsoft Office Communications Server 2007
seems to be ready to ship soon as a separate product.
Will UCMA bi tied to it?

In my view SIP should have the same treatment as HTTP.
Built in Server, like IIS (or IIS extended to support SIP)
Managed API that is part of .NET Framework.

Most likely, this is not going to happen.
Maybe if we get an open source SIP server with the
Apache Web Server scare factor, Microsoft will change
their mind.

And allow us to write applications that use HTTP/SIP
in interchangeable and unified way.

Dream on...