Outpulsing Tips - ISDN

[dwaings]

I'm enquiring from the Long Distance world. I've got a customer who has a Definity PRI terminating on a Nortel DMS-250. The trouble is when the customer is not providing the DMS with any calling party information element on the d-channel, we're not able to generate a calling party number to the called parties. The customer has two 300 line hunt groups with two different nxxs from the same NPA, and can deliver, according to him, only 4 digit station id as the calling party number. Unfortunately, the hunt groups do not overlap. On calls where he gives us the 4 digit calling party information element, we can fill in NPA/NXX assigned to his trunk group the DMS-250. Here's the real question...is there a setting in the Definity that will allow the customer to either a) give us six or more digits as calling party number, b) give us the calling party number information element with a default 4 digit station id. He doesn't have support for his switch, and we MUST have something in calling party information, or else we substitute charge party on the forwarding SS7, which is not displayed on far end (tariff laws come into effect)...

any help would be appreciated

 

[pduarte]

Hi,
I don't have an answer to your question but was wondering if you can help me out.
I am trying to install two PRI t1's from my CO. The T1 are
DMS-250 or DMS-100 Custom. I would like to know if you can provide me with the configs for your DS1 so that I can compare them with mine.
I seem to have a problem with my D-channel in my Definity Switch.
Thanks for the Help in advance.
Pablo

 

[dwaings]

ooh..that's the kicker...we get some of the same questions only we work it in reverse (the long distance dms-250 usually is set up to match the customer switch)...
If I've read the posts right, your options in the Definity are DMS-100 custom, DMS-250 and NI2, correct? If it's a local PRI, then it's probably the DMS-100. I'm not clear on the options in that switch. But using the DMS-100 custom option probably requires that there's a setting on the local carrier switch that requires using SL1 profile. Normally, that's only for other NorTel meridian pbxs, but in our experience, using the SL1 profile on the LEC/IXC switch loaded against the NorTelNorthAmericanPRI (NTNAPRI) protocol standard works better.

Q. What are the troubles with the d-channel? Is it not coming up at all or is it dropping out? There may be an issue with the way the d-channels sync up. The LEC/IXC switches sometimes run SPM vice DTCI cards (difference in hardware, but can play a huge factor on the d-channel). If the T-1 is running to an SPM, you may have to check to see if there's a CRC6 enable option on your end -- the D-channels on the SPMs sync over the CRC-6 bits; if you don't have that enabled, the d-channel will eventually come up but it could take anywhere from a couple minutes to a couple hours. We've also seen in Definity switches where the customers are using inverse polarity on the d-channel, which stops the d-channel from coming up at all.

I don't know who's switching your traffic, but you should be able to use the Lucent Protocols just fine (the LEC/IXC will probably have to use the U.459/5ESS protocol standard). Personally, since our network is all DMS-250s, I try to talk the customers into the NorTel protocols - but a significant number of our customers use U.449 and U.459...their call.

Are you using NFAS? We've seen troubles where the customer equipment was ordered using a back-up d-channel but the cpe was not capable of supporting a backup. We've also seen orders where the customer requested two T-1s on one trunk group, but one active d-channel per T-1. That's prohibited in the trunk tables in the NorTel switches...the symptom is usually the LEC/IXC sees one d-channel come up, the other stays in lockout and you'll swap them back and forth and it won't change...the customer usually sees them both in service momentarily but they don't stay that way.

Hope it helps a little bit. I know only a little about the Definity side, and I know the IXCs are severely restricted in the options they can provide (without extra cost).

 

[dwaings]

Here's an example of the LD network settings...this is from a network DMS-250 that terminates on an SPM for a customer PRI group that's got two T-1s,using NFAs. (used to make 1+, terminate tollfree and can make VPN calls)...trunk group clli and default caller id have been deleted to protect the innocent. These are the important tables, there's other lesser ones that deal with the functionality of the switch, but...

AN SPM Dual T-1 PRI Long Distance Group...running into a DMS-250...

>pos cu(CLLI NAME)
CU(CLLI NAME)
PRA250 0
NPDGP NCON UCS CWCTH
NIL
0 NIL (ISDN 25) $ 0
5
VOICE_DATA 110
( NETSEC Y 1 N 0)$
>table trksgrp
TABLE: TRKSGRP
>pos cu(CLLI NAME) 0
CU(CLLI NAME) 0 DS1SIG
ISDN 5 5 87Q931 2 N YIELD NETWORK PT_PT PVTNET N UNEQ
120 N DEFAULT SPM 35 167 24 64K HDLC
( SPM 35 169 24 64K HDLC)$
$
>table ltdef
TABLE: LTDEF
>pos isdn 25
ISDN 25 B
PRA 46 46 23 23 NTNAPRI V1 SL1PROFL (NOPMD ) $ <<<<PROTOCOL
>table callattr
TABLE: CALLATTR
>pos 25
25 UCS VPNDAL 0 NONE 1
AUTH 0 (switch/trunk grp number) 0 (default caller id)
( ANIDELV CPNPREF) ( CAIN )$

 

[bsimon]

Your customer should be able to send you all 10 digits of the calling party number. This is certainly true if he has a G3 switch with fairly recent code. I'm less certain about old code revisions and smaller switches. Tell your customer to look at the documentation for the Cha ISDN Pub command.

The easy way to handle this: He can provide a constant 10D CID number that globally applies to all stations. This would typically be his site's main telephone number.

The less easy (but preferred) way to handle this: He can populate the ISND Pub table with valid unique 10D numbers that accurately reflect each DID number.

 

[dwaings]

Thanks...the customer consulted his vendor directly instead of asking the LD carrier to fix it from their end...exactly as you stated, parms in the Definity weren't set...appreciate it!