No busy signal when line is in use

[jdlrez]

On a 2616 set with a single DN, I'm having a problem where when the person is on the phone, if someone else in the office dials their extension, instead of a busy signal, they get dead silence.

I looked through the manual thinking it was something disabled in CLS but found nothing obvious.

FBA is set, but I guess is being over-ridden by hunting? Currently I have the set's Hunt set to another ext at the main office. TN program below:

TYPE 2616
CDEN 8D
CUST 0
AOM 0
FDN 601
TGAR 0
LDN NO
NCOS 0
SGRP 0
RNPG 0
SCI 0
SSU 0000
XLST
CLS CTD FBA WTA LPR MTD FNA HTA ADD HFA
MWA AAD IMD XHD IRD NID OLD VCE DRG1
POD DSX VMD CMSD CCSD SWD LND CNDA
CFTD SFD MRD PDN DDV CNID
ICDD CDMD LLCN MCTD AUTU
GPUD DPUD DNDA CFXA ARHD FITD CLTD ASCD CPFA CPTA CFHD
USRD
ENG
RCO 1
HUNT 244
LHK 0
PLEV 02
AST
IAPG 0
ITNA NO
DGRP
MLWU_LANG 0
KEY 00 SCR 233 MARP
CPND
NAME xxx xxx
XPLN 17
DISPLAY_FMT FIRST,LAST
01 SSU 0000
02 AO6
03 TRN
04 RGA
05 CFW 16 601
06 ADL 16
07
08 ADL 16
09 ADL 16
10 ADL 16
11 ADL 16
12 ADL 16
13 ADL 16
14 ADL 16
15
DATE 2 FEB 2007

Thoughts?

 

[bigindian65]

You want them to get a busy if on a call? why hunt & fdn?
mwa? hta? fna?

 

[johnpoole]

chg the set to read cls htd hunt x244

john poole
bellsouth business
columbia,sc

 

[jdlrez]

Thanks John, I'll try that.

 

[acewarlock]

FBA is for Sending DID calls to the OPER if the phone is busy and it over rides HTA and FNA. If the DN on this phone is not a DID or you don't want it to go to the OPER, then remove the FBA.

HTA is for when the DN is busy, in this case it would goto EXT 244.

FNA is for when the user doesn't answer the phone and in this case it will goto EXT 601.

What do you want the phone to do when the phone is busy?

 

[jdlrez]

I would prefer it give a busy sound and the option to press the ring-again button. However VM or Oper roll are all fine.

I can't test this until tomorrow anyway and I'm leaving for the day to battle a plague someone has unleashed on the office, with nyquil.

Thanks for all the help fellas, as usual.

 

[acewarlock]

Your not reading my post right or I'm not explaining it right.

You don't want FBA and HTA programmed at the same time because FBA will take priorty if the call is DID.

 

[jdlrez]

it's a DID capable set but no calls ever go to it via that route. Only in-office via dialing the DN.

 

[acewarlock]

Then remove the FBA.
FNA will send it to 601 Vmail????
HTA will send it to 244

Have you tried calling 601 and 244 to see what happens.

 

[jdlrez]

Changing HTA to HTD gave me what I wanted: busy signal (audible one) when dialing that DN if they're on the phone.

Thanks all.

 

[acewarlock]

That may have gotten you a busy signal, but you haven't fixed the problem, "when the person is on the phone, if someone else in the office dials their extension, instead of a busy signal, they get dead silence"

Dead silence is a problem, there is something wrong in your system.

 

[jdlrez]

Not sure I see that there is still a problem. Now if someone dials this particular extension while it is busy, it gives a busy signal instead of silence, which is what I wanted.

my statement you quoted: "when the person is on the phone, if someone else in the office dials their extension, instead of a busy signal, they get dead silence"

Only applied to the one particular extension, which is now fixed. Sorry if I made it sound like it was with more than one set.

In any case everything is working fine, thanks.

 

[acewarlock]

Still if a caller get dead silence in steat of a busy signal, then something else is wrong.

Did you call ext 601 to see what you get when you call it?????? Maybe silence

 

[jdlrez]

601 gets meridian mail prompt like normal.

I suspect the silence was due to the fact that hunting was turned on, and hunt set to 244, which is this person's old phone at the other office building.

If I had to pull a guess out of my nether regions it might be that 244 is CFW'd manually to the extension in question. So perhaps when we dialed 233 while it was busy, it tried to hunt to 244 which was fwd'd to 233 and got stuck in some kind of infinite loop or something.

Or maybe not. Dunno really.

 

[acewarlock]

That's possible.