My post with lots of Lync 2010 error messages is my highest-rating page, and I’ve been meaning to start an equivalent collection of Lync 2013 messages. And so it begins.
Jump to the relevant section headings or just ^F to search for your specific error:
Signing-In
Contact Management
Instant Messages
Voice / Phone Calls
Skype
Continue reading ‘Decoding Lync 2013’s Client-Side Error Messages’ »
The contents of Cumulative Updates are like a bag of mixed lollies – everyone seems to have a different favourite.
Mine just happens to be the first one listed in this sticky collection of kb’s – because (in this case) I’m aware of customers plagued by dodgy address book entries since their Lync 2013 was commissioned.
What’s your favourite?
Continue reading ‘Lync 2013 Client Update – November 2013’ »
Hot on the heels of the v5.0.0 release comes v5.0.1, and with it, a chance to finally take the .CAB updating process for a test drive!
(There’s a caveat I’ll get to later, but at least I have your attention now).
Every so often a customer will ask me to configure a recording of ringback tone as a Response Group’s MOH source. Their argument is that they don’t want their callers to be placed on hold or appear to be stuck in a queue, so they prefer them to be played ringback tone until their call is answered or they abandon.
Complying with this request will put you in breach of a number of clauses in AUSTRALIAN STANDARD AS/CA S002:2010 “Analogue interworking and non-interference requirements for Customer Equipment for connection to the Public Switched Telephone Network “.
The relevant sections are from 5.3.4 “Supervisory Tones” and 5.3.5 “Automatic Operation”.
Clause 5.3.4.1 defines three “Pre-answer supervisory tones”: ringback tone, busy tone, and the lesser-used “number unobtainable” (NU) tone.
Here’s Clause 5.3.5.3.2 verbatim. The bold “shall” is from the standard. (In case you’re not familiar with Australian Standards, clauses that use the words “shall” or “shall not” are mandatory, whereas other terms including “should” are recommendations only).
CE incorporating automatic answering facilities shall acknowledge the answering of incoming calls from the PSTN by— (a) the transmission of an appropriately worded stored voice or synthesised voice message; or (b) the transmission of one burst of answering tone of 2100 Hz ±15 Hz for a minimum of 2.6 s up to a maximum of 6.0 s, if a calling tone (CNG) as defined in ITU-T Recommendation V.25 [22] has not been received from the originating CE within 2.5 s. The answering tone should be in the range from –7 dBm to –13 dBm; or (c) a post-answer tone dissimilar from a PSTN dial tone, PSTN ring tone, busy tone, or NU tone, as described in Appendix A.
Points (a) & (c) are the clinchers here. (a) states you’ll be in the clear if you play a greeting to the caller first, however if you don’t (as the RGS will permit) and you just throw the caller to your ringback MOH, you’re in breach of point (c).
Continue reading ‘Ringback tone as your RGS MOH violates the Australian Standard’ »
Uploading pre-produced audio recordings into Lync or Exchange can sometimes be a challenge. I’ve previously documented the audio file formats that Exchange and Lync require, and it’s relatively easy to reformat files with a digital audio editor like Adobe’s Audition or Goldwave.
There are however a few circumstances where this isn’t possible – like setting the greetings in an Exchange UM-enabled mailbox. At other times you might not have a network connection, and an over-the-phone method is your only option (e.g. using Exchange’s Telephone User Interface – the TUI – to change an auto-attendant’s greetings).
There are many ways of interfacing between your audio device and the phone lines. A not-uncommon kludge I’ve encountered in the field is to use a Music On Hold line isolation unit (LIU) in parallel with a phone, with the phone on handsfree and muted so that you can navigate the DTMF menus and hear that’s going on without any ambient or background noise leaking into the recording.
I’ve long had a soft-spot for my old ETI-734 “Landline interface”, but it requires an analog phone line, and they’re becoming harder to come by (and that’s probably a good thing!).
A colleague recently introduced me to the Trillium family of telephone recording adapters, and I splurged and invested in the “REC/A-ADPT-USB” you see pictured below.
From this… |
… to this! |
 |
 |
| The ETI-734, published in ETI Magazine, May 1983. | The Trillium “REC/A-ADPT-USB” |
Continue reading ‘Review: Trillium Telephone Recording Adapter’ »
There are MANY blog posts offering you a cure for this one, all of them focussing on the password for the reporting services account, and ensuring it’s set correctly and to never expire (here, here & here are just some examples).
An error has occurred during report processing. (rsProcessingAborted)
Cannot impersonate user for data source 'CDRDB'. (rsErrorImpersonatingUser)
Log on failed. Ensure the user name and password are correct. (rsLogonFailed)
For more information about this error navigate to the report server on the local server machine, or enable remote errors
Continue reading ‘Lync Reports: Cannot Impersonate User For Data Source’ »
The latest Lync 2010 Client updates have hit the streets, taking it to version 4.0.7577.4409. There are a few interesting fixes:
To round out the big week of updates, here’s the latest server update for Lync 2010 .
The server release takes us to 4.07577.223. Sadly, there are NO specific fixes called out in this update.
Wow – seems just about EVERYTHING’s had an update this week. Now it’s the LPE’s turn.
Oct 24th: Ooh – a second sneaky LPE firmware update in October. Same KBs, same download links, but now 4.0.7577.4414.
This cumulative update resolves the following issues:
This update takes Phone Edition to 4.0.7577.4411 4.0.7577.4414. Download the relevant CAB files from here:
And HERE’s PAT’s great “New-CsFirmware.ps1″ script to upload the new CABs for you.
(Thanks to http://www.oiboran.com/ for posting the updated version).
After now several false starts, we have a re-re-release of the September Lync 2013 Client update.
This is the update that introduced speck-checking to Lync IMs, reinstated the old “chasing its tail” circular OCS presence icon in the tray, and – my favourite – “paste special”.
In its current incarnation it’s designated 15.0.4535.1510 with a release date of October 8th – although the two download links used for this post only resulted in “.1507” as at this writing (10th Oct).
2883716 Presence status isn’t updated based on Exchange calendar in Lync 2013
Assume that you install the September 2013 update package for Microsoft Lync 2013 that is mentioned in update 2825630. In this situation, your calendar information and OOF information aren’t synchronized between Microsoft Exchange and Lync 2013. For example, when a meeting is scheduled in your Outlook calendar, the following issues may occur:
Continue reading ‘Lync 2013 – September 2013 Client Update (take 3!)’ »