In our previous post, we introduced changes in Office Communications Server to enable Direct SIP with IP-PBX such as Cisco Call Manager. In this simple example, we provide a configuration of Direct SIP with Cisco Call Manager 4.2.1. Read More

With the hotfixes released in August 2008, Microsoft is significantly improving the capability for Office Communications Server 2007 to exchange calls with SIP-based IP-PBX, in particular from Cisco. As a consequence, Microsoft now supports OCS deployments in Direct SIP with IP-PBX between Office Communications Server and specific versions of Cisco Call Manager. This change gives administrators the possibility to set up Office Communications Server so that it can directly interoperate with IP-PBX using E.164 globally routable telephone numbers without RFC3966’s mandated “+” prefix. Additionally, Office Communications Server will now be able to interoperate with IP-PBX within a private dialing plan, exchanging locally routable private numbers. Read More

Generically, SIP can use (at least) 3 types of transport. Office Communications Server supports TCP and TLS, with the latter being the default (actually, TLS runs on TCP). Various interactions with some partners and customers of late of have posed the Read More

In the Office Communications Group (OCG) white paper “Integrating Telephony with Office Communications Server 2007” we stated that “SIP Trunking” was out of scope for that release but was “under consideration” for future releases.  We are always Read More

Overview Automatic configuration allows Communicator to find and connect to the appropriate LCS server without manually entering a server name into its settings. Communicator has special requirements for DNS and certificates to make this work properly.  Read More