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

Meridian Option 11 - All external calls withheld

Status
Not open for further replies.

Zenoxious

Technical User
Jul 7, 2010
13
GB
This may well be a question for the line provider, but in the off chance it's a setting on the PBX switch I was wondering if anyone knew how to disable withheld external calls.
 
Lots more info needed. What type of trunks, copper, t-1, pri? Do you have DID's or just a main #?? Never actually heard the term "disable withheld external calls" in my 35 years as a phone tech. What exactly do you mean?
 
KCFLHRC - Withheld calls are calls where when you phone out to someone it doesn't display the number that you're calling from. This is a very common feature with phones, well at least in the UK. Essentially I've inherited this Meridian Option 11 system along with it withholding call numbers to external calls automatically. Obviously internal calls are not withheld. I want to disable the number withholding so that when someone within the company phones out the number is not withheld.

I believe our trunk line is copper to the TJF, but I know very little about that part of the infrastructure (in all likelihood I was only a few years old when it was put in). We have a block of DID's associated with the line, but I’m not sure if we only have 1 external number and those DID’s are not split off the main line.
 
you guys use some funny terms! ;>) (We call it caller ID here) you should be able to set your CLID to display in your outgoing DID's.

Sending a Calling Line Identification (callers extension number) to the dialed party over the ISDN D-channel is optional, and can be allowed (or not) per DN. DN's are associated with a CLID entry, which defines the CLID data. To create CLID entries, edit NET_DATA in LD 15:

Example:

LD 15

REG: chg
TYPE: net_data
CLID yes
- SIZE
- ENTRY #
-- DIDN (yes or no)ENTRY # is the CLID entry to be configured. CLID entries must be between 0 and and the value entered at the SIZE prompt - 1 (default 255). Precede entry or entries with X to delete. ENTRY is repeated until <cr> is entered.

ENTRY 0 is the default assignment to a DN in LD 10 or 11, edit this as required:

- KEY # SCR XXXX 0Printing:

Use LD 21 to print the CLID entries - REQ: PRT, TYPE: CLID.
In the entry examples below, ENTRY 0 will not pass the extension number in CLID and ENTRY 1 will pass the extension in CLID.

LD 21

REQ: prt
TYPE: clid
CUST 0
SIZE 256
RNGE

ENTRY 0
HNTN
HLCL
DIDN NO
HLOC
LSC
CLASS_FMT DN

ENTRY 1
HNTN
HLCL
DIDN YES
HLOC
LSC
CLASS_FMT DNNotes:

HLCL - the Local Code for home local number or listed directory number (1-12 digits) - precede with X to remove
DIDN YES - precede the DN of the active DN key with the digits in HLCL
DIDN NO - use digits in HLCL

By default, the phone company usually sends HLCL, and in the absence of further digits, HLCL combined with the base DID number.


D Channel Monitoring
Monitoring D Channel traffic with LD 96 can be a very useful diagnostic tool for checking incoming/outgoing digit patterns for DID calls. See also D-Channel Monitoring for more details.

Use the following commands in LD 96:

ENL MSGI x - enable monitoring of incoming messages
ENL MSGO x - enable monitoring of outgoing messages
DIS MSGI x - disable monitoring of incoming messages
DIS MSGO x - disable monitoring of outgoing messages
STAT MON x - display the monitoring status of one or all D-channels.

Example:

>ld 96
DCH000
.enl msgi 5
.enl msgo 5
.
DCH 5 UIPE_OMSG CC_SETUP_REQ REF 0000002B CH 6 28 TOD 11:37:58
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:3699 NUM PLAN: E164
CALLED #:06975353888 NUM PLAN: E164 Notes:

•During high traffic some of the monitored messages may be lost.
•For the D-Channel monitor messages to be displayed, the system terminal must have USER defined as MTC in LD 17.
•D-Channel message monitoring can produce a lot of TTY output, so remember to disable when no longer required!

 
Thanks for the reply, although I'm a little out of my depth here, I'm not too sure what I'm looking at. Entering the below load I get the following outputs, but I'm not totally sure what it's telling me. Should I be attempting to set the DIDN to yes on entry 1?

REQ: prt
TYPE: clid
CUST 0
SIZE 256
RNGE

INTL

ENTRY 0
HNTN
HLCL
DIDN YES
HLOC
LSC

ENTRY 1
HNTN
HLCL
DIDN NO
HLOC
LSC
 
No - I think that just tells us that you have DID's but you don't have anything built against them. you would have your HNTN folowed buy an area code as well as HLCL would have your NXX the HLOC would have the combo of area code and NXX, etc. I think those changes need to be made in LD 15 according to whatever your dilaing plan looks like in your area. You may need to talk with the local telco provider to make sure you match what they need/send. I have only seen somebody set that up once - a long time ago, so maybe others can chime in. There may be other loads to work with how many digits to insert or remove depending on your dialing plan as well.....You might looks at GHTROUTS site and I think he has some useful tips in there too.
 
Hello Zenoxious. As you are in the UK, did you try out 1470 as I had suggested?. Are you calls going out via a different line provider other that e.g. BT?. You could also try BT's override number of 1280 or even try 12801470 and the rest of the phone number.

What type of lines, do you have?. Analogue, BRI, DASS, I421 or ISDN 30e etc?. If your lines are DASS, then the replies above won't be of much use to you. You might want to contact me via the link below.



All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

If it's working, then leave it alone!.
 
firebirdscrambler - Sorry yes I did, however, it didn't unblock the number, the call came up as withheld still. I tried entering 12801470 but then I got a BT announcer voice saying: "Your request cannot be accepted, please check the user guide".

It's an anologue system I believe, but I can't be sure. Which load could I use to check?
 
Go into LD 21 and at the REQ prompt, key in LTM and press enter a few times until you see a few lines of data that should show you your routes and trunks. Post it here and we can tell you what lines you have.

All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

If it's working, then leave it alone!.
 
This is what I get:

TYPE TLST
TKTP MUS
ROUT 50
DES
TN 020 0 00 03 MBER 1 MUSIC

TYPE TLST
TKTP IDA
ROUT 100
DES I/C_TO_ACD
TN 001 01 MBER 1 01206-xxxxxx
TN 001 02 MBER 2 01206-xxxxxx
TN 001 03 MBER 3 01206-xxxxxx
TN 001 04 MBER 4 01206-xxxxxx
TN 001 05 MBER 5 01206-xxxxxx
TN 001 06 MBER 6 01206-xxxxxx
TN 001 07 MBER 7 01206-xxxxxx
TN 001 08 MBER 8 01206-xxxxxx
TN 001 09 MBER 9 01206-xxxxxx
TN 001 10 MBER 10 01206-xxxxxx
TN 001 11 MBER 11 01206-xxxxxx
TN 001 12 MBER 12 01206-xxxxxx
TN 001 13 MBER 13 01206-xxxxxx
TN 001 14 MBER 14 01206-xxxxxx
TN 001 15 MBER 15 01206-xxxxxx
TN 001 17 MBER 16 01206-xxxxxx
TN 001 18 MBER 17 01206-xxxxxx
TN 001 19 MBER 18 01206-xxxxxx
TN 001 20 MBER 19 01206-xxxxxx
TN 001 21 MBER 20 01206-xxxxxx
TN 002 01 MBER 21 01206-xxxxxx
TN 002 02 MBER 22 01206-xxxxxx
TN 002 03 MBER 23 01206-xxxxxx
TN 002 04 MBER 24 01206-xxxxxx
TN 002 05 MBER 25 01206-xxxxxx
TN 002 06 MBER 26 01206-xxxxxx
TN 002 07 MBER 27 01206-xxxxxx
TN 002 08 MBER 28 01206-xxxxxx
TN 002 09 MBER 29 01206-xxxxxx
TN 002 10 MBER 30 01206-xxxxxx

TYPE TLST
TKTP IDA
ROUT 101
DES I/C_2ND_OG
TN 002 11 MBER 1 01206-xxxxxx
TN 002 12 MBER 2 01206-xxxxxx
TN 002 13 MBER 3 01206-xxxxxx
TN 002 14 MBER 4 01206-xxxxxx
TN 002 15 MBER 5 01206-xxxxxx
TN 002 17 MBER 6 01206-xxxxxx
TN 002 18 MBER 7 01206-xxxxxx
TN 002 19 MBER 8 01206-xxxxxx
TN 002 20 MBER 9 01206-xxxxxx
TN 002 21 MBER 10 01206-xxxxxx

TYPE TLST
TKTP IDA
ROUT 110
DES DDI_1ST/OG
TN 001 22 MBER 1 01206-xxxxx2-DDI
TN 001 23 MBER 2 01206-xxxxx2-DDI
TN 001 24 MBER 3 01206-xxxxx2-DDI
TN 001 25 MBER 4 01206-xxxxx2-DDI
TN 001 26 MBER 5 01206-xxxxx2-DDI



PAGE 002

TYPE TLST
TKTP IDA
ROUT 111
DES DDI_3RD/OG
TN 001 27 MBER 1 01206-xxxxx2-DDI
TN 001 28 MBER 2 01206-xxxxx2-DDI
TN 001 29 MBER 3 01206-xxxxx2-DDI
TN 001 30 MBER 4 01206-xxxxx2-DDI
TN 001 31 MBER 5 01206-xxxxx2-DDI
 
Not sure if this will help or not but here's a couple examples I have of the CLID entries;

Let's say you owned 333-123-0001 through 333-123-9999 and your extensions were 5 digits and began with the number 3

If your extension leading digit matches the last of your NXX it would look like this to push out Caller ID (333)-123-4567,
and you could use the same clid for all the matching extensions 3XXXX

Code:
ENTRY 1 
  HNTN 333  (Area Code)
  ESA_HLCL
  ESA_INHN NO
  ESA_APDN YES
  HLCL 12  (NXX if the extensions were 5 digit length and began with 3XXXX)
  DIDN YES (adds the extension after the HLCL 12, for example, extension 34567 would be added to the HLCL 12 = 12(3-4567)
  HLOC
  LSC
  CLASS_FMT DN

End reslt (333) 123-4567


If the extension range doesn't match the last digit of the HLCL or if your extension numbering doesn't match the DID digits coming in, or if it were a NON-DID extension and you wanted to push out the main telephone number it would look like this to push out Caller ID (333)-123-4567,but you would to have an individual CLID for every number if this were for DID numbers versus main telephone number.

Code:
ENTRY 51 
  HNTN 333  (Area Code)
  ESA_HLCL
  ESA_INHN NO
  ESA_APDN YES
  HLCL 1234567
  DIDN NO (DID set to NO so there is nothing added after the HLCL entry)
  HLOC
  LSC
  CLASS_FMT DN

End reslt (333) 123-4567

Then assign the CLID to the extension;
Code:
KEY  00 SCR 34567 (DID) 1     MARP
        CPND
          NAME Example of CLID Entry 1
          XPLN 15
          DISPLAY_FMT FIRST,LAST
or

KEY  00 SCR 70001 (non DID) 51     MARP
        CPND
          NAME Example of CLID Entry 51
          XPLN 15
          DISPLAY_FMT FIRST,LAST

End reslt (333) 123-4567 for both.
 
So where exactly is the block occurring, inside our network or from our line provider?
 
Thanks for the reply, although I'm a little out of my depth here, I'm not too sure what I'm looking at. Entering the below load I get the following outputs, but I'm not totally sure what it's telling me. Should I be attempting to set the DIDN to yes on entry 1?

REQ: prt
TYPE: clid

ENTRY 0
HNTN
HLCL
DIDN YES
HLOC
LSC

ENTRY 1
HNTN
HLCL
DIDN NO
HLOC
LSC "

Like someone else said, it doesn't look like you have much of anything built (configured) to output as your Caller ID.
Are there other CLID entries?
When you print out a typical phone is it assigned CLID 0?
KEY 00 SCR XXXXX 0 MARP
 
Sorry I didn't get back to you sooner had the equivalent of a thermonuclear disaster on our network last week only it was more horrific.

When printing out the average phone which is not setup as an agent you get the following:

CLS TLD FBA WTA LPR PUA MTD FNA HTA ADD HFA
MWA LMPN RMMD SMWD AAD IMD XHD IRD NID OLD VCE DRG1
POD DSX VMD CMSD SLKD CCSA-CSI SWD LNA CNDA
CFTA SFA MRD DDV CNID CDCA MSID DAPA BFED RCBD
ICDD CDMD MCTD CLBD AUTU
GPUA DPUA DNDD CFXA ARHA FITA CLTD ASCD
ABDA CFHA FICD NAID RNGI AGRD MOAD
UDI RCC HBTA AHA IPND DDGA NAMA MIND PRSD NRWD NRCD NROD
DRDD EXR0
USRA ULAD RTDD RBDD RBHD PGND OCBD FLXD FTTC MCBN
FDSD NOVD
CPND_LANG ENG
KEY 00 SCR 298 0 MARP
CPND
CPND_LANG ROMAN
NAME Some Name
XPLN 27
DISPLAY_FMT FIRST,LAST
01

When phoning from internal phone to internal phone you see the persons name and number come up, however external calls it is always as "Withheld".
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top