Mitel MiVoice Business SIP Trunk Setup

When integrated with MiVoice Business (MiVB), Revolution may require both SIP trunks and generic SIP extensions (SIP registrations in Revolution) for audio to pass between the two platforms.

• For communications from MiVB to Revolution, such as dialing a specific SIP line number to trigger a notification, SIP trunks are used and must be licensed and configured as such on the MiVB.

• For communications from Revolution to MiVB, such as playing an audio page via the MiVB Group Page feature, generic SIP extensions (SIP Registrations in Revolution) are used and must be licensed on the MiVB via either Enterprise User or Single Line Licenses. This is required because the MiVB Group Page feature requires that a Feature Access Code (FAC) be dialed prior to the Page Group number, and FAC's can only be dialed by an extension. The MiVB does not allow FAC's on SIP trunks.

  • If all audio pages to IP Phones are being done via multicast (and not the MiVB Group Page feature), SIP extensions may not be required.

  • If both SIP trunks and SIP extensions/registrations are provisioned and your Notification includes a MiVB Page Group configured as an Endpoint with the Group Page FAC, by default Revolution will use an available SIP extension/registration to deliver the page.

  • If only SIP trunks are provisioned and your notification includes a MiVB Page Group configured as an Endpoint with the Group Page FAC, Revolution will attempt to use an available SIP trunk, which will fail.

Configuring a SIP Registration for MiVoice Business

Refer to the section Add a SIP registration for details about this configuration.

1. Go to Configuration > Phone Systems > SIP

2. Select New > New SIP Registration.

3. Complete the fields, similar to the following, but using information associated with your MiVB setup

   Field	Description
   Name	Use a name that allows you to easily identify your PBX system
   Priority Group	(redundancy only) Controls behavior in an active/active redundancy environment.
   Registrar URI	Enter the string sip: followed by the registrar URI of your PBX, for example: sip:ourMiVB.company.com
   Address of Record	Enter the address of record string associated with your PBX. For example: 1111@ourMiVB.company.com
   Registrar Interval	Enter an integer for this value per your PBX. The default, 300, may be fine in most circumstances.
   Username and Password	Enter the credentials associated with the Address of Record.
   Realm	Enter one or more realms (comma-separated) associated with your PBX.

A Mitel IP phone can receive an audio page via several mechanisms:

• Multicast – this is the preferred method if possible. Both the Revolution server and the Mitel Paging Relays can deliver multicast audio broadcasts to their local subnets. In this scenario, the IP Phones receive the audio of the page via their configured multicast address. The MiVB is not directly involved in the audio delivery, and neither SIP trunks nor SIP extensions are used.

• Revolution Endpoint – in this scenario, each Mitel IP phone extension number is configured in Revolution as an Endpoint. If this Endpoint is included in a notification that includes audio, Revolution will attempt to dial it directly using either a SIP extension if available, or a SIP trunk if not. This method is not typically recommended, as it requires a 1:1 ratio of SIP trunks/extensions to Endpoints. If there are 10 IP Phone Endpoints configured to receive an audio Notification, then 10 SIP Extensions or trunks need to be available, and all recipients' phones will ring. Each recipient will have to answer and wait until the configured <Endpoint Wait %> of endpoints have answered before the audio will be played.

• MiVB Group Page – in this scenario, only the MiVB Page Group number is configured as an Endpoint in Revolution and includes the Group Page Feature Access Code as part of the dial string. Any number of IP phones can be made a member of that Page Group within MiVB (up to the limits for the controller type). Revolution is not specifically aware of which IP phones may be part of which Page Group. When using Group Page, Revolution must use an available SIP extension to dial the Page Group number so that the Feature Access Code can be included.

Note: You only need to configure this if your organization's security policies require SIP trunk authentication from a user agent (in this case Revolution).

In Revolution:

1. Go to Configuration > Phone Systems > SIP.
2. Leave Inbound Digest Realm blank.
3. Enter a name of your choosing for Inbound Username and Inbound Password.
4. Click Save.

In MiVoice Business > SIP Peer Profile > Basic > Authentication Options,

1. Enter the Revolution Username and Password in the User Name and Password fields here.
2. Click Save.