Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Using phantoms for multiple users on a phone, each with DID and voicemail

Multiple Users On One Phone

Using phantoms for multiple users on a phone, each with DID and voicemail

by  phuzzy42  Posted    (Edited  )
USING PHANTOMS TO ALLOW MULTIPLE USERS ON A PHONESET, EACH WITH A DID AND VOICEMAIL

Note: Switches with integrated voicemail, such as Meridian Mail or Call Pilot, should use ACDs instead of phantoms since ACDs don't use up licenses. In my experience with a Meridian 11c and Centigram voicemail (which is external to the switch), ACDs wouldn't work correctly.

The goal is to have one physical phoneset used by several users who each have their own dial-in number and voicemailbox. The physical phoneset is set up normally and has CLS SFA (Secondary Forwarding Allowed) added. Since we'll be forcing the phantom phones to forward to the physical one, we must let the physical phone forward the phantoms' DNs again to voicemail if nobody answers.

On the 11c, phantoms are built starting at loop 61 - check the documentation for your system if you have a different model. Pay particular attention to the CLS and FTR settings. For this example, the physical handset's DN is 3454, the phantom's DN is 3990 , and the voicemail DN is 3980.

Code:
>ld 10

PT0000
REQ:    new                Phantoms cannot be copied (CPY) or moved (MOV).
TYPE:   500                Phantoms are type 500 (analog)
TN      61 1               Phantoms start on loop 61
PHANTOM                    System indicates this is a phantom set
CDEN    <cr>               Card density
DES     TEST               1 to 6 character DESignator
CUST    0                  Customer number (usually 0)
WRLS    NO                 System indicates this is not a wireless phone
DN      3990               This phantom set's extension number
  MARP                     System indicates this is a Multiple Appearance
  CPND new                 Create a new name for Calling Party Name Display
    NAME John,Smith        What another extension sees as a name
    XPLN <cr>              Maximum length of CPND name (defaults to 27)
    DISPLAY_FMT <cr>       Display Format (defaults to FIRST,LAST)
  VMB <cr>                 Create a MerMail or CP mailbox?
HUNT    3454               Where to Hunt to
TGAR    1                  Trunk Group Access Restriction
LDN     <cr>               Listed Directory Number
NCOS    3                  Network Class Of Service
RNPG    4                  Ringing Number Pickup Group
SGRP    <cr>               Scheduled Access Restriction Group
CLS     XFA SFA FNA MWA HTA
                           XFA=Call Transfer Allowed, SFA=Secondary Forwarding Allowed,
                           FNA=Forward No Answer Allowed, MWA=Message Waiting Allowed,
                           HTA=Hunting Allowed
RCO     <cr>               Ringing cycle option
LNRS    16                 Last Number Redial Size
MLWU_LANG  <cr>            Multi-Language WakeUp
PLEV    2                  Priority Level
FTR     FDN 3980           Where calls are forwarded if there's no answer
FTR     CFW 4              Call Forward DNs can be 4 digits
FTR     DCFW 4 3454        Default Call Forward 4 digits to physical phone
FTR     <cr>               End the edit

Note DCFW 4 3454 - this forces the call on the phantom to forward to the physical phoneset. To change the physical phoneset's CLS to include SFA:

Code:
>ld 11
REQ:    chg
TYPE:   3903
TN      13 4
ECHG    yes
TYPE    CLS SFA
TYPE    <cr>

If you get a Loop out of range error message when trying to create a phantom

If you receive an error such as SCH0122, that means phantoms aren't enabled. First, check Common EQUipment in LD 22 to see whether SuperLoop N96 exists.

Code:
>ld 22
PT2000

REQ  prt
TYPE cequ

CEQU
  MPED 8D
  SUPL  000  004  008  012
        016  032  036  040
        044  048  064  068
        072                <-- SuperLoop N96 doesn't exist here
  XCT   000
  CONF  029  030  031  062
        094  095

  DLOP  NUM DCH FRM LCMT YALM T1TE TRSH
   PRI  01 24  ESF B8S  FDL  0    00
  MISP

REQ ****

OVL000

Use LD 97 to create SuperLoop N96.

Code:
>ld 97
SCSYS000
MEM AVAIL: (U/P): 1099977    USED U P: 122328 153950    TOT: 1376255
DISK RECS AVAIL: 236
REQ  chg
TYPE supl                Superloop
SUPL N96                 Add Phantom SuperLoop 96 (N=Phantom, V=Virtual)
WRAP UP SUPL 096  (NEW)  ..OK

MEM AVAIL: (U/P): 1099294    USED U P: 122663 154298    TOT: 1376255
DISK RECS AVAIL: 235
REQ  ****
OVL000

Each SuperLoop gives you the equivalent of four (4) 16-port analog cards (64 TNs). Card numbers in an 11c start at 61, so you can build phantom phones on 61 x, 62 x, 63 x, and 64 x. If you need to build more SuperLoops, use N100 next, N104, etc. (increase by 4).

When a phantom DN rings, it is forced to forward (DCFW) to the physical phoneset - users with displays can see the forwarded number and tell who should pick up. If nobody answers, the call is forwarded again (SFA) to the voicemail DN programmed in the phantom (FTR FDN xxxx).

Mailboxes are set up exactly as if the phantom phones were physical, with the phantom's extension as the mailbox extension number. The users will get no indication voicemail is waiting from a phantom phone, so they'll have to manually check it on their own.

Thanks to Gene Trout for help in figuring this all out.
Register to rate this FAQ  : BAD 1 2 3 4 5 6 7 8 9 10 GOOD
Please Note: 1 is Bad, 10 is Good :-)

Part and Inventory Search

Back
Top