Can't call any numbers starting with "#" in Communicator 2.0 RRS feed

  • Question

  • Hi,


    I have Microsoft OCS 2007 and MOC 2.0 install on my PC, i can't seems to dial any numbers beginning with "#", the click-to-call button just wouldn't comes out, have anyone face this weird problem before ??


    One thing to note is that i am currently using OCS in RCC mode and not EV mode and thus i do not have the Mediation Server installed and running inside my current set-up.


    Any help will be greatly appreciated.


    Best Regards

    Han Zhong


    Monday, October 6, 2008 2:41 AM

All replies

  • You should be normalizing your numbers into either E.164 format (+1234567890) or another format that your phone system recognizes.  Why do you have '#' symbols stored in the number strings?


    Monday, October 6, 2008 12:39 PM
  • Hi,

    Firstly thanks for replying Jeff, i really appreciate it very much, reason for needing to dial a "#" in front is because i am using Microsoft OCS 2007 in RCC mode and hence i have to integrate and make it work with Broadsoft which is a IP Centrex service that my company had subscribe to with the local telco provider.

    The feature access codes provided meant that we have dial something like *95 to turn on the call-forwarding service and then dial #95 if we need to turn the call-forwarding service off and thus my users really need to be able to dial a # in front if they wants to use all the features provided by Broadsoft. Currently they can dial any numbers beginning with # using their deskphone as it won't works on their Communicator 2.0, but i really don't  see this as a long term solution to my problem. Do you know why Microsoft don't allows users to dial a # in front of any digit strings inside Communicator 2.0 ?? Is this a bug or a oversight from them or do i need to configure a dial-plan somewhere in order to do this ?? And why do dialing a * in front works in Communicator but dialing a # in front don't, what is the difference between both and why do Communicator treats both so differently, or does the Communicator software have some kinda digit-string checking mechanism in-built inside  ?? I really needs some englightenment here from Microsoft people...

    Another significant thing to note is that my company do not have a Mediation Server installed at this point of time as we are only using Microsoft OCS 2007 in RCC mode and RCC mode do not need a Mediation Server in order to work properly right ?? Please do correct me if i am wrong...

    By the way, i have already normalize all my numbers into the E.164 format (+6512345678) and everythings are working fine now. Thanks for the advice though and sorry for my ramblings...
    Wednesday, October 8, 2008 11:54 AM
  • I have some info on the normalization process here:




    Also, you are correct that you don't need a Mediation server if only using RCC mode.  Dual Mode or Enterprise Voice Mode would require a Mediation Server.

    Wednesday, October 8, 2008 12:22 PM