Hi All,
I know that this may not be a Mitel problem, but I'm hoping some kind soul can point me in the right direction.
Scenario: We have an ICP3300, LBG and Microsoft LCS. Our machines are using Office Communicator.
Aim: As per Microsoft's recommendations all our contacts are stored in their E164 format as +44 20 71234567. We would like all external numbers that come in to have +44 added to the start and the first 0 to be removed. This would mean that OC is able to look up the number correct in Outlook and present the name of the caller. We already been working on the phone normalisation scripts in LCS, which 'should' be working but the number is still being presented to OC in it's native format e.g. 02071234567 - mighty frustrating.
We've been working on the assumption that it's something to do with dialstrings (as in phone-context=dialstring) as we have got OC CLI working for internal extensions. I'm not sure what URI/context information it is sending and whether LBG is stripping off or manipulating the data so that something gets lost in translation... At a loss basically!
Is there way to check what is coming from the 3300 or configure it for E164, or is it already configured like that out of the box?
Cheers for your time,
Nick
tHowever the number that comes in
I know that this may not be a Mitel problem, but I'm hoping some kind soul can point me in the right direction.
Scenario: We have an ICP3300, LBG and Microsoft LCS. Our machines are using Office Communicator.
Aim: As per Microsoft's recommendations all our contacts are stored in their E164 format as +44 20 71234567. We would like all external numbers that come in to have +44 added to the start and the first 0 to be removed. This would mean that OC is able to look up the number correct in Outlook and present the name of the caller. We already been working on the phone normalisation scripts in LCS, which 'should' be working but the number is still being presented to OC in it's native format e.g. 02071234567 - mighty frustrating.
We've been working on the assumption that it's something to do with dialstrings (as in phone-context=dialstring) as we have got OC CLI working for internal extensions. I'm not sure what URI/context information it is sending and whether LBG is stripping off or manipulating the data so that something gets lost in translation... At a loss basically!
Is there way to check what is coming from the 3300 or configure it for E164, or is it already configured like that out of the box?
Cheers for your time,
Nick
tHowever the number that comes in