››

Mitel Softswitch Integration

Introduction

This document will detail the steps for configuring the Tellabs system for Mitel Softswitch integration.

Document Number

ENG-010579

Applies To

This document applies to the 142R, the 729GP and all OLTs. The recommended software for support of this feature is SR29.1 or above as this is the minimum release for supporting the 142R.

Assumptions

This document only covers the configuration needed for proper interoperability with the Mitel Softswitch. The document assumes the following is true:

TConfig is Set Up: TConfig is the Tellabs Configuration tool for voice and is a part of the EMS software. TConfig should configured properly and operational on the OLT prior to starting this AppNote. If TConfig has not been set up, or you are unsure of its status see ENG-010473 Configuring Softswitch Voice found on the portal. Execute only the portions associated with TConfig Setup and ONT VoIP tab setup.
EMS is reachable from the ONT: The EMS TConfig tool must be able to communicate with the EMS either via having a routed path to the ONT, or a secondary NIC on the voice VLAN. This is necessary for XML file download. Prior to starting this procedure, you should have verified that the ONT has an IP address and can successfully download configuration data from the EMS. Ensure the ONT shows an IP address on the VoIP tab and that the ONT is pingable from the EMS. Resolve any networking issues prior to configuring voice.
DHCP Server Present on the Network: There must be an operational DHCP server on the VLAN designated for voice. The ONTs only support DHCP. The DHCP Response MUST include option 6 to define a DNS entry. If you do not set this up, you will have a DHCP Server Incomplete Response alarm on the EMS for each ONT.
Optional DNS Server: If you intend to use hostnames, then a DHCP server must be defined on the voice network, and it must have entries to resolve the needed hostnames. If only IP addresses are used for reaching the Softswitch then the DNS Server is required. The DNS server entries if used must be configured in DHCP to hand the DNS entries to the ONT. DHCP Option 6 is the only mechanism supported for communicating the DNS server IPs to the ONT.

Tellabs ONT Configuration

This section will give a sample configuration for the Tellabs ONT that is known to work with the Mitel Softswitch for all tested features.

The Tellabs ONT is primarily configured via three standard profiles which define the connectivity to the switch and standard policies for voice lines. Most installations only require one or two sets of profiles based on usage.

The three profiles used by the system are:

Equipment Profile - This profile defines TConfig refresh interval, SIP timer settings and country code/region.
Service Profiles - Service profiles define how to connect to the switch and the registrar. It also allows configuration of the RTP and SIP layer behaviors.
Call Features Profile - Defines the switch type, Dialing plan, Call features supported, hotline/warmline, etc.

Tellabs Equipment Profile

The Equipment profile defines basic connectivity settings for the system. The default profile in most instances will work well for most users. The Equipment Profile defines the following settings:

TConfig Refresh Interval - How often the voice line should poll the server for changes in the profiles. Default is once per day. (This only affects global changes to profiles when no line changes have been performed).
SIP Timers - Allows configuration of Key SIP timers. Typically changes to this are not required.
Country Code - Allows configuration of the call progress tones and local impedance for the voice line to match other countries and regions. The default is US.

Detailed Explanations for each field can be found in Tellabs documentation if modifications are required. Most installations only have a single Equipment Profile for all lines. Typically, the default Equipment profile can be used without modification.

The Default profile has the following characteristics:

Expects UDP operation on standard SIP port 5060.
Refreshes profiles once per day (only affects global changes to profiles where no line change is made.
Sets the lines for US tones and impedances.

Tellabs Services Profile

Only a few modifications are needed for proper operation of the system with the Mitel Softswitch.

Registrar URI - The Registrar URI should be set to the IP Address of the Mitel Softswitch.
Proxy Address - The Proxy Address should be set to the IP address of the Mitel Softswitch.
Outbound Proxy - The outbound proxy can be left blank for all ONTs except for the 729GP. The 729GP requires an outbound proxy for proper operation.
729GP example(substitute your IP): <10.10.10.20>
Realm–Therealmdefinesthesecurity realm to which the SIP line will be authenticated. It is critical that this match the Softswitch or authentication will fail and no voice service will be possible. The ONT strictly enforces checking of the realm and will discard all messages without a matching realm when challenged for authentication. The default realm for many devices is the switch IP. You must consult the Softswitch administrator to find this setting. This is the most common issue with authentication. The 142R will echo whatever is sent from the switch in the realm, so for that ONT the setting is less critical.
EnableRFC2833 – It is recommended that RFC2833 be enabled. This tells the ONT to send dialed digits as messages rather than audio. Typically, this works better with PBX style switches that are using audio feedback and/or using low bandwidth codecs.
Register Headstart – For proper operation, it is critical that the registration interval on the Softswitch be several times the value of the registrar headstart in the Services profile. If this is not true it can cause problems with registration with the switch. The register period configured in the ONT is only a suggestion to the switch and the switch will define the registration interval. It is recommended that the minimum registration interval on the Mitel Softswitch be set to 3x the register headstart

The following changes should typically be made to the profile:

Interdigit Timer – This timer defines how long the system will wait to consider dialing complete before sending the digits. A value of 8 seconds is recommended, but can be tuned to the sensibility of users. Some dial slowly, others want more responsivity.
Critical Timer – Defines the time to wait when there is a partial match on multiple patterns in the dial plan (such as when 7 digit and 10-digit dialing is supported). Digits are sent after a partial match is found and the Critical timer expires with no other digits dialed.
Timed Release – This defines the amount of time the line must be on hook before the call is terminated. Three seconds is the recommended setting.

Tellabs Call Features Profile

It is recommended that two Call Features profiles be created, one with Call Waiting On, the Other with Call Waiting Off. This allows control over whether the users can use these features. Most other features should be enabled and allow the switch to control them. Since Call Waiting is an endpoint function, it should be controlled at the ONT.

If the Mitel has not been added to the list of switches in your EMS it may be necessary to add it on the TConfig Profiles->General Tab.

Softswitch Name Full Form – MITEL-3300
Softswitch Short Form – MITL
Add + Apply – You MUST press both Add followed by Apply so that the new Softswitch will be added. If Apply is not pressed, the entry will NOT be added

The following fields should be modified:

Softswitch Name – Mitel-3300
Digit Map – Load the appropriate digit map for your installation. Typically, one of two profiles will be used:
- Standard-NorthAmerican-Dialplan – Defines a standard dial plan used for lines where it has a typical telco dialing plan for North America. Defines 7-digit dialing, 10-Digit Dialing, 911 with emergency headers, info numbers (211,311, etc), and standard Vertical Service Codes.
- Standard-NorthAmerican-PBX-4digit Dialplan – Defines additional patterns necessary for 4 digit extensions not beginning with 9, and all standard North American dialing plan when prefaced with a 9 to get out to the PSTN. This is typically the correct dial plan for Enterprise and Hospitality.
- Dial Plan Changes – Dial plans can be quite complicated and Tellabs only supports changes to dial plans when any changes are made with the support of Tellabs TAC. Customer changes made without Tellabs TAC support must be supported by the customer.
Enable CW – Recommend creating two Call Features Profiles, one with Call Waiting enabled (with –CW at the end of the profile name) and one with Call Waiting Disabled (with –NoCW at the end of the profile name). This allows control over which users have call waiting and which have no call waiting.
Hold – Recommend Hold being allowed on all profiles.
Enable 3WC – Enable Three Way Calling for users. Typically, can also be configured on the switch side.
Message Waiting – If the message waiting light or stutter dial tone is needed, it is controlled by this attribute. Message waiting MUST be properly configured on the switch for proper operation.
- Visual – Enables the message waiting light on phones that support FSK based message waiting lights. NEON and Voltage Based PBX message waiting lights are NOT supported.
- Audible – Enables the stutter dial tone indication for message waiting.
Enable Caller ID – Typically should be set to Enabled. It can also be controlled on the switch so enabling it allows it to be driven by the switch side.

Voice Line Configuration

Each voice line must be configured with the per user configuration.

This is done via the Ports View->Voice Tab, and right click / properties Menu.

With the SR29.1 load, the entire configuration can be made from the gridded display for all lines:

The following fields should be entered:

Description – Name given to the line. Typically used to identify users name.
AOR URI – For simple installations, just enter the users phone number or extension. The EMS upon apply will construct the AOR as follows: sip:<phone_num>@<proxy_address> which is taken from the Services Profile. If desired, the AOR can be explicitly entered to match local needs. The Cisco Call manager by default appears to accept the IP address of the Call Manager for registrations. Hostname/Domain can be used in the proxy address part of the AOR if needed.
Contact URI User – will be auto populated and typically should not be modified.
Softswitch User – The username used to log into the switch. On most systems, it is the directory number, but varies by installation.
Softswitch Password – The password sent to the switch as part of digest authentication of the switch line. The password will only be used if authentication is on and the switch challenges registrations or outgoing calls. The system requires that a password be entered, so enter a dummy password if authentication is off on the switch.
Services Profile – Select the services profile defined in the previous steps.
Call Features – Select the Call Features profile defined in the previous steps.

Mitel Switch Configuration

Mitel SIP Device Capabilities

The SIP device capabilities on the Mitel switch defines what is essentially a SIP profile which defines all of the settings for devices of that type. Information is configured on the tabs to define how to interface with the Tellabs ONTs. The following section defines the SIP capabilities settings:

Basic Tab

It is KEY that Allow MWI Notifications without Subscriptions is set to YES. Without this, MWI(Message Waiting Indicator, or Message waiting light) will not work properly. Note that all Tellabs ONTs ONLY support FSK based MWI lights. Voltage or Neon message waiting lights will not work.