Phantom Ring 1

[Catachresis]

I am involved in a Nortel option 11 class in which several of our pbx's have developed what we have dubbed the 'phantom ring' while installing analog trunks. As far as we can tell, the problem is limited to the COT trunks we installed in locations 6 0 and 6 1. The phantom ring targets location 6 1 which has an ATDN of 4002 (in this instance it is a problem that is affecting more than one pbx in this exact manner). This location is member two of route group one. There are only two members of grp one and they are both COT trunks. They both have supervision activated, both set to DTN, and both have SIGL set to LOP. The call, when answered, is nothing but silence. No reorder tone, no static, nothing. On the display (we have them running to a 2616) is a '9-2'. 9 is the ACOD programmed for route one (which is the route that TN's 6 0 and 6 1 belong to), and 2 is not used anywhere in the system as a DES. The phantom ring is persistent, elusive, and it showed up in my pbx before I even wired any external connections. (which was how I knew the system was calling itself.) Not 20 minutes after discovering this problem, we wired our trunk connections to the Demarc, then installed tie trunks the the booth next to us. Immediately after installing and confirming the tie trunk, I moved TN 6 1 to 6 5 and the phantom ring ceased... In my booth. It immediately showed up on location 6 1 in the booth to which I had wired my tie connection.

Sorry for the lengthy description, but we are at a loss as to what this could be (and apparently the problem has existed for previous classes as well). If anyone has any info, please help!

 

[johnpoole]

need a copy of the rdb, did you say this was before any jumpers were laid down?.. if so it would most likely be a patch, check the nortel web site. a good test is "can you program a switch to behave that way?" if not you may not be able to "unprogram" it either

john poole
bellsouth business
columbia,sc

 

[Catachresis]

Yes, this was before any jumpers were connected. Here is the RDB for route 1:
TYPE RDB
CUST 00
DMOD
ROUT 1
DES BOOTH1
TKTP COT
NPID_TBL_NUM 0
PRIV NO
SAT NO
RCLS EXT
DTRK NO
PTYP ACO
AUTO YES
ICOG IAO
RANX NO
SRCH LIN
TRMB YES
STEP
ACOD 9
CPP NO
TARG 01
CLEN 1
BILN NO
OABS
TIMR ICF 512
OGF 512
EOD 13952
DSI 34944
NRD 10112
DDL 70
ODT 4096
RGV 640
FLH 510
GRD 896
SFB 3
CRD 512
TFD 0
LEXT 100
SST 3 0
NEDC ETH
FEDC ORG
CPDC NO
SPCT IMM
HOLD 02 02 40
SEIZ 02 02
RGFL 02 02
RVSD 08 31
ILLR 02 02
DRNG NO
CDR NO
MUS NO
MR NO
MANO NO
EQAR NO
FRL 0 0
FRL 1 0
FRL 2 0
FRL 3 0
FRL 4 0
FRL 5 0
FRL 6 0
FRL 7 0
OHQ NO


PAGE 002

OHQT 00
TTBL 0
ATAN NO
OHTD NO
PLEV 2
MCTS NO
ALRM NO
ART 0
SGRP 0
AACR NO

I re-programmed TN 6 1 with a new trunk of the same type pointing to a different key on the 2616 and the problem persisted so my only guess is that it's tied into circuit 1 on the universal trunk card (a short maybe?) or slot 6 in the cabinet... Though this time the display indicated '9-3' and I had the new trunk programmed as the third member of route group 1 (it was previously the second member when it popped up the '9-2'). Again, no jumpers were connected.

 

[worldwidedialtone]

Is MeridianMail hooked up on your PBX? We have had MerMail create phantom rings for us during it's midnight routines.

 

[Catachresis]

No, we don't have Meridian Mail installed. As of now the only solution we have been able to successfully implement is to not use TN 6 1.

 

[techman3030]

You said this was a class with booths, do you have another universal trunk card handy that you could swap out? Also you said this was a problem with several of your PBX's. Are they all built with the same card layout, IE do they all have a problem with card 6?

 

[johnpoole]

all switches were loaded from the same software? 6 1 may be corrupt in your original load

john poole
bellsouth business
columbia,sc

 

[Catachresis]

All the booths (that have this ring condition) have the problem on TN 6 1. Swapping the cards does nothing. Truly perplexing...