Exchange Server TechCenter >
Exchange Server Forums
>
Unified Messaging
>
Exchange 2007 UM with Nortel CS1000 Voicemail number not E.164
Exchange 2007 UM with Nortel CS1000 Voicemail number not E.164
- Hi all
My customer has his PBX Nortel CS1000 directly connectet with the Microsoft Exchange 2007 UM via a SIP Trunk.
All works fine, almost all...
If the User receives an Voicemail messages from an external caller the number will not be shown in an international format such as E.164. The number is always displayd without the international code such as +41 for Switzerland.
In the message header I see the SIP message in the "From" Field like this "From: <sip:44325xxxx@domain.ch;user=phone> This number will be displayed in my Voicemail as caller ID witch is not correct. The right one must be "From: <sip:+4144325xxxx@domain.ch;user=phone>.
In the Message Header "Via" Field the nummber is shown correctly. There is a string like "x-nt-e164-clid: +4144325xxxx@domain.ch;user=phone"
Components:
PBX Nortel CS1000 5.0
Exchange 2007 UM SP1
Does anyone know how the Exchange or Nortel must be configured that the numbers are shown correctly??
Thanks for your help
All Replies
- Hi,
Depends on the nortel rls version. v5 and v6 are slightly different. This matching is done on the Nortel PBX side where you can append the +41. In v5 its done on the cs1k PABX and in v6 on the node of the signalling server.
I remember that there are also some microsoft patches that u should apply for this. All should work with no issues.
I do recommend to upgrade both the nortel version to version 6 and the exchange 2007 SP2.
Regards
Anesh - Hi Anesh
Thanks for your replie. Have you got any information (printscreens, etc) and KB Numbers for Microsoft Patches that this is going to work? The PBX Guy said it is not possible an there is closed Ticket from Nortel which says the same. :-( Nortel says it works only with a full OCS integration.
If you have any configuration information, could you these provide me?
Regards - Hi there,
Both sides need patches. There are a few patches on the nortel side that is needed. What is being used for the SIP connection - the Nortel redirect server or the SIP proxy server. The challenge was always related to the fact that you could not change the infomration set within the SIP trunk, - meaning you could not do any number manipulation on the trunk. The way we worked around this is to have the rules done on the Nortel side before exchange is hit. Checkout the doc from the UC guy: http://theucguy.wordpress.com/2008/10/09/direct-sip-connection-with-nortel-communication-server-50/
There are some assumptions for this setup to work:
1. On the PBX side, you have installed the element manager
2. The pbx is pre-configured to support IP phones and trucks
3. Exchange is configured with a UMdialplan and associated UMIPgateway object. The UMIPgateway points to the IP address of the PBX sip gateway.
4. On the Exchange side install the update rollup package.
Hope that this helps
Regards
Anesh - I have the same problem, Customer is using CS1K Rls 5.5 and Exchange 2007 SP2 they also have Converged Office with OCS, The Caller ID is shown as, The CS1K and UM Serevr are fully patched, the main issue is that when a users tries to return the call it fails I have written a Normailsation rule just so they can return the call, but it should show either the E164 or National Number in thei case 01359244xxx
You received a voice mail from 1359244xxxCaller-Id:
1359244xxx
- Hi
I have had lot of discussions with guys from the nortel PBX System and it seems to be a bug in the nortel PBX System itself. There is an open Ticket now by Nortel. I hope I will get some respons as soon as possible. Will let you know any news.
cheers - hello,
i have the same issue with cs1k 5.5 and exchange 2007 sp1 - if you have any answere from nortel please let me know.
kind regards
jürgen Hello tomcat_75,
any progress on the solution from nortel?
maybe you can post it?kind regards
jürgen
- Hi Jürgen
Unfortunately not. :-( I am still waiting for an Answer from the Nortel support.
kind regards - Hi tomcat_75,
do you have a case-id - because i can then open a case for my site and reference to your case-id
maybe this can help to force a solution.
please contact me on my email juergen"dot"fruehwirth"at"kapsch.net
kind regards
jürgen - we MIGHT have found the fix we are testing over the next few days, will update you all we are looking at using an existing patch designed for SIP Dect.
I have received an update from Nortel
- Problem is identified
- No existing fix until today will solve the problem
- Nortel is claryfing how the patch must be written
waiting for news and will post them.
cheers
