Back in version 1.0/1.1 of SNS that was a delivery channel for Exchange Messenger under Exchange 2K. Since the Messenger Server has moved over to LCS 2003/2005 has anyone create the linkage between SNS2.0 and LCS2005
There idea is that the protocol would be sip but that the redirector on LCS would redirect the alert the appropriate device based on the presence information contained in the LCS registrar database.
Yes I realize that there is a Microsoft Alerts channel for SNS2.0 but there's not way that an outside connection can be made for my customer set..
SIP (LCS) delivery channel for SQL Notification Services
Paulaps
Per our support engineer:
I think it’s a very interesting practice to integrate SNS with LCS. Here’s my update:
==============================
SQL Server Notification Services itself does not handle final notification delivery. Instead, Notification Services sends notifications to one or more delivery channels, each of which acts as a pipe to a particular delivery service, such as an e-mail gateway or .NET alerts server. Delivery channels are instances of particular protocols. Each delivery channel packages notifications into protocol packets required by the target delivery service, then sends the packets to the service for final delivery.
Notification Services supports configuring multiple delivery channels for each of the following delivery protocols:
? The SMTP protocol for sending notifications to Exchange or other SMTP servers.
? The file protocol for sending notifications to operating system files, used primarily for debugging applications.
? An extensible HTTP-based protocol for communicating with a variety of HTTP- and SOAP-based delivery services (including the .NET alerts delivery service).
Microsoft Office Live Communications Server is a logical choice for a delivery service, but none of the delivery channels that ship with the current version of Notification Services use instant messaging (IM). Therefore, in order to take advantage of the enterprise IM environment provided by Live Communications Server, you must develop a custom real-time communications (RTC) protocol and a corresponding custom RTC delivery channel.
A custom protocol for Notification Services must be implemented as a class in a managed-code assembly. The custom RTC delivery channel described in this whitepaper implements the custom protocol as part of the RTCDeliveryChannel class code.
A custom RTC Delivery Channel works with SQL Server Notification Services and Live Communications Server 2003 as follows
l The SQL Server Notification Services distributor picks up the notification, calls the XSLT Content formatter, and passes the following information: message content, message URL, and message type.
l The XSLT Content formatter transforms the message, using a custom XSLT for IM, then returns the formatted message to the Notification Services distributor.
l The Notification Services distributor calls the custom RTC Delivery Channel with the following information: To, From, and the formatted message.
l The RTC Delivery channel sends the instant message to a server running Live Communications Server 2003 and returns a send status to the Notification Services distributor. In response, the Notification Services distributor updates the notification tables with delivery-status information.
[screen shot deleted]
==============================
What we need to do is to develop a custom delivery channel for LCS2003/2005. I attached the full document in this email. Thanks.
If you'd like me to email you the document that the engineer attached please email me at budsup@microsoft.com.
-brenda (ISV Buddy Team)