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

wrong AST´s acquire

Status
Not open for further replies.

amyygt

Programmer
Sep 8, 2005
72
US
Hi,

I have exactly the same situation as in thread959-1052517 but my symposium server is 4.0 and opt81. I restarted the server, and the problem was gone for some TNs, but there are other TNs that are not acquired as AST-POSID, but as AST-DN. If you have any suggestion just let me know.

Thanks in advance,
 
Do you have TAPI Server? Generally when agents are acquired as AST-DN, it means that it's been acquired by TAPI or as an IVR resource.
 
No, I don't have a TAPI Server there. I was comparing the TNS that are acquired appropiately with these ones, and I just see a difference: the DN is configured as SCR in the ones that are being recorded, but as MCR in two keys in the others. I will change that and test.
 
I think that is going to be your issue. The CTI application is going to have difficulty resolving one DN on two keys.

I would be interested to know if that cleared things up. We only use SCR keys for agents and do not have any issues.
 
I already changed the TN´s programming and also I changed one TN from its card, but the problem continues. Any suggestion?
 
Maybe now that you made the change you have to reboot. No idea just throwing it out there.
 
Yes, I forgot to write that we rebooted the server
 
Can you post a print of two TNs; one that works and one that doesn't?
 
This is a TN that works,
DES SER885
TN 008 0 02 00
TYPE 2216
CDEN 8D
CTYP XDLC
CUST 0
AOM 0
FDN
TGAR 7
LDN NO
NCOS 1
SGRP 0
RNPG 0
SCI 0
SSU
LNRS 16
XLST 30
SCPW
SFLT NO
CAC_MFC 0
CLS TLD FBD WTA LPR MTD FND HTD ADD
MWD LMPN RMMD SMWD AAD IMD XHD IRD NID OLD VCE DRG1
POD DSX VMD CMSD SLKD CCSD SWD LNA CNDA
CFTD SFD MRD DDV CNID CDCA MSID DAPA BFED RCBD
ICDD CDMD LLCN MCTD CLBD AUTD
GPUD DPUD DNDD CFXD ARHD CNTD CLTD ASCD
CPFA CPTA ABDD CFHD FICD NAID BUZZ AGRD MOAD
UDI RCC HBTD AHA IPND DDGA NAMA MIND PRSD NRWD NRCD NROD
DRDD EXR0
USMD USRD ULAD CCBD RTDD RBDD RBHD PGND OCBD FLXD FTTC DNDY DNO3 MCBN
FDSD NOVD CDMR
CPND_LANG ROM
HUNT
PLEV 02
CSDN
SPID NONE
AST 00 08
IAPG 1
AACS YES
ACQ AS: TN,AST-DN,AST-POSID
ASID 16
SFNB 1 2 3 4 5 6 9 10 11 12 13 15 16 17 18 19 22 24
SFRB 1 2 15
USFB 1 2 3 4 5 6 7 9 10 11 12 13 14 15
CALB 0 1 3 4 5 6 8 9 10 11 12
FCTB 0
CALL FORCE DELAY TIMER: 2 SEC
ITNA NO
DGRP
PRI 01
MLWU_LANG 0
DNDR 0
KEY 00 ACD 1363 0 3723
AGN
01 NRD
02 MSB
03 AWC
04 ASP
05 TRN
06
07
08 SCN 2723 0 MARP
09 ACNT
10
11
12
13
14
15 CHG
DATE 12 OCT 2006

And this is a TN that doesn't work:
DES MOVIL
TN 004 0 00 13
TYPE 3905
CDEN 8D
CTYP XDLC
CUST 0
FDN
TGAR 3
LDN NO
NCOS 1
SGRP 0
RNPG 0
SCI 0
SSU
XLST 30
SCPW
SFLT NO
CAC_MFC 0
CLS TLD FBD WTA LPR MTD FND HTD ADD CRPD STSD
MWD LMPN RMMD SMWD AAD IMD XHD IRD NID OLD VCE DRG1
POD DSX VMD CMSD SLKD CCSD SWD LND CNDA
CFTD SFD MRD DDV CNID CDCA MSID DAPA BFED RCBD
ICDD CDMD LLCN MCTD CLBD AUTR
GPUD DPUD DNDD CFXD ARHD CNTD CLTD ASCD
CPFA CPTA ABDD CFHD FICD NAID RNGB AGRD MOAD
UDI RCC HBTD AHA IPND DDGA NAMA MIND PRSD NRWD NRCD NROD

DRDD EXR0
USMD USRD ULAD CCBD RTDD RBDD RBHD PGND OCBD FLXD FTTC DNDY DNO3 MCBN
FDSD NOVD CDMR
AUTH 1 3752
2
3
4
5
6
CPND_LANG ROM
HUNT
PLEV 02
CSDN
SPID NONE
AST 00 04
IAPG 1
AACS YES
ACQ AS: TN,AST-DN
ASID 16
SFNB 1 2 3 4 5 6 9 10 11 12 13 15 16 17 18 19 22 24
SFRB 1 2 15
USFB 1 2 3 4 5 6 7 9 10 11 12 13 14 15
CALB 0 1 3 4 5 6 8 9 10 11 12
FCTB 0
CALL FORCE DELAY TIMER: 0 SEC
ITNA NO
DGRP
PRI 01
MLWU_LANG 0
MLNG SPA
DNDR 0
KEY 00 ACD 1340 0 6357
AGN
01
02
03
04 SCR 2357 0 MARP
05 ACNT
06
07
08 MSB
09 NRD
10
11 ASP
12
13
14
15
16
17 TRN
18
19
20 RGA
21 PRK
22 RNP
23
24 PRS
25 CHG
26 CPN
27
28
29
30
31
DATE 9 NOV 2006

Thanks in advanced,
 
Assuming you have a DN > Pos ID translation rule (2XXX becomes 3XXX?) I noticed the second pos id doesn't fit this. Is this a typo?

Is the CTI application is set to register for events on 6357?

DD
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top