Subscribe via RSS Feed Connect on LinkedIn

Strip Lync Calling Extension (;ext=ZZZZ) on Outbound calls via Sonus Gateway

28/04/2014 7 Comments

Quick post for reference really

Lync users are usually setup with their number in the format “tel:+XXXXXXXYYYY;ext=ZZZZ”

Often, YYYY and ZZZ match and are set mainly for PIN sign in on Lync phones.

On a Lync setup I noticed calls were going out with the calling party set as “+XXXXXXXYYYYZZZZ”, obviously incorrect. No matter how I messed with the rules ZZZZ kept getting appended. I could “hack it” by Stripping to “XXXXXXX” and having the extension appended, but it wasn’t right.

I didn’t initially realise that the Sonus has a specific “Type” match for “ext=ZZZZ” on it’s translation rules called “Calling Extension”. Adding a rule to catch and strip this quickly removed the issue. In this example we actually wanted the calls to go out anonymous.

image

 

image

 

Sonus have documented the process nicely here:

https://support.sonus.net/display/UXDOC31/Use+of+Calling+Extension+in+Transformation+Table+for+ext%3Dxxxx+Input+Value

Useful? Please take a second to shareTweet about this on TwitterShare on LinkedInShare on Google+Email this to someone
Tom Arbuthnot

Tom Arbuthnot

Managing Consultant at Modality Systems
Tom Arbuthnot is a Microsoft Lync Certified Master and MVP. He is a blogger, regular on The UC Architects Podcast, contributing writer to Lync Server 2013 Unleashed and speaker at events such as Lync Conference and The Microsoft UC User Group London. He is currently Managing Consultant at Modality Systems.
Tom Arbuthnot
Filed in: Lync • Tags:

Comments (7)

Trackback URL | Comments RSS Feed

  1. Lasse Wedø says:

    Yes, Sonus has really powerful ways of editing “things” with your call. Calling, called, diversion headers, call forking and more. Which is why I recommend all advanced customers to get at least one. I’m in the middle of a fairly advanced setup myself.

    But for those who do not have one, this can (in 2013) be done within the calling rules of Lync. Edit the “calling number translation rule”.
    Match by (^\+\d+*)(\s*\S)*$ and translate to $1

    Should fix the same thing.

  2. Something of interest: on older versions of Sonus(NET) firmware the logic did not behave like this. If you had an entry to grab, for example, the first 10 digits from the calling address/number field, the extension would be stripped off without having to worry about the calling extension field.

    I don’t recall the exact version when they started to treat the extension as a separate field to manipulate, but when updating SBC’s to that version or above the change in logic can cause a bit of pain… Something to keep in mind if updating a gateway from a very old release.

    There was also a change at some point that changed what .* would match. It used to match “something but not nothing” but was changed to “something OR nothing”. This also had an effect on routing logic.

  3. Thanks Tom, I had this issue, and was trying to understand why Calling Address/Number rules didn’t strip the ext=1234. Thanks for posting.

Leave a Reply