Siemens HiPath3550 User manual

1
M
Mi ic cr ro os so of ft t E Ex xc ch ha an ng ge e S Se er rv ve er r 2 20 00 07 7 U Un ni if fi ie ed d M Me es ss sa ag gi in ng g
P
PB
BX X C Co on nf fi ig gu ur ra at ti io on n N No ot te e: :
S
Si ie em me en ns s H Hi iP Pa at th h3 35 55 50 0 w wi it th h A Au ud di io
oC Co od de es s M MP P- -1 11 1x x F FX XO O
u
us si in ng g A An na al lo og g l li in ne es s ( (I In n- -b ba an nd d D DT TM MF F)
)
By : AudioCodes
Updated Since : 2007-02-09
READ THIS BEFORE YOU PROCEED
This document is for informational purposes only and is provided “AS IS”. Microsoft, its partners and
vendors cannot verify the accuracy of this information and take no responsibility for the content of this
document. MICROSOFT, ITS PARTNERS AND VENDORS MAKE NO WARRANTIES, EXPRESS,
IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.

2
Content
This document describes the configuration required to setup Siemens HiPath3550 and AudioCodes MP-
11x FXO using analog lines with inband DTMF as the telephony signaling protocol. It also contains the
results of the interoperability testing of Microsoft Exchange 2007 Unified Messaging based on this
setup.
Intended Audience
This document is intended for Systems Integrators with significant telephony knowledge.
Technical Support
The information contained within this document has been provided by Microsoft, its partners or
equipment manufacturers and is provided AS IS. This document contains information about how to
modify the configuration of your PBX or VoIP gateway. Improper configuration may result in the loss
of service of the PBX or gateway. Microsoft is unable to provide support or assistance with the
configuration or troubleshooting of components described within. Microsoft recommends readers to
engage the service of an Microsoft Exchange 2007 Unified Messaging Specialist or the manufacturers
of the equipment(s) described within to assist with the planning and deployment of Exchange Unified
Messaging.
Microsoft Exchange 2007 Unified Messaging (UM) Specialists
These are Systems Integrators who have attended technical training on Exchange 2007 Unified
Messaging conducted by Microsoft Exchange Engineering Team. For contact information, visit here.
Version Information
Date of Modification Details of Modification
21 March 2007 Version 1

3
1. Components Information
1.1. PBX or IP-PBX
PBX Vendor Siemens
Model HiPath3550
Software Version Rel. 3
Telephony Signaling Analog with inband DTMF
Additional Notes None
1.2. VoIP Gateway
Gateway Vendor AudioCodes
Model MP-11x (MP-114 FXO / MP-118 FXO)
Software Version 5.00AV.023.002
VoIP Protocol SIP
1.3. Microsoft Exchange Server 2007 Unified Messaging
Version RTM
2. Prerequisites
2.1. Gateway Prerequisites
•Current Disconnect must be configured in the gateway and the duration must be adjusted for
better performance for disconnecting calls when the PBX user has disconnected.
•The gateway also supports TLS (in addition to TCP). This provides security by enabling the
encryption of SIP packets over the IP network. The gateway supports self-signed certificates
as well as Microsoft Windows Certificates Authority (CA) capabilities.
2.2. PBX Prerequisites
None.
2.3. Cabling Requirements
This integration uses standard RJ-11C telephone line cords.

4
3. Summary and Limitations
A check in this box indicates the UM feature set is fully functional when using the PBX/gateway
in question.
Siemens HiPath 3550 PBX has several limitations when activating the voice mail functionality. The list
below describes these PBX’s limitations:
•When dialing from an external phone (PSTN) to a PBX’s user extension, and the call is
forwarded to the voice mail (for any reason), and then leaves a voice mail message to the
PBX’s user, the following limitation occurs: The PBX doesn’t support caller-ID from external
numbers and tags them as a call from 02222. Therefore, "02222" is displayed in the send field
of the voice mail message for all external numbers (PSTN).
•When performing blind transfer to an invalid number, the PBX doesn’t support invalid number
notification and the call is routed back to the original transfer user. When an invalid extension
number is defined in the Microsoft Unified Messaging for a particular user, and call transfer by
Directory Search to this user is requested, the user that requests this transfer is routed back
to the Microsoft Unified Messaging welcome prompt.

5
4. Gateway Setup Notes
Step 1: SIP Environment Setup

6
Step 2: Routing Setup
Note: The Proxy IP Address must be one that corresponds to the network environment in which the
Microsoft Unified Messaging server is installed (For example, 10.15.3.207 or the FQDN of the Microsoft
Unified Messaging host).

7
Step 3: SIP Environment Setup (Cont.)

8
Step 4: Coder Setup

9
Step 5: Digit Collection Setup

10
Step 6: Disconnect Supervision Setup