DNIS, number of outpulsed digits, PRI

[NortelGuy1979]

All,

We are converting from a 3D to a 4D dialing plan on our PBX. As part of this, I'm auditing some 2 dozen TF numbers that we have, to determine if they ring to a DID, or present DNIS numbers, etc. Our telco rep hasn't been the most helpful, so I'm piecing this together from what I've found by calling each number and tracing the DCH.

In this post:

http://www.tek-tips.com/viewthread.cfm?qid=1487271&page=283

Someone references Fletch in saying that the telco can outpulse (example) 4 digits, but if LDN0 is 3 digits, only the right-most 3 digits are looked at when the call comes in.

My question is this:
If 4 digits are outpulsed from the CO to us, but our LDN0 is 3 digits, but we have an IDC table that has all 4 of those digits in it, does the IDC table take precedence? I'm thinking it does, as we have some TF numbers presenting with 4 digits converting to 3 digits, and they're routing correctly (even though LDN0 is 3 digits).

Next question (assuming DNIS length from telco is 4 digits, as well as outpulsed digit length is 4 digits on DID)
If a TF number has DNIS on it, but also has a "ring-to number" assigned to it (IE, TF number 800-555-1234 rings to DID number 310-555-6413) does the PBX receive both 1234 as DNIS but also digits 6413? Or just DNIS? Or just DID?

I have to admit - DNIS and DID digits have always confused me; and the NTP's don't help. The main configuration they seem to explain is if a TF number points directly at a trunk group with no DID digits assigned, and that route is auto-terminate to an ACD-DN, and DNIS is simply carried with the call (but not used to determine what DN to route the call to).

Any help would be appreciated.

Thanks!
-Matthew

Matthew - Technical Support Engineer

 

[johnpoole]

your idc can see 4 digits and translate that even with a 3 digit ldno... but if it's in the route from the vendor your only getting 3.. the provider can't send mixed length on the same ckt.. unless your playing with some new voip apps

dnis would come in on a unique route.. in that case the idc applied to that rdb can see all the digits and translates corectly..

when a provider calls a did a dnis, he's young.. for 800 inbound service without special routes and trunks, it's a simple call forward to the did..

you will not see dnis and did digits both.. i've worked both dms and pbx.. another thing to look at, atdn.. if you have a route that gets no digits, auto yes on the rdb then atdn of any key 0.. and yes that key can also be a did

john poole
bellsouth business
columbia,sc

 

[johnpoole]

we just went 4 to 5 on 7000 stations.. ran scripts for 24 hours..45k changes.. no one missed a call (hosp)

we had the provider send 5 digits 10 days prior to cut.. idc back to 4.. left the ldn 4.. ran clean.. so after making 4 vacant number.. changed 4000 to 555000, matched the idc entry.. for 100's of keys

changed the ldn to 5 digits..

then the script changed 555000 to 44000, removed the idc entry for that one dn.. the scripts does stat each station, and disu when idle..

great scripts, took about 200 hours to get then right, did not have to freeze the database untill the day of cut..


maybe you can't use any of this, but then maybe one or two steps may help//

john poole
bellsouth business
columbia,sc

 

[johnpoole]

and you need a new vendor.. and this may be the perfect time to find one that will work with you

john poole
bellsouth business
columbia,sc

 

[NortelGuy1979]

This is actually what I found.

When we have FlexDNIS, but no DNIS is specified on the TF number in the ESM database, then the DNIS properties of the 5ESS trunk group take affect; it will outpulse the last X digits of the "RTN" (route-to number), where "X" = how many digits are specified to outpulse on that trunk group.

If we have FlexDNIS on the TF number AND DNIS digits are defined in the ESM database, then those are outpulsed - they take precedence over the default DNIS settings on the 5ESS trunk group.

So the telco side of the mystery is solved.

Then, I went on to figure out why I had this one TF number presenting 4 digits on the DCH (on an NI2 DID route), but those 4 digits weren't in my IDC nor PBX. The last *3* digits were in the PBX.

The route was set to DNIS = NO, and our LDN was 3 digits. As it turns out, if the DNIS = NO on the route, then only the last x digits of the outpulsed digits are looked at, where X = the digit length of LDN0. Alternatively, if those digits (however many are outpulsed) are on an IDC, then they are translated that way. Basically, it's like 911guru said in that post - the LDN0 controls how many digits are looked at, but you can receive MORE than that.

If the route is set to DNIS = YES, then the LDN0 length is strictly enforced UNLESS the digits are on the IDC table.

Basically:

If DNIS = YES then IDC = YES (required)
Number of digits in Called Party Number is strictly adhered to (must match LDN0 length or be in IDC)
Assume LDN0 = 3 digits
If CPN = 3 digits, it must be valid DN or be on IDC table to convert, or re-order is returned
If CPN = 4+ digits, it must be on IDC table to convert, or re-order is returned


If DNIS = NO and IDC = YES
Number of digits in Called Party Number is not strictly adhered to (does not have to match LDN0 length, only be equal or greater)
Assume LDN0 = 3 digits
If CPN = 3 digits, it must be valid DN or be on the IDC to convert, or re-order is returned
If CPN = 4+ digits and it is NOT on the IDC table, then the last 3 digits must be valid DN or re-order is returned
If CPN = 4+ digits and it IS on the IDC table, then it is converted


If DNIS = NO and IDC = NO
Number of digits in Called Party Number is not strictly adhered to (does not have to match LDN0 length, only be equal or greater)
Assume LDN0 = 3 digits
If CPN = 3 digits, it must be valid DN, or re-order is returned
If CPN = 4+ digits, then the last 3 digits must be valid DN or re-order is returned

The confusion in our situation came in where we have one main route where the 5ESS trunk group is set to outpulse 3 digits by default, and DNIS = YES on our side, so the LDN0 length is strictly adhered to unless the digits are on the IDC table. Our main TF number was set to a 4 digit DNIS, and it was on the IDC, so that made sense.

Then we had a second route where the 5ESS trunk group is set to outpulse 4 digits by default, and DNIS = NO on our side, so the LDN0 length was NOT strictly adhered to, and only the last 3 digits had to match even if 4 or more digits were outpulsed from CO. The TF number we had pointed to THIS route was set to a 4 digit DNIS, and it was NOT on the IDC table, but it still terminated where I expected, so I was confused as to how. (Not on IDC and not a valid DN; but last 3 digits were valid DN).

I now officially hate DNIS, and I hate converting from 3 digit to 4 digit. ;-)

-Matthew

PS - we do have some DIDs that outpulse different digit lengths on the same PRI circuit (and trunk group on the 5ESS) - I'm not sure how they do that. Most are 3 digit, but I found one outpulsing 7 digit. It's Paetec; who knows...

Matthew - Technical Support Engineer

 

[johnpoole]

you've got it nailed ess5 can do some tricks that a dms can't...

1st thing is to go back through them one at a time and force your vendor to make digit length match... the 7 digit is fubar... my data geek boss wanted me to have all dids send 10 digits... right and it would take 4 days to edd and we would get a free ini anytime we did ld 49 change


I now officially hate DNIS, agree
converting from 3 digit to 4 digit. should be my hobby...


how can we have this much fun and still get paid?

john poole
bellsouth business
columbia,sc