locked
Lost ‘with’ translation RRS feed

  • Question

  • Hi,

    I am trying to get my head round translation rules but keep getting lost and wondered if someone endowed with a RegEx talent could give me a hand.

    Scenario:

    We have a cisco UCM ‘Staying for the forcible future unfortunately, although the seed has been planted’ that Our Lync deployment subtenants using sip. I have done a fair bit of testing with voice interoperability and all the basic call flow, meeting bridges, sy ring all work as expected with single 1 to 1 number mappings.

    But now as more and more people request enterprise voice I have to look at alternatives to burning additional real world phone numbers per user thanks to the E.164 configuration, my initial thought is there must be a Private range “like Class c/b for IP’s” that we could use but I have been unable to find any documentation so think it Is not possible?

    The second thought which is far more likely although would require some more rules would be to have several Pilot number DDI “1 in each range” that we append with ;ext=XXXX/XXXXX “yes 4 and 5 digit numbers by range” and sacrifice, but am a tad lost on how to get this working as expected.

    From testing I have only seen the Pilot number being shown on the CUCM handsets so believe there must be some form of translation required on the Calling Rule so they match with Users CUCM number?

    For instance on CUCM your extension could be:

    7079

    With a Lync Pilot of:

    Tel:+44203171715231

    The user’s number would be Tel:+44203171715231;ext=7079

    CUCM would Sy ring using mobility:

    5231;ext=7079 Or: 203171715231;ext=7079 “if needed”

    And that part works

    However when you ring CUCM extension from Lync from any extension you only see the E.164 number like: +44203171715231 “No ext” where we would ideally see just 7079.

    I would expect the rule to pattern match +44203171715231 with at least 13

    Then remove 13 “^\+44203171715231(\d*)$” and just show the ext but not really sure how to do it and the translation rule builder seems not to support interesting requirements.

    Any pointers would be gratefully received

    Many thanks

    James   

    Monday, August 12, 2013 11:50 AM

Answers

  • Lync is sending +44203171715231;ext=7079 to Cisco but Cisco ignores the ;ext=7079. 

    The Translation rules on the Calling number doesn't translate alpha numeric so you rule would need to use the (\s*\S*)* to match anything after.

    I would do something similar to: ^\+44203171715231(\s*\S*)(\d{4})$ and work with $2 either add + or not depending on requirements

    $1 = ";ext="

    $2 = "7079" or +$2= "+7079"


    Monday, August 12, 2013 2:43 PM

All replies

  • Lync is sending +44203171715231;ext=7079 to Cisco but Cisco ignores the ;ext=7079. 

    The Translation rules on the Calling number doesn't translate alpha numeric so you rule would need to use the (\s*\S*)* to match anything after.

    I would do something similar to: ^\+44203171715231(\s*\S*)(\d{4})$ and work with $2 either add + or not depending on requirements

    $1 = ";ext="

    $2 = "7079" or +$2= "+7079"


    Monday, August 12, 2013 2:43 PM
  • You can modify Lync calling number with Lync Server 2013.

    Check the following link on Lync 2013 Calling Party Number Translation Rules

    http://tsoorad.blogspot.in/2012/10/lync-2013-calling-party-number.html


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Tuesday, August 13, 2013 12:53 PM
  • Perfect, That was exactly what i was after!

    have since configured and tested and I'm seeing what i would expect! 

    Many thanks 

    James 


    Monday, August 19, 2013 7:33 AM