DID displayed on caller ID 2

[it44]

Hi all.

Is there a way to display a DID on a customers caller ID? (meaning an external caller). The company wants to purchase another main line in order for our MCR group to call customers so that the new number can display and the current main line does not receive so much volume. I thought maybe saving some money may be beneficial if I could get it done.

I have the call center setup on an MCR (the did in question). That MCR has a DID, but when you call out on it the caller ID displays the main line.

Thanks for the time.

 

[johnpoole]

that's done in the clid table

ENTRY 5
  HNTN 899
  ESA_HLCL
  ESA_INHN NO
  ESA_APDN YES
  HLCL 444
  DIDN YES
  HLOC
  LSC
  CLASS_FMT DN

then on the set mcr 1000 5 would send the did 899 444 1000. if didn is no, yor can enter a dept for the dept to tramint the same number.. if only key 0 is did, then for the other keys to send the same number as the entry 5 on key 1 mcr 3000 d will send the clid (did) of key 0.. prt clid in 21 change net in ld 15

john poole
bellsouth business
columbia,sc

 

[it44]

here are my entries John. Entry 0 is our main line. Im focusing my outbound caller id on Entry 2. I changed Entry 0 DIDN to "no" and Entry 2 DIDN to "yes". Still when I call my cell I get Entry 0 ID.



>ld 21
PT1000

REQ: prt
TYPE: clid
CUST 0
SIZE 27
RNGE

INTL

ENTRY 0
HNTN 999
ESA_HLCL 999
ESA_INHN NO
ESA_APDN NO
HLCL 9998888
DIDN NO
HLOC
LSC
CLASS_FMT DN

ENTRY 1
HNTN 999
ESA_HLCL 888
ESA_INHN NO
ESA_APDN YES
HLCL 888
DIDN YES
HLOC
LSC
CLASS_FMT DN

ENTRY 2
HNTN 990
ESA_HLCL 994
ESA_INHN NO
ESA_APDN YES
HLCL 994
DIDN YES
HLOC
LSC
CLASS_FMT DN

ENTRY 4
HNTN 999
ESA_HLCL 999
ESA_INHN NO
ESA_APDN YES
HLCL 999
DIDN YES
HLOC
LSC
CLASS_FMT DN

ENTRY 5
HNTN 777
ESA_HLCL 888
ESA_INHN NO
ESA_APDN YES
HLCL 777
DIDN YES
HLOC
LSC
CLASS_FMT DN


PAGE 002


ENTRY 6
HNTN 888
ESA_HLCL
ESA_INHN NO
ESA_APDN YES
HLCL 8888888
DIDN NO
HLOC
LSC
CLASS_FMT DN



Thanks

 

[GHTROUT]

If this MCR key is not on KEY 00 ~and~ KEY 00 DN has a CLID entry of the letter "D" - then that is overtaking all the lines. If thats it, change KEY 00's CLID to something else

 

[acewarlock]

Post the TNB of the MARP'ed set here and it will make it easier for us to help you.

 

[GHTROUT]

Geez, that wouldn't be any challenge at all then.

 

[it44]

This is my DN. I placed the MCR on Key 8 for testing. I noticed that KEY MCR had an entry of 0. Is my DN routing through entry 0 because of that?

DES  2616B
TN   005 0 00 11
TYPE 2616
CDEN 8D
CUST 0
AOM  0
FDN  5489
TGAR 1
LDN  NO
NCOS 3
SGRP 0
RNPG 0
SCI  0
SSU
LNRS 16
XLST
CLS  UNR FBD WTA LPR MTD FNA HTA TDD HFA
     MWA LMPN RMMD SMWD AAD IMD XHD IRA NIA OLA 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 AUTU
     GPUD DPUD DNDA CFXD ARHD FITD CLTD ASCD
     CPFA CPTA ABDD CFHD FICD NAID BUZZ AGRD MOAD AHD
     DDGA NAMA
     DRDD EXR0
     USMD USRD ULAD RTDD RBDD RBHD PGND OCBD FLXD FTTC DNDY DNO3 MCBN CDMR
CPND_LANG ENG
RCO  0
HUNT 5489
LHK  1
LPK  1
PLEV 02
CSDN
AST
IAPG 0
AACS NO
ITNA NO
DGRP
MLWU_LANG 0
DNDR 0
KEY  00 SCR 5477 2     MARP
        CPND
          NAME it44
          XPLN 27
          DISPLAY_FMT FIRST,LAST
     01 SCR 3477 D     MARP
     02 TRN
     03 AO6
     04 CFW 4  5477
     05
     06 MWK 5489
     07
     08 MCR 5483 0
        CPND
          NAME BDC MCR
          XPLN 27
          DISPLAY_FMT FIRST,LAST
     09 ADL 16  3200
     10 ADL 16
     11 ADL 16
     12 ADL 16
     13 ADL 16
     14 ADL 16
     15
DATE 28 FEB 2006


NACT

 

[it44]

got rid of entry 0 and it still displays main number. I have the DN set to entry 2. Maybe the issue is at the CO?

 

[johnpoole]

it could be, they can ignore your clid and send a clid that was agreed to when you bought the service.

john poole
bellsouth business
columbia,sc

 

[it44]

it must be John, because we were bought out by another company and the caller ID is displaying the old company name with the main number. So customers see us as the Old company. If I want to get that changed as well, is that tied to the problem I am having?

 

[johnpoole]

yes it is. i've had that before. you outed clid 0, you can't be sending. to check any clid table..ld 96 enl msgi x on the d and you'll see the clid that your sending. if the provider does not look at that field it's a param in there switch.. i have one t1 as a backup outbound through a unique office, and they only send the listed.. same clid tables on my end sends my did on key 0 and dept dn on key 1

john poole
bellsouth business
columbia,sc

 

[it44]

went to ld96

DCH000
.stat serv
DCH 010 SERV : DSBL
.


do I have to enable to view?

 

[vztech]

it44


you could make a quick change to CLID 0 and insert a number within your DID range to see if it sends it out.

or change CLID 0 to DIDN yes and make a call and see what it sends.

sounds like the CO as John said

It's only dialtone-VZ

 

[Godofhell]

We had this issue come up and discovered that Verizon had stopped sending our Caller ID. Verizon was capturing our caller ID and changing it to the main billing number. We had to submit a written request to have them remove the restriction since they claimed it was a goverment requirement that enforced this change. After some time of dealing with Verizon, we switched to QWEST and now we get the Caller ID just fine. We are using PRI services.

 

[johnpoole]

sounds like the CO as John said

john poole
bellsouth business
columbia,sc

 

[it44]

Bsouth claims they have entered the did's in the screening table; however my main line number is still displaying out.

I rebuilt the clid table and back to square 1.

 

[johnpoole]

check your dch to see if your sending the clid tables you built. i seldom believe any provider until i verify what i am sending.. bellsouth is just like the rest, unless you verify your work, they will always say their end is right

john poole
bellsouth business
columbia,sc

 

[it44]

went to ld96

DCH000
.stat serv
DCH 010 SERV : DSBL
.


do I have to enable to view?

 

[it44]

Ok john, here is what the pri is sending

.stat dch
DCH 010 : OPER  EST   ACTV  AUTO         DES : LOCALPRI
.enl msgi 10
.
DCH000
.
DCH 10 UIPE_IMSG CC_SETUPCOMP_IND  REF 00007181 CH 2 2 TOD  10:56:56 CK 08AAF1BB


DCH 10 UIPE_IMSG CC_ALERT_IND  REF 00000482 CH 2 21 TOD  10:57:02 CK 08AB2B64

DCH 10 UIPE_IMSG CC_SETUP_CONF   REF 00000482 CH 2 21 TOD  10:57:04 CK 08AB3A64

DCH 10 UIPE_IMSG CC_SETUP_IND  REF 00007201 CH 2 3 TOD  10:57:08 CK 08AB4F95
CALLED  #:3200 NUM PLAN: UNKNOWN   TON: UNKNOWN
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:7703501877 NUM PLAN: E164  TON: NATL

DCH 10 UIPE_IMSG CC_SETUPCOMP_IND  REF 00007201 CH 2 3 TOD  10:57:10 CK 08AB6969

 

[Reusser]

what you posted was in incoming call - do the same thing but post an outgoing call
that includes the setup.

DCH 10 UIPE_OMSG CC_SETUP_IND <-- out going (OMSG)

DCH 10 UIPE_IMSG CC_SETUP_IND <-- Incoming (IMSG)