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]

FLEN is 7 by the way..

 

[3tdp33ler]

Look at INST on Incoming rout.
Is something there?

 

[johnpoole]

prt ldn data, you'll see a three digit number. that's usually the case when your getting 3 digits from the co for did's.. change that to any 7 digit number and your switch now will rec 7 digits. but your local provider would have to send you 7 digits.. are you using qsig? have your cisco either send 3 digits or add a 9 as the leading digit.. if that trunk in nortel has an ncos high enough to make the call it will trunk to trunk... btw it's better for maint to match a route... my route to my bcm on this site is route 98, in slot 98, tn's 98 1 to 98-23 dch is 98 dgt rlb are all 98.. makes for a cleaner switch when you have 40 pri's or even if you only have 2 or 3..

john poole
bellsouth business
columbia,sc

 

[itsnosecret]

The problem is , I am receiving 7 digits ok from the CO.
but then the 11c is stripping 4 digits off before going to trunk..Thats the bit Im trying to work out why.. any ideas?

 

[Reusser]

Wonder if there is a patch for this - What type of trunk inbound from Mobile? Tie/DID and what type out bound?

Also what rls is your switch?

 

[HASAGO]

I am assuming that this is a new setup? I tend to agree with what john said above. The PABX will not always look at the whole 7 digits of the incoming number. This wll be defined by the LDN length and also by the CO. Although you can see the full 7 digit number in the D Channel messaging does not mean that the PABX is taking noticeof all digits. The full 7 digits will be seen regardless. Hope this helps?

 

[johnpoole]

not a patch, i had the same problem with a dnis issue years ago, they sent 4, local did sent 3, ldn was a 3 digit number.. changed it to a four digit, dnis worked did's died.. solved by buying packages for ld 49, turned the 4 digit dnis to a three digit usable number... that was over a decade ago, and as we say down south, i ran that rabbit once, 98 percent of what i know is from mistakes that i make

john poole
bellsouth business
columbia,sc

 

[itsnosecret]

yep my LDN is 3 digits.

454.. so does this mean I need to increase this to a 7 digit number? or get rid of it to allow 7 digits to leave on my trunk.

isnt the LDN for consoles.?

 

[HASAGO]

There may be implications with making the LDN 7 digits. This may mean that your whole extension range will be affected. You may be able to have mulitiple LDN lengths? I am assuming that your current extension range is 3 digits also. Is there any reason why you can't use the 3 digits that you recieve from the mobile trunks? I am not clear on what you are trying to achieve with sending the calls from mobiles to Cisco link?

 

[itsnosecret]

7 Digits come in from mobile pri trunk and 7 digits must exit on a different trunk (TIE trunk )but only 3 digits leave.

What Im trying to acheive is the sending of the 7 digits that was recieved on the PRI mobile trunk to be sent to the TIE trunk with no loss of digits.

There is a LDN of 454 but It has no NIT service or anything like that when I print NIT in LD 21, so I dont think its in use (NOT SURE?).

What are my options? can I increase to 7 digits (Will it allow me?)or get rid of it if there is no console? or do you always have to have something in the LDN ..
The current extn range is 3 digits (correct)
I dont want this to effect anything on the switch.
all I want is the 7 digits coming in to be passed to another trunk group(cisco trunk) but it only sends 3 digits.

Hope its making sense? I think Im getting somewhere but need you help .thanks.

 

[itsnosecret]

Come on guys,, surely I can send what I receive on one trunk and pass the same digits to the other trunk , even if its 7 digits? and my extn range is 3 digits.
The 7 digits incoming must be passed to the other route becuase it includes a country code (3/4 digits) and an extn number of a distant end.and the 7 digits could be different each time.!

Any ideas.. I know its a tricky one .but thanks for your help

 

[telecomnorth]

On your PBX go to LD 86, print out the ESN block and check the response to NCDP. NCDP stands for number of digits for CDP routed calls and on your PBX it is likely set for 3. On CDP routed calls a Nortel PBX will wait to receive the number of digits defined in NCDP, route the call, and ignore any additional digits.

Do not change this setting or the length of the LDN(s) in LD 15.

The one solution I can think of right now is to build each seven digt number that you want to route to the Cisco as a seven digit TSC in the Nortel PBX. You system will need to have software package 150/DNXP - DN expansion.

Let us know if this works.

 

[telecomnorth]

Include a county code? As county codes vary in length and value you may be forced to go the your Telco service provider and have them provide a constant lenght of DNIS with a commmon lending digit(s).

For example, always 8 digits in length, always with the leading digit 5, with the four digit extension at the end of the string, and the county code just prior to the extension number.

50443550 = UK extension 3550. In the PBX route with a TSC of 50443550.

My example may be off a bit. But it's the constant lenght and leading digit that likely will be necessary just to get the DNIS number to fit your PBX numbering plan.

In reference to by previous post the TSC seems to over ride the NCDP defination so the additional digits should be passed onto the Cisco. Should...but you gotta test it.

 

[itsnosecret]

NCDP in the ESN was at 3 but I we changed that to 7 some time ago.
The problem I have is that the country code is not really the country code, its more a prefix.
Ie 807xxxx would be Finland, 827xxxx maybe Singapore.
are you saying that the each entry in DSC's /TSC's should be a constent length?

I tried making 807 a TSC but it sill does the same, it has to be something to do with the LDN or something else.

at the moment all of the country prefix's are set as DSC's and all go to the same route.

 

[telecomnorth]

The NCDP being already set for 7 does bring the spotlight back to the LDN being set at 3. So from another angle....

I have found that the use of IDC tables overrides the LDN setting. So on the route receiving the 7-digit DNIS calls modify/create a IDC table entry that screens for "8" and converts it to "8". No change in the DNIS value but should bypass the LDN setting. Than with a CDP/DSC entry of 807 you'll be speaking Lutefiskish in no time.

It should work...

 

[telecomnorth]

My mistake. Lutefisk came over with the Norwegians. With the Fins came the the sauna - and later on the cell phone.

 

[itsnosecret]

so just to be sure, I create a IDC of 8 to convert to 8.
I dont need to put 4 digits in here for each country?

 

[johnpoole]

i don't see what 8 to 8 will do, it's a non issue. your ldn is 3 and you can't add one that is 7. if your getting 3 for ddi's, you can have the provider send 7, chg the ldn to 7 uses an idc to drop the 1st 4, apply that to the did route and then you can route 7 in and 7 back out.. i do not see another way, even with idc to add that tandem route.. if your ac1 is 9, i would build an idc that sees 807, and sends 9807, because your getting the actual 7 digits, it should work the same as an analog station, dial 9 807 plus 4. and the call sends 807 plus 4 to the far end.. that would require a rlb sending 807 (nxx here) to the tie route

john poole
bellsouth business
columbia,sc

 

[telecomnorth]

John, your design should also work.

The two elements that need to be dealt with here are that LDN is sized at 3 digts in length and introducing a IDC table into the call processing.

With the LDN at 3 digits the PBX than looks for a 3 digit DNIS(pass-three-digits) on incoming calls. Additional digits are ignored.

With an IDC table in the mix the PBX, ignores the pass-three-digits setting imposed by the size of the LDN, accepts all passed digits as long as there is a left-to-right match with an IDC entry, and routes the call. So here the IDC entries could be set at 8 8, 807 807 , or 807xxxx 807xxxx.

With the above listed IDC entries the DNIS passes through the IDC table with no alteration. For example, when 8075555 passes through as 8075555 a CDP/DSC of 8, 807, or 8075555 can be used to route the call over to the Cisco trunks.

If I'm reading your post correctly your design has the IDC table with entries of 8 98, 807 9807, or 807xxxx 9807xxxx, inserting a leading digit of 9, and than using a SPN, NXX, NPA, or LOC under AC1 to route the call over ot the Cisco trunks. This routing should also do the trick.

But like always...for both designs...ya gotta test it.