locked
Office Communicator not normalising numbers RRS feed

  • Question

  • All,

     

    I have the following rule in my location profile which was created by the enterprise route helper:

     

    ^([1-8]\d{2})$

    +442031239$1

     

    So when I type '172' in the box at the top of the Office Communicator client, should I not expect '+442031239172' to appear in the results list underneath?

     

    Also, my Line URI is 'tel:+442031239172' and User B is 'tel:+442031239174', when I enter '174' in the box should I not expect 'User B' to appear by name in the results box?

     

    Is there a way of copying the phone number normalisation rules in the location profile into the Address Book normalisation file, as I have not yet set this up yet.

     

    Thanks in advance,

     

    Andrew.

    Thursday, November 20, 2008 5:17 PM

All replies

  •  

    http://communicatorteam.com/photos/oc_blog_pics/images/72/original.aspx

     

    That's what I'm looking for... I thought all that was needed is normalisation rules in the location profile. Can anyone help?

     

    Thanks in advance,

     

    Andrew.

    Thursday, November 20, 2008 9:36 PM
  • I have part of this issue fixed - the location profile was not set on the 'Voice' tab of the 'Front End Server' container properties.

     

    However, typing an extension '174' which normalizes to '+442031239174' does not resolve to 'User B', even when dialled, it remains as just tha E.164 number. OCS should do this?

     

    Andrew.

    Thursday, November 20, 2008 11:44 PM
  • It should change to UserB as when you are dialing the number

    Maybe there is a mistake in the Line URI or Normalization? You must compare them exactly!

     

    msRTCSIP-Line tel:+xxxxxxxx174

    is the same as the normalized number +442031239174

    Friday, November 21, 2008 9:18 PM