long story short, we have a tieline between two offices. A tech accidentally changed something on the route from my office to far end so that far end sees our seven-digit number instead of our individual DNs, and that's incorrect (they should just see our DNs). When far end calls us the caller ID is fine (tech only messed up my end). I called far end and did a trace and calling number does show my full seven-digit #. when I trace far end calling me calling number shows four-digit DN (again, which is correct). Any simple way to fix this? I've printed both routes (theirs and mine) and can't figure it out. Many, many thanks in advance.
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 Wanet Telecoms Ltd on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
CALLER ID ON TIELINE
- Thread starter coniglio
- Start date
are they both markes int or ext.. a internal trunk should show 4 digits a externalr should show clid.. the pni number needs to match and check the rcap of the dch on both ends.. and find a new tech
john poole
bellsouth business
columbia,sc
john poole
bellsouth business
columbia,sc
- Thread starter
- #3
- Thread starter
- #5
Nortellian
Technical User
print the clid table in the switch that is working and the one that is not working correctly and compare them. You may be able to figure out the difference. But unless the tech changed the clid table than that isn't it.
Avaya911PLM
Vendor
INT and EXT in the RDB do not control the CLID length. This prompt is used for distinctive ringing purposes.
CLID is controled by the CLID tables, and how what you dial matches in your CDP, and/or ESN data.
CPND being sent over the DCH is controlled in the RCAP settings of the DCH.
--
Fletch
Visit the Nortel Technical Support Portal at:
CLID is controled by the CLID tables, and how what you dial matches in your CDP, and/or ESN data.
CPND being sent over the DCH is controlled in the RCAP settings of the DCH.
--
Fletch
Visit the Nortel Technical Support Portal at:
Avaya911PLM
Vendor
That would be controlled by the DCH RCAPS. CPND support was released for NI-2 interfaces with 25.40.
--
Fletch
Visit the Nortel Technical Support Portal at:
--
Fletch
Visit the Nortel Technical Support Portal at:
Avaya911PLM
Vendor
Check the CTYP and try remarking it in a DMI table.
--
Fletch
Visit the Nortel Technical Support Portal at:
--
Fletch
Visit the Nortel Technical Support Portal at:
I actually gave that some thought and tried that out this afternoon by way of: I modified the CTYP to CDP in the DMI table and ensured that the RLI was pointed to that respective DMI. Nothing changed on the way the digits are sent to the far end.... any other ideas?
---
Andy Pham, ACS/FS-IT
Honeywell International, Inc.
andy.pham@honeywell.com
---
Andy Pham, ACS/FS-IT
Honeywell International, Inc.
andy.pham@honeywell.com
Avaya911PLM
Vendor
So let me get this straight.
You dial a 4 digit number, CDP picks this up as a DSC, you are going to an RLI and out an entry with a DGT marked as CDP to a route with a DCH using D100, and the CLID you are sending is 10 digits?
--
Fletch
Visit the Nortel Technical Support Portal at:
You dial a 4 digit number, CDP picks this up as a DSC, you are going to an RLI and out an entry with a DGT marked as CDP to a route with a DCH using D100, and the CLID you are sending is 10 digits?
--
Fletch
Visit the Nortel Technical Support Portal at:
Yes that is correct. If you look below, I believe the config will be accurate to your asking. Here are the dumps:
Here's the DGT dump from LD 86
FEAT DGT
DMI 3
DEL 0
CTYP CDP
----
Here's the RLB dump from LD 86
FEAT rlb
RLI 9
ENTR 0
LTER NO
ROUT 20
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
CNV NO
EXP NO
FRL 0
DMI 3
FCI 0
FSNI 0
SBOC NRR
OHQ NO
CBQ NO
ISET 0
NALT 5
MFRL 0
OVLL 0
----
Here's the CDP dump from LD 87
FEAT cdp
TYPE dsc
DSC
DSC 41
FLEN 0
DSP LSC
RLI 9
NPA
NXX
DSC 60
FLEN 0
DSP LSC
RLI 9
NPA
NXX
DSC 61
FLEN 0
DSP LSC
RLI 9
NPA
NXX
DSC 68
FLEN 0
DSP LSC
RLI 9
NPA
NXX
---
Andy Pham, ACS/FS-IT
Honeywell International, Inc.
andy.pham@honeywell.com
Here's the DGT dump from LD 86
FEAT DGT
DMI 3
DEL 0
CTYP CDP
----
Here's the RLB dump from LD 86
FEAT rlb
RLI 9
ENTR 0
LTER NO
ROUT 20
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
CNV NO
EXP NO
FRL 0
DMI 3
FCI 0
FSNI 0
SBOC NRR
OHQ NO
CBQ NO
ISET 0
NALT 5
MFRL 0
OVLL 0
----
Here's the CDP dump from LD 87
FEAT cdp
TYPE dsc
DSC
DSC 41
FLEN 0
DSP LSC
RLI 9
NPA
NXX
DSC 60
FLEN 0
DSP LSC
RLI 9
NPA
NXX
DSC 61
FLEN 0
DSP LSC
RLI 9
NPA
NXX
DSC 68
FLEN 0
DSP LSC
RLI 9
NPA
NXX
---
Andy Pham, ACS/FS-IT
Honeywell International, Inc.
andy.pham@honeywell.com
The RDB CLEN = 1 and here's the associated CLID entry in NET_DATA:
ENTRY 1
HNTN 763
ESA_HLCL
ESA_INHN NO
ESA_APDN YES
HLCL 391
DIDN YES
HLOC
LSC
CLASS_FMT DN
Is anything misconfigured?
---
Andy Pham, ACS/FS-IT
Honeywell International, Inc.
andy.pham@honeywell.com
ENTRY 1
HNTN 763
ESA_HLCL
ESA_INHN NO
ESA_APDN YES
HLCL 391
DIDN YES
HLOC
LSC
CLASS_FMT DN
Is anything misconfigured?
---
Andy Pham, ACS/FS-IT
Honeywell International, Inc.
andy.pham@honeywell.com
Avaya911PLM
Vendor
CLEN in the RDB is applicable to inbound calls only. It does not control CLID for outbound.
What does your NET_DATA block look like?
--
Fletch
Visit the Nortel Technical Support Portal at:
What does your NET_DATA block look like?
--
Fletch
Visit the Nortel Technical Support Portal at:
How does CLEN in RDB control CLID in inbound calls? I don't understand. However, here's my LD 15 NET_DATA...
TYPE NET_DATA
CUST 00
OPT RTD
AC2
FNP YES
ISDN YES
PNI 1
PINX_DN
MBG 0
BSGC 65535
PFX1
PFX2
HLOC
LSC
RCNT 5
PSTN NO
TNDM 15
PCMC 15
SATD 1
OCLI NO
TRNX YES
EXTT YES
FTOP FRES
VNR NO
NIT 8
FOPT 0
---
Andy Pham, ACS/FS-IT
Honeywell International, Inc.
andy.pham@honeywell.com
TYPE NET_DATA
CUST 00
OPT RTD
AC2
FNP YES
ISDN YES
PNI 1
PINX_DN
MBG 0
BSGC 65535
PFX1
PFX2
HLOC
LSC
RCNT 5
PSTN NO
TNDM 15
PCMC 15
SATD 1
OCLI NO
TRNX YES
EXTT YES
FTOP FRES
VNR NO
NIT 8
FOPT 0
---
Andy Pham, ACS/FS-IT
Honeywell International, Inc.
andy.pham@honeywell.com
I just gave this another thought, is there a CLS or classification in RDB, ADAN or BCH that determines if a DN matching CDP is considered an internal call?
I began thinking like this when received messages today in Meridian Mail
* Call within Meridian-1 leaving MM message
Message 1, from extension 1234, received today at 1:15 PM
* Call from tieline to Meridian-1 leaving MM message
Message 1, from phone number 2345, received today at 1:15 PM
Could it be true that if the system thinks the call originates from the PSTN it would id itself so?
In reverse, an outgoing call from Meridian-1 to tieline would ID as an external call, henceforth sending NPA+NXX+DN
Does this make any sense?
---
Andy Pham, ACS/FS-IT
Honeywell International, Inc.
andy.pham@honeywell.com
I began thinking like this when received messages today in Meridian Mail
* Call within Meridian-1 leaving MM message
Message 1, from extension 1234, received today at 1:15 PM
* Call from tieline to Meridian-1 leaving MM message
Message 1, from phone number 2345, received today at 1:15 PM
Could it be true that if the system thinks the call originates from the PSTN it would id itself so?
In reverse, an outgoing call from Meridian-1 to tieline would ID as an external call, henceforth sending NPA+NXX+DN
Does this make any sense?
---
Andy Pham, ACS/FS-IT
Honeywell International, Inc.
andy.pham@honeywell.com
- Status
Similar threads