I’ve been bashing at this script for almost 4 years now and the main post’s getting a bit long with the revision history. I’ve taken a leaf from a peer’s book and decided to spin the entire history out into its own post. Whether the ancient history is of use to anyone remains to be seen, but here it is regardless.
| Here’s the main post for this script. |
Continue reading ‘Convert-SonusSbcConfigToWord.ps1 – Revision History’ »
Sonus introduced “Fax Tone Detection” in the SBC 1k/2k v6.1.1 b459, but it has a glitch in it: turn it off and you’ll get 1-way voice.
From their online documentation: Fax Tone Detection
Specifies whether or not the Sonus SBC 1000/2000 system will detect Fax tones produced by the terminating side fax machine. Fax tone detection(V.21 flags) is used when Fax calls are received from TDM to a Fax server and the voice call needs to be switched to a Fax call using T.38. If Fax tone detection is enabled, the SBC Edge detects the Fax tone from TDM and switches to Fax mode (it will initiate a re-INVITE with T.38 support to the Fax Server). If Fax tone detection is disabled, the SBC Edge will pass-through the Fax tones to the Fax server and the Fax server will have to detect them and initiate a re-INVITE to switch to Fax mode with T.38.
I’ve encountered this with ISDN to the carrier feeding SIP to SfB, and from a SIP carriage service to an ISDN PABX. The fix is to ensure Fax Tone Detection is set to Enabled on the Media List. The issue doesn’t manifest itself for SIP-SIP calls.
The issue has been documented as SYM-23041 and is due to be fixed in a future release.
– G.
Determining the number of SIP channels to licence in your new SBC is often based on an educated guess. Many customers migrating to SIP from ISDN have been historically over-resourced for ISDN channels as their carrier (at least here in Oz) typically forces multiples of 10 channels so as to sell a 2MB PRI ISDN as a 10, 20 or 30 channel service. With luck your carrier can provide traffic figures, or a “busy hour” high water mark to note the highest number you’re expected to reach.
Having made that leap of faith you might be a little uneasy when it goes into production, but if you’re using a Sonus SBC 1k/2k/SWe you’ll be comforted to know it keeps a 25-hour rolling window so you can keep an eye on the call breakdown.
From the System / Licensing / Current Licenses page, click “Historical Usage” in the menu bar at the top:
Fixed in this week’s release of Cloud Connector Edition 1.4.2 is an issue where complex characters in your O365 password will prevent CCE from operating (or upgrading) successfully.
You’re prompted to provide O365 Admin credentials with the “Register-CcAppliance” step of the CCE installation process. This commandlet *will* accept a complex password without error, however if you look in “C:\Program Files\Skype for Business Cloud Connector Edition\ManagementService\CceManagementService.log” you might see things aren’t going so well:
CceService Error: 0 : Unexpected exception when reporting status to online: System.Management.Automation.CmdletInvocationException:
Logon failed for the user tenantadmin@tenantname.onmicrosoft.com. Please create a new credential object, making sure that you have used the correct user name and password.
---> Microsoft.Rtc.Admin.Authentication.CommonAuthException: Logon failed for the user tenantadmin@tenantname.onmicrosoft.com'. Please create a new credential object, making sure that you have used the correct user name and password. --->
Microsoft.Rtc.Admin.Authentication.CommonAuthException: Failed to logon with given credentials. Make sure correct user name and password provided. ---> Microsoft.Rtc.Admin.Authentication.IdcrlExtendedException:
Continue reading ‘Complex Passwords OK in Cloud Connector Edition 1.4.2’ »
This March update takes the server to 5.0.8308.987 from January’s 5.0.8308.984. Only two components need updating this time ’round.
Nothing apparently. I can confirm no new PowerShell Commandlets materialised following its installation.
Continue reading ‘Lync 2013 Server Update – March 2017’ »
By my reading it’s been 5 months since our last security update to the Office 2013-based Lync/SfB client, and this one takes us from 15.0.4903.1001 to 15.0.4911.1000. It’s listed as Critical as there’s the risk of remote code execution.
Kb 4013075 “This security update resolves vulnerabilities in the Microsoft Graphics Component on Microsoft Windows, Microsoft Office, Skype for Business, Silverlight and Microsoft Lync. These vulnerabilities could allow remote code execution if a user either visits a specially crafted website or opens a specially crafted document.
To learn more about the vulnerability, see Microsoft Security Bulletin MS17-013.”
This security update also contains fixes for the following nonsecurity issues:
Continue reading ‘Lync 2013 / SfB 2015 Client Security Update – March 2017’ »
Sonus announced the SWe Lite at Ignite in the US late last year and we’ve been anxiously awaiting its arrival. Well, IT’S HERE!
The SWe Lite is the “Software Edition” of Sonus’ well-established Enterprise-grade Session Border Controllers, the SBC 1000 and SBC 2000.
I’m particularly impressed with the look and feel. At a quick glance it’s indistinguishable from a 1k or 2k:
The GA build supports up to 100 SIP calls, 25 transcoded or encrypted sessions and a call setup rate of 10 calls per second. It’s a faithful port of the SBC we’re familiar with, so includes the bulk of the features we’ve come to rely on for years including the powerful AD integration & the invaluable real-time channel monitor (shown above).
Notably absent is inbuilt Music On Hold, although we’re assured that’s coming soon. Check out the datasheet or the page “Functional Differences Between SBC Edge and SBC SWe Lite” for more of the engineering and feature specifics.
Sonus is letting an “unlicenced” SWe Lite carry up to 5 ordinary SIP calls or 3 encrypted/transcoded calls – more on that below. In the screen-grab above I’ve established 3 calls successfully over TLS to Skype for Business and a failed fourth call attempt is what generated the “Failed to acquire licence” you can see in the Alarm View.
I’m on record saying Call Park is my favourite PABX feature, and its great that we have it available to us in Skype for Business.
“Parking” a call transfers it off to a “holding bay” where the caller hears MOH until such time as someone retrieves the call. If they’re left waiting too long a timeout returns it to the party who parked it.
In SfB you initiate the process by clicking Transfer, then selecting “Park the call”. All going well the call vanishes to places unknown and is replaced with a message to say “the call is parked”, and a special “Orbit” number you – or anyone – can dial to retrieve it.
Its utility eclipses that of a simple call transfer when you don’t actually know where you need to transfer the call to, or if you want to securely (or secretly) manage the process. It’s the perfect answer for a range of scenarios:
| Preparation Installation Operation Tips, tricks and traps Debugging |
There’s an old joke that goes “Q: Why do people take an instant dislike to <InsertNameOfUnpopularPolitician>?” “A: It saves time”. And so it is with SEFAUtil.
Without doubt SEFAUtil is an indispensable utility. “Secondary Extension Feature Activation Utility” – to give it its full name – ships in the Lync and Skype for Business “Resource Kit” (“ResKit”) download pack. When correctly integrated into the topology it gives support staff the ability to query, set and cancel all manner of call-forwarding and team/delegation settings from the comfort of their cube, without needing to visit the user or reset their AD password in order to do it remotely (after signing in as that user). It’s a godsend when someone goes on leave unexpectedly or has a catastrophic PC failure with an urgent incoming call pending, and as equally helpful when configuring the settings for executives and other ‘sensitive’ users.
This February 2017 update takes the server from 6.0.9319.272 to 6.0.9319.277 & updates 5 components on my Standard Edition Front-End.