Something is deleting 4 digits (DGT?)

[itsnosecret]

Please help me with this one.

BACKGROUND:
Icoming PRI trunk from Mobile operator to 11c
Outgoing TIE trunk to CISCO router.

for arguments sake.

Mobile trunk (DCH 13)is ROUTE 1
Cisco trunk is (DCH 14) ROUTE 2

DSC 807 points to RLI 2 which points ROUTE 2(CISCO ROUTE.)

DMI = 0 in both cases.

Now here is the fun part.

When I put MSGI/MSGO on both DCH 13 AND DCH 14.
INCOMING FROM MOBILE TRUNK GIVE'S ME 7 DIGITS (NOTHING WRONG HERE.)
THE SAME CALL THEN DECIDES TO STRIP 4 DIGITS OFF MY AND THE SWITCH TRY'S AND ROUTES A 3 DIGIT NUMBER OVER THE CISCO TRUNK (VERY BAD.)

There is no TSC for this 807 xxxx range , so I even outed the DSC 807 and created a TSC of 807 (for a test) and the same thing happens..

So it would appear the my translations are ignoring the DSC and using some other reference that is stripping off 4 digits?
When you dial locally (EXTN HOSTED OF 11C) it routes ok with 7 digits.

NO LSC on switch and the SPN 8 is going off to route 0 (a different route) so its not that either.

IDC set to NO on Incoming PRI trunk.

Can anyone help? I think I need some help with Routing..
Wish I could do a traver like the DMS!!
Need help on this one... thanks.

 

[itsnosecret]

Ok its D -Day tomorrow, tech on site to configure IDC and hopefully put this one to bed.

I will let you know how we get on..

Thanks very much in advance especially Telecomnorth and Johnpoole.

Lets hope the idea works..
ps Im going to learn loads from this forum..

 

[itsnosecret]

Well guys both didnt work.

I tried IDC with 807 to 807 & 8-8 and also tried converting 807 - 0807 to go via SPN and Im still getting the same results?

even with the above setup the outpulsed digits are still on 3 digits in length (the last 3 digits of the 7)
Package is turned on. can you see any dramas with the below?

All my IDC are set to YES
DCNO is 5
NDNO is also 5
AND THE ORGINATING TRUNK
ROUTE 2

INCOMING FROM CO

TYPE RDB
CUST 00
DMOD
ROUT 2
DES VODAFONE
TKTP DID
SAT NO
RCLS EXT
DTRK YES
BRIP NO
DGTP PRI2
ISDN YES
MODE PRA
IFC EURO
CNTY ETSI
SBN NO
PNI 00000
NCNA NO
NCRD NO
ISAR NO
CPFXS YES
ADDP NO
INTC NO
DSEL VOD PTYP DCO
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
RANX NO
SRCH RRB
TRMB YES
SETP
ACDO XXXX
TCPP NO
TARG
BILDN NO
OABS
INST
IDC YES
DCNO 5
NDNO 5 *
DEX YES
DNAM NO
MFC NO
ICIS YES
OGIS YES
TIMR...

DTD NO
SCDT NO
2 DT NO
DDO NO
DRNG YES
NDRI 00
CDR NO
CCO NO
NATL YES
SSL
CFWR NO
IDOP NO
VRAT NO
MUS YES
MRT 40
MR NO
PANS YES
EQAR NO
FRL...
..
OHQ NO
OHQT 00
TTBL 0
PLEV 2
OPR NO
PRDL NO
EOS NO
DNSZ 0
RCAL NO
MCTS NO
ALRM NO
BTT 30
ACKW NO
ART 0
PECL NO
DCTI 0
SGRP 0
AACR NO




LD 49
REQRT
TYPE IDC
CUST 0
DCNO 5
PRT SDID
SDID YES
IDGT CDGT
807 0807


LD 90
PRT
NET
AC1
SPN 0807
FLEN 4
ITOH NO
RLI 2
SDRR NONE
ITEI NONE


LD 86
PRT
RLB
RLI 2
LTER NO
ROU 1 (VOIP TRUNK)
.....


LD 21
PRT
RDB
ROUT 1
DES VOIP_TRK
TKTP TIE
ESN NO
RPA NO
CNVT NO
SAT NO
RCLS INT
DTRK YES
BRIP NO
DGTP PRI2
ISDN YES
MODE PRA
IFC EURO
CNTY ETSI
SBN NO
PNI 00000
NCNA NO
NCRD NO
CTYP UKWN
INAC NO
ISAR NO
TGAR 0
CPFXS NO
HNTN 8
HLCL 936
ADDP NO
INTC NO
DSEL VOD
PTYP DTT
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
SRCH LIN
TRMB YES
STEP
ACOD XXXX
TCPP NO
TARG
BILDN NO
OABS
INST
IDC YES
DCNO 3 (THIS IS THE VOIP TRK,INCOMING)
NDNO 3
DEXT NO
DNAM NO
ANTK
SIGO STD
MFC NO
ICIS YES
OGIS YES
TIMR....

 

[telecomnorth]

The last three digits of the seven? I should have asked for that is an important clue.

What is the AC1 value? 9, 0, other

The IDC entry of 807 0807 is missing the AC1. If AC1 is 9 than the entry needs to be 807 90807. Remember the strip the 0 off with a DMI so the PBX sends 807xxxx.

What happens to the call when it is routed with just the three digits? silence, reorder, ???? What does the Dchannel message list?

As a simple test chg the DSEL in the Voip Route to VCE and test. Having this set for Voice or Data (VOD) may not be required here.

Are you able to enter all seven digits the IDC? 807xxxxx 807xxxx ? If so, test with DCS of 807.

Does the PBX have DN expansion - Option 150 DNXP ?

 

[itsnosecret]

MY AC1 = 0.

But the D-Channel trace says dialled digits are 870 (last 3 from 8071870)in all cases of each test I have done.
Not sure what the user gets when they dial the number as its from a mobile phone over the route in New Zealand.

BTW changing the LDN fixed the problem but I had to revert back as it effected extn dialling etc..

package 150 is there when I print the PKG in LD 22.

just tried IDC OF 807X870to convert to 807X870(the test number) and it fails again.
Also changed the route to VOICE no joy here too (im still geting called #:870 num plan : e164 in my call trace.

 

[telecomnorth]

When you changed the LDN to a number 7 digits in lenght did fix the problem? That's a valuable clue.

With the AC1 being 0 than your spn 0807 is incorrect. It should be just 807.

Programming review:

If IDC entry is 8071870 8071870 than route with DSC 807 via a RLB with no DMI/DGT assigned. Your original post indicated that a call from local PBX telehone to 807xxxx would be successful. Verify that it is still working.

If IDC entry is 8071870 08071870 than route with SPN 807 under AC1 via a RLB with no DMI/DGT assigned. Also test with a local PBX telephone dialing 08071870.

Prt DGT 0 in LD 86 and post for review.

 

[itsnosecret]

just tried your IDC 8071870 TO 08071870 , made the SPN 807 under AC1 go to route (with no DGT) and I still get the same thing..
just had confirmation that extn dialling to the 807 number works.

Nothing in DGT 0 to print..

Help!!! what is going on with the switch..could it be a patch problem?

changing the LDN fixed the problem but effected other stuff (as you said) so I had to revert that back.

I guess this is getting too hard to fix, I have ran out of ideas. thanks for your help anyway.. if you have any more ideas keep them coming.

 

[telecomnorth]

We've getting close. Test the following design adjustments.

1) Change the LDN to 7 digits in lenght allowing for 7 digit DNIS calls to routing properly. Create 3 digit IDC enteries for the extensions and place on the related trunk routes. Example: 454 454, 455 455, and so on. No change to the dialed digits just matching values. Create one for an existing extension and test. If this works than create IDC entries for all extensions and place on all necessary trunk routes.

or

2) Out all LDN enteries. Create the 3 digit DNIS's for extensions as listed above and test. If this design is the answer you will have to create matching IDC enteries, both 3 and 7 digits, for all inbound DNIS calls covering all possible inbound trunk routes.

If either of these designs is implemented permanently you will than have to deal with the fact that the old LDN of x454 has been changed. Two options are to make x454 a DN appearance on a phone or build an ACD Que of x454 with a NCFW to a existing extension. Even if x454 is not dialed from the public do put it back in the system somewhere in case it is target for a Voice Mail opt outs, FNA, Hunt, and the like.

Patches? As release 23 is End-of-Life(?) Nortel will not create new patches. I don't know if existing patches can still be downloaded from Nortel or if there is one related to this issue. You would have to check with a Nortel distributor.

For what it's worth I suspect your running up against a software design issue and not a patch issue.

 

[itsnosecret]

I would think it was a design issue,
however using DSC's in a CDP is nothing new.

For example I bet many companies have set up similar using the following as an example: (only an example)

PBXA(extn range 6xx)-TIE---PBXB(2XX)---TIE--PBXC (5XXX)

Note how the PBXC has a 4 digit range, so if PBXA wants to dial PBXC it means PBXB has to pass more digits than its current LDN (EXNT length) etc..

Unless in a true CDP design all ranges have to be of equal length? what's your experience in CDP, and is what Im doing something that has never been done before, or is what we are doing not the normal way of doing things (ie mixing number lengths?) Just a thought..?