I've never been a Mac fan (probably due to that chip I'm POSITIVE Microsoft installed in my skull back in the day). However, since they can be found in the corporate environment from time to time, it was inevitable that I would eventually have to deal with an issue with it.
Communicator for Mac 2011 provides pretty much the same features as the PC Lync client, including Enterprise Voice. A few Mac in our office have tried to use the Enterprise Voice functionality, but it never seemed to work as advertised. The documentation kept referring to a phone icon in the client, but all our Mac users had just a microphone icon in its place. They could only make Communicator-to-Communicator calls.
With me being the Mac non-expert that I am, I dealt with the issue in the best way I knew how: Google for help. That turned up nothing (this was a few months ago), so I did the next best thing: I ignored the issue. However, a client had the exact same issue, and thanks to their help (Yanick from Distributel), we've finally got a solution.
Yanick did some digging and found some references to a requirement for populating the Business phone number for Enterprise Voice users to allow Communicator for Mac to work. I found this excellent post from Keenan Crockett at Pointbridge. I won't rehash what he says there, because it describes exactly what to do, with one small but important omission: The phone number you enter in Active Directory seems to have to be in E.164 format (ie +15552221111).
Our phone numbers were entered as 15552221111, and even though we do have a valid, functional Company_Phone_Number_Normalization_Rules.txt file that successfully normalizes numbers to E.164 for Lync, it wasn't enough for the Mac client. Once Yanick and I added the + sign in front of all our numbers, and followed the directions in Keenan's blog (Update-CSAddressBook, delete client address book files etc), the Mac client's screen switched from this:
Communicator for Mac 2011 provides pretty much the same features as the PC Lync client, including Enterprise Voice. A few Mac in our office have tried to use the Enterprise Voice functionality, but it never seemed to work as advertised. The documentation kept referring to a phone icon in the client, but all our Mac users had just a microphone icon in its place. They could only make Communicator-to-Communicator calls.
With me being the Mac non-expert that I am, I dealt with the issue in the best way I knew how: Google for help. That turned up nothing (this was a few months ago), so I did the next best thing: I ignored the issue. However, a client had the exact same issue, and thanks to their help (Yanick from Distributel), we've finally got a solution.
Yanick did some digging and found some references to a requirement for populating the Business phone number for Enterprise Voice users to allow Communicator for Mac to work. I found this excellent post from Keenan Crockett at Pointbridge. I won't rehash what he says there, because it describes exactly what to do, with one small but important omission: The phone number you enter in Active Directory seems to have to be in E.164 format (ie +15552221111).
Our phone numbers were entered as 15552221111, and even though we do have a valid, functional Company_Phone_Number_Normalization_Rules.txt file that successfully normalizes numbers to E.164 for Lync, it wasn't enough for the Mac client. Once Yanick and I added the + sign in front of all our numbers, and followed the directions in Keenan's blog (Update-CSAddressBook, delete client address book files etc), the Mac client's screen switched from this:
To this:
Our Mac users are now able to dial phone numbers from within Communicator for Mac 2011. We're almost completely out of the woods, however we are experiencing one odd issue. Whenever we type a number in the dialpad, Communicator crashes with exception EXC_BAD_ACCESS after entering anything more than 6 digits. We can dial successfully if we select the user's phone number from our contact list. We've got the latest updates installed. Has anyone else seen this behaviour?
Hi Ken,
ReplyDeleteSorry to bother, but is there a way to send you e-mail or would you rather get my questions here?:)
Big Mac client feature difference from Lync client: no E9-1-1 support.
ReplyDeleteYou've gotten farther than we have at our office. Office Communicator 2011 won't even start. OC 2011 crashes on startup with EXC_BAD_ACCESS. The only thing we can tell is that it has to do with enabling the Enterprise Voice profile.
ReplyDeleteAny progress on the error message David mentioned above???? I can't get Communicator to run since I installed it 2 months ago.
ReplyDeleteWe got the same issue with EXC_BAD_ACCESS. I got it working before I installed the latest hotfixes for Lync Server 2010.
ReplyDeleteNow it is not working for user with/without enable enterprise voice.
I have encoutered this problem before. In my case, it is the Office 2011 Outlook not configured to use Exchange, but the Communicator of Mac option the calender/presence integration is enabled. Unchecking such integration resolved by problem. If you have difficulty even to go to the option page, try to set the Communicator's preference "DisableCalendarPresence" to 1
ReplyDeleteTry this http://www.microsoft.com/download/en/confirmation.aspx?id=27748
ReplyDelete