Inbound CLID gets lost

[MagnaRGP]

Good Day all.

Maybe I've stared at this for too long, but I can't seem to find the issue here...

I have a CS1kE and I'm setting up Converged Desktop with an MCS5100. When a call comes in from the PSTN it is answered by the CallPilot auto attendant. If the caller is transferred to a set on the CS1k, the caller's CLID displays on the set. However, if the call is transferred to a SIP client user (unconverged) on the MCS, the CLID display shows the DN of the CallPilot port and not that of the inbound caller. The even stranger bit is, if a call lands on a converged user, the inbound CLID on the hard set is correct, but simultaneously, the CLID on the SIP client is the PCA DN.

Here is a shot of the DCH messaging of a test call:

DCH 77 IMSG SETUP REF 0000800F CH 77 15 TOD 16:49:25
CALLING #:5191234567 NUM PLAN: NUM UNKNOWN/UNKNOWN (UNKNOWN)
CALLED #:0273 NUM PLAN: E164/NATIONAL / NPA

DCH 77 OMSG CALLPROC REF 0000800F CH 77 15 TOD 16:49:25

DCH 77 OMSG ALERT REF 0000800F CH 77 15 TOD 16:49:27

DCH 77 OMSG CONNECT REF 0000800F CH 77 15 TOD 16:49:27

DCH 77 IMSG CONN ACK REF 0000800F CH 77 15 TOD 16:49:27

DCH 110 OMSG SETUP REF 000001AD CH 252 0 1 12 TOD 16:49:45
FEAT :CRID
FEAT :CDS
FEAT :NCID
PROGRESS: ORIG ADDR IS NOT ISDN
CALLING #:7250 NUM PLAN: PRIVATE/ABBREVIATED (CDP)
CALLED #:7060 NUM PLAN: PRIVATE/ABBREVIATED (CDP)

DCH 110 IMSG CALLPROC REF 000001AD CH 252 0 1 12 TOD 16:49:45

DCH 110 IMSG ALERT REF 000001AD CH 252 0 1 12 TOD 16:49:45

DCH 77 IMSG DISC REF 0000800F CH 77 15 TOD 16:50:01
CAUSE :NORMAL CALL CLEARING

DCH 77 OMSG RELEASE REF 0000800F CH 77 15 TOD 16:50:01

5191234567 displays on the converged hard set.
7250 is the MCN key on the PCA that forks the call --this is what displays on the SIP Client (unconverged)
7060 is the DSC which sends the call to the MCS5100

SIP Trunk route:

TYPE RDB
CUST 00
ROUT 110
DES SIP_TRKS
TKTP TIE
M911P NO
ESN NO
CNVT NO
SAT NO
RCLS EXT
VTRK YES
ZONE 255
PCID SIP
CRID NO
NODE 6501
DTRK NO
ISDN YES
MODE ISLD
DCH 110
IFC SL1
PNI 00001
NCNA YES
NCRD YES
TRO NO
FALT NO
CTYP UKWN
INAC YES
ISAR NO
DAPC NO
PTYP ATT
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
SRCH LIN
TRMB YES
STEP
ACOD 7110
TCPP NO
TARG 01
CLEN 1
BILN NO
OABS
INST
IDC NO
DCNO 0 *
NDNO 0
DEXT NO
ANTK
SIGO STD
STYP SDAT
ICIS YES
TIMR ICF 512
OGF 512
EOD 13952
DSI 34944
NRD 10112
DDL 70
ODT 4096
RGV 640
GRD 896
SFB 3
NBS 2048


PAGE 002

NBL 4096
TFD 0
SST 5 0
NEDC ORG
FEDC ORG
CPDC NO
DLTN NO
HOLD 02 02 40
SEIZ 02 02
SVFL 02 02
DRNG NO
CDR NO
MUS NO
MANO 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
AUTH NO
TDET NO
TTBL 0
ATAN NO
OHTD NO
PLEV 2
ALRM NO
ART 0
SGRP 0
ARDN NO
AACR NO

SIP route DCH:

ADAN DCH 110
CTYP DCIP
DES SIP_Trks
USR ISLD
ISLM 4000
SSRC 1800
OTBF 32
NASA NO
IFC SL1
CNEG 1
RLS ID 25
RCAP
MBGA NO
H323
OVLR NO
OVLS NO

PCA DN:

DES PCA
TN 248 0 00 00 VIRTUAL
TYPE PCA
CDEN 8D
CTYP XDLC
CUST 0
NUID
NHTN
CFG_ZONE 000
CUR_ZONE 000
ERL 0
ECL 0
FDN
TGAR 1
LDN NO
NCOS 7
SGRP 0
RNPG 0
SCI 0
SSU
XLST 0
CLS UNR FBD WTA LPR MTD FND HTD TDD HFD CRPD
MWD LMPN RMMD SMWD AAD IMD XHD IRD NID OLD VCE DRG1
POD DSX VMD SLKD CCSD SWD LND CNDD
CFTD SFD MRD DDV CNID CDCA MSID DAPA BFED RCBD
ICDD CDMD LLCN MCTD CLBD AUTU
GPUD DPUD DNDD CFXD ARHD CNTD CLTD ASCD
CPFA CPTA ABDD CFHD FICD NAID BUZZ AGRD MOAD
AHA DDGA NAMA
DRDD EXR0
USMD USRD ULAD RTDD RBDD RBHD PGND OCBD FLXD FTTC MCBN
VOLA VOUD CDMR ICRD MCDD T87D MSNV FRA PKCH
CPND_LANG ENG
HUNT
PLEV 02
DANI NO
SPID NONE
AST
IAPG 0
AACS YES
ACQ AS: TN
ASID 32
SFNB 1 2 3 5 6 9 10 11 12 13 15 16 17 18 19
SFRB 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
USFB
CALB 0 1 2 3 4 5 6 7 8 9 10 11
FCTB
ITNA NO
DGRP
PRI 01
MLWU_LANG 0
MLNG ENG
DNDR 0
KEY 00 ACD 7998 0 7690
AGN
01
02 MCN 7250 0 MARP
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17 TRN
18 AO6
19 CFW 16
20 RGA
21 PRK
22 RNP
23
24 PRS
25 CHG
26 CPN
27
28
29
30
31
DATE 22 JUL 2008


Any thoughts? Thanks.

 

[macaodha]

I'm getting the same issue when CallPilot transfers calls over PRI tie lines to a Cisco system. If I find the answer, I'll post it here.

 

[Reusser]

I'm pretty sure I have seen a patch for that. make sure you have all patches that apply for the MCS5100 and AST

 

[macaodha]

One thing I just thought of - basically the system is initiating a transfer, which will initially send the DN of the person (or in this case the CallPilot port) that initiates the transfer, then the transfer is completed. When a call goes out a PRI trunk, there is an initial d-channel message that would logically send that initial DN, and if a different caller ID were to show up, an additional d-channel message would have to be sent. My guess is that this is not even supported on the DMS-100 protocol which is what I am using. Does anyone know if this is something that QSIG would support?