ACOD Showing on agent set

[bliemsgirl]

On Monday it seem an agent was seeing 6900 show up on her display. I did a print on this number and it seems to be an ACOD. There seemed to be quite a number of calls coming from this number and it seems the route is is a SIP trunking route, which as far as I know is not in use at the moment. Any idea why this could be happening?

REQ: prt

TYPE: rdb

CUST 0

ROUT

ACOD 6900


TYPE RDB
CUST 00
ROUT 0
DES SIP TRUNK
TKTP TIE
M911P NO
ESN NO
RPA NO
CNVT NO
SAT NO
RCLS EXT
VTRK YES
ZONE 00011
PCID SIP
CRID NO
NODE 597
DTRK NO
ISDN YES
MODE ISLD
DCH 16
IFC SL1
PNI 00001
NCNA YES
NCRD YES
TRO NO
FALT NO
CTYP CDP
INAC NO
ISAR NO
DAPC NO
MBXR NO
MBXOT NPA
MBXT 0
PTYP ATT
CNDP UKWN
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
SRCH LIN
TRMB YES
STEP
ACOD 6900
TCPP NO
PII NO
AUXP NO
TARG
CLEN 1
BILN NO
OABS
INST
IDC NO
DCNO 0 *
NDNO 0
DEXT NO
ANTK
SIGO STD
STYP SDAT
MFC NO
ICIS YES
OGIS YES
PTUT 0
TIMR ICF 512


PAGE 002

OGF 512
EOD 13952
DSI 34944
NRD 10112
DDL 70
ODT 4096
RGV 640
GTO 896
GTI 896
SFB 3
NBS 2048
NBL 4096

IENB 5
TFD 0
VSS 0
VGD 6
EESD 1024
SST 5 0
DTD NO
SCDT NO
2 DT NO
NEDC ETH
FEDC ETH
CPDC NO
DLTN NO
HOLD 02 02 40
SEIZ 02 02
SVFL 02 02
DRNG NO
CDR NO
NATL YES
SSL
CFWR NO
IDOP NO
VRAT NO
MUS YES
MRT 90
PANS YES
RACD 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
OHQ NO
OHQT 00
CBQ NO
AUTH NO
TTBL 0
ATAN NO
OHTD NO
PLEV 2
OPR NO
ALRM NO
ART 0
PECL NO
DCTI 0


PAGE 003

TIDY 6900 0
ATRR NO
TRRL NO
SGRP 0
CCBA NO
ARDN NO
CTBL 0
AACR NO

 

[trvlr1]

If this is not being used you might want to turn it down and see if the number continues to appear. Based on what you have said, there is a good possibility calls are indeed coming across that circuit.

 

[Supernn]

The ACOD is only showing if the CLID is missing from the caller I believe.

 

[bliemsgirl]

@Supernn would that mean the caller would be calling with a private number for example?

 

[Supernn]

@Bliemsgirl That is indeed the case in our environment, it shows the ACOD and the RouteMember, e.g. 6900 - 23

 

[trvlr1]

But that does mean calls are coming in on that route ......

 

[bliemsgirl]

That seems to be the main route for our incoming calls.
How is the CLID activated?

 

[trvlr1]

First do a test with a phone you know is sending caller ID (ie a cell phone) and see if you get anything from that. If this were a PRI you could turn on D channel monitoring and see what is being sent in to the PBX, do not know if this is something you can do with a SIP trunk .....

 

[bliemsgirl]

I did a test call with my cell phone and blocked my number from showing and they saw 6900 on their set. So that is most likely the issue, someone calling in from a mobile phone with a blocked number and the CLID not showing. Is the CLID sent through the PBX or the cell phone company?

 

[trvlr1]

It comes from the telco to you, and from the user to them via cell company of other telco, but in many cases the number can be manipulated by the users into showing nothing or a completely bogus number if they wish. This is why it is so difficult to block numbers from nuisance callers etc.

 

[bliemsgirl]

The company I work for is a telco company and I checked with the team and they are sending all numbers even if the caller has blocked their call id on their phone.

Would adding a new entry to the CLID table solve this?

 

[trvlr1]

If the number is blocked to them, how do they know what to send? I can understand with local numbers, but what if the call is from the other side of the country, or another country, with the number blocked .....
Having said that, I know there is a lot of information in the header that they could probably extract the originating number, but that would seem like a lot of work and over and above what a telco would normally do. The fact that you were able to block your own cell phone number seems to prove that was an incorrect statement from them anyway.

 

[bliemsgirl]

No I think you are understanding it wrong.

I blocked my own number on my phone when I dialed 8193445 (which is not in the CLID table) It was a new number that was created a few months ago.
On the telco side all numbers are open and should be sending the number.

Isn't there also a config on the PBX side that shows the Caller id? Maybe it wasnt configured for the new number.

The other 2 numbers in the CLID table do show call id even if the caller blocks their call id on their phone.

Maybe that helps a little more.

ENTRY 0
HNTN
ESA_HLCL
ESA_INHN NO
ESA_APDN YES
HLCL 8190000
DIDN NO
DIDN_LEN 0
HLOC
LSC
CLASS_FMT DN

ENTRY 1
HNTN
ESA_HLCL
ESA_INHN NO
ESA_APDN YES
HLCL 8193444
DIDN NO
DIDN_LEN 0
HLOC
LSC
CLASS_FMT DN

 

[CaseFile]

If the below is from the PBX
CLID in this usage

ENTRY 0
HNTN
ESA_HLCL
ESA_INHN NO
ESA_APDN YES
HLCL 8190000
DIDN NO
DIDN_LEN 0
HLOC
LSC
CLASS_FMT DN

Is for outgoing calls.
It has no effect on incoming calls.
If you see the 6900-XX, then there is no incoming CLID with the call.
SIP and Cell phones have strange interactions sometimes.
Also, how you are blocking the ID from the calling phone can make a difference