Mino – The UC Guy

Microsoft Unified Communications Blog

Archive for October, 2008

October 2008 Communicator Update

Posted by Mino on October 27, 2008

Description of the update for Communicator 2007: October 24, 2008

This update fixes the following issues:
Advertisements

Posted in Common Errors, communicator client, Miscellaneous | Tagged: , , , , , , | Leave a Comment »

The Speech Server Scoop on OCS 2007 R2

Posted by Mino on October 15, 2008

The GotSpeach Guy Wrote on his Blog

Ok the word is getting out now about Office Communications Server 2007 R2 so I thought I would give you some details on how this will affect Speech Server developers.

First let me say that there are no changes for Speech Server in OCS R2. It will still be a separate install and the bits will be the same. You will still use Visual Studio 2005 and all of the development tools are the same.

Now for the cool news about the R2 release.

R2 will include the new UC Managed API 2.0. The API shows the new approach for developing Speech Applications going forward: speech technology will be an integrated developer capability in the whole of the UC platform. The UCMA 2.0 API does consist of 3 API major pieces – Core (including a SIP signaling stack and a media stack), a managed server Speech API and UC Workflow Activities that are built on top of both the core and server speech managed APIs. All together make the one UC Managed API 2.0.

The UCMA 2.0 Server Speech SDK will support 12 languages with both ASR and TTS: US English, Canadian French, Mexican Spanish, Brazilian Portuguese, UK English, German German, French French, Italian, Japanese, Mandarin (simplified/mainland plus traditional Taiwanese), Korean.

And get this – it will support Visual Studio 2008! Actually the UC Workflow Activities support both activities for speech as well as for IM automated agents (a.k.a. bots).

More info –

  1. You can develop Speech Server (2007) applications just like you have in the past (using VS 2005)
  2. You can now develop speech “bots” using the new Workflow Activities on top of the UCMA 2.0, or in managed code only using the Core and Speech APIs, if you are really hard core.
  3. The UCMA Speech SDK will be missing some of the tools that you are currently used to having. For example there is no grammar tool but SRGS grammars are still supported and you can use the existing Grammar Editor (in VS2005) to create grammars, or use your favorite XML editor.
  4. Conversational grammars may or may not work due to changes in the way the engine works.
  5. OCS 2007 R2 has no VXML support on top of UCMA 2.0. This might change for the future ’14’ release. SALT definitely is dropped from the roadmap.
  6. The UCMA is much closer to SIP but will still be familiar to you. It will be able to manipulate the SIP stack and the media stack as well.
  7. In the next ’14’ release (the one after R2) Speech Server will no longer be a standalone install but will be an integral part of OCS.

You are probably wondering how you can get your hands on Office Communicator 2007 R2?
The official Launch Date will be early February. Till then there only is a very small private beta.

There however is a Developer program called Metro (http://www.discovermetro.net) for managed Microsoft accounts.

Managed ISVs and Corporate developers just need to get in touch with your Microsoft (Partner) Account Manager asking if you can be admitted to this Metro program. The Metro program gives access to Hyper-V images of a complete developer OCS 2007 R2 setup, including speech, training across the world in the complete platform, and a (email only) help desk, in exchange for a commitment to build applications on the UC (OCS 2007 R2 and Exchange) platform.

I am really excited about this as it will allow us Speech Server developers better access to the core OCS components and will give us a new way to develop speech applications. For now the best approach will probably be to keep developing the way you have in the past and start experimenting with the new stuff before settling on it for all of your development. Or at least that is the approach I plan on using.

Gold Systems (the company I work for) has OCS R2 up and running in production and we are very excited about the new release

I’ll blog more on the UCMA later.

Posted in Miscellaneous | Tagged: , , , , , , , , | 2 Comments »

OCS 2007 Audio/Video bandwidth calculation

Posted by Mino on October 13, 2008

Medium Min High Quality
Data 56kbps 56kbps
Voice 50kbps 80kbps
Video 50kbps 350kbps
RoundTable (Conference video phone) 50kbps 350kbps

Note that the requirements are cumulative –

Data + Voice + Video =

56 + 50 + 50 = 156kbps (Minimum Quality)

or

56 + 80 + 250 = 386kbps (High Quality)”

Here are some calculations I have used. however the 300KBps is only video stream single direction.  Bidirectional video consists of two streams..

The following formula can provide rough bandwidth consumption estimates for conferencing with Audio / Video.

Note:  Calculation results will be displayed in Mbps

CC = Concurrent Conferences

PPC = Participants Per Conference

 

Conference Type

Bandwidth Consumption Mbps

Audio with Application Sharing

(((CC * PPC)*14KBps)+((CC *PPC)*90KBps))*10^-3

Audio and Video

(((CC * PPC)*14KBps)+((CC *PPC)*600KBps))*10^-3

Another OCS 2007 Audio Bandwidth Calculation

Audio Codec
Frame Size [ms]
Codec payload bit rate
[bits / sec]
Total payload bit rate
[bits / sec]
Actual bit rate
[bits / sec]
Without
redundancy
With
redundancy
RTAudio@16KHz
20
24000
29000
45000
74000
RTAudio@16KHz
40
24000
26500
34500
61000
RTAudio@16KHz
60
24000
25666
31000
56667
RTAudio@16KHz
20
18000
21000
37000
58000
RTAudio@16KHz
40
18000
19500
27500
47000
RTAudio@16KHz
60
18000
19000
24333
43333
RTAudio@8KHz
20
8800
11800
27800
39600
RTAudio@8KHz
40
8800
10300
18300
28600
RTAudio@8KHz
60
8800
9800
15133
24933

Posted in A/V Edge Server, Consolidated Edge, Edge Server, Miscellaneous | Tagged: , , , , , , | 7 Comments »

How to complete basic backup of your OCS installation, including configuration and databases.

Posted by Mino on October 13, 2008

First we look at the configuration on the front end server. In this scenario we will complete backup of Front end and mediation server from the front end server. If you have additional servers they are easily added to this script.

  • First Create an folder on the C: drive of the FE server called “Backup”
  • Browse to the new folder “c:\Backup”
  • Create a new .bat file called “OCS-backup.bat”
  • Edit the .bat file

—– Content of OCS-backup.bat——–
“C:\Program Files\Common Files\Microsoft Office Communications Server 2007\lcscmd” /config /action:export /level:machine /configfile:c:\backup\[name of front-end server]-Serversettings.xml /fqdn:[fqdn of front-end server]

“C:\Program Files\Common Files\Microsoft Office Communications Server 2007\lcscmd” /config /action:export /level:machine /configfile:c:\backup\[name of mediation server]Serversettings.xml /fqdn:[fqdn of mediation server]

“C:\Program Files\Common Files\Microsoft Office Communications Server 2007\lcscmd” /config /action:export /level:pool /configfile:c:\backup\[poolname]-Pool.xml /poolname:[poolname]


“C:\Program Files\Common Files\Microsoft Office Communications Server 2007\lcscmd” /config /action:export /level:global /configfile:c:\backup\[poolname]-Global.xml /poolname:
[poolname]

“C:\Program Files\Common Files\Microsoft Office Communications Server 2007\lcscmd” /config /action:export /level:global,pool /configfile:c:\backup\[poolname]-GlobalAndPool.xml /poolname:
[poolname]

————END————-

Please note that the pool name is the same as the hostname of the Front End server in Standard Edition deployment.

  • Save the file and give it a test run. You should get 5 .xml files in c:\backup directory

Backup of the Access Edge server is very similar. It should be backed up, however it is not needed every day, depending on your company’s security requirements. Backing up configuration every time a change is applied to the server is a very good idea.

The command is the same as for the Mediation and Front End server:

——-Access Edge Backup——–

“C:\Program Files\Common Files\Microsoft Office Communications Server 2007\lcscmd” /config /action:export /level:machine /configfile:c:\backup\Serversettings.xml /fqdn:
——–END——–

Then we move to backing up SQL Databases:

If you have a backup application that supports SQL 2005, its possible to backup the databases directly.

If you are left without this tool, there are other ways. In this case i will describe the procedure for the Standard edition of OCS deployments, and there for assume that OCS is using an SQL 2005 Express.

First you need the Microsoft SQL Server Management Studio Express

  • Download and install the package on your Front End server

This enables you to view and generate SQL scripts. For this deployment, the below scripts will work:

———–RTC-backup.sql———–
BACKUP DATABASE [rtc] TO DISK = N’C:\Backup\rtc.bak’ WITH NOFORMAT, INIT, NAME = N’rtc-Full Database Backup’, SKIP, NOREWIND, NOUNLOAD, STATS = 10
GO
—————END————–

———–RTCconfig-backup.sql———–
BACKUP DATABASE [rtcconfig] TO DISK = N’C:\Backup\rtcconfig.bak’ WITH NOFORMAT, INIT, NAME = N’rtcconfig-Full Database Backup’, SKIP, NOREWIND, NOUNLOAD, STATS = 10
GO
—————END————–

———–RTCdyn-backup.sql———–
BACKUP DATABASE [rtcdyn] TO DISK = N’C:\Backup\rtcdyn.bak’ WITH NOFORMAT, INIT, NAME = N’rtcdyn-Full Database Backup’, SKIP, NOREWIND, NOUNLOAD, STATS = 10
GO
—————END————–

  • Create the 3 .sql scripts and save them to the c:\backup folder.
  • Now create a new .bat file called OCS-sql-backup.bat

———–OCS-sql-backup.bat———–

sqlcmd -S .\rtc -i c:\backup\rtc-backup.sql

sqlcmd -S .\rtc -i c:\backup\rtcconfig-backup.sql

sqlcmd -S .\rtc -i c:\backup\rtcdyn-backup.sql

—————END————–

Now you have 2 .bat files (OCS-sql-backup.bat & OCS-backup.bat) and all that is left is to create a couple of Scheduled Task to run these every day, and configure your file level backup to take backup of the c:\Backup folder.

Posted in Miscellaneous, OCS Backup & Recovery | Tagged: , , , | Leave a Comment »

How to strip “Remove” the + from all outgoing SIP communication from an OCS Mediation server ?

Posted by Mino on October 13, 2008

It might be useful in a Cisco direct SIP environment to automatically strip the + from all outgoing SIP communication from an OCS Mediation server.

To do this, create a text (XML) file called MediationServerSvc.exe.config and place it in the location of the MediationServerSvc.exe file. It should be in the ‘C:\Program Files\Microsoft Office Communications Server 2007\Mediation Server’ directory. The contents of this file should be:

<?xml version=”1.0″ encoding=”utf-8″ ?>
<configuration>
<appSettings>
<add key=”RemovePlusFromRequestURI” value=”Yes”/>
</appSettings>
</configuration>

Now, you are free to normalize to E.164 without having to worry about your Cisco devices getting confused!

Srouce : http://jimraymond.wordpress.com/ 

Posted in Cisco 4.x Integration, Cisco 5.x Integration, Cisco 6.x Integration, Mediation Server, Miscellaneous, Nortel CS1000, PBX Integration, Quintum's gateways | Tagged: , , , , , , , , , | 2 Comments »

A/V edge server doesn’t work from outside, and external users have problem using audio/video

Posted by Mino on October 13, 2008

 AV edge server requires external interface  that has a public IP address that can route onto the Internet, This Edge interface requires that its traffic to and from its Edge interface be routed with no NAT applied.

you have to assign A/V external interface with a public IP address(no NAT) and connect to check the issue.
The Edge external adapter should have three (publicly routable) IP addresses — access, a/v, and web conf, and in that case, you should want default gateway on external interface pointing to your ISP

If the access, WebConferening Edge server have internal IP and using NAT
while A/V Edge server uses public routable IP address, it will rises
problems in this configuration. If we have defined two gateways in the
routing table, when internet request is coming, we unable to route it to
the correct gateway and it will cause problem. Thus we can only configure
one gateway in this configuration.

To workaround this issue, please either assign another two public IP
addresses for Access and Web Conferencing Edge servers, or install the A/V
Edge server in a separate server.

If the issue persists,  perform the following steps to test the issue:
1. Make sure necessary ports are open correctly
Policy Rules
Local Port: 443 TCP (STUN/TCP)
Direction: Inbound and outbound STUN/TCP media communications
Remote Port: Any
Local IP: The internal IP address of the A/V Edge Server
Remote IP: Any IP address

Local Port: 5062 TCP (SIP/MTLS)
Direction: Outbound (For authentication of A/V users)
Remote Port: Any
Local IP: The internal IP address of the A/V Edge Server.
Remote IP: Any IP Address

Local Port: 3478 UDP (STUN/UDP)
Direction: Outbound (for internal users to send media to external users)
Remote Port: Any
Local IP: The internal IP address of the A/V Edge Server
Remote IP: Any IP Address
Note: If you are using ISA Server as your firewall, you must configure the
rule for send/receive

Following ports should be opened for A/V edge server external interface.
Local Port: 443 TCP (STUN/TCP)
Direction: Inbound (for external users access to media and A/V sessions)
Remote Port: Any
Local IP: The external IP address of the A/V Edge Server
Remote IP: Any IP Address

Local Port Range: 50,000-59,999 TCP (RTP /TCP)
Direction: Inbound/Outbound (for media transfer)
Remote Port: Any
Local IP: The external IP address of the A/V Edge Server. This IP address
must be a publicly routable IP address.
Remote IP: Any IP Address

Local Port: 3478 UDP (STUN/UDP)
Direction: Inbound (for external users connecting to media or A/V sessions)
Remote Port: Any
Local IP: The external IP address of the A/V Edge Server
Remote IP: Any IP Address
Note: If you are using ISA Server as your firewall, you must configure the
rule for send/receive

Local Port Range:  50,000-59,999 UDP (RTP/UDP)
Direction: Inbound/Outbound (for media transfer)
Remote Port: Any
Local IP: The external IP address of the A/V Edge Server. This IP address
must be a publicly routable IP address.
Remote IP: Any IP Address

2. Check the global setting
a. On the Front End Server, open Office Communications Server 2007.
b. In the console tree, right-click the Forest node, click Properties, and
then click Global Properties.
c. Click the Edge Servers tab.
d. Check the A/V Edge Servers, the listed value is ocsedge2007 with port
5062.

Posted in A/V Edge Server, Common Errors, Consolidated Edge | Tagged: , , , , , , , , | 4 Comments »

you are unable to enable the new user for the OCS on ADUC (Active Directory Users and Computers) after introducing the Windows Server 2008

Posted by Mino on October 13, 2008

If you have an existing Windows Server 2003 forest running Office
Communications Server, and upgrade any of its domain controllers to Windows
Server 2008, Office Communications Server will not work correctly; some UI
elements will disappear, and you will be unable to add more Office
Communication Server servers or pools. To resolve this issue, you simply
reissue the command to prep the Active Directory forest for Office
Communications Server.

To do so using the user interface, use the Prep Forest option of the
deployment tool

(for more information, see “Running Prep Forest” in the Microsoft Office
Communications Server 2007 Active Directory Guide).

To prep the forest using the command line, use the following command:

LcsCmd.exe /forest /action:ForestPrep

After doing this, please check if the issue still exists. For more
information, please view the URL below:

Windows Server 2008 Support
http://technet.microsoft.com/en-us/library/cc707718.aspx

Then please uninstall and reinstall  the OCS 2007 administrative tools on
the Windows 2008 domain controller. To do so, follow the steps below:

1. Insert the OCS 2007 installation CD media on the Windows Server 2008
domain controller .
2. Lunch the Installation and select to install the Administrative Tools.
3. After the Administrative Tools installation finished. Please check if you
could enable users for OCS 2007 from ADUC.

Reference:

Office Communications Server 2007 Document: Supportability Guide
http://www.microsoft.com/downloads/details.aspx?FamilyID=f8cc9b59-225f-425d-bd3a-e506396c6207&DisplayLang=en

Posted in Common Errors | Tagged: , , , , , , , , , | 1 Comment »

Microsoft Unified Communications endpoints

Posted by Mino on October 12, 2008

I have been testing some Nortel UC endpoints in my office and they are doing great , i already got them beside our CIsco 7940 IP Phone and let me say that i stoped using the Cisco and enjoying my LG-Nortel color phone .

Those Endpoints either are standalone IP endpoints with Communicator built in or as USB handsets that are driven by Office Communicator on the desktop.

IP Phones

1- The LG-Nortel IP Phone 8540 is an intelligent IP Phone that helps improve productivity and work performance for information workers

2- The LG-Nortel USB Phone is designed to deliver a high-quality user experience.

3- The NEC UC USB Phone is a USB device that can be plugged directly into a PC USB port, enabling high-quality wideband sound

4- The Polycom CX200 Desktop Phone helps to enable hands-free calls with remarkable wideband voice quality from a PC.

5- The Polycom CX700 IP Phone is a standalone IP phone with remarkable wideband voice quality and large touch-screen color display.

6- The ViTELiX VX-200 helps turn a PC into a multifunctional, high-quality telephone extension.

7- The ViTELiX VX-100 helps turn a PC into a multifunctional, high-quality telephone extension.

8- The ViTELiX VX-200 Duo helps turn a PC into a multifunctional, high-quality telephone extension and has an additional standard telephone socket at the rear.

9- The Jabra GN9330 USB Headset is among the first wireless office headsets to offer true wideband audio

10- The LG-Nortel Bluetooth Headset is a wireless solution helping users to make or receive calls on their PCs without speakerphones

11- The Polycom CX100 Speakerphone helps to enable hands-free calls with remarkable wideband voice quality from a PC

Posted in Phone Edition | Tagged: , , , , | 1 Comment »

Microsoft OCS 2007 R2-New Version ( Updated )

Posted by Mino on October 12, 2008

There will be a new version announced in November 2008 and released in January 2009, this will be Office Communications Server 2007 R2and one major difference will be it’s transition to a 64bit ONLY platform a la Exchange 2007. This version will transpose your voicemails to text so you can still access them even if in a meeting (or the quiet car of a train..) among other new features.

OCS 2007 R2 will also have more Telephony style features including the ability to hunt groups…

There will then be a completely new version-OCS 2009/2010 (probably 2010)-released to coincide with the availability of Office 14. This along with the expected release of Sharepoint 2010, will help bring a more unified feel to the Office family. It is also expected that this new version will contain inbuilt translation services so if you receive an email in say Spanish, Exchange can read it back to you in English

 

Updated :

Office Communications Server 2007 R2 Features:

The most exiting feature, is the “one number calling” concept. It has been introduced in the original Unified Communications wave in the fall of 2007, but in the R2 build, it should be here. What to expect is not to say, but as I understand it will be a more simplified process of calling UC enabled users. I expect there to be more logic in OCS to how one person can be contacted.

LiveMeetin dial-in is another requested feature, which should allow users to have a choice of using the LiveMeeting client audio or dialing direct to the meeting to get Audio access.
We will see more presence information in more applications

The Communicator Web Access will be upgraded to allow application sharing the within the web application (however this is done…..)

We are also looking at an “attendant console” which will be some kind of switchboard for forwarding calls and so on. This is a feature often used by a front desk or service desk, and will give them the joy of presence information and VoIP.

Also a telephony queue system should be included, and will give people dialing in to the system, access to a touchtone menu to have their calls forwarded to the right department/person and so on.

The TAP program has started June 2008, and the new R2 version will be released to companies in the program.

The OCS 2007 R2 product should be released December 2008 or January 2009

Wave 13
This is the internal name for Office Communications Server 2007 R2 at Microsoft. The “wave” indicates that we can expect more than just e few additional features in this release, and from what i have seen and heard so far, this will be true. Wave 14??? Yes there is also a Wave 14, most likely to be OCS 2009.

64-bit
Its official now. The OCS team is now openly discussing the next release on their blog, and its confirmed that OCS 2007 R2 will be 64 bit only. Rumor has it that some components might still need to be 32 bit, like the Communicator Web Access.

BETA
There has been rumors of an public beta of Office Communications Server 2007 r2, but there is none out there yet. I am not sure we will see a public beta of OCS 2007 R2, because of the limited time until its release. The current beta program is running as an TAP program (Technology Adoption) and is out there for selected customers mostly in the US. There have been inside rumors of a second program, but I’m not sure this will be public.

Source: Richard Gibbons  on http://richfrombechtle.wordpress.com/2008/10/06/microsoft-ocs-2007-r2-new-version

Posted in Miscellaneous | Tagged: , , , , , , , , , , | 2 Comments »

ConfigUpdatesServer.vbs script might result in the error “ERROR: OCS Common Files not found in registry”

Posted by Mino on October 12, 2008

During configuration of the OCS 2007 Software Update Service you need to run the ConfigUpdatesServer.vbs script. However running the script might result in the error “ERROR: OCS Common Files not found in registry”.

If you are using a 64-bit version of Windows 2003 the error can be caused by running the command with the 64-bit version of cscript and since OCS 2007 is not a native 64-bit application it stores its registry information in the 32-bit area of the registry.

To overcome the problem use the 32-bit version of cscript found in c:\windows\syswow64.

Posted in Common Errors | Tagged: , | Leave a Comment »