What are the correct normalization rules to enable dial-out from a Lync conference bridge to Cisco Callmanager 7.1.5 extension?

Hi.  I need to create the proper normalization rules in Microsoft Lync to enable dial-out to internal four digit extensions on a Cisco Communications Manager 7.1.5 phone system.  The numbers in Lync are stored in E.164 format (+1 (262) 555-0123).

I have built normalization rules which strip all but the last four digits of the number to dial, but the call still fails in Lync, with the error that the number is not in service.  See the attached file that contains the rule.

Does anyone have experience with bridging a Lync (or OCS) and Cisco voice environments that knows how this should be setup?


 screenshot of normalization rule.
mptcmanageAsked:
Who is Participating?
 
MikeKaneConnect With a Mentor Commented:
I use these 2:
^\+1222333(79\d{2})$   becomes    $1       (strip off all but the last 4)
^\+(\d*)$  becomes                           9$1     (i use 9 for an outside line)

The 1st one takes any e164 that starts with +1222333 and leaves the last 4 which is are the extensions.   So +12223337001 becomes 7001.  

The 2nd one takes every other number and tags on a 9 to go outbound.   So +12223335555 becomes 912223335555.  

That's all I needed.   Your setup may be different, especially if you need to route out to other SIP trunks for remote branches.
0
 
MikeKaneCommented:
I had this EXACT same issue.   I was using normalization to strip off all but the last 4 of a E164 formatted number to send to the SIP trunk to CUCM.    I discovered that this does not work.    Instead, Use normalization to format everything LYNC sends to a e164 number +12223334444 and route this through the SIP trunk.   Then on the sip trunk, use translation rules to change it to a 4 digit extension here....     I banged my head over this for a week.  


So on the normalization rules, I use:
National                   ^1?([2-9]\d\d[2-9]\d{6})(\s*\S*)*$                     +1$1
International      ^011(\d{7,})$                                                             +$1
7xxx Extensions      ^(7\d{3})                                                     +1222333$1
NA-ServiceCodes      ^([2-9]11)$                                                     $1

This way, everything that is dialed becomes a +12223334444 style number.     In case someone just dials a 4 digit extension, i.e. 7344, this also becomes a full E164 number.  

Then on the SIP trunk config, use a translation pattern to match
(assume 222 is areacode and 333 is prefix)
^\+1222333(79\d{2})$   becomes    $1       (strip off all but the last 4)
^\+(\d*)$  becomes                           9$1     (i use 9 for an outside line)
That way the trunk handles stripping off the extension and adding a outbound prefix for everything else.  


Hope that helps.


0
 
mptcmanageAuthor Commented:
This is a good start.   I have internal four digit extensions working.  What do you translation patterns look like to get external calls routed to the PSTN?
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
mptcmanageAuthor Commented:
Hmm.  The first rule for internal extension works well.  The second rule for outside calls does not work, even to custom numbers that are already properly formatted.

Any advice?  I'm a Lync novice.
0
 
MikeKaneCommented:
Do you have any other rules in there?  

On that rule, I assumed the '9' would be the number to get an outside line.    Is true in your environment.    From a desk phone on CM, what would a sample oubound number look like.     On the CM, do you have and translation patterns that could further adjust the number.      On the PSTN router, you should run some debugs so show outbound dialed numbers and see if they are coming across with the proper format.   For example "debug isdn q931 detail"    then "term monitor" to watch the packets.(Don't leave debugging on indefinitely)
0
 
mptcmanageAuthor Commented:
We do use 9 for outbound access.  A sample outbound number is 9-1-262-334-3413.  There are minimal translation patterns on CM and they do not change the number.  I'll have a look at the router to see what digits are being sent, if any.
0
 
mptcmanageAuthor Commented:
I don't see any digits making it to the router.  This could be in the css and partition config, which I'll have to look at tomorrow.
0
 
MikeKaneCommented:
Any luck today?
0
 
mptcmanageAuthor Commented:
Not yet.
0
 
MikeKaneCommented:
Updates?
0
 
mptcmanageAuthor Commented:
The problem is in CallManager.  This will suffice for Lync.  I will post the complete solution once testing is complete.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.