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

Cant log in to new ACD Que

Status
Not open for further replies.

Imstillhere

IS-IT--Management
Jun 6, 2008
334
US
PBX IS CS1000 RLS 6.0 with cc7.0
This is my first attempt and building an acd que with symposium...
I built a new ACD que(acddn 3334) based on an exsisting working one. Pretty much defaulted all the way thru the first time then changed a couple of items to match the working one.
I built 2 agents in the que.
The Firmware is up to date on the phones.(M3904)I have headsets connected thatare working and no handset in cradle. if i press the dwc key it shows the que..all zeros of course but it shows it.
The MaxP was lowered to 10 since there will only be 6 agents when i get this working.
The phones are built on different cards. TN's 36 0 3 3 and 52 0 3 4
here is printout of the acddn, the que and one of the agents. Both apprear to be acquired by Symposium...im just looking for a default login at this point..something..When I hit key 0 once or twice nothing happens at all..when i call the que (3334) it just goes to vmail since no one is logged in. Any suggestions on what i did wrong will be helpful, Thank you.

REQ: prt
TYPE: dnb
CUST 0
DN 3334
DATE
PAGE
DES

DN 3334
CPND
NAME ROI Acd Que
XPLN 27
DISPLAY_FMT FIRST,LAST
TYPE ACDN
ACID 2677 TN 036 0 03 03
ACID 2682 TN 052 0 03 04
**********************************
**********************************
CUST 0
ACDN 3334
MWC NO
DSAC NO
MAXP 10
SDNB NO
BSCW NO
ISAP NO
AACQ YES
ASID 17
SFNB 33 35 36 37 38
USFB 1 3 4 5 6
CALB 1 3 4 5 6 8 11
RGAI NO
ACAA NO
FRRT
SRRT
NRRT
FROA NO
CALP POS
ICDD NO
NCFW 4100
FNCF NO
FORC NO
RTQT 5
RTQO NRD
SPCP NO
OBTN NO
RAO NO
CWTH 1
NCWL NO
BYTH 0
OVTH 2047
TOFT NONE
HPQ NO
OCN NO
OVDN
IFDN
OVBU LNK LNK LNK LNK
EMRT
MURT
RTPC NO
HOML NO
RDNA NO
LABEL_KEY0 NO
ACNT
NRAC YES
NDFL
DAL NO
RPRT NO
RAGT 4
DURT 30
RSND 4
FCTH 20
CRQS 100
IVR NO
OBSC NO
OBPT 5
CWNT NONE
************************
************************
TN PRINTOUT

DES MDF3
TN 036 0 03 03
TYPE 3904
CDEN 8D
CTYP XDLC
CUST 0
ERL 0
FDN 4100
TGAR 0
LDN NO
NCOS 7
SGRP 0
RNPG 15
SCI 0
SSU 0000
LNRS 16
XLST
CLS CTD FBD WTA LPR PUA MTA FNA HTA TDD HFA GRLD CRPD STSD
MWA LMPN RMMD SMWD AAD IMD XHD IRA NID OLA VCE DRG1
POD DSX VMD SLKD CCSD SWD LNA CNDA
CFTD SFA MRD DDV CNID CDCA MSID DAPA BFED RCBD
ICDD CDMD LLCN MCTA CLBD AUTU
GPUA DPUA DNDA CFXD ARHA FITA CNTD CLTD ASCD
CPFA CPTA ABDD CFHD FICD NAID RNGB AGRD MOAD AHD
DDGA NAMA
DRDD EXR0
USMD USRD ULAD RTDD RBDD RBHD PGND OCBD FLXD FTTU DNDY DNO3 MCBN
CDMR PRED MCDD T87D PKCH
CPND_LANG ENG
RCO 0
HUNT 4100
LHK 1
LPK 2
PLEV 02
PUID
DANI NO
SPID NONE
AST
IAPG 0
AACS YES
ACQ AS: TN
ASID 17
SFNB 2 5 6 7 8 9 10 11 12 13 15 16 17 18 19 28 29 33 35 36 37 38
SFRB 1 2 15 32 33 34 35 36 37 38
USFB 1 3 4 5 6 7 9 10 12 13 14 15
CALB 1 3 4 5 6 8 9 10 11 12
FCTB
ITNA NO
DGRP
PRI 01
MLWU_LANG 0
MLNG ENG
DNDR 0
KEY 00 ACD 3334 0 2677
AGN
01 NRD
02 MSB
03 DWC 3334
04 SCR 2453 0
CPND
NAME Parkland_PreReg_VM
XPLN 27
DISPLAY_FMT FIRST,LAST
05 SCR 2455 0
CPND
NAME Portsmouth_PreReg_VM
XPLN 27
DISPLAY_FMT FIRST,LAST
06 SCR 2744 0
07 SCR 6233 0
08
09
10
11
12
13
14
15
16 MWK 2100
17 TRN
18 AO6
19 CFW 16 3604
20
21 PRK
22 RNP
23
24
25
26
27 CLT
28 RLT
29
30
31
DATE 12 JUL 2012
 
Try going off hook on Key 0 of the agent phone and then try to login with the Agent ID (2677) or the extension that appears on Key 4 (2453) to login to the queue. Hopefully this will work! :)
 
Have you built a new CDN for it in LD23? Have you added it to the Master Script yet?

Phil, the Phriendly Phone Man
 
I would concur with rpneal44.

Your first line 1st post says you have CC7.

What you have done is built an ACD (3334) and I suspect you have been modifying the extension key programming. You have a wee bit of a dilema here.

**** Added after I did the following but: Your ACD looks like it is acquired by Call Pilot. (VSID 17) It will not work for you***** (but see below)

1: You should NEVER NEVER change extension programming when the extension is acquired by CC7 (or any other version or by Call Pilot..... it can corrupt the PABX database).

2: Every thing you are saying relates to a basic ACD configuration, not CC7

3: As stated... CC7 configuration. This will need to include:

i: CDN configuration in both PABX and CC7
ii: Skillset programming
iii: Master script mods to incorporate the new CDN, and where to point it
iv: An application script to handle the CDN
v:Announcements as required
vi: Skillset/s
vii: Allocation of Agents to skillset (by implication, the sets are not important, but the agent login is)

I think your problem is that you have used the wrong ACD


Would 4100 happen to be your voicemail by any chance??????
 
DAYTONAUSER... i dont get any prompts when hitting key 0..looking for enter agent ID at least.. but nothing at all.

RPNEAL44 I have not created a CDN yet, just the skillsets, a validated but

DFKSYDNETY I do not make any changes while aquired, dacr agt in 48 and in CC,null key 0, return thru disu the TN,go back in and make my changes adding back the msb ndr dwc keys ect..
Yes 4100 is our voice mail.

I will delete my current set up and start over with just PBX ACD until i get my login prompt. Once i get that I will add the necessary components in CC. I Looked at the other 3 call centers and each of their acddn's has an asid of 17 as well... a 4th que does not??

My initial plan was to use the 3334 acddn as a transfer for opt 2 in a call pilot application that is already built, the people are currently in an MRC type set up and i want to transition them to symposium. Let me crawl before i walk though and just get a basic acd set up working frist. Thank you guys for your support...I'll keep at this..ive got a few weeks to play with it.
 
Activate MSB then press key 0 to login. You also need to build your agents in Contact Center Administration and give them login IDs and assign them to skillsets.


 
OK go figure... I deleted everything and started over with just basic pbx acd programming..and i was still having the same issue...could not log in. I had a tested/working headset connected, but no handset was ever connected, the cradle was off hook already so why would i need a handset, none of the 3905's have handsets connected,only headsets....well i decided to plug in a handset as well as a headset just for kicks.....once I connected a handset the agent would log in.....WTH? Is this something that a 3904 has to have and 3905 does not? The firmware is the same...interesting.
 
A 3905 set has as it's primary device a headset, while a 3904 uses a handset. Something has to be plugged into THAT port on the set to be able to log into the Q.

Phil, the Phriendly Phone Man
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top