Mino – The UC Guy

Microsoft Unified Communications Blog

Archive for the ‘Phone Edition’ Category

PreCallDiagnostic Tool

Posted by Mino on September 21, 2009

The PreCallDiagTool is an application that reports expected audio quality as it relates to the network effect. The tool should be installed on any desktop or laptop PC that suffers from inconsistent network connection quality. The PreCallDiagTool can provide a quick check of the current network conditions and also preserve a history of quality data to let users profile their network performance over time or other conditions. The tool is particularly useful for home/mobile users and users using WIFI access points.

The tool is available for download here: http://www.microsoft.com/downloads/details.aspx?FamilyID=f16ab4c2-353f-4c9b-b353-22a656c03c9b

Monitor

Advertisements

Posted in communicator client, Mediation Server, Miscellaneous, OCS 2007 R2, OCS Tools Kit, Phone Edition | Tagged: , , , , , , | Leave a Comment »

No Name Appears When Callings from OC to Cisco or vice versa

Posted by Mino on August 10, 2009

One of the frustrating drawbacks when Implementing OCS enterprise voice integrating with Cisco Call Manager or other PBX is that No name would appear in Communicator 2007 when a telephone user calls a Communications Server 2007 user or vice versa .

The only solution by then was to place a media gateway in the middle between mediation and IP-PBX and use a translation feature built in the media gateway to edit the packet header and add Caller Name before sending it to the PBX.

But Finally Microsoft has listened to my prayers and they have released July fix for OCS 2007 R2, once they were released our team started to do the testing in our LABs. At the beginning things didn’t work fine but in the end it worked and it appeared that we only applied the server side updates while the KB 971844 includes Office Communicator update too.

However, even with these fixes, this don’t send display name by default. So, this configuration in KB 972721 will be also necessary. Below are the snapshots taken by our Engineer Amr Nassar who has worked on this and successfully made it work after applying those Fixes.

Calling from Office Communicator R2 with ext 6000 to Cisco IP Phone with ext 10000

From OCS

Calling from  Cisco IP Phone with ext 10000 to Office Communicator R2 with ext 6000 

From Cisco

But let me also share Microsoft explanation on why this problem happens in the first place and what these updates fix?

Problem Explanation:

When a Private Branch Exchange (PBX) telephone user calls a Microsoft Office Communications Server (OCS) 2007 R2 user, the calling party name that exists in PBX is stripped at the OCS 2007 R2 Mediation Server. Because the PBX telephone user does not exist in Active Directory, no name appears in Microsoft Office Communicator 2007 R2

This problem occurs because the OCS 2007 R2 Mediation Server does not forward the display name information from the Unified Communications (UC) side to the gateway side. Therefore, the Communicator 2007 R2 client does not receive the display name information.

Update 970679 introduces functionality for the Mediation Server role of Communications Server 2007 R2 to forward Display Name information that is part of the From header between its gateway side and its proxy side.

A file called MediationServerSvc.exe.config should be created in the Mediation Installation Directory which be default is at  %programfiles%\Microsoft Office Communications Server 2007\Mediation Server

This file should contain.

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

Posted in AVAYA, Cisco 4.x Integration, Cisco 5.x Integration, Cisco 6.x Integration, Cisco 7.x Integration, communicator client, Mediation Server, Nortel CS1000, OCS 2007 R2, PBX Integration, Phone Edition, Quintum's gateways | Tagged: , , , , , , , , , , , , , , | 3 Comments »

How to Fix Exchange UM Certificate errors when Integrating with OCS 2007

Posted by Mino on May 19, 2009

Typically When Exchange 2007 is installed, it generates a self-issued certificate for use with IIS, SMTP, and SIP (if you’re using UM).  This certificate generally isn’t ideal for Outlook and OWA clients because it’s not trusted by any machines except for the Exchange server, and one of the first tasks to do is replace this certificate with one that is trusted by the user’s machines.

So typically you would request to buy a Public certificate for the Exchange and usually people don’t include the internal FQDN of the servers in this request.

On the Other Hand when you deploy the OCS 2007 you will require Certificate for each OCS server and this is required for securing the communication internally between OCS to OCS servers and OCS to Client. So you will deploy internal Enterprise CA in your domain to issue the certificates for the OCS , and since this is Enterprise CA so it will be published in the Active directory and it will be trusted by default for all internal domain user computers.

However when you try to integrate the OCS 2007 with the Exchange UM by this design , the first thing you will notice that the Voice mail is not accessible from the Communicator client  and it is giving you communicator error whenever you click on voice mail ,and you will find lots of Certificate event logs and OCS Protocol stack errors on both OCS front end and Exchange UM Server.

The reason behind that is because the Exchange UM server is still using the Exchange Self Signed certificate for its internal name and it is trying to communicate with the OCS using this certificate , and since the OCS doesn’t know anything about this issuer so it drops the connection.

To solve this problem we will have to replace the Exchange UM self signed certificate with one from the same CA that the OCS 2007 is using. To accomplish this task simply run the below command on the Exchange command shell.

New-ExchangeCertificate -GenerateRequest -Path c:\UMrequest.req -SubjectName “c=US, o=Contoso, cn=umsrv.mydomain.local” -DomainName mydomain.local  -PrivateKeyExportable $true

This will generate a request on the C: drive under the name of UMrequest.req  for the UM server internal FQDN umsrv.mydomain.local , open it with notepad and copy the content and then go to the PKI auto enrolment page https:\\pkisrv.mydomain.local\certsrv   to issue the certificate and save it locally .

Then we need to import the certificate to exchange and Enable it for UM service usage , my certificate is saved on the C: drive with the name of UMCertificate.cer

Import-ExchangeCertificate -Path c:\UMCertificate.cer

The last thing we will do is to enable this certificate for UM usage, first make sure to copy the Thumbprint of the certificate that you will see in the command shell then run the below command .

Enable-ExchangeCertificate -Thumbprint 5113ae0233a72fccb75b1d0198628675333d010e –Services UM

Restart UM service and restart OCS Front End Server and now you will get the UM working fine with the OCS and you will no longer see the protocol stack errors.

Posted in Certificates, Common Errors, communicator client, Front End Server, Mediation Server, OCS & Exchange07, OCS 2007 R2, Phone Edition, Unified Messaging | Tagged: , , , , , , , , , , | 3 Comments »

0x2ee7/0 Update error on Old Tanjay Phone trying to update from OCS R2 Server

Posted by Mino on April 10, 2009

Just Another strange problem that kept me awake for 3 days and it was solved by a small action.

I have implemented OCS 2007 R2 Edition Enterprise Front End running on windows 2008, connected to SQL 2008 Backend Server which is also running on windows 2008. The front End is using a file share which is running on windows 2008 too.

I received a Tanjay phone so I had to do the normal steps of updating the firmware to make it work with the R2 , I had a look for sure at the Rui Silva link which really explains in details how the update process goes.

According to the Microsoft document and all blogs you have to do the following before you plug the phone:

·         Create an A record in your DNS with ucupdates-r2.<DNS domain name and point it to your front end server IP or the pool IP

·         Make sure that your domain name is provided into the DHCP scope options 119 and 015

·         Download the latest firmware version, (3.5.6907.0). The downloaded file is a self-extracting executable that contains a .cab archive with all the supported phones.

·         From the Front end server, run the Device Update Service Management Console: open the OCS R2 Management Console, right click the pool and select Device Updater. From the Tools menu, click Upload .cab File, navigate to the .cab file that you want to upload, and then click Open.

·         After the update file is uploaded ,the corresponding firmware can be approved for all devices in the organization by selecting it and then clicking Approve

·         Plug the phone and leave it even without sign in and it will take IP from the DHCP and then asks the DHCP for the Domain name provided in the scope options and after it does that it will go to the DNS and asks for the record ucupdates-r2 under that domain name it received and then it will know from which OCS it should get its updates.

·         If the version of the device is less than 1.0.522.98 ( which is my case ), it will first get updated to an interim build (1.0.522.103) that comes with OCS 2007 R2. This means that, in this case, 2 upgrade cycles are necessary before the device gets the approved/pending build.

Till now all things sounds normal and fine for me and I did all that by the book , however I found that I am not able to take the updates and I am getting on the phone update error (0x2ee7/0) . After some searching I found that this error means “12007 ERROR_INTERNET_NAME_NOT_RESOLVED The server name could not be resolved

Hmmm, Interesting …why would it say so?!!!, ok then I did some more troubleshooting

·         On the Front end I Confirmed that a Virtual Directory named OCInterim is created under the DeviceUpdateFiles_Int and DeviceUpdateFiles_Ext folders in IIS. This folder contains the interim version (1.0.522.103) necessary for devices that are currently with version 1.0.522.98 or lower.

·         I made sure that all these directories doesn’t require SSL , I went to the IIS 7 and clicked on the virtual directories then SSL and made sure that the option require SSL option is not checked

·         I tried to Open a browser and navigate to the URL that contains the update (for example http://ocs.demo.local/DeviceUpdateFiles_Int/UCPhone/LG-Nortel/IP8540/A/ENU/ 3.5.6907.0/CPE/CPE.nbt). I was able to download the CPE.nbt file. A common cause of problems for the Enterprise version has to do with permissions in the shared updates folder. If that’s the case, you’ll get a 500 HTTP error in the IIS log, but in my case it was fine.

·         As I was trying to update a really old version of the software, I made sure that’s not blocked by the Client Version Filter. Using the OCS Management Console, right click the pool name, select Filtering Tools and then Client Version Filter. Edit the OCPhone field to allow rather than block.

·         I used wbemtest on the Front end server and I looked for the string MSFT_SIPUpdatesServerSetting , navigated to InternalUpdatesDownloadURL and  InternalUpdatesStoreURL . They were NULL so I thought that was the problem and I edited the entry to include this InternalUpdatesDownloadURLhttps://FQDN-front-end/RequestHandler/ucdevice.upx   InternalUpdatesStoreURL: http://FQDN-front-end/DeviceUpdateFiles_Int

I was sooo sure it will work and the phone will take the updates but Naaaa , it just kept giving me the same stupid error .

To make long story short, here is what I have tried and it solved my problem , I configured WINS with a new record named UCUPDATES pointing to the front end.

Yes WINS and UCUPDATES not UCUPDATES-R2, this has nothing to do with the DNS A record but in the end it appeared that the phone was too old to communicate well with the DNS and specially that it was not running R2 framework then how would it understand the DNS A record of UCUPDATES-R2 !!!

Once I did that and restarted the Phone, the error is gone and in 3 minutes I found it restarting for the first time and after another 3 minutes it restarted for the Second time and here it is running the latest R2 framework.

Posted in OCS 2007 R2, Phone Edition | Tagged: , , , , , , , , , , , , , , , , | 5 Comments »

Jabra Dial 520

Posted by Mino on March 15, 2009

Any Post starting with this disclaimer means that this post was not written by me however I have liked it and added to my blog. I will also include the link to the original or Similar post to provide credit to the original author.

http://blogs.technet.com/jkruse/archive/2009/02/25/jabra-dial-520.aspx 

I’ve received a Demo unit of the JABRA Dial 520 under the UC Voice program and I have been showing it to our client to get their feedback.

Everyone is very happy with its cool look and the plug and play thing as you don’t need to configure anything once you plug it the communicator will automatically chose it as the default device. You will be able to call any number and click dial so it will open communicator client and place the call.

The voice quality is good but when you receive a call on your communicator client the JABRA 520 will just blink white light without telling you the number of the caller, quite disappointing to me 😦 

But as an overall I like it and will really love it if the screen shows me the number or the name of the caller

 jabra

 

jabra2

Posted in communicator client, Good Articles take from Other Blogs, OCS 2007 R2, Phone Edition | Tagged: , , , , , , | Leave a Comment »

Communicator 2007 R2 Phone Accessibility

Posted by Mino on March 9, 2009

A common request for RFP is support for TTY. What is it? A TTY is a device that enables people who are deaf, hard of hearing, or speech-disabled to use the telephone by typing messages back and forth to one another instead of talking back and forth. In order to communicate, a TTY is required at both ends of the conversation, unless the call is placed through Relay. OCS now supports integration with TTY with OCS R2.

Under options you can turn on tty mode and connect a keyboard to a device such as the Catalina phones for OCS.  I haven’t seen documentation on this yet but I’ll post when I know more.

phone-accessibility6

Posted in communicator client, OCS 2007 R2, PBX Integration, Phone Edition | Tagged: , , , | Leave a Comment »

Tanjay (LG-Nortel) “Cannot download certificate because domain is not accessible. If the problem persists, contact your system administrator”

Posted by Mino on February 20, 2009

I had this problem with the Tanjay new phone when I plugged it to my DHCP network and i was not able to find the problem .

However after little trials i found the below solution.

 Normally there is two ways to logon to Active Directory:

1.       Domain\username

2.        username@domain.local

 

I was getting this certificate error because I was trying username@domain.local  however I have found that if you log into the phone using domain.local\username

 

The phone is able to find the domain and download the certificate.

 

I found this out while doing a packet trace on the phone one day and found this search behavior

 

Netbios AD name: test

UPN Suffix: test.local

DNS Suffix: abc.com – this is given to the phone via DHCP

 So the DNS queries from the phone was this

 

Away from all these complicated trace like stuff, if you want to solve this problem just login with domain.local\username   and it will work fine  J

Posted in Certificates, Phone Edition | Tagged: , , , , , | 6 Comments »

Plantronics Strengthens Unified Communications Portfolio With Its First Phone Handset Optimized for Microsoft Office Communicator 2007

Posted by Mino on February 5, 2009

New Wideband Handset Eases Unified Communications Adoption by Providing a Familiar Option to Professionals

tn-501514_audio1100m_jpeg

.Audio 1100M USB Handset Optimized for Microsoft Office Communicator

SANTA CRUZ, CA–(Marketwire – February 3, 2009) – Plantronics, Inc. (NYSE: PLT) today expanded its growing portfolio of Unified Communication products Optimized for Microsoft Office Communicator with the new wideband .Audio™ 1100M USB phone handset. Plantronics’ unified communication product portfolio also includes corded and wireless headsets, giving IT purchasers a broad selection of PC audio products as they deploy Microsoft Office Communicator 2007.

The Plantronics .Audio 1100M USB phone handset is optimized for Office Communicator 2007 to provide the functionality of a familiar phone interface for business users adopting PC telephony. The .Audio 1100M features a standard, 10-key dial pad combined with call-answer and call-end keys, a visual ring indicator, a speakerphone activation key and ringer volume control. A headset jack is also available on the handset for users who want a hands-free option.

The Plantronics MCD 100 USB speakerphone, also announced today, is an option for those conducting group conference calls via Office Communicator 2007. It provides 360-degree room coverage so more than one person can participate in a PC-based audio conference. To achieve call clarity, the MCD 100 includes acoustic echo cancellation, noise suppression and equalizer algorithms embedded within the product.

 Pricing and Availability

All Optimized for Microsoft Office Communicator Plantronics products are now available and may be purchased through authorized Plantronics resellers. The .Audio 1100M, a USB phone handset, has an MSRP of $79.00. The MCD 100, a USB speakerphone, has an MSRP of $179.00. Announced in September 2008, the .Audio 630M, a multi-purpose binaural headset featuring stereo, has an MSRP of $49.95. The .Audio 615M, a monaural headset, has an MSRP of $44.95. The SupraPlus Wideband USB monaural noise canceling headset has a MSRP of $169.00.

Posted in Miscellaneous, Phone Edition | Tagged: , , , | Leave a Comment »