Issue with ACD-DN and SDNB = YES 1

[Skaret]

Can someone please tell me if this is a bug or not supported?

Setup:
FNAD FDN
FNAT FDN
FNAL FDN

ACD-DN 5642 with SDNB=YES.

Set configured with:
CLS HTA, HBTA, FNA, CFTA
FDN 5690
EFD 5690
HUNT 5690
EHT 5690
KEY 0 ACD 5642 0 165642
KEY 1 NRD
KEY 2 MSB
KEY 3 SCR 8904 0

Test:
Set logged into ACD and Busy on ACD
Incoming external call to SCR do not EHT to 5690 (WRONG??)
Incoming internal call to SCR do not HUNT to 5690 (WRONG??)

NTP says:
Secondary DN Call Blocking (SDNB) blocks out new incoming calls to the Secondary DN on an agent's telephone, so the agent can handle current ACD calls without interruption. An agent telephone is considered ACD active when a call is presented or connected to the agent's ACD In-Calls key.

With Secondary DN Call Blocking enabled (SDNB = Yes), an incoming call to the Secondary DN of an ACD active agent telephone receives a busy tone.

When Hunting is enabled and the secondary DN is called, the incoming call hunts to the Hunt DN specified.

 

[KCFLHRC]

Check your LHK setting and make it as high as your scr keys

 

[Skaret]

As far as I know LHK is only used for Short Hunt, we are not talkin about Short Hunt in this case. If SDNB=NO every thing works fine, beside when agent is active on ACD. When active on ACD (SDNB=NO) and a call arrive SCR, the SCR will ring and disturb the agent.

 

[RickyPone]

I would change the lhk like kc said. You can always change it back. It has to be built that way for your hunt to work regardless.

 

[Skaret]

Thaks to KCFLHRC. LHK solved the problem.