Understanding CLID
The North American Numbering Plan (NANP) has a 10 digit format: NPA-NXX-XXXX, where:
NPA- Numbering Plan Area code = home national code: HNTNNXX- Central Office (within NPA) = home local code: HLCLXXXX- Line Number (subscriber) = local number: DN
Caller ID is typically: HNTN+HLCL+DN, where:
- HNTN - National code for home national number (1-6 digits)
- HLCL - Local code for home local number, or Listed DN (1-12 digits)
- DIDN - Append DN? YES, NO or SRCH. SRCH uses first DN (from KEY 0) with DIDN=YES
E.164 is an international standard, max. 15 digits, comprised of:
- +Country code (1-3 digits)
- Subscriber number (max. 12 digits)
Phone company PRI programming can over-ride your CLID programming. If directed, the carrier can send a specific number (or no number) on a PRI even if you have your CLID table setup right. So call your circuit provider and tell them you want to send custom CLID from the PBX (in DID range). Carriers may block calls with incomplete/incorrect Caller ID to prevent CLID spoofing attempts.
Print your CLID table by going into LD 21:
| >LD 21 | |
| REQ: PRT | |
| TYPE: CLID | Calling Line Identification entry data |
| CUST 0 |
You will see something like this:
| ENTRY 0 | DNs using CLID 0 |
| HNTN 212 | Send this as the NPA (do not include the 1 in the NPA) |
| ESA_HLCL | |
| ESA_INHN NO | |
| ESA_APDN YES | |
| HLCL 840 | Send this as the NXX |
| DIDN YES | This means: YES, append the DN on the end of the NPA & NXX |
| HLOC | |
| LSC | |
| ENTRY 1 | DNs using CLID 1 |
| HNTN 212 | Send this as the NPA (do not include the 1 in the NPA) |
| ESA_HLCL | |
| ESA_INHN NO | |
| ESA_APDN YES | |
| HLCL 8404000 | Send this as the 'listed directory number' (eg, operator) |
| DIDN NO | This means: NO, don't append the DN to the NPA & NXX |
| HLOC | |
| LSC |
This example is fairly typical, and would display the users actual DID if their DN was referring to CLID 0 (default) and would display the main number of the company if using CLID 1.
Make changes to your CLID table in LD 15, NET_DATA:
| >LD 15 | |
| REQ: CHG | |
| TYPE: NET | |
| TYPE NET_DATA | |
| CUST 0 | |
| OPT | |
| AC2 | |
| FNP | |
| CLID YES | Answer YES to this prompt to modify the CLID table. |
You can assign a CLID table entry to each DN on a phone in LD 11, if none is specified, the DN is assigned entry zero (default).
If the CLID table entry you want to use with DN 3299 was 2, then the DN key would be set up as follows:
| >LD 11 | |
| REQ: CHG | We can use 'easy change'... |
| TYPE: 2616 | |
| ECHG: YES | |
| ITEM: KEY 00 SCR 3299 2 | Use CLID entry 2 for this KEY/DN 3299 |
Using the Entry 0 and Entry 1 examples from above:
| KEY 0 SCR 2879 0 | Entry 0 will send 212-840-2879... the DID # |
| KEY 0 SCR 2879 1 | Entry 1 will send 212-840-4000... the Main # |
When you make rollover DNs; make the CLID entry D to tell the system to DIG back a key until it finds a real CLID table reference. Otherwise, if you make external calls out on a rollover key, the person receiving the call will not see the callers primary number.
| KEY 8 SCR 3456 D | D to 'dig' back to the first real CLID reference and use it (not 3456) |
Doing this does not change the internally displayed number.
Blocking CLID:
The Calling Number and Name can be permanently blocked on a per station basis with CLS option CLBA in LD 10/11.
CLBA- Activate Calling Party Number and Name per-line blocking(CLBD)- Deactivate Calling Party Number and Name per-line blocking
CLBA will block outgoing Calling Number and Name on ALL calls from that phone.
CLBD (default), blocking disabled. The user may dial the Calling Party Privacy (CPP) Flexible Feature Code to block number/name for individual calls, eg: If *22 is the Flexible Feature Code for CPP, you would dial *2291xxxxxxxxxx to block the outgoing Calling Party Number for that call.