• RELEVANCY SCORE 3.80

    DB:3.80:Dial Plan: Normalization Rules (Not Always Are Applied...) z9





    Hi
    I've found that normalization rules are only applied when you dial manually the telephone number...
    If you dial from Outlook or Buddy List, this normalization rules are not applied
    I need to force apply normalization rules on all cases...

    DB:3.80:Dial Plan: Normalization Rules (Not Always Are Applied...) z9

    Hi,Carlosdlra,
    I agree with Thamara,the ABS normalization rule should not skip the dail plan normalization rule except you didn't include the expected number in it or it's in E.164 format.
    Would you please check your normalization rule in dial plan to see if you have set the rule for the number in your contact?
    In addition,here are two great blog articles about Normalization rule posted by Ken for your reference.
    http://ucken.blogspot.com/2011/01/enterprise-voice-best-practices-in-lync.html
    http://ucken.blogspot.com/2011/10/lync-normalization-rules-rcc-and-you.html
    Regards,
    SharonSharon Shen
    TechNet Community Support

    ************************************************************************************************************************
    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.

  • RELEVANCY SCORE 3.61

    DB:3.61:Dial-Out Conferencing W/Out Enterprise Voice (Normalization Translation Rules) 7s






    I'm having issues with dial-out conferencing applying Normalization and Translation rules. In my production environment I have not deployed Enterprise Voice. When I try to make a dial-out The conference calls you, my normalization rules that I've
    created don't get applied, nor does the translation rule I have defined. I can verify using an S4 log and viewing the SIP Invite.
    I have another instance of Lync 2010 in a lab with Enterprise voice deployed and the same rules configured. In the lab, the normalization and translation rules are applied as expected when trying to dial-out.
    Is this a limitation of the environment when Enterprise Voice is not deployed? Are these functions not available or some how disabled?

    DB:3.61:Dial-Out Conferencing W/Out Enterprise Voice (Normalization Translation Rules) 7s

    Here's a script to do wahat you want, assuming extension is in the IPPhone AD attribute and phone number is in phone AD attribute.

    $enabledUsers = Get-CsAdUser -Filter {Enabled -ne $Null}
    foreach ($user in $enabledUsers)

    {

    write-host $user.Name

    $ext=$user.IPPhone

    $phoneNumber = $user.Phone

    $phoneNumber = $phoneNumber -replace [^0-9]

    if ($ext.length -gt
    0)
    {$phoneNumber = TEL:1 $phoneNumber ;ext=$ext}
    Else
    {$phoneNumber = TEL:1 $phoneNumber}

    Set-CsUser -Identity $user.Identity -LineUri $phoneNumber

    }

    *edited to deal with blank IPPhone

  • RELEVANCY SCORE 3.57

    DB:3.57:Dialing Rules Not Normalizing - Cant Transfer Via Auto Attendant Menu as





    Under Exchange 2010 we were never able to get 4 digit extensions in auto attendant menus to transfer - we would get the the call could not be transferred - returning to main menu message. We specified the whole 11 digit DID instead and
    transfers worked, so we stuck with that for the last couple of years. I now realize the latter worked because our Global Dial Plan in Lync had a normalization rule for 11 digits (but not for 4). It never occurred to me before because we only use User Dial
    Plans and the fact that Exchange normalizes via the Global Dial Plan in Lync doesn't appear to be well documented.
    Fast forward to our Exchange 2013 migration, which is now complete, and all the AA settings came over as they were before and still work. BUT we have our first changes to be made now that the holidays are approaching, and we've discovered that in 2013
    the gui forces you to use the number of digits your dial plan extensions are set for (in our case 4) - it won't accept the 11 digit workaround any more (existing 11 digit values continue to transfer properly).
    The problem with using the Global Dial Plan in Lync to normalize is that we have 3 different user dial plans, and there are some overlapping extensions between them - so the global dial plan won't work for us.
    My understanding is that Exchange dialing rules should be used to normalize the numbers before they get passed to Lync - but it doesn't seem to work. I created a dialing rule
    for number pattern xxxx with 1619683xxxx as the
    dialed number, but it doesn't work. Snooper shows that the plain 4 digits are still getting passed directly to Lync with no normalization, and fail.
    Anyone know how to get the dialing rules to normalize properly?
    Thank you!

    DB:3.57:Dialing Rules Not Normalizing - Cant Transfer Via Auto Attendant Menu as

    Received this gem from PSS:
    You opened a professional case. For professional case, we are not able to open DCR to product team.

    Please open a premier case to us so that I can raise DCR as per your request.

    I am sorry for that . But this is our policy and hoping you can understand.

    If you can not open premier case, I suggest you can use my suggested workaround to use adsiedit.msc to modify the AA transfer menu to bypass this limitation in GUI.

    PSS case # is 113122011043395 in case anyone here has any ideas on how to get this in front of the team. This policy is ridiculous - we can't afford a premier case.

  • RELEVANCY SCORE 3.51

    DB:3.51:Polycom Cx600 Doesnt Apply The Normalization Rules On Lync Server dk


    Hello,

    We have Polycom_CX600_Rev-5 phone with latest version (4.0.7577.4451)
    http://support.microsoft.com/kb/2988181/en-us
    Also we have some normalization rules that removes 2 from numbers starts with 2, thisnormalization rule working fine with Lync client but it doesn't work with the Polycom device CX600.
    When i call this number from Polycom dial pad, the normalization rule applied successfully and the number appears without 2 and the call established successfully.
    But when i call this number by accessing my contacts then choosing this number , normalization rule is not applied and the number appears in this format 2XXXXXXXXXXX and the call ended.
    Please can anyone has a solution for this issue?
    Thank You,

    DB:3.51:Polycom Cx600 Doesnt Apply The Normalization Rules On Lync Server dk

    There are also cases in the Lync client where this occurs, I'd probably class them as bugs, regardless best thing you can do is keep everything in Lync as E164, then strip at trunk or gateway level.Andrew Morpeth
    Lync Server Specialist - Auckland, NZ
    Blog - http://www.lync.geek.nz

    Please remember, if you see a post that helped you please click Vote As Helpful and if it answered your question, please click Mark As Answer

  • RELEVANCY SCORE 3.48

    DB:3.48:Local Speed Dial/Personal Speed Dial ps



    Can someone please tell me the cutoff limits for Local and Personal speed di

    als.

    I thought local in the system could be 99 and personal was 12.

    Client is using Office manager to add local speed dials and it will not allow him to add after 32.  the button is grayed out.

    Is there a setting i must change uc540?

    Thanks,

    7bridgesol

    DB:3.48:Local Speed Dial/Personal Speed Dial ps


    Can someone please tell me the cutoff limits for Local and Personal speed di

    als.

    I thought local in the system could be 99 and personal was 12.

    Client is using Office manager to add local speed dials and it will not allow him to add after 32.  the button is grayed out.

    Is there a setting i must change uc540?

    Thanks,

    7bridgesol

  • RELEVANCY SCORE 3.43

    DB:3.43:Pap2t Takes Long To Dial p9



    Hi All,

    i'm using a PAP2T and it  takes about 5 seconds before it starts to dial. Is there anyway to speed this up?

    thanks

    DB:3.43:Pap2t Takes Long To Dial p9


    You can use # at the end of the number to send the call immediatly.

    You can also adjust interdigit timers and dial-plan to get minimum delay (regional and line menu).

    Regards.

  • RELEVANCY SCORE 3.23

    DB:3.23:Speed Dial zs



    How to add a speed dial in q10?

    DB:3.23:Speed Dial zs


    BlackBerry needs to provide speed dialing on the Q10as it has been on earlier BlackBerry smartphones, by pressing the respective keypad key; rather than going through 2-3 steps to activate speed dial, as existant on the Q10.

    I would rather call BlackBerry's keypad speed dialing on the Q10 as 'slow dialing'.

    Don't get me wrong; I love BlackBerry phones, the Q10 being my 4th BlackBerry phone since 2008.

    BlackBerry are you reading all the posts in this forum?

  • RELEVANCY SCORE 3.19

    DB:3.19:Lync Client Normalization 91


    Hi All
    Today I woke up with a strange problem on Lync. Iam have a normalization rule for 5 digit numbers.
    ^(10\d{3})$
    For some reason, only one number fails. When I dial this number 10210, its getting normalized to 10210. All other numbers starting with 10 are working fine except for this one. Even if I remove all normalization rules, this number still gets translated.
    Testing with Test-CsPstnOutboundCall is successful but from lync client, it fails because Lync Client normalizes the number and adds a to the number hence it fails
    Can someone point in the right direction

    Regards zizebra http://auction.joyoustimes.net

    DB:3.19:Lync Client Normalization 91

    I got the same issue and guess what, the problem is related to the AddressBook norm rules. they are applied before the dialplan norm rules (high priority). Try to manage your addressbook norm rules and your DP norm rules
    best regards

  • RELEVANCY SCORE 3.15

    DB:3.15:Cucm 10 Speed Dial pp



    Hi there,

     

    I just installed a new CUCM v10 in my company,

    I am trying to add Speed Dials using the self care portal but unfortunately it just give me the abbreviated dial option:

    Please refer to the attachement .

    N.B:The entreprise speed dial option is set to true.

     

    Kind regards

    DB:3.15:Cucm 10 Speed Dial pp


    Does the phone have speed dial buttons added?  You should see it on the page with the line configuration options such as forward all settings.

     

     

    User guide- http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/useroptions/10_0_1/CUCM_BK_U263A6A9_00_uc-self-care-user-guide_1001/CUCM_BK_U263A6A9_00_uc-self-care-user-guide_1001_chapter_00.html#CUCM_TK_SBB32D1D_00

  • RELEVANCY SCORE 3.07

    DB:3.07:Field Normalization 1a



    Hello All,

    For field normalization onto the fields which are filled through discovery, is there any process which could be achieved without consuming much of time.

    I just tried achieving this by activating Field Normalization Plugin and tried normalizing the field through aliases and by using rules. The result was positive.

    Question is as of now there are more than hundreds of data which needs to be normalized. Whether the normalized field data captured through an update set/ direct pull by xml file.. could be moved to other instances or is it a good practice to perform this again manually.

    Thanks..

    DB:3.07:Field Normalization 1a


    Hi Samar,

    Better to perform changes manually , i would suggest this is good.

  • RELEVANCY SCORE 3.03

    DB:3.03:Lync With Exchange Um: Wrong Caller Id m7


    Hi,
    I am having trouble setting up the correct translation rules for the caller ID.
    Our SIPprovider always provide numbers without theleading 0 - but that's not really the issue. I catch this with Normalization Rules in the Lync dial-plan. Let's use an example: the caller ID is 91234567 (or 091234567 with leading zero) and with
    dial rules, lync is showing this correctly as 32 9 123 45 67.
    But when the user doesn't pick up, he receives an email (missed call notification) with caller id 91234567. Is there a way to modify this? If there is, where should it be modified?
    - Lync Dial plan translation rules?
    - Lync Sip Trunk configuration translation rules?
    - Exchange UM Dial Plan?
    - ...
    We already tried lots of different options here!

    DB:3.03:Lync With Exchange Um: Wrong Caller Id m7

    Additional Explanation can be found here:
    http://lwocs.blogspot.com/2010/03/fun-with-normalization-reverse-name.htmlMohammad Saeed Abdelaziz | MCSE 2003 | MCTS: Lync, OCS, Exchange2007 | CCNP | UC Voice Specialist http://ms-uc.blogspot.com/

  • RELEVANCY SCORE 3.02

    DB:3.02:Lync External Access Prefix Doesnt Work? 71


    EDIT: Ok, I did a little reading on what this setting actually does: http://ucken.blogspot.com/2011/03/internal-extension-dialing-in-lync.html

    It only causes Lync to ignore rules that are marked as 'internal extension' when 9 is pressed. It has nothing to do with what Lync actually sends to the PBX. Where would I set up what Lync sends to the PBX? Obviously I'd want to normalize
    all numbers to E.164 in my dial plan, how do I normalize those to number that the PBX can route?

    Original Post:
    I have voice/mediation deployed with a direct SIP connection to our IP-PBX. For external calls our PBX requires a 9 prefix. I have my Global Dial Plan set with 9 for the external access prefix, however it doesn't seem to be applying it to calls sent to
    the PBX. The only way I can get external calls working is with one of my normalization rules:
    Pattern: ^(\d{10})$
    Translation Rule: 9$1
    So any 10 digit long distance number dialed will be prefixed with a 9 and sent to the PBX and completed successfully. As soon as I remove the 9 from the rule (while still having 9 set as the external access prefix on the dial plan) it no longer works.
    I'd prefer to keep the 9 out of my normalization rules, why isn't the external access prefix set in the dial plan working?

    DB:3.02:Lync External Access Prefix Doesnt Work? 71

    Hello,

    can you tell me what exactly you did, in dial plan, normalization rules, voice policy and trunk configurations,
    As I have Internal extensions was working fine, but my issue in the External calls to/from IP/PbX

    Best Regards, TT

  • RELEVANCY SCORE 3.00

    DB:3.00:Normalization Rules For Countries 9s


    Where can I find normalization rules for the most important countries? It is very difficult to configure all the rules for the different countries.

    DB:3.00:Normalization Rules For Countries 9s

    I'm in Germany too :-)
    You will need a normalization rule for international calls: starts with 00, remove 2 digits, add and another one for national calls: starts with 0, remove 1 digit, add 49
    The rule with 00 must be above the other rule, otherwise the Inland rule would also match on numbers startung with 00. This can also be avoided by creating the rule for national calls like starting with 0[1-9], remove 1 digit, add 49
    Johann (Berlin)Johann Deutinger | MCITP Lync 2010 | MCTS Exchange 2010 | ucblog.deutinger.de

  • RELEVANCY SCORE 2.97

    DB:2.97:Lync Normalization Rules And Internal Numbers kx


    I have the following dial plan and trunk configuration :
    Name : TEST
    Pattern To match : ^(\d{2})$
    translation Rule : 3237777779$1
    Name : BelgInternational
    Pattern To match : ^((\)|(00))?([1-9][0-9]{7,15})$
    Translation Rule : $4
    I have 25 enterprise voice enabled users , of which 2 have the line uri : tel:3237777779;ext=88 and tel:3237777779;ext=50
    I also have a Response Group created using the number 3237777779 (I also test adding ;ext=99 to it)
    When I dial to 323777777988 I get an error AMBIGIOUS CALL 485 plus I see in the logs it is still using the BelgInternational instead of the TEST.

    Where I am doing what wrong ??

    DB:2.97:Lync Normalization Rules And Internal Numbers kx

    Actually, I now created a dialplan, voice policy, pstn usage, route for each of the numbers used in the response group. I only changed the SUPPRESS CALLER ID in every route. This way I can assign different policies to certain users but stil use my sip numbers
    for the response groups.
    This seems to work

  • RELEVANCY SCORE 2.93

    DB:2.93:Initiating Ocs Call From Outlook Page sz


    Hi,When I right-click on a user's name in outlook and initiate a call, the call fails. On further investigation, we noticed that the Addressbook normalization rules are not applied when a user is shown in Outlook window. Is that by design. Does anyone tried this ?We are using OCS2007 released version integrating with Outlook 2003 SP2.I appreciate any input on this!Thanks,Murali

    DB:2.93:Initiating Ocs Call From Outlook Page sz

    Hi
     
    You should detail a bit more what you've done: the different configurations of your Mediation Server are the more important (location profile, normalization and routes)
    The format of the Outlook contacts numbers are also important, you will need to create normalization rules depending on that format.
    I can dial from Outlook contact without any AddressBook normalization use (only rules in location profile)

  • RELEVANCY SCORE 2.92

    DB:2.92:Speed Dial x9



    Hi

    we are using cisco 7902 series ip phone.i want to activate speed dial facility and abbreviate dialing in it,but how to do that.(Cisco Call Manager 4.1)

    Thanks

    DB:2.92:Speed Dial x9


    See the following link regarding configuring speed dial in CCM. The 7902 can have up to 4 speed dials.

    http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a0080094765.shtml

    Hope this helps. If so, please rate the post.

    Brandon

  • RELEVANCY SCORE 2.91

    DB:2.91:Obiee With Normalization j1


    Which type of normalization (which normal form) is using OBIEE ?

    DB:2.91:Obiee With Normalization j1

    OLAP is based on Dimensional modeling. If you need more info ;) read Kimball books on internet :)

  • RELEVANCY SCORE 2.89

    DB:2.89:Configuring Speed Dial mc



    Other than using the web interface to configure speed dial on a 7941/61 IP phone, is there a way to configure speed dial/ auto dial using the phone interface?

    Thanks!

    Marvin

    DB:2.89:Configuring Speed Dial mc


    Hi Marvin,

    Just to add a note to Milans good info, you can configure "Fastdials" via the IP Phone;

    Fastdials

    http://www.cisco.com/comm/applications/CCNP/qlm/7961/index.htm

    IP Phone Services - Built In (Fastdials)

    http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_administration_guide_chapter09186a00803ed6bd.html#wp90868

    Hope this helps!

    Rob

  • RELEVANCY SCORE 2.88

    DB:2.88:Speed Dial Blank For External Numbers sx



    We are using CIPC 2.1.2.0 with Call Manager 6.0.1.2119-1. Using extension mobilty and configured speed dials. Internal numbers work but external numbers are blank when the speed dial button is clicked on.

    The phone button template is the standard IPC SCCP and the buttons are designated for speed dial. The number can be dialed ordinarily.

    External number speed dial do not also work on

    the hard phones.

    DB:2.88:Speed Dial Blank For External Numbers sx


    Try the BUG - CSCsd31071

    Workaround: For issue #2 (See Note below)

    Issue #2 - Exiting Phone with existing Speed Dial BLF

    1. Move the existing Speed Dial BLF to the "Unassigned Associated Items" list, save and close the popup.

    2. Select the Speed Dial BLF link on the "Phone Configuration" page to modify it.

    3. Move the Speed Dial BLF from the "Unassigned Associated Items" to "Associated Items", save and close the popup.

    Note: If BLF Speed Dial is added in the "Destination" field instead of selecting Directory Number from "Directory Number" drop-down list on BLF Speed Dial page, after it is saved, this filed changes to "blank" which is incorrect (a new error). But this field was added. To add this destination, please follow above steps for the workaround to a destination value to BLF Speed Dial field.

  • RELEVANCY SCORE 2.88

    DB:2.88:Blf Speed Dial In Cme 3s



    Hi,

    I am using the BLF speed dial for the operator phone. It seems that the monitoring of the extesion is not working. I am using the extenstion mobility in this system.The BLF speed dial is configured in the user profile.

    Can any please let me know the cause of the problem.

    Faizal

    DB:2.88:Blf Speed Dial In Cme 3s


    silly me.

    You are correct "Presence" was not enabled.

    I just need to read the documentation closer,  it was burried under a SIP presence configuration but it is not part of the SIP-ua configuration.

    Interesting thought thou,  Presence icons work with out the presence service being enabled when using the button monitoring.   but wont work with the speed dial unless the Presence Service is enabled.

    thanks your your help.

  • RELEVANCY SCORE 2.88

    DB:2.88:Contact Card Numbers And Clicking To Dial Behavior xd


    I'm trying to figure out the behavior of clicking the phone number in a user's contact card.
    I've setup normalization rules so that their number in Lync displays as 1 (xxx) xxx-xxxx.
    I setup the dial plan in Lync as such: ^1([1-9]\d\d\d{7})$ with the translation rule as: 91$1
    The call is being sent via SIP to a Cisco Call Manager v8.6 cluster. Call Manager requires a 9 to precede the number to be sent out to the PSTN.
    Now, if I just manual dial the number from the Lync phone interface it works; i.e. 15557891234 is translated into 915557891234 and is successfully sent out to the PSTN. However, if I click on that same number on a user's contact card the call
    will fail.
    I looked at the client logs via Snooper and I see that the failed call, just clicking from the contact card, gives me a 404 error with the To field addressed to 15557891234@company.com. The manual call shows the To field as 915557891234@company.com.
    I'm trying to figure out why that difference is happening. Why, when clicking on the number in the contact card, are the normalization rules not in effect to translate the number to the proper format?

    DB:2.88:Contact Card Numbers And Clicking To Dial Behavior xd

    Glad to be of service. And thank you for the nice words about my blog. Good luck with the rest of it!Ken Lasko | Lync MVP | http://UCKen.blogspot.com | http://LyncOptimizer.com

  • RELEVANCY SCORE 2.88

    DB:2.88:Application Dial Rules For Multiple Regions(Countries) x9



    Hi,

    I am in a process of implementing Application dial rules for Multiple countries who will be using CUCI-Lync for  calls.

    The main concern is the overlapping pattern that are present for the dial plans across these regions.

    I am just wondering whether is there a way to implement Application dial rules as region specific i.e one specific for Australia, one for Hong Kong etc.

    DB:2.88:Application Dial Rules For Multiple Regions(Countries) x9


    Hi,

    I am in a process of implementing Application dial rules for Multiple countries who will be using CUCI-Lync for  calls.

    The main concern is the overlapping pattern that are present for the dial plans across these regions.

    I am just wondering whether is there a way to implement Application dial rules as region specific i.e one specific for Australia, one for Hong Kong etc.

  • RELEVANCY SCORE 2.85

    DB:2.85:Problem With Normalization Rule 19


    Hello!
    I want to normalize a numbers according next rule:
    9038889922 goes to 79038889922
    I had create next Normalization Rule in Dial Plan:
    Pattern To Match:^\(9\d{9})$
    Translation Rule: 7$1
    When I type9038889922 in Dialed number to test field, system output target 79038889922 in Translation rule.
    It seams to be ok, but when i type9038889922 in Test Voice Rouing, system ouput that No Matching Rule Exist.
    I think, rules with plus () does not work, but passes in Dial Plan.

    DB:2.85:Problem With Normalization Rule 19

    Hi, algoreal.
    9038889922 perfectly normalizing to 79038889922by different rule...

  • RELEVANCY SCORE 2.84

    DB:2.84:7 Digit Dialing - Opinions? pk


    So I am working on an Enterprise Voice implementation for a multi-site environment where users can roam between locations. (And they might also be at home). Right now, 7-digit dialing is available on our current phone system, after you press
    9 for an outside line.
    I can use the Dialing Rule Optimizer to create 7-digit normalization rules, but I'm not sure what scope would make sense. Global would not, obviously, but pool, site or user? Does it make sense for 7-digit dialing to only work if someone is physically
    at a particular site? Or if a user's number is in a particular area code, should that user's 7-digit dialing always be the same regardless of where they are? Just looking for any opinions...
    Also in regards to normalization rule precedence. If I have a global dial plan and a site or pool dial plan, do I need to duplicate the rules from the global plan to the other plan, or will the global plan act as a fallback?

    DB:2.84:7 Digit Dialing - Opinions? pk

    An SBA is actually its own site (a branch site), so it will have its own dial plan. And I'm actually not sure what happens dial-plan wise when you failover to the secondary registrar. My gut feeling is that you'll still use your original dial
    plan rules, because even though your server is down, you're still a member of that site, and hence dial plan.

  • RELEVANCY SCORE 2.84

    DB:2.84:Applying Normalization Rule Over Call Work\Mobile Shortcut In Lync 2010 Client 83


    Hello everyone,
    This is my question:
    I'm using a dial plan includes set of normalization rules, in order to transfer calls to our Avaya PSTN.
    When I manually dial the numbers from the Dial a contact or dial a number filed, the normalization rules are working properly.
    But when i try to make a calls using the Lync contactcall - work shortcut which populated by the ABS, the dialed number is not normalized.
    **I do not want to normalize the Lync server ABS (I want the number to stay written as is and have the normalization rules translatethe numbers only when dialing, the reason for that,
    is because our users will also use those contact cards entries for clarifying phone numbers for dial using land phones, and If I will edit those entries to be shown as normalized, the numbers will not be useable outside lync.

    Is it possible to make the dial plan normalization rules work over the Call Work shortcut?
    For example, If I'll click on a my contact, and click Call and then
    work 44****** it will use my dial plan, and translate the number to what I've determined

    Many thanks!

    DB:2.84:Applying Normalization Rule Over Call Work\Mobile Shortcut In Lync 2010 Client 83

    Thank you very much for the answers, I decided to made some normalizations via our Avaya PSTN, which solved the issue. (So for now, i'll leave the E.164 numbers in ABS as is.)

  • RELEVANCY SCORE 2.84

    DB:2.84:Best Practice For Normalization Rules kf


    Hi,
    I am trying to create normalization rules just 2 of. 1 which allows a user to dial externally and the other to dial an extension of someone internally. The test involves phones rather than the occ and so for normalization of the extension rule I have set
    if a 2 digit number is dialled then do nothing.
    So the Line URI of the user in question would have the full external number assigned to them with the extension tel:0xxxxxxxxx;ext=xx Is this correct?
    Also regarding extensions this test lab I am creating is using a gsm router and so doesnt have extensions am I correct in thinking that OCS will manage the extension side of things?
    Thanks!

    DB:2.84:Best Practice For Normalization Rules kf

    You will probably need more than one rule to dial externally. Can you give more examples of what you want your users to dial and what their phone numbers are? I would highly recommend using the Enterprise Voice Route Helper tool that comes with the Resource
    Kit to help with your rules. Here is aguide for helping with the tool:
    http://www.microsoft.com/downloads/details.aspx?FamilyID=cc5bd675-b91b-4339-8b4b-a11378061c95displaylang=en
    Here is the Resource Kit:
    http://www.microsoft.com/downloads/details.aspx?familyid=9E79A236-C0DF-4A72-ABA6-9A9602A93ED0displaylang=en
    Give us more info and we can help with your rules.

  • RELEVANCY SCORE 2.84

    DB:2.84:Ocs Integration And Dial Rules mk



    Hi all,

    i've the OCS integrated with a CUCM 7.1.3 and all CUCMOC client are working fine. I'm trying to understand the normalization rules that i must to setup.

    At the moment we have configured in the ldap server the numbers in E164 format like +39 049 xxxxx where x is the local number. I've already configured the Application dial rules and the directory lookup dial rules in the CUCM and what still i need to do is to run the COP file for the generation of the xlm files in the TFTP for the CUCMOC. Here is where i've some problem since that i can't find the COP file in the software download area.

    The documentation says to navigate to Cisco UC Integration for Microsoft Office Communicator where i can only find the CUCMOC client, where i can download the COP file for the generation of the dial rules?

    Another question, what steps are required if the ldap server store the telephone number in a private format like 2xxx? Is required the configuration of normalization rules in the OCS for translate the private number in a E164 format needed by the MOC?

    Thx,

    Christian

    DB:2.84:Ocs Integration And Dial Rules mk


    Right, simply download the file. See my other post. (or actually Michaels tip!)

    https://supportforums.cisco.com/message/1214921#1214921

  • RELEVANCY SCORE 2.83

    DB:2.83:Export/Import Of Dialplan / Normalization Rules zj


    I
    would like to export
    the
    dialplan /
    Normalization
    rules(possibly
    via
    Powershell)
    and import it
    on a different
    server
    Lync
    Unfortunatelyi
    can not find a solution.

    Thanks in advance

    DB:2.83:Export/Import Of Dialplan / Normalization Rules zj

    Hi,
    Another way for your reference in the post below.
    http://social.technet.microsoft.com/Forums/en-US/ocsmanagement/thread/8adddc98-9ce1-4160-ac96-b047ad661286/
    Regards,
    SharonPlease 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.

  • RELEVANCY SCORE 2.82

    DB:2.82:Lync 2013 Mobile Client Does Not Use Normalization Rules pk


    Lync Mobile client doesn't apply the normalization role like the desktop client , i hope anyone can help me with this.

    DB:2.82:Lync 2013 Mobile Client Does Not Use Normalization Rules pk

    Thanks guys issue resolved after changing all the normalization rules but till know we don't know why the mobile clients was behaving differently from the desktop one.

  • RELEVANCY SCORE 2.82

    DB:2.82:Lync Normalization - How A Phone Number Gets Normalized And Routed m7


    There's some debate here about how numbers are normalized depending on their source and routed. Can someone help clarify for me?
    Lync client - numbers entered manually here, are normalized via the dial plan rules. When submitted this normalized number is routed via route andtrunk configuration rules. Right?
    OUtlook contacts - these numbers are normalized and routed similar to the manually entered numbers, right?
    Here is the area of debate -- Addressbook numbers - these numbers are normalized from AD and stored in the AB. Since these numbers are already normalized, do they get subjected to the dial plan normalization or not? I believe not. My stand is
    that since they have already been normalized, when you select a number from the addressbook, it is routed via the rout and trunk rules.

    Thanks!!
    Tom

    DB:2.82:Lync Normalization - How A Phone Number Gets Normalized And Routed m7

    Numbers normalized by the ABS are not re-normalized so when you click-to-call Lync will 'dial' the number as it was stored. In the client you will only see the displayed format but if you open up the GalContacts.db file you will see that every entry
    has both a normalized 'display' string (e.g. (312) 555-1234)
    and a normalized 'dialing' string [e.g. 1312551234).Jeff Schertz, Microsoft Solutions Architect - Polycom | Lync MVP

  • RELEVANCY SCORE 2.82

    DB:2.82:Samsung A157 - Set Up Speed Dial dp



    To create Speed Dials, press Menu Address Book Speed Dial List.

    Speed dial number 1 is set to your Voicemail and cannot be edited.

    Any contact that has a phone number field with information in it can be added to a speed dial.

    Scroll to or type in the speed dial number you want to assign a contact to and press the key to set the speed dial.

    Select the contact from your contact list and press the key.

    To make a call using a speed dial, enter the speed dial number at the dial screen and press Send or press and hold down the last digit of the speed dial number to dial the number without pressing Send.

    DB:2.82:Samsung A157 - Set Up Speed Dial dp


    To create Speed Dials, press Menu Address Book Speed Dial List.

    Speed dial number 1 is set to your Voicemail and cannot be edited.

    Any contact that has a phone number field with information in it can be added to a speed dial.

    Scroll to or type in the speed dial number you want to assign a contact to and press the key to set the speed dial.

    Select the contact from your contact list and press the key.

    To make a call using a speed dial, enter the speed dial number at the dial screen and press Send or press and hold down the last digit of the speed dial number to dial the number without pressing Send.

  • RELEVANCY SCORE 2.82

    DB:2.82:Lync Client And Uc Phones No Longer Searching By Number.... m3


    If you enter in the person's last four digits of their phone number, the clients will no longer find them. The dial-plan normalization rules and phone number normalization rules have not changed since deployment.

    Any ideas?

    DB:2.82:Lync Client And Uc Phones No Longer Searching By Number.... m3


    The update is that it still does not work.
    As far as setting things in E.164 format, everything since RTM has not changed. The phone numbers have always been in xxx-xxx-xxxx format and have worked just fine. Now, just so we are clear that the E.164 format is not the issue, we also have all of the
    Exchange UM stuff in E.164 format and they cannot be search by their number either. Something else is the issue.

    We have the same issue. What's funny is, I never realized it until today. Somebody sent an overhead page for me to call a certain number and didn't say who the numberbelongedto. So, I went to my Lync client because I know that it was an on-net DID,
    but got back what Dan is getting...the DID tagged with the location code we use to dial. We, too, are looking for suggestions to modify this so we CAN search by DID.

  • RELEVANCY SCORE 2.81

    DB:2.81:Using Powershell To Add Multiple Normalisation Rules To A Dial 1s


    Hey,
    I have been looking and looking and cant seem to figure out how I can add multple normalisation rules to a dial plan using powershell.
    I have a standard set of 6 or so normalisation rules already created. I would like to create dial plans from powershell and have these rules added.
    Any ideas how I can do this?
    Thanks,
    Andrew

    DB:2.81:Using Powershell To Add Multiple Normalisation Rules To A Dial 1s

    Thanks for all yourinputguys! I'll let you know how I get on with all your suggestions.

    Thanks,
    Andrew

  • RELEVANCY SCORE 2.81

    DB:2.81:Cusp Pre-Normalization Vs. Dial-Peer And Voice Translation Rules a3



    Hi all,

    I was hoping to consolidate as much dial-plan and digit manipulation as possible in CUSP but am having issues finding decent documentation (and examples) on how to effectively utilize pre-normalization policies.   The Telco is delivering 4 digits DNIS/DIDs that need to be expanded to 10 digits and then based on the assigned prefix routed to CVP/ICM, non-agent phones on a call center CUCM cluster, or another cluster altogether. 

    Because of this I am expanding them on the ingress gateway via voice translation rules.  The call center related DNIS numbers are scttered throughout the larger range so there are quite a few exact match dial-peers configured in order to get the correct routing.  This effectively means that the routing decision is made at the gateway ( by assigning the prefix there) as opposed to centralizing it at the CUSP.

    One of the items I could really use is better information on what regular expressions CUSP accepts.  CUSP seems to see the . (period) as a literal rather than a wildcard and does not seem to like what we commonly use in IOS.  Should the regular expression be enclosed in "" as in grep or egrep?

    It would also be helpful to get better details on the "rules of engagement" on how the normalization policies actually work.  If I configure the module as shown below p6980 will work but p6990  will not.  If I change the trigger sequence number for p6990 to 5 then it does fire, but p6980 is then broken.

    policy normalization p6980

    uri-component update TO all user ^698 899222698

    uri-component update request-uri user ^698 899222698

    end policy

    !

    policy normalization p6990

    uri-component update TO all user ^699 899222699

    uri-component update request-uri user ^699 899555699

    end policy

    !

    policy lookup cvp-policy

    sequence 1 cvp-routes request-uri uri-component user

      rule prefix

      end sequence

    end policy

    !

    trigger routing sequence 1 by-pass condition mid-dialog

    trigger routing sequence 10 policy cvp-policy condition in-cvp-enterprise

    trigger pre-normalization sequence 1 by-pass condition mid-dialog

    trigger pre-normalization sequence 10 policy p6980 condition in-cvp-enterprise

    trigger pre-normalization sequence 20 policy p6990 condition in-cvp-enterprise

    Could someone please give me an example of how this would be written for CUSP:

    rule 1 /^698[0-4]/ /899222\0/

    Any help would be greatly appreciated!!

    Many thanks,

    Art

  • RELEVANCY SCORE 2.78

    DB:2.78:Dial Plan Translation Rule ^\+6666$ (Staring With Plus Symbol) Not Working zk


    I have two Dial Plan Normalization Rules in Lync Control Panel - Voice Routing - Dial Plan - Site Scope
    Normalization Rule 1:

    The pattern to match = ^6666$The translation patter = 5001
    Normalization Rule 2:

    The pattern to match = ^\6666$The translation patter = 5001
    When I dial 6666, the call is routed to 5001, but when I dial 6666, the call is not routed to 5001
    Why does TranslationService Lync Server Application does not match the patter for translation?

  • RELEVANCY SCORE 2.76

    DB:2.76:Impact Normalization - Impact Relationship Atrium 8.1 j1



    Hi,

    We are using Atrium CMBD 8.1. I wanted to explore the option of using using Normalization feature "Impact Normalization". As per the documentation if the relationship name matches the OOB Impact normalization rules by automatically Has Impact, Impact Weight and Impact Propagation Model, Impact Direction will be populated when relationships are being imported/created

    We are creating relationships through Atrium Integrator Spoon. The relationship names are maintained as per the relationship naming convention but Has Impact and Impact Direction are not being added when relationships are created.

    Has anybody faced the similar issue in 8.1.?

    DB:2.76:Impact Normalization - Impact Relationship Atrium 8.1 j1


    Hi Raghavendra

    From your post it doesn't looks like you are running any job on the dataset. Unless you run batch job or continuous job or inline mode, normalization will not apply any features. Are you running any jobs on the dataset after data is created?

    thanks

    Murali

  • RELEVANCY SCORE 2.76

    DB:2.76:Normalization Roles + ks


    Hello,

    i have a problem, When a number is composed of a '' for international numbers. I can't translate the number. It's good in my Normalization Rules but
    it's not good in Test Voice Routing. There two pictures to explain/

    My Normalization Rules

    toEscaux_PLUS:
    ^\(\d{4}\d)$
    6000$1

    But in
    Test Voice Routing :

    He can not find my Normalization Rules. Do you have a solution?, Lync does not support the ''? bad Normalization rules?

    Thank you in advance for your reply.

    BastienPironnet Bastien

    DB:2.76:Normalization Roles + ks

    I try with a phone and it's Ok! it's probably a bug in the Test Voice Routing.

    I had a other problem with my dial plan and internationnal call was blocked i had thinking it was a probleme with the '' but I have modifiy my Normalization rules and Trunk configuration and now all is OK.

    Thank for your reply.
    Pironnet Bastien

  • RELEVANCY SCORE 2.76

    DB:2.76:Cant Change Normalization Rules kf


    We upgraded from OCS R1 to R2 (Enterprise Edition). Since the migration I cant change any more the normalization rules. I can edit the location profile and after a normalization
    rule. However the OK button stays grey under edit location profile and I cant apply the changes. When we had both environments (R1 and R2) running in parallelI was able to change the normalization rules using the R1 admin tools. Now we completely
    uninstalled all R1 servers and I still cant apply the changes under R2. Anyone knows where this might be locked?
    Thanks a lot for your replies.

    DB:2.76:Cant Change Normalization Rules kf

    Great, that worked! I can change them using the Voice route helper. Thanks a lot! Strange though that I cant change it directly in the OCS Voice
    Properties. But this workaround will do the trick.

  • RELEVANCY SCORE 2.76

    DB:2.76:Understanding Extensions And Normalization Rules d8


    New to OCS/Lync, I am a bit confused on working with extensions and normilazation rules, I have read several resources and forums, but can't seem to get the overall picture on how to get these to work withlync and the proper format for AD user objects.For
    example, for the most part 90% of users do not have a DID and will have a 4 digitextension, say starting at 2001. With the incoming main office number of (514)333-2222. (USA) Typical user to user internal call would just dial the 4 digit extension.
    So correct me If I am wrong:
    If I follow the E.164 format, for user Joe
    In Lync:
    Line URI: tel15143332222;ext=2001
    Normilzation Rule:
    Looking at the Build Normilzation Rule Box
    Length set to: Exactly 4
    Digits to add: 15143332222
    Results:
    Pattern to Match: ^(\d(4))$
    Translation Rule: 15143332222$1
    Should I check the Internal Extension option?
    As far as the ordering of Normilzation Rules, where should this extension rule be placed, if other standard rules exist such as International, 11 digit, 10 digit,.. rules?
    On the AD User Object, what is the correct format for the telephone field using RFC3966 formating with an extension?
    Say another internal user decides to call Joe using his contact card information populated from lync (either via the Lync client or a device)which displays 15143332222 X 2001, how does lync handle this call, do I need to create another normilzation
    rule to handle this?
    Thanks

    DB:2.76:Understanding Extensions And Normalization Rules d8

    Thanks, I read through that, and also
    http://ucken.blogspot.com/2011/01/enterprise-voice-best-practices-in-lync.htmlwhich is more relevant to lync. I did end up figuring everything out. I'll go through my findings.
    As mentioned above users use a main office number with a 4 digit extenstion, for example Joe's full number would be (514)333-2222 ext 2001, Bobis (514)333-2222 ext 2002.
    Configuring Joe in Lync:
    Line URI: tel15143332222;ext=2001
    I then added a normalization rule so when Joe makes and internal call to Bob he is dialing 2002. What I was getting stuck on is the Normaliztion Rule builder in Lync does not support advance Regular expressions, I had to manually modify the Translation rule,
    Overall it looks like this:
    Pattern to Match: ^(\d(4))$
    Translation Rule: 15143332222;ext=$1
    Dialing 2002 translates to 15143332222;ext=2002
    On the Active Directory Side of things, I used the following format for the telephone field:
    15143332222 x2002
    Created a Company_Phone_Number_Normalization_Rules.txt document under the Lync Share \1-WebServices-1\ABFiles\ directory with your NormalizationAddress Book Rules:
    ##
    ## Normalize all AD phone numbers to E.164
    ##
    \?[\s()\-\./]*1?[\s()\-\./]*\(?\s*([2-9]\d\d)\s*\)?[\s()\-\./]*(\d\d\d)[\s()\-\./]*(\d\d\d\d)[\s]*
    1$1$2$3
    Resulting in phone numbers appearing as: 1 (514) 333-2222
    X2002 in the lync client and device.
    To speed things up I ran a Update-CSAddressBook from the Lync PowerShell, waited about 5 minutes, rebooted my phone, Polycom CX700, signed out of the Lync Client, deleted everything under: C:\Users\%username%\AppData\Local\Microsoft\Communicator
    Everything now works. Comments or suggestions?
    Thanks

  • RELEVANCY SCORE 2.75

    DB:2.75:Can Lync 2010 Softphone/Clients Dial Other Softphone/Clients By Extension? mz


    Hi all,
    I am running through a brand new lync 2010 deployment. We have just a single server for the time being while we perform some testing. The mediation server is synonymous with the other core lync server roles. We have a dialogic dmg 1008
    gateway for inbound/outbound call processing. I was wondering if it is possible to dial other users within the office by extension # instead of finding them in the lync client. The reason is that we intend to replace our entire pbx and would like
    calling parties to be able to dial by extension. I havelooked allover and all i keep finding is how to create normalization rules to send extensions to your PBX sip peer. I can't seem to find anything with the setup of extention to extension
    dialing. Maybe i'm missing something insanely obvious?

    Thanks,
    Paul

    DB:2.75:Can Lync 2010 Softphone/Clients Dial Other Softphone/Clients By Extension? mz

    Hi Paul,
    Yes, you will need to configure the normalization rules, but you do not need to route those normalized numbers to PBX.
    Here is the basic explanation: If you want to dial by extension, the normalized number should match the Line URI of the contact so that the Reverse Number Lookup component can find the user associated with that phone number.
    Below you can find an example, however remember that the correct normalization rule would be dependent on the Tel URI's you assigned to your users.

    Example for 4 digit extension
    User1: 15556664401
    User2: 15556664402
    If you want user1 to call user2 by dialing 4402, then you will need a normalization rule as follows;
    Pattern: ^(\d{4})
    Translation rule: 1555666$1

  • RELEVANCY SCORE 2.75

    DB:2.75:Default Country For Lync Web App Dial-Out pc



    We have enabled dial out for guest users joining conferences using Lync Web App, but we will only route calls nationally--within the U.S/Canada.
    We have also had complaints from several Web App users that dial-out doesn't work, but after talking to them, they didn't select U.S. as the country, so Lync didn't prefix the number with 1.
    Lync Normalization rules do not appear to be applicable to the Web App, as I have a 10-digit NANP match that does prefix 1.
    My question is simple, Can I default the country to U.S?
    Thanks,
    mG
    If a post is helpful, please take a second to hit the GREEN ARROW on the left, or mark as ANSWER. Mark A. Gutowski

    DB:2.75:Default Country For Lync Web App Dial-Out pc

    Hi,
    By design, the Lync Web App users can only Call Me with entering the full E.164 phone number or selecting the country code if s/he did't use a standard E.164 format. The normalization rule can not be picked by unauthorized users
    such as guest.
    Here is another post for your reference.
    http://social.technet.microsoft.com/Forums/en/ocsconferencing/thread/913b6464-442a-4e4d-a73d-d1078b44e737
    Best Reagards,
    Kent

  • RELEVANCY SCORE 2.75

    DB:2.75:How Many Normalization Rules Can I Create In A Dial Plan? 1j


    Hello.
    I'm working in a customer where each lync user extention needs to be configured like a normalization rule, because they don't have any consecutive extention numbers available to assign.
    So, my question is if there is any restriction or limit about how many normalization rules can I create in a dial plan? I need to configure 100 extentions and I need to know if it is posible and if it is posible what disadvantages I could will have.
    Thanks and regards

    DB:2.75:How Many Normalization Rules Can I Create In A Dial Plan? 1j

    Hi,

    You might be thinking of slide 41 of this presentation

    http://channel9.msdn.com/Events/TechEd/NorthAmerica/2012/EXL318

    The comment they make in the presentation is that Lync 2010 CU5 had improvements in this area.

    You can now add more than 100 normalization rules to your dial plan without the call setup time getting to bad, before CU5 every 100 normalization rules would add about 3-5 seconds to the call setup.

    Still Lyncs call setup times are not great compared to other systems (yes, I have compared.) so there are still room for improvement in Lync.

    /mk

  • RELEVANCY SCORE 2.75

    DB:2.75:Ocs 2007 R2 Ignoring Certain Normalization Rules On The Server Side 7p


    Hi everyone,
    I'm working on an OCS 2007 R2 configuration, and I'm having some issues with phone number normalization...
    Basically, because of limitations on the media gateway (old version of Cisco CM)and IT department policies here which don't allow me to modify it's configuration on certain areas, I'm force to have OCS denormalize phone numbers before they are dispatched
    to the media gateway. So, I need the mediation server to send the media gateway the numbers already formatted as they would be dialed internally (for instance, remove 1 and add 9 before external number to get to the PSTN). I realize this type of configuration
    is far from ideal, but it's pretty much the only option I got currently...
    I've setup different normalization rules for this, and everything seemed to be working fine on the client side with office communicator 2007. A number such as 1 555 555 5555, for instance,is changed to 95555555555 by the client and it reaches
    the media gateway correctly. Calls work without issues there.
    My problem appears when normalization needs to happen on the server side, such as when using callforwarding, simultaneous ringingor the forward missed calls features. I noticed that, although calling these kind of numbers from the client worked
    correctly, those other features didn't worked with the same numbers.
    I did some testing with the route helper, which allows to test normalization rules processing on the client and server side. It looks like when normalization is processed on the server side, if the number starts with OCS will skip any normalization and
    directly send the original number to the gateway. The client side always processes the normalization rules, even if the number starts with .
    So, basically my question would beif there's any way to have numbers that start with go through normalization when processed on the server side (as the client side does). I tried the WMI setting for stripping the signon the mediation server
    (which I need anyways because this gateway doesnt support that character), but that didn't help with this problem...

    Thanks in advance,
    Juan G

    DB:2.75:Ocs 2007 R2 Ignoring Certain Normalization Rules On The Server Side 7p

    So my nomalization rules have no ? in them
    but my Route Patten to the Mediation server is
    ^\?(\d*)$
    That might be it, but how do I correct it?
    Eric
    My Question has been moved here
    http://social.technet.microsoft.com/Forums/en/ocsvoice/thread/967e5f9c-67a5-4523-a5be-6360e8c69551

  • RELEVANCY SCORE 2.74

    DB:2.74:Thread: Bordermanager 3.7, Proxy Functions, Access Rules - Content Filtering And Severe Speed Degradation cs


    Need a simple quick answer from anyoner who is familiar with education

    type sites concerning Bordermanager 3.7, proxy functions and access

    rules (involving Novell associated content filtering products). All Ineed to know is a yes or no answer so I can either invest in

    corrective surgery on our servers or ditch and move on to another

    product.

    I.E.

    Do education WANs actually have success using the above? When we use

    our proxy it cuts access speed to near dial-up speeds (down from an

    OC3 fiber line with 3m of direct Internet connection). We only need

    the proxy because it is required by content filtering software.

    Ken

    *******

    Kenneth J. Goncalves, CNE5

    Information Systems Manager

    EASTCONN Regional Educational Service Center

    Information Technology Department

    376 Hartford Turnpike

    Hampton, CT 06247

    http://www.eastconn.org

    DB:2.74:Thread: Bordermanager 3.7, Proxy Functions, Access Rules - Content Filtering And Severe Speed Degradation cs

    Hi all

    I am using BM3.7 and SurfControl in a school environment with a 500k

    satellite connection to the internet, which is happily supporting our

    needs.

    I am getting almost the same speeds throuhg the proxy as I am from a

    PC

    directly connected, any slow down is not an issue here although the

    satellite system dropping off line is, but hopefully this will be

    sorted in

    the next week ( difficult to type with fingers crossed}

    John

    Westonbirt School

    UK

    Craig Johnson craigsj@ix.netcom.com wrote in message

    news:VA.00002482.005c7ec5@athlon3...

    In article 0pdd9vcc0n3rn6spc9jl62u0g9l5o8dnt1@4ax.com, Matthew

    Shuter

    wrote:

    have not heard of any problems with it,

    There is a known error issue (winsock errors), and a patch should be

    coming out soon (from Novell).

    Craig Johnson

    Novell Support Connection SysOp

    *** For a current patch list, tips, handy files and books on

    BorderManager, go to http://nscsysop.hypermart.net ***

  • RELEVANCY SCORE 2.74

    DB:2.74:Speed Dial 33



    Is the Motorola Droid is speed dial capable?

    DB:2.74:Speed Dial 33


    Check te market for "speed dial old school"

    It brings back the old style (program numbers 1-99) to contacts. it cost .99 but is well wort it.

  • RELEVANCY SCORE 2.74

    DB:2.74:Performance With 2000 Normalization Rules px


    I need to know the performance in a environment with 2000 normalization rules on dial plan.
    Company has 5000 employeers

    DB:2.74:Performance With 2000 Normalization Rules px

    Hi,
    Usually , you use Normalization rule for ; International numbers, domesticnumberswith different city codes , and mobile operators numbers, SOS numbers . no need for the big number numbers of all this normalizations rule , because
    two much normalization need to much routing, usage, policies and these all will be very difficult for admins to manage all this.
    even you can start with generic normalization rule , then assign one by one ; like normalization rules for all national calls , then later you can add specific one for landlines, mobile,SOS number and so on.
    Regards,
    Ahmed

  • RELEVANCY SCORE 2.73

    DB:2.73:6125 Dialling Problems (Speed Dial)? mk


    Hello,
    I need help urgently! Phone purchased June 2006, worked well until recently I cannot dial 3 numbers which were in speed dial. I tried without using speed dial codes, still doesn't work. I removed the numbers from speed dial, still I am unable to dial these numbers ONLY. The calls simply do not go through. I can dial all other numbers in my contacts and I can also send text messages to these 3 numbers. Please help me for these are the numbers of my family!!!
    I have since tried another contact's number in speed dial and that works, why won't the old ones work or even with a normal dial!!!

    Thank you.

    DB:2.73:6125 Dialling Problems (Speed Dial)? mk

    Hi Roger,
    I know this might end up getting a bit tedious but have you tried taking note of those contacts and their details, deleting them and then re adding them to your contacts and speed dial? Perhaps there was a bug in the speed dial which has transferred to those contacts. Give that a try... If it doesn't work make sure your software is up to date at www.nokia.co.uk/softwareupdate

    Hope that works

    Stuart



    There is something to be learned from a rainstorm

  • RELEVANCY SCORE 2.73

    DB:2.73:How To Enter Speed Dial Numbers 79



    How to enter speed dial numbers

    DB:2.73:How To Enter Speed Dial Numbers 79


    Hi richtip,

    There is not a speed dial function built into the dialer on the phone, except for the one for voicemail.

    There are some very good suggestions available in this previous discussion, which I found by typing the words speed dial into the big search box on the home page:

    Re: Speed dial on Defy XT?

    ~~~~~

    SouthpawKB, customer since 2011, not a republic wireless employee

  • RELEVANCY SCORE 2.72

    DB:2.72:New Dial Plan Voice Policies Not Taking Effect With Polycom Cx 600 Desktop Phone In Production Deployment, Worked Fine In Testing d9


    Hi,
    We are in the process of Migrating Cisco CUCM Voice Gateway (From another vendor to Cisco).
    The requirement is all internal calls between Cisco IP Phones Lync to be flown through CUCM. Means internal extension to extension. Remaining all calls like Mobile, National, International, Toll Free, Emergency, Shared numbers calling to be routed
    to Cisco Voice Gateway.
    We created the test dial plan, Voice policies, Route and assigned it to couple of user from Lync (2 extensions) and from Cisco side we have taken 2 IP Phones which is pointed to new CUCM. We tested all below scenarios,everything was working fine.

    Lync to Lync Call using internal Extension number – Routed through Cisco new CUCMLync to Cisco Call using internal Extension number – Routed through Cisco new CUCMCisco to Lync Call using internal Extension number – Routed through Cisco new CUCMLync to Hotline Numbers (66XX, 68XX Numbers) – Routed through Cisco GatewayLync to Shared Numbers starting with 600 (Verified the number 600535353) - Routed through Cisco GatewayLync to Emergency numbers Toll Free Numbers (Not verified the emergency Number as we decided to do it at end) - Routed through Cisco GatewayLync to Landline Numbers – Any 7 digit numbers - Routed through Cisco GatewayLync to National Numbers – Starting with 3,4,6,7,8 followed by 7 digits - Routed through Cisco GatewayLync to Mobile Phones – Starting with 05 contains exactly 10 digits - Routed through Cisco GatewayLync to International Numbers – Starting 00 contains at least 11 digits - Routed through Cisco GatewayAll Incoming calls – From Landline, Mobiles, International Numbers - Routed through Cisco GatewayCall Transfer – To another Lync Extension, Cisco Extension, Landline, Mobiles, International NumberConference – with another Lync Extension, Cisco Extension, Landline, Mobiles, International NumberCall Forwarding – To another Number, Voice mailResponse GroupsClick to call – As if user try to place a call by directly click the number from Outlook, Websites will be in E.164 formatDial in meeting – Conference calls are works fine
    But when we roll out to the production we are facing issues listed below
    1) The phones we used during testing are working which is using same dial plan, Voice policy, Route, PSTN Usage. But from production most of the phones are not working (using the same dial plan, voice policy, Route). Also Problem is only with external calls
    as the internal calls are working fine between Cisco Lync even in production (Routed through CUCM) NOTE: All incoming calls are working fine (From international, local, national, extension)
    2) How long its going to take for Lync to push the new voice policies, Dial plans to the Phones?
    3) Is there a way to forcefully update the policies, dial plans to the Phone?
    4) Also the environment is using over 100 dial plans, so I just copied and pasted the Normalization rules that we tested and working fine. Most of the dial plans are assigned to individual users as every dial plan contains a normalization rule for
    international calling with Unique Prefix (Example: User John international Normalization rules says #1234#00#CountrycodePhonenumber, means if John has to place the international call he need to dial #1234# followed by 00 and then country code, then actual
    phone number). In this case how long its take for the users / phones to get updated with new dial plans?
    6) Is it recommended to use multiple dial plans ? What are the best practices?
    5) Also calls are working fine one failing on subsequent tries. Means when I dial first 1 or 2 times. Call fails, but when I try 3rd time and subsequently it works. After some again there will be failure during 1 or 2 attempts. Why is it so?
    6) After updating the dial policies, voice Route, Voice policies If i reboot all the phones from Switch, Will the changes take effect immediately?
    7) Also when some one calling from mobile or external number to Lync extensions they cant here any Dial tones or caller tunes? Its working fine when they call Cisco Extensions. Also to Lync its working if we dial in E.164 Format, if we dial like 023XXXXX
    format its not working. Any guess about this issue?
    Waiting for some one to help,
    Best regards
    Krishna

    Thanks & Regards Krishnakumar B

    DB:2.72:New Dial Plan Voice Policies Not Taking Effect With Polycom Cx 600 Desktop Phone In Production Deployment, Worked Fine In Testing d9

    Hi Eason,
    Thanks for your reply.
    As I mentioned previously, the only reason I am seeing of having multiple Dial plans is to give user a kind of security restrictions to make international calls by having unique dial plans assigned to single user. Not all the users are allowed to make
    international calls.
    Though we can achieve this with voice policy, If the user not logged off on Polycom phone devices still some one can make calls using the credentials of user who logged in to the phone EVEN IF ITS LOCKED.
    If the management said to remove this restrictions we are good to go with Single dial plan assigned to all users with different voice policies (we have around 6 voice policies)
    The final question is HOW LONGS ITS GOING TO TAKE THE PHONE DEVICES (POLYCOM CX 600 we are using) TO TAKE EFFECT WITH NEW POLICIES/DIAL PLANS)Thanks & Regards Krishnakumar B

  • RELEVANCY SCORE 2.72

    DB:2.72:Cwa - Dial Out Normalization For Anonymous a3


    Using the Dial-out feature with an anonymous user it seems the normalization rules associated with the location profile do not apply.For instance we have a normalization rule for enterprise voice users that places a 9 in front of whatever number is dialed.  This works well with the EV users however the 9 must be dialed when an anonymous user uses the dial-out feature in CWA.Any ideas?Thanks in advance.Jack

    DB:2.72:Cwa - Dial Out Normalization For Anonymous a3

    Hi What do you mean by an anonymous user uses the dial-out feature in CWA, could you please describe it more detail.Do you mean an anonymous user who take part in a meet in the internal network, and then dial-out another one in the external network. I just  know an anonymous user can be invited to a meet, and how it work as you referred.May be i do not know the point or  I misunderstand you. If so please tell me.I will do more research regarding to your issue.Thanks a lot!Regards!

  • RELEVANCY SCORE 2.72

    DB:2.72:Speed Dial In Uccx 39



    anyway I could accomplish the following using UCCX???

    Need to dial a 800 number, pause enter a site code, pause, enter a provider number…

    Example dial 18664694323 pause 313# pause 40162#

    DB:2.72:Speed Dial In Uccx 39


    Hi, use the send digit string step when you use the place call step, also use the delay step to wait for sending the extra digits you need.

    Start

    Accept

    contact=Place Call(to number)

         Successful

              send Digit String (contact, "")

              delay # of seconds

              Send Digit String (contact, "")

    Gabriel

  • RELEVANCY SCORE 2.72

    DB:2.72:Help With Dial/Normalization/Translation Rule 1d


    Hi guys,

    my SIP Trunk provider is sending me non-valid phone numbers {without at start} so I defined users Line URI without and couple of Normalization rules to translate local area numbers to international format {421xxxyyyyyy}. All of them are defined in
    Global Dial Plan. Everything went OK until I needed to connect AnalogDevice with AudioCodes gateway. Then I discovered that I need to use E.164 phone numbers for correct call routing from AnalogDevice contact acrooss Lync server.

    So I decided to change all Line Uri to E.164 format and translate all incoming calls. I understand normalization rules are bi-directional, for incom. and outgo. calls so I set RemovePlusFromUri to True and defined new normalization rule to add to any call.
    So, in this configuration I Can dial out but Can't dial in. It end up with death-halloo tone. Now I also cannot dial AnalogDevice

    At this stage I am little helpless.

    Thanks for help

    DB:2.72:Help With Dial/Normalization/Translation Rule 1d

    Hi,Patrik,
    Would you please elaborate more on your Lync deployment? Also you can enable Lync logging tool with selecting S4,SipStack and Mediation server on Lync FE server and Mediation server to trace the sip log then use snooper to analyze it to get more specific
    information for troubleshooting.
    Besides,here are some great blog posts talking about Normalization rule for your reference
    http://ucken.blogspot.com/2011/01/enterprise-voice-best-practices-in-lync.html
    http://ucken.blogspot.com/2011/10/lync-normalization-rules-rcc-and-you.html
    http://designinglync.blogspot.com/2011/05/lync-dial-plans-and-normalization-rules.html
    http://technet.microsoft.com/en-us/library/gg413082.aspx
    B/R
    SharonSharon Shen
    TechNet Community Support

    ************************************************************************************************************************
    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.

  • RELEVANCY SCORE 2.71

    DB:2.71:I Have Lost My Speed Dial Home, Can I Restore. I Still Have Set As Speed Dial In Bookmarks. 1a



    I found a new tool bar on the firefox page which i took off, when next using firefox, my speed dial page had gone......

    In bookmarks there is still the set as speed dial option.

    Help please to get my speed dial pages back

    Thank you

  • RELEVANCY SCORE 2.71

    DB:2.71:Tanjay Cx700 And Ocs 2007 89


    I have implemented OCS and everything works except the Tanjay'sI cannot dial out it says Call Denied Format of number unsuccessfully check normalization rules Do I have to create specific rules for these devices? Thanks 

    DB:2.71:Tanjay Cx700 And Ocs 2007 89

    The Tanjays do not like the Quick Dial ticked either this prevented the phones from picking up the rule

  • RELEVANCY SCORE 2.71

    DB:2.71:Normalization Rule Works Once, Then Fails dd


    I have a set of normalization rules to handle 4 ranges of 4 digit extensions

    DB:2.71:Normalization Rule Works Once, Then Fails dd

    Hi,It could be either the client or the server. To eliminate the server, my suggestion is to download and install the OCS R2 Resource Kit utilities on the front-end server. This will give you a utility called Enterprise Voice Route Helper. You can enter in a dialed number like 8181, select a policy location profile, then simulate dialing the number. It will show you which normalization rule it matches, along with which route it will take (or which user's extension it matches).This utlitity is really helpful for diagnosing normalization rule issues on the server side. Even if it doesn't solve your issue here, it's a good resource to know how to work.But if I had to guess, it sounds like your problem has more to do with the client. You shouldn't really ever see it work once and then not again. What version of the MOC client do you have running? I would definitely make sure it's current on patches.Regards,MattMatt McGillen, PointBridge - https://blogs.pointbridge.com/Blogs/mcgillen_matt/default.aspx

  • RELEVANCY SCORE 2.70

    DB:2.70:How Are Extensions Used In The Line Uri Field cf


    My question is about the LINE URI examples I've seen where ext= is used. For example line uri: tel:14255551212;ext=51212. What is the purpose of placing ext=51212? Is it just informational? Through normalization rules, users should
    be able to dial 51212 regardless of the ext= entry, right?
    Thanks!

    DB:2.70:How Are Extensions Used In The Line Uri Field cf

    If you're looking for Directory Assistance, I would send in-bound callers directly to an speech enabled Exchange Auto-Attendant.

  • RELEVANCY SCORE 2.69

    DB:2.69:Speed Dial Using Press And Hold Line Key On 500s Sidecar 98



    Speed dial: press and hold idle line key

    Will this functionality be enable with the 500S side car ?

    DB:2.69:Speed Dial Using Press And Hold Line Key On 500s Sidecar 98


    Thank you for the input, I'll submit a feature request on this issue.

  • RELEVANCY SCORE 2.69

    DB:2.69:Blocking Access To Speed Dial For Some User Groups 17



    Hi,

    I have speed dial configured with *, the speed dial no looks like" *1234, *234 etc....

    I would like to block pantry users to have access to the speed dials...I tried blocking them using RP: *!, but it's not working...Any better idea??

    DB:2.69:Blocking Access To Speed Dial For Some User Groups 17


    It's translation pattern..

    Rgds,

    Partha

    Mobile: +971503507853

  • RELEVANCY SCORE 2.69

    DB:2.69:How To Change A Batch Of Speed Dial Number Using Bat ? j3



    I want to change the speed dial number on all the phones , I tried to use BAT ,but I have no idea how to update existing speed dial . Please help ! Thanks in advance . ( Callmanager 4.13)( BAT 5.14)

    DB:2.69:How To Change A Batch Of Speed Dial Number Using Bat ? j3


    Thanks for your information ,I know when I insert new phones I can use the template to add "speed dial" . But I need to update existing phones with new "speed dial" number ,I can not find such option in "update phone" section.

  • RELEVANCY SCORE 2.68

    DB:2.68:Export Custom Normalization Features 91



    Hi,

    Is there any way to export (or move to another server) custom rules from normalization features?

    DB:2.68:Export Custom Normalization Features 91


    All The Normalization rules are stored in BMC.CORE.CONFIG:BMC_NormalizationRule form. Rule for different features are distinguished by Feature Id field

    So, to get all Rules related to Custom Normalization

    1. Open BMC.CORE.CONFIG:BMC_NormalizationRule in Search mode

    2. Set Feature Id to com.bmc.ne.feature.GenericNormalizationFeature

    3. Search

    You can export the searched data in Arx/csv format and can be imported at any other server.

    Thanks,

    Devendra

    View Devendra Yadav's profile

  • RELEVANCY SCORE 2.68

    DB:2.68:Normalisation Question dp


    Hi
    I have normalization rules like below in order. i can see 416, 905, 647 normalise properly to 1 and PSTN calls work. ALso international calls normalise fine. But when I dial 12012342324 it always normalising to 2012342324 instead of
    12012342323. I have restarted Lync many times.
    local ^((416|905|647|289)\d{7})$
    NA ^1(\d{10})$
    International ^(011)([2-9]\d{6,14})$

    Any help would be greatly appreciaed.

    DB:2.68:Normalisation Question dp

    Thanks All. My apologies for not replying promptly. Itworked fine after we had to restart the Lync service.

  • RELEVANCY SCORE 2.67

    DB:2.67:Speed Dial mj



    HP Officejet J4540 All-in-One Printer

    I tried to set up speed dial on this machine according to the users manuel, my problem is that

    using the Devise control panel....under setup I can't find any option for "New Speed Dial"

    Is there another wany to set up speed dial??????

    DB:2.67:Speed Dial mj


    HP Officejet J4540 All-in-One Printer

    I tried to set up speed dial on this machine according to the users manuel, my problem is that

    using the Devise control panel....under setup I can't find any option for "New Speed Dial"

    Is there another wany to set up speed dial??????

  • RELEVANCY SCORE 2.67

    DB:2.67:Normalization Rules For Outbound Calls 17


    Can someone please explain how to use normalization rules for outbound calls?  I've read the OCS Enterprise Voice Guide a few times and I guess I still don't get it.
     
    Here is what I've observed:
     
    (1) If I don't have any normalization rules, then when I enter a 5 digit number in the MOC and make the call, the call is rejected and the OCS log shows 404 No matching rule has been found in the dial plan for the called number.
     
    (2) If I have a normalization rule that matches any 5 digit number, and does not modify the number, i.e., matching pattern is ^(\d{5})$ and translated pattern is $1, then when I enter a 5 digit number in the MOC, the MOC returns No results found. and I cannot make the call.
     
    (3) If I have a normalization rule that matches any 5 digit number, and translates it to E.164, i.e., matching pattern is ^(\d{5})$ and translated pattern is +122233$1, then when I enter a 5 digit number in the MOC, the MOC translates to the E.164 format and I'm able to dial - the call cannot be completed because I don't yet have a PBX hooked up (I'm trying to get calls between MOC and PBXs to work), but at least I can see the call be routed to the mediation server.
     
    My questions are:
    - In (1), if matching rule does not mean normalization rule, then what is OCS referring to?
    - In (2), why does the MOC not allow me to dial?
    - In (3), this looks like it will work (I'll know more when I have the PBX hooked up), but translating a 5 digit number to E.164 and then back down to 5 digits at the PBX seems like overkill.  Is there another way of sending out just the original dialed number instead of E.164?
     
    Thanks in advance.

    DB:2.67:Normalization Rules For Outbound Calls 17

    For (2), I'm still somewhat confused.  Remember I'm dialing a 5-digit PBX number, not a communicator user, so I don't expect to match any communicator users' configured number.  But failing to find a match, shouldn't the OCS then route to the mediation server?
     
    For (3), I understand the need to convert to E.164 for routing to a PSTN gateway.  But when routing to a PBX, is it necessary to send E.164?  It would seem easier to send the dialed number in the original form than to undo the E.164 conversion at the PBX. 
     
    By the way, I do finally have it working using these E.164 rules, I just wanted to know if there was a simpler way.
     

  • RELEVANCY SCORE 2.67

    DB:2.67:Uc 500 Speed Dials And Local Speed Dials For 7940 7960 kk



    Can an phone user configure his/her own personal speed dials on the phone. ?  The Local speed dials could be updated using the CUE GUI, but there is no option to do a personal speed dial.  Also when the speed dial is configure, any idea how to access the speed dial with just using the speed dial code?

    DB:2.67:Uc 500 Speed Dials And Local Speed Dials For 7940 7960 kk


    Jibu,

    CME 4.3 was re-numbered 7.0 and it is available for the UC500 in 12.4(20)T or higher. Make sure you are using the appropriate IOS so the command shows up.

    Thanks,

    Marcos

  • RELEVANCY SCORE 2.66

    DB:2.66:Modify Speed Dial Using Bat 5.0 s3



    Dear All,

    I can create a New VGC Phone and config the Speed Dial for each port using BAT 5.0

    Can I modify the Speed Dial for each VGC Phone using BAT?

    Thanks.

    C.K.

    DB:2.66:Modify Speed Dial Using Bat 5.0 s3


    BAT allows you to bulk-add or bulk-update large numbers of phones, CTI ports, H.323 clients, Cisco

    VGC virtual phones, Cisco VGC phones, and user combinations such as phones and users, CTI ports and

    users, H.323 clients and users, Cisco VGC virtual phones and users, and Cisco VGC phones and users.

    BAT also allows you to bulk-delete large numbers of phones, CTI ports, H.323 clients, Cisco VGC

    virtual phones, and Cisco VGC phones.This URL should be useful.

    http://www.cisco.com/univercd/cc/td/doc/product/voice/sw_ap_to/admin/bulk_adm/4_4_3/bat_phon.htm

  • RELEVANCY SCORE 2.66

    DB:2.66:Dual Forking Is Not Working. x1


    Colleagues,

    At present I am setting up a dual-forking functionally on OCS R2 server.

    What has been done:

    In the edit policy window I checked the Allow simultaneous ringing of phones

    Using enterprise voice route helper I created Normalization rules and routes.

    I can call to PSTN number without any problem.

    But when I try to call from MOC to local numbers I am received fast busy and the message telling me that the call was not completed or has ended.

    Below are normalization rules which were created:

    For PSTN calls I use the following:

    Normalization rule:

    ^\*(\d{4}\d)$
    $1

    Route
    ^\*(\d{4}\d)$ pointing to our mediation server.

    This scenario is working without any problem.

    For local calls I use:

    Normalization rule:

    ^(4\d{3})$

    442073677979;ext=$1

    Route
    ^(4\d{3})$ pointing to our mediation server

    I installed a sniffer on Medition server and I can see that no messages arrives at mediation server when I try to call to local number.

    I have no idea what is wrong.

    With regards,
    A.

    DB:2.66:Dual Forking Is Not Working. x1

    Sorry. the route was incorrect now it is working

    thanks for your help.

    with regards,
    A.

  • RELEVANCY SCORE 2.66

    DB:2.66:Using Bat To Update Speed Dials 7x



    Callmanager 5.1.3. I want to update the fifth speed dial for a number of phones. As a test, I create a csv file using the bat spreadsheet with MAC, description, and the fifth speed dial fields, and upload the file. When I go to "Update Phones" it doesn't find any phones with that MAC. I noticed that the file type "update phones" requires is "custom file" not "CSV". Is there a difference? What format does the file need to follow? Am I asking too much of BAT?

    FYI, I tried several variations for the header, with everything from just MAC and Speed Dial 5 to the following:

    DEVICE NAME,DESCRIPTION,DIRECTORY NUMBER 1,SPEED DIAL NUMBER 1,SPEED DIAL LABEL 1,SPEED DIAL LABEL ASCII 1,SPEED DIAL NUMBER 2,SPEED DIAL LABEL 2,SPEED DIAL LABEL ASCII 2,SPEED DIAL NUMBER 3,SPEED DIAL LABEL 3,SPEED DIAL LABEL ASCII 3,SPEED DIAL NUMBER 4,SPEED DIAL LABEL 4,SPEED DIAL LABEL ASCII 4,SPEED DIAL NUMBER 5,SPEED DIAL LABEL 5,SPEED DIAL LABEL ASCII 5

    DB:2.66:Using Bat To Update Speed Dials 7x


    Hi:

    Have you gotten around this problem.

    I am also trying to update multiple phones speed dial information and unable to do it through BAT file.

    Finally I did by changing every single phone manually.

    The insert specific phones with over ride option, always inserts additional speed dials instead of updating existing one.

    Thanks

    Ramesh

  • RELEVANCY SCORE 2.66

    DB:2.66:Abbreviated Dialing 77



    Call Manager verson 4.1.3

    Is there a way to display the speed dial name when using abbreviated speed dialing?

    DB:2.66:Abbreviated Dialing 77


    We also needed to do this but could'nt find a way. AbbrDial entries are stored in CM's SQL database, not DC Directory (like Fast Dials and PAB entries). The table is just: device id, speed dial index, speed dial number and the label/name. It appears that the name is only used for reference when accessing via CCMUser or CCMAdmin.

    We ended up using Fast Dial lists for group speed dials (a few key presses slower than AbbrDial though).

  • RELEVANCY SCORE 2.66

    DB:2.66:Validate Phone Number Against The Number Normalization j1


    using UCMA how can i validate a phone number against lync number normalization process or pipeline?
    In other words I want to pass 0404073236 and get it translated to the correct E.164 Format such as 61404073235 by using the Lync Server Dial Plan normalization rules.

    Is anyone aware of how to do this programmatically?

    DB:2.66:Validate Phone Number Against The Number Normalization j1

    If you are using UCMA to sign in as a user then you will get the user's assigned normalization rules via provisioning data (endpoint.GetProvisioningData()). These normalization rules are nothing but regex that you need to apply in a certain order. You could
    use regular .Net RegEx class to apply these rules and the number.

  • RELEVANCY SCORE 2.66

    DB:2.66:Lync Web App Call Me Default Country pd


    We have enabled dial out for guest users joining conferences using Lync Web App, but we will only route calls nationally--within the U.S/Canada.
    We have also had complaints from several Web App users that dial-out doesn't work, but after talking to them, they didn't select U.S. as the country, so Lync didn't prefix the number with 1.
    Lync Normalization rules do not appear to be applicable to the Web App, as I have a 10-digit NANP match that does prefix 1.
    My question is simple, Can I default the country to U.S?
    Thanks,
    mGIf a post is helpful, please take a second to hit the GREEN ARROW on the left, or mark as ANSWER. Mark A. Gutowski

    DB:2.66:Lync Web App Call Me Default Country pd

    Hi,Mark,
    Seems it's by design,the Lync web app userscan only use Call Me with entering the fullE.164 number or selecting the country code.As I know,normalization rulescan only be used by the authenticated users in your orgnization,a guest whois
    unauthenticated usersvia Lync Web App will not pickup the normalization rules when they are using Call Me.
    Here is an old threadtalking about the similar issue for your reference.
    http://social.technet.microsoft.com/Forums/en/ocsconferencing/thread/913b6464-442a-4e4d-a73d-d1078b44e737
    Regards,
    SharonSharon Shen
    TechNet Community Support

    ***************************************************************************************************************************************************************************** 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 t

  • RELEVANCY SCORE 2.65

    DB:2.65:Does Data Normalization Speed Up Filemaker? k8



    I just read the handout from fmPro on optimizing speed. I don't recall any strong suggestion toward data normalization.

    Coming from a sql mindset, I tend to "always" create join fields and query from those tables.

    So, creating in fmpro, I have been doing the same thing, but, my relationship graph is a mess.

    Does data normalization positively affect fmPro query speed?

    Thanks!

    Scott

    DB:2.65:Does Data Normalization Speed Up Filemaker? k8


    Not a strong suggestion, but it is on page 13

    Interesting, that they chose not to use the word "normalization"

    Since FileMaker 7, they do advise against "wide" tables, which makes sense

    FileMaker downloads the entire record, to get one field

    greg

    I don't recall any strong suggestion toward data normalization.

  • RELEVANCY SCORE 2.64

    DB:2.64:+ Getting Added To Dialed Numbers When Normalization Rule Specificially Does Not Call For It f7


    Starting this morning, when users dial a 4-digit extension number from their OCS 2007 R2 client, the number is being translated to include . (IE. 5555 translates to 5555)
    I checked the normalization rules and it should be sending the number as dialed (IE. 5555 = 5555). I can't find where this change has occured and as a quick fix made changes to the Gateways. We are about to start our Lighthouse project to upgrade
    toLync, and our Director wants to know how this happened.
    I spoke with our network engineer and no changes were made to our front end servers or mediation servers.
    Any ideas?Rich Pederzani Telecom Engineer

    DB:2.64:+ Getting Added To Dialed Numbers When Normalization Rule Specificially Does Not Call For It f7

    Thank you for the info. I am going to make the necessary changes and re-test.Rich Pederzani Telecom Engineer

  • RELEVANCY SCORE 2.63

    DB:2.63:Unable To Find An Exact Match In The Rules Set 73


    This question may have already been raised here, but I have searched and read the topics on normalization rules and have not found my specific issue. I apologize if this is a repeat, though. I am running OCS 2007 R2, and I have a mediation server which connects to our CallManager 6 system via a SIP trunk. This is all fairly normal, from what I have read. Our local phone numbers are 7xxxx. I have one Location Profile with 2 Normalization Rule setup in it. Norm. Rule #1's Phone pattern regular expression is ^(7\d{4})$ and the translation pattern is just $1. This takes the 7xxxx numbers and sends them straight to CallManager. This works great, as I can type my 5-digit number and it dials my phone. Norm. Rule #2's Phone pattern is ^(\d{10})$ and the Translation patterns is 9$1. I want to type the 10-digit number into Communicator and have it send that number to CallManager to dial out to, say, my cell phone. When I dial my cell phone on my voip phone, I dial 9 plus the 10-digit number. I know the translation pattern is working, because in Communicator it changes the number and adds a 9 to the front of it. It says it can't complete the call, though, and in the event log, I see the following: 404 No matching rule has been found in the dial plan for the called number. ms-diagnostics: 14010;reason=Unabled to find an exact match in the rules set Can someone help me troubleshoot this? The normalization rule stuff is pretty complicated, and I haven't found a simple explanation of what I need to do.

    DB:2.63:Unable To Find An Exact Match In The Rules Set 73

    Ok, so that worked. Now I am wondering why it worked. Isn't the phone pattern used to take a given number and then translate it using the translation pattern? If that is correct, then why would adding a 9? to the phone pattern make the difference when I am only dialing a 10 digit number with no 9 prefix?

  • RELEVANCY SCORE 2.63

    DB:2.63:Normilzation Rules And The Tanjay (Polycom Cx700) Phone j7


     
    I have a problem when dialing numbers from a Polycom CX700 Tanjay phone.  If
    I pick up the receiver or hit the speaker phone button and then start to
    dial a number, the phone dials after entering 3 digits.  I am not able to
    enter the rest of the number.  If I enter the number first and then hit the
    call button, the CX700 behaves like MOC on my PC and dials the number.
    I understand that when you take the CX700 off hook and dial the number, it
    uses its location profile's normilization rules to know when to start
    dialing. We use 3 digit extensions internally, so I have a normilization
    rule for 3 digit extensions.  I also have 3 more rules, for seven digit, 10
    digit, and Long Distance US numbers.  I know that the CX-700 is dialing
    after entering 3 digits because of the 3 digit normilization rule.
    If I delete the 3 digit extension normalization rule, the 7 digit rule seems to control things... so that If I try to dial 18606331234 the CX700 starts to dial after the first 7 digits, 1860633 is what is passed on to the gateway.  It seems that the first rule that matches the digits entered causes the CX700 to start dialing. 
    I would like to know what I need to do to be able to call both 3 digit extensions and seven or ten digit phone numbers from the CX700 phone in the off hook position.  Is it possible?
    Here are my 4 normalization rules, listed in the same order as defined in
    the Location profile:
    LDCallingUS^1(\d{10})$+1$1
    10DigitCallingUS^(\d{10})$+1$1
    7Digit^(\d{7})$+$1
    3DigitExtension^(\d{3})$+$1

    DB:2.63:Normilzation Rules And The Tanjay (Polycom Cx700) Phone j7

    Paul,
    I just figured this out with the help of MS.
    You need to click the 'No Quick Dial' checkbox...
    ...and THEN go to the raw tab and remove the 't' by the '?'.
    This should allow the Tanjay to use the rule, but disable the quick dial.
     
    Jim

  • RELEVANCY SCORE 2.63

    DB:2.63:What New In Xml Data Type If We Can Store Data Into Separate Columns? kp


    Being new to XML Data Type I want to know what is the need to store our data in XML format if we can save it into separate Columns?
    1. Is this practice being widely using in creating databases and maintaining information moreefficiently?
    2. Does this process follows Normalization rules?
    3. What are the pros cons?~Manu
    http://sqlwithmanoj.blogspot.com/

    DB:2.63:What New In Xml Data Type If We Can Store Data Into Separate Columns? kp

    The XML data-type is not designed to compete with Normalization, but complement it. If your data is genuinely semi-structured, hierarchical, generally not a good fit for a normalized database, then the XML data-type can be a good choice, dependent
    on your data and data access requirements.
    Data between systems is often exchanged as XML so this provides a good choice for storing passed data, either for audit or querying purposes. The decision to persist to tables and columns from XML is dependent on yourdata and data access requirements.
    The idea of a database in a cell is not a good one.
    Have a look through this great article, especially the 'Motivating Scenarios for XML Storage' section:
    XML Support in Microsoft SQL Server 2005
    http://msdn.microsoft.com/en-us/library/ms345117(SQL.90).aspx

  • RELEVANCY SCORE 2.63

    DB:2.63:Using Isdn Pri For Dial Back Up jc



    Has anybody had any experience using ISDN PRI for high speed dial back up ? I'd like to see sample configs if possible.

    Thanks

    DB:2.63:Using Isdn Pri For Dial Back Up jc


    PRI to PRI works fine using MLPPP. I prefer to limit the MLPPP bundle to a single PRI (24 or 30 channels). If you need more, there is a hack to force DDR over multiple PRIs illustrated in my book (see listings 5-6 and 5-7 on my web site) , but the addressing limitations are pretty severe and it depends upon bugs in Cisco's RIP implementation to generate the required forcing traffic.

    Good luck and have fun!

    Vincent C Jones

    www.networkingunlimited.com

  • RELEVANCY SCORE 2.62

    DB:2.62:Normalized Number Is Shown On Lync 2010 Even Though Original Outbound Dialed Number Wants To Be Shown. c3


    My customer wants to use individual prefix per location for outbound call through another PBX system because they have to identify which location outbound call comes from. At first they configured the following at normalization rules in
    user dial plan.
    ^(0\d{9}\d) 101$1
    It worked but one unexpected behavior occurs on Lync 2010. They expected Lync 2010 shows original dialed number before normalization but normalized number (1010311112222 ) was shown on conversation history tab. They want to prevent this
    number display since end users might be confused and ask if Lync 2010 can show original number (0311112222) or alternative number (101*0311112222) in place of 1010311112222 in order that end users can identify digits before *are prefix number.

    I tried something to carry out it and found out the solution but I’m not sure if my configuration is proper or not. I want somebody to verify what I did is appropriate configuration.
    My modified configuration of normalization rule is below.
    ^(0\d{9}\d)
    101*$1
    ^101\*(0\d{9}\d)

    101$1

    Lync 2010 only shows 101*0311112222 and Lync 2010 sends 1010311112222 as dialed number to gateway through mediation server. Even if I configured only 1supst/sup line normalization rules and removed 101* and added 101 on translation
    rules in trunk configuration, it didn’t work.

    Is this behavior as Lync design? Is my configuration change proper or not?
    I really want to know how/what I should configure to meet customer requirement. If we can show original dialed number on Lync 2010 it would be great but I couldn't find out it.
    Regards,
    Tatsuya

    DB:2.62:Normalized Number Is Shown On Lync 2010 Even Though Original Outbound Dialed Number Wants To Be Shown. c3

    Hi,Tatsuya,
    You can try to set normalization rule in dail plan as below
    ^(0\d{8}\d)$ -- $1
    Then you can set another normalization rule in Trunk configuration to add 101 prefix when it sent it PBX system
    ^\(\d{9}\d)$ --101$1 (If you would like to remove the sign before itarrives to PBX system)
    or
    ^(\\d{9}\d)$ --101$1 (If you would like to pertain the sign before itarrives to PBX system)

    B/R
    Sharon
    Sharon Shen
    TechNet Community Support

    ************************************************************************************************************************
    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.

  • RELEVANCY SCORE 2.62

    DB:2.62:Application Dial Rules Not Working For Cisco Mobile 8.1 a3



    Hello!

    We have a CUCM 8.5 and a CUP 8.5

    I have configured some application dial rules. They work when i use the Personal Communicator.

    They don't when I use the Cisco Mobile 8.1 on my iPhone.

    I have configured them using the CUCM GUI.

    What am i doing wrong?

    Thx

    Jens

    DB:2.62:Application Dial Rules Not Working For Cisco Mobile 8.1 a3


    Hello!

    We have a CUCM 8.5 and a CUP 8.5

    I have configured some application dial rules. They work when i use the Personal Communicator.

    They don't when I use the Cisco Mobile 8.1 on my iPhone.

    I have configured them using the CUCM GUI.

    What am i doing wrong?

    Thx

    Jens

  • RELEVANCY SCORE 2.62

    DB:2.62:Officejet 6500a E710n - How To Dial Using Speed Dial? cj



    I helped a customer set up a OfficeJet 6500a E710n and she wants to use the fax speed dial- Using remote access to her PC I have been able to set up a Speed Dial #1, but she does not know how to actually tell the machine to dial this number. I do not see a way top dial a fax from the computer and am trying to fix this over the phone. The manual does not list how to dial from speed dial (it only has instructions on how to set up speed dial number) and there is no speed dial button on the printer. Can you provide step by step instructions for how to dial using speed dial?

    DB:2.62:Officejet 6500a E710n - How To Dial Using Speed Dial? cj


    I helped a customer set up a OfficeJet 6500a E710n and she wants to use the fax speed dial- Using remote access to her PC I have been able to set up a Speed Dial #1, but she does not know how to actually tell the machine to dial this number. I do not see a way top dial a fax from the computer and am trying to fix this over the phone. The manual does not list how to dial from speed dial (it only has instructions on how to set up speed dial number) and there is no speed dial button on the printer. Can you provide step by step instructions for how to dial using speed dial?

  • RELEVANCY SCORE 2.61

    DB:2.61:Is Speed Dial Avail On Iphone? kd



    Is speed dial available on iphone?

  • RELEVANCY SCORE 2.61

    DB:2.61:Dsl And Dial Up Connections 9f



    I have lost the ability to connect via DSL wired. It now Automatically goes ahead and connects via Dial Up Connection. I am using Internet Explorer 9.0.8112.1641. How can I get back to connecting only via DSL and NOT Dial Up?

    DB:2.61:Dsl And Dial Up Connections 9f

    In IE, you must go to Tools - Connection. In there, there should be a setting that tells IE not to use the Dial-up connection.




    If you are the original poster (OP) and your issue is solved, please remember to click the "Solution?" button so that others can more easily find it. If anyone has been helpful to you, please show your appreciation by clicking the "Kudos" button.

  • RELEVANCY SCORE 2.61

    DB:2.61:Unique Lync Routing/Normalization Question - Transfer To Voicemail Directly mz


    We have SNOM 821 endpoints in our organization and these phones are missing one key feature--directly transfer a call to voicemail. However, I think I may have gotten around it, but need some help with creating Lync rules to make it work.

    Please excuse my ignorance of the call routing process, as one of these steps may not be in the right order and that is why my implementation is not working.

    Description of procedure:
    1. Normally an extension for us is three digits. Ex. 200
    2. To transfer to voicemail with the phone, I want the receptionist to dial a leading 7. Ex. 7200
    3. Lync normalization rule to turn 7200 into: 13305551212;ext=200@domain.org;opaque=app:voicemail;user=phone
    (I have verified that sip:13305551212;ext=200@domain.org;opaque=app:voicemail;user=phone will dial directly into a user's voicemail box.)
    The normalization rule works correctly, but the SIP log on the phone reports this:

    ms-diagnostics: 14008;reason=Not a phone number;source=LYNC-FRONTEND.domain.local;CalledNumber=7200;RuleName=HQ-DirectVM-Normalization;RulePattern=^7(\\d{3})$;RuleTranslation=13305551212;ext=$1@domain.org;opaque=app:voicemail;user=phone;TranslatedNumber=13305551212;ext=200@domain.org;opaque=app:voicemail;user=phone;ValidationFailureDetails=Character '@' at offset 20 is not allowed.;appName=TranslationService
    That tells me that it is erroring at the @domain.org part of the SIP address. Is that something I should add later in the routing process?
    I am sure I am just not approaching this correct, but there must be a way to do it. That said, if you know of a better way, please let me know!
    The SNOM phones have great features, but lack of direct VM transfers is annoying.
    Thank you in advance!
    Brad Schleifer

    DB:2.61:Unique Lync Routing/Normalization Question - Transfer To Voicemail Directly mz


    Hi,
    Have you dialed the number to test?
    I doubt that your Translation rule works.
    Regards,
    Lisa

  • RELEVANCY SCORE 2.61

    DB:2.61:Office Communicator R2 z3


    I have installed OCE and I am trying to setup the Phone part of it. Yhis is a bit confusing. I am getting Unable to route. Response code 403 will be returned. when I setup my normalization rules. Basicaly I want everyone to be able to dial anywhere anyhow. We do not restrict long distance or any call for that matte. How the heck do I set this up? I also need it to dial 9 to get an outside line firstAny help would be fantasticCheersSean

    DB:2.61:Office Communicator R2 z3

    Thanks for the inputfunny thing is that I can call my mobile using the communicator call and I get the message to please answer the next call and then it disconnects. This leads me to believe that my dial strings are nto right. I am only guessing. excuse my ignorance on this.There are so many places that human error can come into play it is mind numbing.cheersSean

  • RELEVANCY SCORE 2.61

    DB:2.61:Pause In Pstn System Speed Dial Cucm 9.1 p1



     

     

     Hi im looking for the way to configure pause in SYSTEM speed dial cucm 9.1 using mgcp gtw.

    I know ist possible via user speed dial but our client wants a SYSTEM speed dial like PBX ...

     

    Exemple :

    user dial 4444 then 4444 translated to 9.14162547878,,,,,5555

    tks for your solution.

     

    DB:2.61:Pause In Pstn System Speed Dial Cucm 9.1 p1


    Not possible, there's no way to insert the pause in a translation pattern, it won't even accept the comma as a valid entry.

  • RELEVANCY SCORE 2.61

    DB:2.61:Phone Normalization Weirdness xd


    Just got OCS 2007 standard integrated with Avaya AES server, and I am running into issues with phone normalization.
    Our users phone numbers are set up in AD as XXX-XXX-XXXX
     
    I have tried a couple of normailization rules to get these to dial as extensions.
     I have tried
    \(?\s*(503)\s*\)?[\s()\-\./]*(769)[\s()\-\./]*(24\d\d)[\s]*+1$1$2$3
    should return +150376924xx
     
    \(?\s*(503)\s*\)?[\s()\-\./]*(769)[\s()\-\./]*(24\d\d)[\s]*+$3
    should return +24xx
     
    both these rules show the desired result when i use testPhoneNorm
     
    but after an addressbook sync, the addressbook shows the user as having no phone number when you click to call in communicator.  If I remove the rules and resync the addressbook they come back in xxx-xxx-xxxx format.
     Any ideas why these numbers disappear?

    DB:2.61:Phone Normalization Weirdness xd

    Thanks for all the replies.  I got it worked out, I guess I was a bit confused about where the pattern matching for our internal numbers would take place.  I havethe ABS normalizing everything and the AES matches patterns of our dial plan.

  • RELEVANCY SCORE 2.61

    DB:2.61:Lync With Sip And Exchange Um: Wrong Caller-Id dz


    Hi,
    I am having trouble setting up the correct translation rules for the caller ID.
    Our SIPprovider always provide numbers without theleading 0 - but that's not really the issue. I catch this with Normalization Rules in the Lync dial-plan. Let's use an example: the caller ID is 91234567 (or 091234567 with leading zero) and with
    dial rules, lync is showing this correctly as 32 9 123 45 67.
    But when the user doesn't pick up, he receives an email (missed call notification) with caller id 91234567. Is there a way to modify this? If there is, where should it be modified?
    - Lync Dial plan translation rules?
    - Lync Sip Trunk configuration translation rules?
    - Exchange UM Dial Plan?
    - ...

    DB:2.61:Lync With Sip And Exchange Um: Wrong Caller-Id dz

    Exchange does not normalize phone numbers so you need the full number to get into exchange- Belgian Unified Communications Community : http://www.pro-exchange.be -

  • RELEVANCY SCORE 2.61

    DB:2.61:Lync 2013 Normalization Rules And Company_Phone_Number_Normalization_Rules For Extenstions 7k


    We have users that do not have DIDs.

    Example:
    In AD the userstelephone field will be 13035554444;ext=208
    In Lync their Line Uri will be tel:13035554444;ext=208
    Other Lync users should be able to dial 208 and get this user.
    Lync Normalization rule:
    ^(208)$
    13035554444;ext=$1
    Company_phone_Number_Normalization_rules
    \?[\s()\-\./]*1?[\s()\-\./]*\(?\s*(\d\d\d)\s*\)?[\s()\-\./]*(\d\d\d)[\s()\-\./]*(\d\d\d\d)[\s]*;Ext=(\d{3})
    1$1$2$3;Ext=$4
    If 208 is dialed only the 1303555444 shows up.
    Where am I off on this?

    DB:2.61:Lync 2013 Normalization Rules And Company_Phone_Number_Normalization_Rules For Extenstions 7k

    Thanks. It seems to work.
    One curious thing is that the input number 233 shows on the screen as
    1 (303) 555-4444
    X233 instead of the 1(303) 555-4444;Ext=233
    The user name only resolves once the 1 (303) 555-4444
    X233 is clicked to dial.

  • RELEVANCY SCORE 2.60

    DB:2.60:Can Not Dial Phone Number On Lync Contact... Dial Desktop Phone Number Ok, But When Dial Mobile Phone Number Failed, Both Are In The Same Format... 81


    If this is normalization rule issue, why the same format of Desktop phone and Mobile phone, but one success, and the other failure? Really odd.
    Found in the log,

    ms-diagnostics: 14010;reason=Unable to find an exact match in the rules set;source=IT-LYNCFE1.NTST.COM;CalledNumber=555*******;ProfileName=DefaultProfile;appName=TranslationService

    But the successful call shows the numbers translated into 1777xxxxxxx

    Any idea why 2 phone numbers in the same format(10 digits ), 1 get normalized, and successfully dialed, but the one NOT normalized at all?

    Thanks in advance for your help!

    Thank you!

  • RELEVANCY SCORE 2.60

    DB:2.60:Speed Dial 8k


    Does the Vortex lg have speed dial for contacts?

    DB:2.60:Speed Dial 8k

    Does the Vortex lg have speed dial for contacts?

  • RELEVANCY SCORE 2.60

    DB:2.60:How Do I Set Up And Use Speed Dial On My Samsung Gusto 2? d7



    To create Speed Dials, press Menu Contacts Speed Dials. You can add up to 998 speed dials. Speed dial number one is set to your Voicemail and cannot be edited. Any contact that has a phone number field with information in it can be added to a speed dial. Scroll to or type in the speed dial number that you want to assign a contact to and press the OK key to Set the speed dial. Select the contact from your contact list and press the OK key. Select Yes and press the OK key again.

    To make a call using a speed dial, enter the speed dial number at the dial screen and press Send or press and hold the last digit of the speed dial to dial the number without pressing Send.

    DB:2.60:How Do I Set Up And Use Speed Dial On My Samsung Gusto 2? d7


    To create Speed Dials, press Menu Contacts Speed Dials. You can add up to 998 speed dials. Speed dial number one is set to your Voicemail and cannot be edited. Any contact that has a phone number field with information in it can be added to a speed dial. Scroll to or type in the speed dial number that you want to assign a contact to and press the OK key to Set the speed dial. Select the contact from your contact list and press the OK key. Select Yes and press the OK key again.

    To make a call using a speed dial, enter the speed dial number at the dial screen and press Send or press and hold the last digit of the speed dial to dial the number without pressing Send.

  • RELEVANCY SCORE 2.60

    DB:2.60:How To Create Address Book Normalization Rules jj


    Hi guys
    I have ocs 2007 r2 and enterprise voice enabled.
    am trying to figure out how to create normalization rules for dialing from address book,the issue is that:
    i have create a simple normalization rule and it works fine only if i dial from dialpad but not when calling from address book on moc.
    i know that there is something called e164 standard that must be met.
    could someone point me to the right direction?
    for starter what i need is to dial outside for example what and where do i update the address book if i want to translate this:
    address book number:972-545-xxxxx target translation should be: 90545xxxxxx
    i didnt find any good resource on how to do it from address book.
    Thanks for helping

  • RELEVANCY SCORE 2.60

    DB:2.60:Internal Call Failing - Ab Normalization Issue c7


    Hi Everyone.
    I'm having a rather interesting issue and it seems to be growing throughout the company. I'll try to explain as in depth as possible.

    When a user attempts to call another user or to transfer a call internally to another user by simply:
    1. Searching for the user
    2. Clicking the Call icon.
    The call immediately fails with Call Failed.
    Looking at the issue in further depth, I found that when I hover over the usersCALL icon, I see that the number is normalized to e.164 format from their AD telephone entry, however it's missing the 1 for the country code. So the number
    looks like 8105551212. Then when you click the down arrow next to the CALL button you see the number has been normalized from AD correctly (810) 555-1212. This is because it is attempting to make an international call
    because 81.. makes Lync think itis dialing international
    If you click the CALL button directly, the call fails. If you click the down arrow and select the WORK number or LYNC CALL, it will work fine. You can also type in the 4 digit extension and have it normalize perfectly to the full e.164
    format and it will successfully call.
    I have cleaned up the AB Normalization file and tested the normalization rules using ABServer.exe and they normalize correctly. I have also tested the normalization with the dial plan normalization as well. Everything seems to be in place correctly.
    I have manually regenerated the Address Book. But still no luck. I have multiple sites, each one with its own SBA. All are up to date.

    This is not happening at every site or for every user, but I do see it happening randomly. It's frustrating for the receptionists especially when it comes to transferring calls and they can't.

    Anyone with some ideas?

    John K. Boslooper | Sr. Voice Engineer | Lutheran Social Services of Michigan

    DB:2.60:Internal Call Failing - Ab Normalization Issue c7

    Hi Eason,
    It does not happen between to users when they select LYNC CALL. Only when they click directly on a user which the incorrect normalization has taken place. There are no event log messages, but when I start the logging tool, I can see the problem.

    If you hover over a user with the incorrect normalization, you will see the phone number displayed as 8105551212. It should be displayed as 18105551212 or 1 (810 555-1212. When you attempt to click on the number as displayed (8105551212),
    the server doesn't realize that you are attempting to dial within the US because it thinks you re dialing a country code of 8 or 81.

    In the logging tool, you see Lync sending 0118105551212 to the PSTN gateway.

    I do understand the Voice routing process in Lync, but I think the initial normalization is off and therefore not matching up to a Lync user. 8105551212 does not match up to a Lync user. 18105551212 does.
    John K. Boslooper | Sr. Voice Engineer | Lutheran Social Services of Michigan

  • RELEVANCY SCORE 2.60

    DB:2.60:Auto-Generated Number For All Users s8


    We're on Lync Server 2013, running a front-end pool consisting of 3 front-end servers. Users are VoIP enabled. We're seeing some inconsistent behavior while right-clicking an user and selecting the Call option. Even though the respective target
    users don't have an Other phone number set in AD, the Lync client seems to be somehow auto-generating a normalized entry and presenting this as an Other entry in the contextual menu that allows calls. The entry always begins with 1
    (425). Strange enough, this is the prefix used in some sample normalization rules in a Microsoft article
    here.
    Even though Dial Plans - to my understanding - shouldn't alter this (they only apply normalization rules for manually dialed numbers only), I've searched through all the normalization rules but there's none that start with 1 (425). I've also tried running
    ABSConfig, yet this tool crashes systematically on multiple machines (the Lync servers have updates dating from less than 2 months ago).
    Also - there's no normalization .txt file created in the ABFiles in the Lync Share, as in

    this article. Taking a look in the local GalContacts.db file shows the regular phone numbers, but not this one - hinting that it's something the Lync client creates on the fly. Additionally, no Lync Address Book Web Query is visible in Fiddler when browsing
    through the users' phone numbers in the Lync client.
    Adding to the problem is that some users see the Other entries, while others don't - eg. user X right clicks user Z and sees a wrong Other entry, while user Y right clicks user Z and doesn't see any wrong entry containing Other.

    First question is what could trigger this behavior in the client ? Secondly, has ABSConfig.exe become broken by a recent update ?

    DB:2.60:Auto-Generated Number For All Users s8

    According to the 2nd article - I've created an emptyCompany_Phone_Number_Normalization_Rules.txt file and placed it in the Lync file share, in order to avoid any suspicion that the built-in file might be used. I've updated the address book but unfortunately
    can't restart the FE services at this time. There's no still no change in the client.
    Yet - the problem here is the numbers shown aren't present in the files making up the Lync address book inside the local user's sip profile folder.

  • RELEVANCY SCORE 2.60

    DB:2.60:Software Name Normalization pm



    Hi,

    We're using Remedy 7.6.4 integrated with SCCM to import discovered software CIs.

    Data from SCCM is not normalized and we need to get it normalized before importing into the CMDB.

    I understand there is a normalization engine in Atrium but I think there we actually need to build our own rules.

    Is it a way to periodically and automatically download from Internet new normalizations rules with new sofwares names so we don't have to maintain them manually all the time?.

    At least it could do 90% of the job.

    Thanks,

    Frdrick

    DB:2.60:Software Name Normalization pm


    I'm also in the normalization process and although your question was similiar I decided to post a new message. Normalization primarily takes care of duplicates, but you should have a tool that will ping your server and update as new items are uploaded.

  • RELEVANCY SCORE 2.60

    DB:2.60:Lync Normalization Rules 89


    Based on the reading and understanding of Lync Dial plans and normalization (http://masteringlync.com/2013/04/07/understanding-voice-routing-dialing-behaviors/ I have the following query :-
    Dial plans rebuild the number
    Voice routes point the call in the right direction after it is rebuild.
    For a site that is build 4 digit internal extension, is it a must to add the rules in dial plan for normalizating the number to E164 and select the specific extension as Internal extension ?
    Lync user A 2001 (44 20 7841 2001) dials User B 2002 ( 44 20 7841 2002). Lync serarches the internal database and routes the call automatically to User B even if this user is not present in Normalization rule and routes the call.
    I presume the same behaviour applies when a lync phone makes a call.
    For a call received from external, Lync will match the number to E164 format and will route the call the relevant extension.

    Given this case, why exactly internal extensions needs to be added in dial plan normalization rule and when exactly internal extensions needs to be added in dial plan normalization rules.

    Normalization rules should just have various outbound dialing excluding internal extensions is my view.

    If anyone could clarify my query it will be helpful

    DB:2.60:Lync Normalization Rules 89

    I think I'm reading the question a bit differently.
    Given this case, why exactly internal extensions needs to be added in dial plan normalization rule and when exactly internal extensions needs to be added in dial plan normalization rules.

    Normalization rules should just have various outbound dialing excluding internal extensions is my view.
    If your userscan dialeach other byextension andit worksdespite E.164 numbers being assigned to the users, then you don't necessarily needto add internal extensions inthe dial plan normalization. If it didn't
    work, this would be the when, although in my view it's just good practice to have them in there.
    Do you have the ;ext=2001 in the user's LineUri? This may be helping.

    Please remember, if you see a post that helped you please click Vote As Helpful and if it answered your question please click Mark As Answer.
    SWC Unified Communications

  • RELEVANCY SCORE 2.59

    DB:2.59:Incoming Calls Using Only Extensions Without Normalization Rules ck


    We have users with this teluri: 34xxxxxxxxx;ext=yyyy
    If I don't create normalization rules to convert incoming calls to teluri: 34xxxxxxxxx;ext=yyyy format, could I call to users using only extensions??
    Example: Source (Lync User A) teluri: 34916791724;ext=1234
    Outgoing calls: Lync send to Telephony provider this teluri and converts it to 3460655xxxx, where xxxx is 1234.Destination(User B)recieves this 34606551234
    Incoming calls: Telephony provider recieve a call to 34606551234 andsend to Lync 1234, could I Lync to contact with User A

    DB:2.59:Incoming Calls Using Only Extensions Without Normalization Rules ck

    Hi,

    For incoming calls, the number 34606551234 should be sent to Lync directly as tel uri of user did use the E.164 format that includes plus sign.

    Here is a great blog for you to understand why the number need to be normalized as E.164 Formatting.
    http://ucken.blogspot.com/2010/12/enterprise-voice-best-practices-in-lync.html

    Regards,
    Kent Huang
    TechNet Community Support
    ************************************************************************************************************************

    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.

  • RELEVANCY SCORE 2.59

    DB:2.59:Inbound Normalization Not Workin px


    Hi!
    In our Lync system I cannot get inbound normalization to work unless the normalization rules for inbound callsare present in the Global dialplan. I tried to follow various blogs on how to configure inbound normalization using a site or pool plan. But
    when I look in the traces I can see that Lync applies the defaulProfile on the inbound call which causes it to fail with a 404. Should I be able to handle inbound normalization outside the GLobal plan or do I have to use that?
    Regards

    DB:2.59:Inbound Normalization Not Workin px

    Hi All!
    Since we will be using different gateways in different countries I would prefer to not use the global dialplan and instead use the pool level - gateway so we can have different rules based on location, if the gateway is not able to fix the normalization
    for us.
    I followed the blog but this still does not work. And now I'm no longer understand if this should work or not :)

  • RELEVANCY SCORE 2.59

    DB:2.59:Multiple User-Dialplans Sharing Same Normalization Rules? 9j


    Hello,
    we have a lot of user Dialplans (50) for each PRI in its location. These Dialplans have nearly 30 normalization rules for fast dialing other locations. Do i have to create for each dialplan new normalization rules or can i link to existing ones? I dont want
    to manage 30x50 normalization rules ;)
    thanks and regards.

    DB:2.59:Multiple User-Dialplans Sharing Same Normalization Rules? 9j

    Hi Wolfgang,
    Sorry for my late answer.
    I have had a test about it. It indeed can notuse site or global policy if you assign a user policy for a account.
    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.