missed call vs manual dial
hi! My normalisation rule works fine when dialing from Lync or clicking any missed call in my outlook inbox. eg. if my received call is 61118888 (manual dial or missed call number in outlook). It will append a + to the number. The problem is this doesn't work in the missed call tab in the Lync client itself. When I  dial the missed call in the Lync client 61118888, it doesn't append the + in front to become a E164 number. Any idea what could be wrong? Thanks.
July 15th, 2013 10:21am

Here is what i've done to fix it, all the calls were coming in as +10 digit missed calls, I need to figure out a way in order to add a +8 for local calls and +81 for long distance one where 8 is the external number that my IP PBX uses to pickup and outside line.

I created 2 new normalization rules:

First Rule:
1. If the number looked like +555xxxyyyy local number , remove the + and add +8 to it and place it under the normalization rule when dialing from OCS.

Second Rule:
1. If the number looked like +777xxxyyyy long distance number,  remove the + and add +81 to it and place it under the under the normalization rule so that it will match the local numbers as local and not long distance.

http://social.technet.microsoft.com/Forums/lync/en-US/c876faf6-60a8-4e6a-bd32-4e21e5f05a0a/missed-calls-not-being-translated

July 15th, 2013 4:59pm

Did this issue happen to other Lync users?

Please test that with your Lync accoutn on other computer.

Free Windows Admin Tool Kit Click here and download it now
July 16th, 2013 5:37am

hi! Slight correction to the description of my issue. I can make a call by using manual dial, clicking missed call from Outlook (It will append the +), and the Missed Call tab in Lync client. What doesn't work is the Conversation tab>Calls received/missed in the Lync client. When I dial the missed number which is not in the E164 format, it doesn't append a + to the number, whereas this work in everywhere else.

This happens to all the user login. Any clue? Thanks.

Thanks.

July 16th, 2013 11:20am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics