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 IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DNs assigned to virtual set go to reorder 1

trmg

IS-IT--Management
Sep 23, 2007
184
US
Hello!

I have a Meridian 1 Option 11C running CS1K 5.5. I am attempting to configure a virtual set that is the MARP for a group of SCRs. The idea being that I can configure them on the virtual set and leverage line key hunting (LHK) to hunt through them regardless of how the physical set are configured. I have never built a virtual set before and, naturally, I'm running into an issue that's likely something easy I am overlooking.

Any SCR I define on the virtual set I have built (3904V) when called gets reorder. If I configure DCFW to point somewhere, calls are then happily forwarded.

The virtual set configuration is below. I have the two SCRs defined on a M2616 as well. When these SCRs are assigned to the 3904V, the M2616 never rings unless I remove them from the virtual set. And as stated before, if I define DCFW, calls to these SCRs are forwarded. If I undefine DCFW, calls to these SCRs go to reorder (RELEASE AND TRY AGAIN). What dumb thing am I missing?

Code:
DES  TSTVRT
TN   064 0 00 00  PHANTOM
TYPE 3904V
CDEN 8D
CUST 0
ERL  0
FDN  3999
TGAR 1
LDN  NO
NCOS 0
SGRP 0
SCI  0
SSU
XLST
CLS  CTD FBA WTA LPR MTD FNA HTA TDD HFD GRLD CRPD STSD ELD
     MWD LMPN RMMD SMWD AAD IMD XHD IRD NID OLD VCE DRG1
     POD DSX VMD SLKD CCSD SWD LND CNDD
     CFTD SFA MRD DDV CNID CDCA MSID DAPA BFED RCBD
     ICDD CDMD LLCN MCTD CLBD AUTU
     GPUD DPUD DNDD CFXD ARHD CLTD ASCD
     CPFA CPTA ABDD CFHD FICD NAID BUZZ AGRD MOAD AHD
     DDGA NAMA
     DRDD EXR0
     USMD USRD ULAD RTDD RBDD RBHD PGND OCBD FLXD FTTC DNDY DNO3 MCBN
     CDMR MCDD T87D PKCH
CPND_LANG ENG
RCO  0
HUNT 3999
LHK  2
PLEV 02
DANI NO
AST
IAPG 0
AACS NO
ITNA NO
DGRP
MLWU_LANG 0
MLNG ENG
DNDR 0
DCFW  3999
KEY  00 SCR 3097 3     MARP
     01 SCR 3098 3     MARP
     02    
     03    
     04    
     05    
     06    
     07    
     08    
     09    
     10    
     11    
     12    
     13    
     14    
     15    
     16    
     17 TRN
     18 AO6
     19 CFW 16
     20 RGA
     21 PRK
     22    
     23    
     24 PRS
     25 CHG
     26 CPN
     27 CLT
     28 RLT
     29    
     30    
     31    
DATE  2 JAN 2025
 
I believe the calls will always end up on the DCFW when calling a DN assigned on a phantom TN. What is configured on the other phones that prevents you from using one of them as MARP?
 
so to allow it to hunt up the keys (not used it much) I thought you set the HUNT to 0, also not sure why the virtual set is required say Physical set 1 has 3097 on key 7 and 3098 on key 8 and LHK set to 8 and Physical set 2 has 3097 on key 4 and 3098 on key 5 and LHK set to 5, etc. then doesn't it do what you want it to do?
 
HUNT shouldn't prevent hunting up the keys, I have my HUNT setup for voicemail on my phones and calls are hunting up the keys when I have an active calls on the first keys. I still believe the issue is because there is a phantom TN in the equation
 
The reason for the virtual set is because I want to control the hunting and forwarding independently of the sets these SCR DNs appear on.

There are a couple of threads I stumbled across that seemed to hint a virtual set is a way to achieve this, but it's unclear on if they were successful, haha. This is what led me down this rabbit hole.

https://www.tek-tips.com/threads/call-forward.1724761/ (this one I'm unsure of the OP went with a virtual set or using MCRs)

The SCRs in the example could be MARP'd to one of the physical M2616's, but it would be keys 13/14. That would probably work with LHK set to 14. However another factor is I don't want these SCRs affected by the CFW or MSB settings of any physical phone. My understanding is if the MARP'd set enables MSB or CFW that the SCRs will follow this regardless of the state of the other TNs they're assigned to?
 
I think the confusion is virtual vs phantom TN, here you have created a phantom TN. If you create a TN in a virtual loop instead, your setup will most likely work.
 
So, that's what I originally tried as I have superloop 112 defined as a virtual loop for IP phones, but I get SCH1942 [Virtual Terminal must be defined on a phantom loop (Overlay 11)] when I specify one of the TNs under superloop V112 (TNs 77-80). Maybe I'm picking the wrong set type for this...
 
OK I built an i2004 (2004P2 specifically) using TN 80 15 and it looks like this may do the job.
 
For reference here is the set configuration. This allows calls to x3094 to "roll up" to x3095 and then to voicemail if both SCRs are busy. Same for x3096, "rolls up" to x3097 and then to voicemail if both are busy. I left some space inbetween in case I want/need to add additional SCRs to each group (not likely, but who knows).

Thank you @merton888 for identifying that a phantom TN was the issue here.

Code:
DES  TSTVRT
TN   080 0 00 15  VIRTUAL
TYPE 2004P2
CDEN 8D
CUST 0
NUID
NHTN
CFG_ZONE 001
CUR_ZONE 001
ERL  0
ECL  0
FDN  3999
TGAR 1
LDN  NO
NCOS 0
SGRP 0
RNPG 0
SCI  0
SSU 
XLST
CLS  CTD FBA WTA LPR MTD FNA HTA TDD HFD CRPD
     MWD LMPN RMMD SMWD AAD IMD XHD IRD NID OLD VCE DRG1
     POD DSX VMD SLKD CCSD SWD LND CNDD
     CFTD SFA MRD DDV CNID CDCA MSID DAPA BFED RCBD
     ICDD CDMD LLCN MCTD CLBD AUTU
     GPUD DPUD DNDD CFXD ARHD CLTD ASCD
     CPFA CPTA ABDD CFHD FICD NAID BUZZ AGRD MOAD AHD
     DDGA NAMA
     DRDD EXR0
     USMD USRD ULAD RTDD RBDD RBHD PGND OCBD FLXD FTTC DNDY DNO3 MCBN
     VOLA VOUD CDMR ICRD MCDD T87D KEM2 MSNV FRA  PKCH
CPND_LANG ENG
RCO  0
HUNT 3999
LHK  31
PLEV 02
DANI NO
AST 
IAPG 0
AACS NO
ITNA NO 
DGRP
MLWU_LANG 0
MLNG ENG
DNDR 0
KEY  00 SCR 3096 3     MARP
     01 SCR 3097 3     MARP
     02     
     03     
     04     
     05     
     06 SCR 3094 0     MARP
     07 SCR 3095 0     MARP
     08     
     09     
     10     
     11     
     12     
     13     
     14     
     15     
     16     
     17 TRN
     18 AO6
     19 CFW 16 
     20 RGA
     21     
     22 RNP
     23     
     24 PRS
     25 CHG
     26 CPN
     27     
     28     
     29     
     30     
     31     
DATE  3 JAN 2025
 
After thinking about it again, I do not even believe you need the virtual TN. MSB only affect the prime DN and CFW only affects the DN either on key 0 or DNs that appear only on one TN. Since your DNs are on multiple TNs and not on key 0, CFW wouldn't affect them.
 
Hmm. I will play around with it and see if I can eliminate the virtual set.
 

Part and Inventory Search

Sponsor

Back
Top