Communications processor for connection of simatic s7-300 / to profibus dp (50 pages)
Summary of Contents for Siemens HiPath3550
Page 1
: 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.
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.
Page 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...
Page 4
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: •...
Page 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).
Page 13
Step 9: Endpoints Setup Note: The phone numbers must correspond to your network environment as the dial plan pilot number is configured for this PBX in the Microsoft Unified Messaging server (For example, 11111).
Page 20
4.2. TLS Setup The specific gateway software version used in this PBX Configuration Guide was not tested for TLS. However, TLS was tested successfully for other gateway software versions operating with Microsoft Exchange 2007 TLS capabilities. Refer to the procedure below for TLS setup. Step 1: PBX to IP Routing Setup Note: The Proxy IP Address and Name must be one that corresponds to the network environment in which the Microsoft Unified Messaging server is installed (For example, 10.15.3.207 for IP Address and...
Page 21
Step 2: SIP Environment and Gateway Name Setup Note: Assign an FQDN name to the gateway (for example, gw2.fxoaudiocodes.com). Any gateway name that corresponds to your network environment is applicable; the only limitation is not to include underscores in the name (Windows Certification server limitation).
Page 23
Step 4: DNS Servers Setup Note: Define the primary and secondary DNS servers' IP addresses so that they correspond to your network environment (for example, 10.1.1.11 and 10.1.1.10). If no DNS server is available in the network, then skip this step.
Page 24
Step 5: Internal DNS Setup Note: If no DNS server is available in the network, define the internal DNS table where the domain name is the FQDN of the Microsoft Unified Messaging server and the First IP Address corresponds to its IP address (for example, exchange2007.com and 10.15.3.207).
Page 25
Step 6: NTP Server Setup Note: Define the NTP server’s IP address so that it corresponds to your network environment (for example, 10.15.3.50). If no NTP server is available in the network, then skip this step (as the gateway uses it’s internal clock).
Page 26
Step 7: Generate Certificate Setup Use the screen below to generate CSR. Copy the certificate signing request and send it to your Certification Authority for signing.
Page 27
Step 8: Uploading Certificates Setup The screen below is used to upload the sign certificates. In the “Server Certificate” area, upload the gateway certificate signed by the CA. In the “Trusted Root Certificate Store” area, upload the CA certificate.
Page 28
5. PBX Setup Notes For our test setup: ext. 1023 is a pilot number of a GW hunt group. Test user phone ext.1000 Step 1: Voice Mail Analog Station Ports Setup Assign Voice Mail analog station ports. Path: Options > Setup Station > Station...
Page 32
Step 2: Voice Mail Analog Hunt Group Setup Configure VoiceMail analog hunt group. Path: Settings > Incoming Calls > Groups/Hunt Groups Ext. 1009 and 1010 are the hunt group members.
Page 35
Step 5: Minimum Flash Timer Setup To configure Minimum Flash Timer: 1) In the Stationview window, choose the Template Editor tab pertaining to the extension. 2) From the Parameter drop-down list, select the option 'Minimum pulse length for flash', and then define the following fields: Factor = 3, Base = 100 ms.
Page 36
Step 6: Maximum Flash Timer Setup To configure Maximum Flash Timer: 1) In the Stationview window, choose the Template Editor tab pertaining to the extension. 2) From the Parameter drop-down list, select the option 'Maximum pulse length for flash', and then define the following fields: Factor = 6, Base = 100 ms.
Page 38
Confirm the Active Directory name of the calling party is displayed in the sender field of the voicemail message. Dial user extension and leave a voicemail The Siemens PBX doesn’t support caller-ID from an external phone. from external numbers (all calls have 02222 calling number).
Page 39
Call Transfer by Directory Search when the called party does not answer. Confirm the call is routed to the called party’s voicemail. Setup an invalid extension number for a Siemens doesn’t support invalid particular user. Call Transfer by Directory number notification and the call is routed back Search to this user.
Page 40
extension. Confirm the FAX is received in the user’s inbox. Setup TLS between gateway/IP-PBX and Exchange UM. Replace this italicized text with your TLS configuration: self-signed certificates or Windows Certificate Authority (CA). Dial the pilot number and logon to a The gateway supports TLS.
Page 41
6.1. Detailed Description of Limitations Failure Point The Siemens HiPath 3550 PBX doesn’t support caller-ID from external numbers Phone type (if phone-specific) All types Call scenarios(s) associated with failure point List of UM features affected by failure point Sender field of the voicemail message for...
7. Troubleshooting The tools used for debugging include network sniffer applications (such as Ethereal) and AudioCodes' Syslog protocol. The Syslog client, embedded in the AudioCodes gateways (MP-11x, Mediant 1000, and Mediant 2000), sends error reports/events generated by the gateway application to a Syslog server, using IP/UDP protocol.
Page 43
3. To determine the Syslog logging level, use the parameter Debug Level and set this parameter to '5'. 4. Change the CDR Report Level to 'End Call' to enable additional call information. Step 4 Step 3 AudioCodes has also developed advanced diagnostic tools that may be used for high-level troubleshooting.
Page 44
Appendix 1. Dial Pilot Number and Mailbox Login • Dial the pilot number of the UM server from an extension that is NOT enabled for UM. • Confirm hearing the greeting prompt: “Welcome, you are connected to Microsoft Exchange. To access your mailbox, enter your extension...”...
Page 45
b. From an External Phone a. From an external phone, dial the extension for a UM-enabled user and leave a voicemail message. b. Confirm the voicemail message arrives in the called user’s inbox. Confirm this message displays the phone number as the sender of this voicemail. 5.
Page 46
• Note: Even though some keys are associated with three or four numbers, for each letter, each key only needs to be pressed once regardless of the letter you want. Ignore spaces and symbols when spelling the name or email alias. a.
• Once it is received in the user’s inbox, use OWA’s Play-On-Phone to dial an internal extension. • Confirm the voicemail is delivered to the correct internal extension. b. To an External Phone number • Dial the extension for a UM-enabled user and leave a voicemail message. •...
Page 48
9. FAX • Use the Management Console or the Management Shell to FAX-enable a user. • Management Console: a. Double click on a user’s mailbox and go to Mailbox Features tab. b. Click Unified Messaging and then click the properties button. Check the box “Allow faxes to be received”.
12. Message Waiting Indicator (MWI) • Although Exchange 2007 UM does not natively support MWI, Geomant has created a 3rd party solution - MWI2007. This product also supports SMS message notification. MWI 2007 website • Installation files and product documentation can be found on Geomant’s 13.
Need help?
Do you have a question about the HiPath3550 and is the answer not in the manual?
Questions and answers