PBXgateway II Quick Installation Guide
40
5. Done. The office TN is configured to ring 6 times before going into voicemail.
Provisioning the Primary Voice Channel of the Mobile Phone’s TN – Ch1
1. Provision a new TN for the remote phone on the Meridian. Wire this TN into the RemoteConneX
PBXgateway on an available port.
Note: This port does NOT require DID capability.
Tech Tip:
Nortel’s Reach Line cards do no support the secondary channel required for the
RemoteConneX application.
2. On the Meridian maintenance terminal, use
>LD 11
(a.k.a. overlay) to configure this TN to the same
Directory Number (DN) assigned to the user’s office phone.
3. Select a phone
TYPE
that supports Analog Terminal Adapter (ATA) functionality. We recommend
phone type M2616, however other Meridian phone sets that also support the ATA functionality are:
M2006, M2008, M2016, M2216 and M2617. Configure the selected phone with the same class of
service as the user’s office TN.
Tech Tip
: It is NOT necessary for the phone type to match the type
used at the office TN, since only the first ten (10) line/feature buttons are accessible from a mobile
phone.
WARNING: Do not configure a key as Message Waiting Key (MWK) for this TN to prevent
interference with voicemail and call routing functions.
4. On
>LD 11
,
program this TN with the same
RNPG
value as the office TN when prompted.
5. Program
KEY 00 to 9
to match the line keys of the office TN so that all inbound calls will ring at the
office and at the remote phones at the same time.
6. This TN must have a
CLS of FLX
D
, CPT
A
, VCE, WTA.
7. Program any of the first 10 keys to allow A06 (Conference) & TRN (Transfer). Remember these
settings when programming the RemoteConneX PBXgateway.
Provisioning the Secondary Data Channel of the Mobile Phone’s TN – Ch2
1. On the Meridian maintenance terminal, use the
>LD 11
to add Analog Terminal Adapter (ATA)
functionality to this TN. Refer to the
Meridian 1
documentation for more details on programming an
ATA. Although no ATA adapter is used for the RemoteConneX application, the programming
required for the ATA applies to the remote phone’s TN configuration. The ATA functionality must be
added to this TN.
Tech Tip
: Nortel’s Reach Line cards do no support the secondary channel required
for the MobileConneX application.
2. This TN must have a
CLS of FLX
A
, CPT
D
, VCE, WTA.
Tech Tip
: If Ch1 is “TN 3 0 5 0” (loop 3, shelf
0, card 5, unit 0), then Ch2 would be “TN 3 0 5 16”.
3. Program
KEY 00
as Single Call Ringing SCR yyyy. The “yyyy” field should contain the Directory
Number (DN). The SCR appearance MUST be DID capable to allow the mobile user to dial the
Directory Number to access the corporate PBX.
1. Done. The Meridian 1 PBX is now configured to support
one
user.
SCENARIO #2: Only Mobile Phone Is Used
Provisioning the Primary Voice Channel of the Mobile Phone’s TN – Ch1
1. Provision a TN for the remote phone on the Meridian 1. Wire this TN into the MobileConneX
PBXgateway on an available port.
Note: This port must be DID capable
.
Tech Tip
: Nortel’s Reach
Line cards do no support the secondary channel required for the MobileConneX application.
2. On the Meridian maintenance terminal, use
>LD 11 (i.e. overlay)
to configure this TN.
3. Select a phone
TYPE
that supports Analog Terminal Adapter (ATA) functionality. We recommend
phone type M2616, however other Meridian phone sets that support the ATA functionality are:
M2006, M2008, M2016, M2216, and M2617. Configure the selected phone according to the
company’s standard class of service.
