# SIP Phone Support - Programming

## Overview

This topic applies to the programming of SIP phones (Generic and Mitel branded), including Single Line Phones. For Mitel SIP-DECT base station programming, see Programming Mitel SIP-DECT Base Station - Summary.

## Before You Begin

- Ensure that you register the SIP device with MiVoice Business and that only one instance of the prime line(s) is registered. SIP endpoints must not register for shared line appearances.

- Some SIP Phones may use DHCP to obtain the DNS server address, others may directly be programmed with a DNS server address. If a DNS server is used, ensure that it is configured with MiVoice Business' FQDN and matching IP address.

- Ensure that the IP Users and/or Single Line Users licenses are entered in the License and Option Selection form. SIP phones, in general, require an IP User license. However, generic SIP phones can be programmed as Single Line Phones. In this case, a Single Line Users (formerly Analog Lines) license is used instead of an IP Users license.

- Ensure that Class of Service, Interconnect Restriction, and Intercept Handling is programmed for each generic SIP phone.

- Ensure that either Call Forward No Answer (CFNA) or system rerouting is programmed for SIP phones. This ensures that calls receive predictable behavior because MiVoice Business may not always be aware of the SIP device state due to the nature of the SIP protocol. For example, if CFNA is programmed, users can take advantage of the SIP Call Reject feature to redirect incoming calls to their CFNA destination.

- Generic SIP devices need a Mitel root certificate to connect to the MiVoice Business system. The certificate is provided in the Device Certificate form . To install it, follow the instructions provided by device manufacturer.

## Programming

To program SIP telephones, use the following forms:

1. Network Elements form (applicable only for SIP-DECT devices)

2. Add the SIP-DECT Manager as a network element.

2. SIP Device Capabilities form

Many Mitel SIP devices have a pre-programmed SIP Device Capability that is automatically selected when the Device Type is programmed. On pre-programmed SIP Device Capabilities there are just a few options that can be modified for site-specific requirements. Devices with pre-programmed SIP Device Capabilities are: 5603, 5604, 5607, 5610, 5613, 5614, 5624, UC Endpoint and 612/622/632/650 SIP-DECT endpoints.

NOTE: If possible, import data into the form using the Import function; see About Importing Form Data for details. If form data is not available, continue with the following steps.

- To program the SIP device as a multiline set or to use local set conference capabilities, set the "Replace System based with Device based In-Call Features" field to 'Yes' (recommended for all SIP sets). Complete the other fields as required. Additionally, at least one of the keys of the SIP device must be configured as Multicall to its own prime DN in the Multiline Set Keys form.

- Many SIP sets provide their own local conference capability, which is useful for 3-party conferences. In order to use MiVoice Business hosted conferences for larger conferences, SIP phones can Refer a call on a second line to the Conference Call Feature Access Code (FAC). The code can either be pre-programmed into a menu item or key on the phone, or it can be entered manually and sent by the phone in a REFER message. For example, to enter a FAC manually on an IP DECT (Global) Solution wireless handset, the user presses the "r" key twice and then dials the code. Additional conference attendees can be added in the same way.

- To support Callback, Busy Override, and Camp-on on SIP phones, set the Enable Digit Collection During Busy or Alerting State option to "Yes".

- To enable only devices with TLS to register and place calls, set the TLS Only option to "Yes".

- To enable distinctive ring tones for internal calls, external calls, and callbacks to SIP phones, set the Distinctive Ring Tones option to "Yes".

- Set the method that the system should use to support Call Park and Retrieve for SIP phones. See the Support for Call Park option in the Device Capacities form.

- To prevent the system from updating SIP phone displays with connected party name and number information during transfers, conferences, and call forwarding scenarios, set the Allow Display Update to "No".

- To set up Inward Dialing Modification for inbound calls, add new rules in the Inward Dialing Modification form ( ), and then associate the rules to the SIP device in the SIP Device Capabilities form.

- Set "Invite Ringing Response Timer" to a value other than the default, 0. A non-default value ensures that calls to an out-of-range 5624/5634 SIP Wireless Handset enters out-of-service state instead of busy or receives Call Forward No Answer treatment.

- In Call Routing and Administration Options, set "Replace System based with Device based In-Call Features' to 'No' to allow single line phone the ability to use System Based transfer and Conference feature.

- To support Secure Real-time Protocol (SRTP) voice encryption, set the Allow Device To Use Multiple Active M-Lines option to "Yes" and AVP Only Device to "No". Setting the first option to "Yes" is necessary to deal with negotiations between two M-lines only one of which supports SRTP. Ensure that Voice Encryption Enabled and Voice/Video SRTP Encryption Enabled are set to "Yes" in the System Options form.

NOTE: To prevent SRTP negotiations with a SIP device, set the option "AVP only device" to "Yes". This will limit negotiations to AVP and allow unencrypted media streaming only.

3. User and Services Configuration form

Complete the Device Type, Service Level, Directory Number, User PIN (if applicable), SIP Password, Interconnect Number, and Tenant Number fields. Assign a name, department, and location to the directory number. Change the SIP Device Capabilities number if you want to override the pre-programmed number and use a user-defined SIP Device Capabilities number.

3. The following device types are supported: 5302 IP Phone, Generic SIP Phone, 5505 SIP, 5603 SIP, 5604 SIP, 5607 SIP, 5610 SIP, 5613, 5614, 5624, 5634, UC Endpoint, and the following SIP-DECT devices: 612, 622, 632, 650.

4. User PIN is for Hot Desk user authentication. SIP Password is for regular SIP device registration and authentication. The username for both is the DN.

When programming a SIP-DECT device:

- Select the Sync with SIP-DECT Manager check box.

When programming a Single Line Phone:

3. Select 'Generic SIP Phone' as the Device Type.

4. Set the Service Level to Full.

5. Select the Single Line Phone check box. (When selected the Keys tab is automatically grayed out and cannot be used.)

4. Multiline Set Keys form (not applicable to Single Line Phones)

- To program the 5302 IP phone as a multiline set, program Button Number 2 with a Line Type of "Multicall." Enter the directory number of the 5302 IP Phone in the Button Directory Number field.

- To program all other SIP devices as multiline sets, program one or more additional buttons with a Line Type of "Multicall". Enter the directory number of the SIP device in the Button Directory Number field. Note that entering DNs of other devices is not supported.

5. (Optional) Multiline Appearance Groups form (not applicable to Single Line Phones)

- Change the ring type at each telephone where this number appears.

- Change the group type from "key system" to " multicall" or vice versa.

6. (Optional) Default Account Codes form

- Create a default account code number that will appear in all SMDR records for the station.

7. (Optional) Station Attributes form

- If the User and Services Configuration form was not used to create this device, assign a Class of Service, Class of Restriction, and Intercept Number to the directory number of the telephone. Change the SIP Device Capabilities number if you want to override the pre-programmed number and use a user-defined SIP Device Capability number.

- (Optional) Assign a Default Account Code Index number.

8. SDS Form Sharing

- Ensure that the SIP Device Capabilities form is shared. The default is "All Cluster Members." You can also restrict records from being shared by specifying the SIP Device Capabilities Numbers not to share in "Records Not Shared" portion of the form.

9. Class of Service Options

Configure the following parameters:

- Set "Public Network Access via DPNSS" to Yes in the COS of SIP Phones to allow calls over trunks (including SIP trunks).

- Set Force Device Busy If Any Line In Use to Yes to prevent phones from receiving calls when they are already engaged in a call.

- Disable the Auto Camp-on Timer to allow devices to hear busy tone when calling busy extensions.

NOTES

- If no telephone directory name is programmed for a SIP device on MiVoice Business, the system will default to the SIP display name. For some SIP devices, the SIP display name can be provisioned. For others, such as the Phone or 5610 SIP, the display name cannot be provisioned and defaults to the "username" which is typically the DN of the device. To prevent users of generic SIP devices from programming their own display name, you should always add an entry and provide a name for all of these devices in the Telephone Directory form.

- If you delete telephones, you must also delete the corresponding directory entries and voice mailboxes.

Related Topics

- SIP Phone Support - Description

- SIP Phone Support - Conditions

- SIP Phone Support - Maintenance