trentsteenholdt1
Technical User
Help! lol Please 
I have an issue where one of my sites, Site A is producing a bizarre CLID number that I can't seem to match to any configuration! From what I can see, it doesnt match any of my CLID tables, DGT and RLB or even something crazy in LD90!
Here is the scenario.
Least cost routing is in place and workig fine (except this CLID joy! :-/ ).
Site B (e.g. DN=4318 - CDP) calls a number that Site A has been given lower cost for (e.g. 0894630700 - CDP) in LD90 SPN's/ LD 86 RLI.
Call is pushed to Site A so the call can go out over the PRI on Site A. The call goes out just fine, but something crazy happens when it hits the Site A PRI - The CALLING ID changes to...
0894334318 - Last 4 digits being the orignal DN and 089433. 089433 is close, but not actually, the HLCL for Site A. HLCL is 9433 and HNTN = 8.
Here is a trac of the virtual trunk TN that an example call from Site B to Site A PRI occurs.
But this is the thing, nothing in my LD86 DGT's or RLI is saying to add 089433 to the route, nor does any of my CLID's match! Well not from what I can see.
I wont print my DGT's or RLI's as there are heaps in Site A, but below is my CLID table. ENTRY 1 can be ignored in this case as it's used for Site C Branch office.
Any ideas or help on what it is would be greatly appreciated!
So everyone knows, I want the end result to be that the CLID for this type of call is the main reception LDN of Site A. I have the exact same set up, I think, on Site B and C and it's producing the correct CLID, that is - nothing bizarre like the adding of digits occur on the DCH of the PRI's. The CDP number stays the same, matches the rule of being non-DID and uses ENTRY 2 in the CLID table.
Cheers
Trent Steenholdt
Systems Engineer
The University of Notre Dame Australia
-Great scott!
I have an issue where one of my sites, Site A is producing a bizarre CLID number that I can't seem to match to any configuration! From what I can see, it doesnt match any of my CLID tables, DGT and RLB or even something crazy in LD90!
Here is the scenario.
Least cost routing is in place and workig fine (except this CLID joy! :-/ ).
Site B (e.g. DN=4318 - CDP) calls a number that Site A has been given lower cost for (e.g. 0894630700 - CDP) in LD90 SPN's/ LD 86 RLI.
Call is pushed to Site A so the call can go out over the PRI on Site A. The call goes out just fine, but something crazy happens when it hits the Site A PRI - The CALLING ID changes to...
0894334318 - Last 4 digits being the orignal DN and 089433. 089433 is close, but not actually, the HLCL for Site A. HLCL is 9433 and HNTN = 8.
Here is a trac of the virtual trunk TN that an example call from Site B to Site A PRI occurs.
Code:
.trac 112 0 15 1
ACTIVE VTN 112 0 15 01
ORIG VTN 112 0 15 01 IPTI RMBR 20 2 INCOMING VOIP GW CALL
FAR-END SIP SIGNALLING IP: 10.187.70.30
FAR-END MEDIA ENDPOINT IP: 172.16.35.47 PORT: 5200
FAR-END VendorID: Nortel CS1000 SIP GW release_7.0 version_ssLinux-7.00.20
TERM TN 021 19 IPMG 000 0 V PHYSICAL TN 000 0 13 16 DID RMBR 0 49 OUTGOING TRUNK CALL
VGW TN 000 0 13 16
FAR-END H.323 SIGNALLING IP: 172.16.30.11
FAR-END MEDIA ENDPOINT IP: 172.16.32.22 PORT: 5552
FAR-END VendorID: Not available
MEDIA PROFILE: CODEC G.729A NO-LAW PAYLOAD 20 ms VAD OFF
PDCA 2 PAD 0 0 PCML A A
RFC2833: RXPT 101 TXPT 101 DIAL DN 00894630700
MAIN_PM ESTD
TALKSLOT ORIG 4 TERM 4 JUNCTOR ORIG0 TERM0
EES_DATA:
NONE
QUEU NONE
CALL ID 1 14212
---- ISDN ISL CALL (ORIG) ----
CALL REF # = 386
BEARER CAP = VOICE
HLC =
CALL STATE = 10 ACTIVE
CALLING NO = 4318 NUM_PLAN:PRIVATE TON:ABBREVIATED ESN:CDP
CALLED NO = 00894630700 NUM_PLAN:PRIVATE TON:ABBREVIATED ESN:CDP
---- ISDN ISL CALL (TERM) ----
CALL REF # = 2233
BEARER CAP = VOICE
HLC =
CALL STATE = 10 ACTIVE
CALLING NO = 0894334318 NUM_PLAN:PRIVATE TON:SUBSCRIBER ESN:UNKNOWN
CALLED NO = 0894630700 NUM_PLAN:E164 TON:UNKNOWN ESN:UNKNOWNBut this is the thing, nothing in my LD86 DGT's or RLI is saying to add 089433 to the route, nor does any of my CLID's match! Well not from what I can see.
I wont print my DGT's or RLI's as there are heaps in Site A, but below is my CLID table. ENTRY 1 can be ignored in this case as it's used for Site C Branch office.
Code:
>ld 21
PT1000
REQ: prt
TYPE: clid
CUST 0
SIZE 3
RNGE
INTL 61
ENTRY 0
HNTN 8
ESA_HLCL
ESA_INHN NO
ESA_APDN YES
HLCL 94330
DIDN YES
DIDN_LEN 3
HLOC
LSC
CLASS_FMT DN
ENTRY 1
HNTN 8
ESA_HLCL
ESA_INHN NO
ESA_APDN NO
HLCL 91920
DIDN YES
DIDN_LEN 3
HLOC
LSC
CLASS_FMT DN
ENTRY 2
HNTN 8
ESA_HLCL
ESA_INHN NO
ESA_APDN YES
HLCL 94330
DIDN NO
DIDN_LEN 0
HLOC
LSC
CLASS_FMT DNAny ideas or help on what it is would be greatly appreciated!
So everyone knows, I want the end result to be that the CLID for this type of call is the main reception LDN of Site A. I have the exact same set up, I think, on Site B and C and it's producing the correct CLID, that is - nothing bizarre like the adding of digits occur on the DCH of the PRI's. The CDP number stays the same, matches the rule of being non-DID and uses ENTRY 2 in the CLID table.
Cheers
Trent Steenholdt
Systems Engineer
The University of Notre Dame Australia
-Great scott!
