Archive of posts filed under the Ribbon / Sonus category.
The Mk-II Safety Net for Lync Gateway AD-Lookups
My August “Safety Net for Lync Gateway AD-Lookups” plugged a sometimes embarrassing hole in the AD-lookup process, but it still left a smaller one. Whilst it ensured a user was EnterpriseVoiceEnabled before the UX would send a call to them, it didn’t cater for those deployments where the user’s msRTCSIP-Line number was in the “;ext=” …
Continue reading ‘The Mk-II Safety Net for Lync Gateway AD-Lookups’ »
A Safety Net for Lync Gateway AD-Lookups
Superceded 12th Nov2012 by the Mk-II. A not uncommon user-misconfiguration for a Lync user is to find their account possessing a LineURI (their “msRTCSIP-Line”) telephone number, but for them to not be enabled for Enterprise Voice. This more commonly occurs in the early stages of a deployment (ahead of cutover), or as the on-site admins …
Continue reading ‘A Safety Net for Lync Gateway AD-Lookups’ »
Configuring a Tenor FXS Gateway for HOTLINE operation
Long-thought impossible, it turns out that you CAN configure an NET Tenor (nee Quintum) FXS gateway for HOTLINE operation. Here’s how.
Calling a busy Tenor port fails with SIP 503 instead of 486
The NET Tenor appears to have a bug in its “108 Routing” (a feature enhancement I wrote of here and here). If you make a call to an FXS port that’s busy, the Tenor reports “SIP/2.0 503 Service Unavailable” instead of “SIP/2.0 486 Busy here”, and this is reflected back to the calling party. A …
Continue reading ‘Calling a busy Tenor port fails with SIP 503 instead of 486’ »
NET UX2000 SIP Override Tables
Updated 12th December 2011. (Scroll to the bottom) We’ve found here in Oz with the UX that occasionally a random failure code from the carrier is enough to block the entire gateway. The NET faithfully interprets the applicable standards, mapping the ISDN failure messages to their SIP equivalents, then sends the resulting message to Lync. …
Tenor “108 Routing”
The NET (nee Quintum) Tenor gateway family has recently seen a functionality injection with the introduction of what they’re calling “108 Routing”. Until now the Tenor has had some limitations in its routing capabilities. One such restriction was that the outbound (IP) destination was either H.323 or SIP – you could never run both in …