locked
Normalization Rules for Incoming Phone Calls RRS feed

  • Question

  • I'm evaluating OCS 2007 Public Beta behind a PBX. The PBX cuts of the prefix "0" of the incoming call number (showing 78-719123456 instead of 078-719123456).

     

    So Communicator can not make a successfully number to name resolution.

     

    Does OCS 2007 / Communicator Beta address this problem?

     

    Thanks, Captain MESO

     

    Friday, April 6, 2007 3:12 PM

Answers

  • The number has to match exactly for communicator to resolve the name.

    Here is a possible workaround:

    Do all phone numbers have a 0 in the front?

    If so, you can enter your user's phone numbers in Active Directory without the 0. Then on your outgoing normalization rules add the zero back in for external routing.

    Does that make sense?

     

    Tuesday, April 10, 2007 6:40 AM
  • That is correct.

     

    As another possibility, you should be able to configure how your PBX or VOIP gateway does it's number manipulation as well so that it leaves the 0 there.

    Saturday, April 21, 2007 12:15 AM

All replies

  • The number has to match exactly for communicator to resolve the name.

    Here is a possible workaround:

    Do all phone numbers have a 0 in the front?

    If so, you can enter your user's phone numbers in Active Directory without the 0. Then on your outgoing normalization rules add the zero back in for external routing.

    Does that make sense?

     

    Tuesday, April 10, 2007 6:40 AM
  • Hi Thom,

     

    From your descriptions I understood that OCS doesn't support normalization rules for incoming call. Have I understood you correctly?

     

    Thanks, Captain MESO

    Thursday, April 12, 2007 11:43 PM
  • That is correct.

     

    As another possibility, you should be able to configure how your PBX or VOIP gateway does it's number manipulation as well so that it leaves the 0 there.

    Saturday, April 21, 2007 12:15 AM