• No results found

Mobile UC Enabled Accelerator

The section discusses the integration process for a Mobile UC with/without a PSTN Access enabled Accelerator.

The steps below describe the unique configuration areas needed to integrate the Mitel PBX with the Accelerator solution. Refer to the Accelerator

Provisioning Guide for a comprehensive explanation of Accelerator provisioning.

Voice Network: PBX/Trunk Dial Plan

1. Add Trunk Dial Plan (required) – There are no unique configuration items for Trunk Dial Plans and the Mitel PBX. Refer to the Accelerator Provisioning Guide, Voice Networks, PBXs, Add Trunk Dial Plan section.

2. Add PBX (required) – No unique configuration items for adding a PBX.

Refer to the Accelerator Provisioning Guide, Voice Networks, PBXs, Add New PBX section.

If your enterprise intends to use the Route via Enterprise mobile policy by routing Pilot DNs through the PBX to the Accelerator, go ahead and provision the Pilot DNs on the PBX’s main page under the Pilot Numbers section. Note that the Pilots here must be E.164 routable.

Also, if your enterprise intends to use the Call Move service, go ahead and provision the Call Service Pilots on the PBX’s main page under the Call Service Pilot Numbers section. Note that the Pilots here do not have to be E.164 routable. Note that the Call Move feature access code can be found on the Accelerator provisioning page at: Services ->Feature Settings.

Add Trunk Groups/Trunk (required) –

o Host Address, Port and Transport Type should match the IP Address of the Mitel PBX with a port value of 5060.

If the hostname is entered, the Accelerator queries the DNS server for the associated DNS SRV records. This allows for redundancy and/or load balancing based on the DNS SRV records if the customer has deployed multiple Mitel servers. Refer to the Accelerator Provisioning Guide, Voice Networks, PBXs (Add/Modify), Add Trunk Groups/Trunks section.

o Trunk Group Request URI parameters are not used by the Mitel PBX and therefore do not need to be provisioned.

Add Line Groups/Line (required) –

o Host Address, Port and Transport Type should match the IP Address of the Mitel PBX with a port value of 5060.

If the hostname is entered, the Accelerator queries the DNS server for the associated DNS SRV records. This allows for redundancy and/or load balancing based on the DNS SRV records if the customer has deployed multiple Mitel servers. Accelerator Provisioning Guide, Voice Networks, PBXs (Add/Modify), Add Line Groups/Line section.

o Line Group Request URI parameters are not used by the Mitel PBX and therefore do not need to be provisioned.

Add CTI Peer connection (required for Call Move service) - A CTI Peer will need to be configured for each extension range defined for the Mitel PBX.

o Only Use Extension in CTI Requests and Monitor Desk Phones for MWI should both be checked. Refer to the Accelerator

Provisioning Guide, Voice Networks, PBXs (Add/Modify), Add CTI Peer section.

Add Least Cost Routing (optional) - No unique configuration items for Least Cost Routing. Refer to the Accelerator Provisioning Guide, Voice Networks, PBX, Least Cost Routes, Add Least Cost Routes section.

Voice Network: Extension Ranges

3. Add Extension Ranges (required) – No unique configuration items for adding an Extension Range. Refer to the Accelerator Provisioning Guide, Voice Networks, Extension Ranges, Add New Extension Ranges section.

Voice Network: Carrier Gateways

4. Carrier Gateways (required if your enterprise routes calls between the wireless carrier and the Accelerator) – If your enterprise intends to use an SBC or Carrier Gateway between the carrier and the enterprise, then add a Carrier Gateway. Be sure to supply the Outbound Domain as required by the add Carrier Gateway page.

If you are using Pilot numbers to route calls from the wireless carrier to the Accelerator using the Carrier Gateway, provision the Pilot Numbers on the Carrier Gateway’s main page. Depending on your configuration, the Pilot numbers here may need to be E.164 routable.

Add Trunk Groups/Trunk (required if using a Carrier Gateway) – o Host Address, Port and Transport Type should match the value of

the carrier’s SIP endpoint.

If the hostname is entered, the Accelerator queries the DNS server for the associated DNS SRV records. This allows for redundancy and/or load balancing based on the DNS SRV records if the customer has deployed multiple Mitel servers. Refer to the Accelerator Provisioning Guide, Voice Networks, Carrier Gateway (Add/Modify), Add Trunk Groups/Trunks section.

Trunk Group Request URI parameters are normally not required by most SIP endpoints, however, consult your carrier’s instructions.

Add Least Cost Routing (optional) - No unique configuration items for Least Cost Routing. Refer to the Accelerator Provisioning Guide, Voice Networks, Carrier Gateway, Least Cost Routes, Add Least Cost Routes section.

Voice Network : Voice Mail

5. Add Voice Mail for the Mitel PBX in the Accelerator system. Select PBX as the Voice Mail Server Type. Refer to the Accelerator Provisioning Guide, Voice Networks, Voice Mail Servers, Add Voice Mail Server section.

Subscriber Dial Plan/Subscribers

6. Add Subscriber Dial Plan - (required) - No unique configuration items for adding Subscriber Dial Plans. Refer to the Accelerator Provisioning Guide, Subscribers, Add Subscriber Dial Plan section.

7. Add Subscribers (required) - Several items to note when provisioning subscribers:

Enterprise Desk Number - Should match the extension provisioned on the Mitel PBX for the user.

Home PBX – Select the newly created Mitel PBX as the subscriber’s Home PBX.

Direct Inward Dial (DID) - Should match the full national phone

number provisioned on the Mitel PBX for this user. The value here on the subscriber page is recommended if the subscriber’s DID does not map directly to their desk extension. If the subscriber’s DID does map directly to their desk extension, provision their DID in the Extension Range page under the DID Supported section.

SIP Address - Should match the directory number of the Multi-Line user that is associated with this subscriber. This value maps to the Mitel new user’s ‘Number’ bullet found on page 27.

Line Group – Should match the IP address of the Mitel PBX.

Home PBX Provides Orig Svcs – When checked, the Accelerator always originates the call on behalf of the mobile user for mobile originations into their home PBX within the enterprise.

If you have only Mobile UC enabled in your Accelerator license key then you are finished. Proceed to the Useful Commands section on page 33 to verify your configuration.

If you also have PSTN Access enabled, proceed to the next section, PSTN Access Enabled Accelerator on page 32.

Related documents