Configuring for Integra Telecom SIP Solutions

Transcription

1 February 2013 Configuring for Integra Telecom SIP Solutions

2 Section Title Page Background 1 Table 1 Software & Firmware Versions Tested 1 Figure 1 Generic IP PBX Test Configuration (with Transparent SIP Proxy) 1 Configuration Steps 3 Section 01: Initial MCD Connection & Login 4 Section 02: MCD Configuration 8 Form Name: Class of Service Options 8 Form Name: Codec Settings 10 Form Name: Date and Time 10 Form Name: DID Ranges for CPN Substitution 11 Form Name: Fax Advanced Settings 11 Form Name: Fax Services Profiles 12 Form Name: LAN Policy (QoS) 12 Form Name: Network Elements 13 Form Name: Network Zone Topology 14 Form Name: Network Zones 15 Form Name: SIP Peer Profile 15 Form Name: SIP Peer Profile Assignment by Incoming DID 19 Form Name: System IP Ports 19 Form Name: System IP Properties 20 Form Name: System Options 22 Form Name: System Speed Calls 21 Form Name: Trunk Attributes 22 Form Name: Trunk Groups 23 Form Name: Maintenance Logs - Info 23 Form Name: Backup 24 End of Configuration Procedure 25 Troubleshooting 26 Steps 01-07, Customer Side 26 Steps 08-12, Integra Telecom Side 27 ii

3 This document provides general technical guidance for configuring the Mitel Communications Director (MCD) IP PBX (a.k.a. Mitel 3300) appliance to properly interface to and interoperate with the Integra Telecom SIP Solutions trunks. It is not intended to serve as a step-by-step configuration guide. The goal of this document is to ensure that when properly configured the MCD will interoperate with Integra Telecom s SIP-based equipment and network. In order to establish a configuration and compatibility baseline, Table 1 below shows the software and/or firmware versions used for testing and evaluation in the Integra Telecom Lab. Table 1 Software & Firmware Versions Tested Network Element Version Metaswitch Call Feature Server SU11 Adtran NetVanta 3305 Proxy R E and R E Mitel MCD 3300 Release Level 6.0 Mitel MCD 3300 Active Software and The generic IP PBX test configuration is shown in Figure 1 below. This configuration ensures proper SIP call handling between the customer-supplied IP PBX platform and the Integra Telecom equipment and network. Figure 1 Generic IP PBX Test Configuration (with Transparent SIP Proxy) IP PBX PSTN Metaswitch Call Agent Acme Packet SBC WAN w Adtran SIP Proxy LAN Data Note: Some schools of thought like to consider everything outside of or beyond the IP PBX itself to be part of the PSTN. For this testing, the beginning of the PSTN does not matter; as in to and out of the IP PBX are the more important considerations. Page 1 of 27

4 It is very important to note that this document only addresses the SIP trunk side of the Mitel MCD Items such as; internal Quality of Service (QoS) policies, IP Phones (with attendant firmware upgrades), dial plans and call routing, feature and long distance access codes, along with end-user accounts and passwords are not part of this configuration document. Page 2 of 27

5 It is presumed that there is direct knowledge and expertise or that knowledge and expertise is readily available for the MCD. Therefore, this section contains the data fill for the various configuration forms, using the Mitel System Administration Tool. The forms are addressed below in alphabetical order. There is no consideration given to element/object dependencies or provisioning hierarchy. The information provided is the data fill needed for interop. The following is a mini legend of the configuration parameters that are detailed within this document. Mandatory Integra Provided Entry The red outline boxes indicate that the information is mandatory as provided by Integra Telecom. This includes settings, data fill, as well as detailed account information as provided. Customer Defined Entry The blue outline boxes signify that the customer selects the desired provisioning data fill. Examples include: private IP addresses and user-friendly object names for provisioning. Page 3 of 27

6 Section 01: Initial MCD Connection & Login Connect (via an Ethernet cable) the selected personal computer (PC) to the same local area network (LAN) that contains the Mitel MCD 3300 device. Start the Microsoft Internet Explorer (IE) application (the only officially supported web browser for the MCD). Although other web browsers, such as Mozilla Firefox and Google Chrome can emulate IE tabs via add-ons, their complete compatibility cannot be assured. Thus, it is best to simply use the Mitelspecified web browser: IE. In the IE address bar, enter the IP Address of the MCD to be configured. In this example, the IP Address for the MCD is: This is shown outlined in blue below. Press the Enter Key to continue. At this point, a Certificate Error warning message may be displayed in IE. This is an attempt to protect the user by blocking navigation to a website (the MCD in this case) with questionable credentials. This must be bypassed in order to continue. Because the MCD is actually a known and trusted website, select the Continue to this website (not recommended) link. This is shown outlined in red below. Page 4 of 27

7 Next, the Mitel Terms and Conditions page is displayed. Select the Accept button to continue. This is shown outlined in red below. Page 5 of 27

8 Next, the MCD login page is displayed. Enter the appropriate user credentials in the Login ID: and Password: fields. This is shown outlined in blue below. Press the Log In button to login and continue. This is shown outlined in red below. The MCD will now display the tool launch webpage. Select the System Administration Tool button. This is shown outlined in red below. Page 6 of 27

9 Finally, the MCD System Administration Tool webpage is displayed as shown below. It is recommended that a confirmation the software version in the MCD be executed. Select the About hyperlink in the top right navigation portion of the page. This hyperlink shown outlined in red below. As shown above, this example MCD is running Release Level 6.0 and Software Load This is shown outlined in blue above. At the top of the left side navigation menu, select View Alphabetically in the drop down menu list. This is shown outlined in red below. Page 7 of 27

10 Section 02: MCD Configuration Within the Systems Administration Tool the forms listed below provide the data fill requirements (outlined in red) and recommendations (outlined in blue). Each form name is provided with a screen shot of the selection for clarity. In addition, the necessary notes related to the data fill examples are shown below. Form Name: Class of Service Options Change an existing Class of Service to include the desired call services for the new SIP trunk. Alternately, the new SIP trunk may be added to an existing Class of Service that may already be in use. Page 8 of 27

11 If Call Forwarding to the new SIP trunk is desired, the Call Forwarding (External Destination) option must be set to Yes. This is a discretionary parameter; thus, the customer must be aware of the security and billing implications. To allow for T.38 faxing on the new SIP trunk, the Fax Capable option must be set to Yes as shown above. Appropriate T.38 licensing must be provided by Mitel. The new SIP trunk serves as an interface to and from the Public Switched Telephone Network (PSTN). Therefore, the Public Network Access via DPNSS option must be set to Yes. A discretionary parameter is Public Network to Public Network Connection Allowed. This option will impact Call Forward, Call Transfer, and Three Way Call scenarios. While these scenarios may be desirable, the customer must be aware of the security and billing implications. Note that DPSS (Digital Private Signaling System) is the European Union equivalent to the North American PSTN. Page 9 of 27

12 Form Name: Codec Settings Use Change to filter (disable) the undesired Codecs to provide the MCD Codec set used in SIP Session Discovery Protocol (SDP) messages. If G.729a licenses are available, this option should be set to No. The G.729a Codec is the preferred Codec for the new SIP trunk. For T.38 faxing the T.38 Codec (protocol) must be set to No. Note that the G.711a and G.711u Codecs cannot be filtered (set to Yes ). Form Name: Date and Time Page 10 of 27

13 If desired, the Integra Telecom Network Time Protocol (NTP) servers may be used for time of day synchronization. The host name is shown above. The Change button is used to configure these parameters. Form Name: DID Ranges for CPN Substitution Internal extensions may be configured for individual, 10-digit Calling Party Number (CPN) value substitution. Change one or more of the 20 available ranges. Form Name: Fax Advanced Settings The parameters above must be set (using the Change button) to allow proper T.38 faxing support. This configuration ensures that ITU-T V.17 (G3) and ITU-T V.34 (Super G3) facsimile transmissions, via T.38, are successful. Change values to those shown above. Page 11 of 27

14 Form Name: Fax Services Profiles Change the default Inter-Zone Fax Profile. Set the Maximum Fax Rate to the desired rate. The recommendation is V.17 at 14.4 Kbps as shown above. High Speed Redundancy, Low Speed Redundancy, Error Correction Mode (ECM), and Override Non-Standard Facilities (NSF) options must be configured as shown above. Next, assign ( Change Member ) the Inter-Zone Fax Profile created above to an Intra-Zone Fax Service Profile. Note that typically, default values are left alone as Profile 1. A new profile is created with the desired values. Form Name: LAN Policy (QoS) Page 12 of 27

15 In order to match the QoS values on the new SIP trunk and the Integra Telecom network, inspect and ensure the Voice Media DSCP value is 46. This is the default value for RTP audio. Change (using the Changer Button ) the Voice Signaling DSCP value to 24. The default value is 26. Form Name: Network Elements Using the Add button, create a Network Element for the new SIP trunk. Page 13 of 27

16 The Name field is a customer defined name for the new SIP trunk. The Network Element Type is Other as selected from the drop down menu. The data fill for the FQDN or IP Address field will be an FQDN value provided by Integra Telecom. In this example, the FQDN is: paroxy1.integravoip.net. The Zone field is the value that is to be set up for the Network Element. In this example, the Zone is 5. Enter the remaining mandatory values, as shown above, in the SIP Peer Specific configuration fields. The transport type must be UDP in all instances. Likewise, the ports will always be The FQDN value will be the same as provided above and will be provided by Integra Telecom. Form Name: Network Zone Topology When the Zone is created (below), it may optionally be assigned to parent and ancestor groups. This is customer discretionary routing for the new SIP trunk. In this example, Zone 1 includes T.t8 Faxing capabilities. Zone 5 has RTP compression enabled; allowing the G.729a Codec to be used on the new SIP trunk. No specific hierarchy was needed in the test environment. Page 14 of 27

17 Form Name: Network Zones As desired, Change one or more of the 999 available Network Zones to allow for T.38 faxing and RTP compressed Codec use. Again, this is a customer discretionary series of fields; based in the routing needs for the MCD. Form Name: SIP Peer Profile Add a new SIP Peer Profile for the new SIP trunk. The Zone assignment should be made to ensure the appropriate RTP Codecs are used. Configuring this section is the key to ensuring the MCD will work with the Integra Telecom SIP Solutions trunk. Page 15 of 27

18 In the Basic tab, the Network Element value must agree with the one set up in that section. The Registration User Name, Authentication User Name, and Password values are provided by Integra Telecom. The Maximum Simultaneous Calls value is the number of SIP sessions as ordered by the customer. No Authentication is needed for incoming calls. This is a drop down menu selection. Finally, the IP Address radio button for the Address Type field must be selected. All radio buttons on the Call Routing tab should be set to No. Page 16 of 27

19 In the Calling Line ID tab, enter the Default CPN [Calling Party Number] and Default CPN Name as provided by Integra Telecom. The remaining parameters should be set as shown above. Skip to the Signaling and Header Manipulation tab. The Trunk Group Label field should be filled with an easy to remember and identify name for the group. It is mandatory to select the No radio button for the E.164: Enable sending + parameter. The remaining parameters should patch those shown in the screen shot above. Page 17 of 27

20 In the Timers tab, the values for Keep-Alive (OPTIONS) Period, Registration Period, Registration Period Refresh (%), and Registration Maximum Timeout values as shown above. The important parameter is Registration Period Refresh (%). This must be set to 99(%) to prevent excessive Registration chatter. The value for Session Timer is an optional limitation on the duration of a call (a SIP session). Any value entered other than 0 (infinite) will result in automatic disconnect of calls in progress when the time expires. Continue to the Key Press Event tab. Subscriptions and Subscription Events are not supported by Integra Telecom on the SIP trunk. Therefore, all values in this tab must be set as shown above. Page 18 of 27

21 In software version there is an Outgoing DID Ranges tab. The tab was deprecated in software version This information is also covered in the DID Ranges for CPN Substitution section above. DID ranges may be set up here if desired. Form Name: SIP Peer Profile Assignment by Incoming DID Incoming DIDs and/or DID ranges may be set to correspond with the SIP Peer Profile Label as shown above. If desired, Add an entry using the Add button. The SIP Peer Profile Label value must be selected from the auto populated drop down menu. Form Name: System IP Ports The SIP UPD Port must be set to 5060 in the text box. The TCP and TLS protocols are not used; facing the new SIP trunk. However, internally, they may be in use and should be set to the corresponding values for internal traffic. Page 19 of 27

22 Form Name: System IP Properties The Host Name parameter may be set to any customer defined value. The System IP Address and Subnet Mask values are also customer defined. These values must be provided to Integra Telecom to allow appropriate configuration of the equipment. Integra Telecom will provide a Gateway IP Address based on the other information entered on this form. At the bottom of the page, the Domain Name Service (DNS) portion of the form must be completed. The Domain Name for the MCD is provided by Integra Telecom. If the Integra Telecom DNS servers are to be used, the IP Addresses above must be entered in the Primary DNS Server and Secondary DNS Server fields. Otherwise, customer provided or public DNS servers may be used. Page 20 of 27

23 Form Name: System Options There are about 70 options and parameters on the System Options form. One to review and consider for modification is the Maximum CO Trunks In A Conference value. This is a discretionary parameter. This option will impact Three Way Call and other Conference Call scenarios. While these scenarios may be desirable, the customer must be aware of the security and billing implications. Form Name: System Speed Calls Page 21 of 27

24 System Speed Calls may be used to rudimentary DID-to-extension routing. In the example above, incoming DID had six digits removed and a 7 prefixed. Then, is forwarded to extension This DID digit manipulation is set in the Trunk Attributes section coming up next. Form Name: Trunk Attributes Select one of the 150 available Trunk Service Number rows. Use the Change button to configure the selected row. The trunk must be placed in the appropriate Class of Service to allow the desired call traffic and routing. In this example, six of the ten inbound digits are removed. This is the Dial In Trunks Incoming Digit Modification Absorb field. The digit 7 is inserted for the System Page 22 of 27

25 Speed Calls form previously mentioned. This is completed using the Dial In Trunks Incoming Digit Modification Insert field. The Trunk Label is a discretionary value for the name of the trunk. Form Name: Trunk Groups The new SIP trunk may be added to an existing Trunk Group. Alternately, a new Trunk Group may be created by using the Add button. In this example, a single SIP trunk was used and establishing a Trunk Group was unnecessary. If the discretionary Trunk Group is configured, then the new SIP trunk must be added to the Trunk Group created or amended above. The Add Member button is used for this purpose. Again, in this example, this form was not used. Form Name: Maintenance Logs - Info Page 23 of 27

26 In order to confirm that the new SIP trunk is operational, authenticated, and successfully registered with the Integra Telecom Metaswitch Call Feature Server, the Maintenance Logs Info form may be used. In the Maintenance Info Logs window, scroll down to find an entry with details equivalent to this example: SIP trunk Meta Account Registrar proxy1.integravoip.net has registered successfully. The registration will expire in 30 seconds. Form Name: Backup Page 24 of 27

27 It is highly recommended that a Backup of the configured database be completed at this time. This process is administered via the Backup form. The details of the database backup ate customer discretionary and are shown above. Select the Start Backup button to commence the automated process. END OF CONFIGURATION PROCEDURE At this point, the Mitel Communications Director MCD 3300 appliance is properly configured to interface with the Integra Telecom SIP Solutions trunk. Calls in to and out of the IP PBX should also be possible at this time. If this is not the case, proceed to the next section; Troubleshooting: Items to Check. Page 25 of 27

28 Comprehensive troubleshooting of a SIP Solutions trunk that does not properly authenticate and register is not part of this configuration document. However, experience has shown that there is a reasonable list of basic Items to Check as part of the nominal customer turn up process. Traditionally, one or more of the following steps of confirmation and basic troubleshooting will yield the location of any problem(s) with the exchange of SIP messaging. Confirming the SIP Register message within the Integra Telecom s BrixWorks monitoring system generally provides a wealth of information on the nature of the issue; including any possible improper configuration. Therefore, it is appropriate to initiate that step only after the initial customer site configuration confirmation and connectivity testing has been completed (Steps 1-7 inclusive). This section represents a logical troubleshooting methodology from the customer location to the Metaswitch Call Feature Server. Items to Check 01. Confirm that the Mitel Communications Director MCD 3300 s WAN port is properly connected to Adtran demarcation device s LAN Ethernet port (typically, eth 0/0 ) with active LED illuminated. 02. Confirm the MCD 3300 has the proper WAN port TCP/IP interface configuration (IP address, Subnet mask, Default gateway, and Primary and Secondary DNS server). 03. Confirm the MCD 3300 can ping the LAN gateway IP address (inside) of the Adtran demarcation device at the customer site. 04. Confirm the MCD 3300 can ping the WAN IP (outside) address of the Adtran demarcation device at the customer site. 05. Confirm the MCD 3300 can resolve, ping, and if necessary, trace route to the FQDN (provided by Integra Telecom) of the Metaswitch Call Agent serving the customer site. 06. Confirm with Integra Telecom that the SIP account information provided for the MCD 3300 SIP Peer Profile data fill configuration (FQDN, Username, Password, etc.) is correct. 07. Confirm that the information provided by Integra Telecom is properly entered in the MCD Page 26 of 27

29 08. Confirm with Integra Telecom that they can see the SIP Register messages from the MCD 3300 within the BrixWorks call monitoring system. 09. Confirm with Integra Telecom that they can ping and, if necessary, trace route to the WAN IP (outside) address of the Adtran demarcation device at the customer site. 10. Confirm with Integra Telecom that they can ping and, if necessary, trace route to the LAN IP (inside) address of the Adtran demarcation device at the customer site. 11. Confirm with Integra Telecom that they can ping the WAN IP address of the MCD 3300 appliance from within the Adtran demarcation device at the customer site. 12. Confirm with Integra Telecom that they can resolve, ping, and, if necessary, trace route from within the Adtran demarcation device to the FQDN of the Metaswitch Call Agent serving the customer site. Page 27 of 27