Home
>
Lucent Technologies
>
Communications System
>
Lucent Technologies DEFINITY Communications System Generic 2.2 And Generic 3 V2 DS1/CEPT1/ISDN PRI Reference Manual
Lucent Technologies DEFINITY Communications System Generic 2.2 And Generic 3 V2 DS1/CEPT1/ISDN PRI Reference Manual
Have a look at the manual Lucent Technologies DEFINITY Communications System Generic 2.2 And Generic 3 V2 DS1/CEPT1/ISDN PRI Reference Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 413 Lucent Technologies manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
DEFINITY Communications System Generic 2.2 and Generic 3 V2 DS1/CEPT1/ISDN PRI Reference 555-025-107 Issue 1 July 1993 Layers 2 and 3 Page 5-25 ISDN PRI Layer 3 5 G3V2 systems d efine the following b earer c ap ab ility c lasses: nVoic e/voic e-g rad e d ata nMode 0 digital data nMode 1 digital data nMode 2 digital data nMode 3 digital data nWideband (G3V2 only) G2.2 systems d efine the following b earer c apab ility c lasses: nVo i c e nVoic e Grad e Data nMode 0 nMode 1 nMode 2 nMode 3 nUnknown Digital nUnknown Analog nMod e 3/2 Ad ap tive nX. 2 5 Both systems have a separate field for the information transfer c ap ab ility, either restric ted or unrestric ted d ig ital d ata. For d efinitions of mod es 0, 1, 2, and 3, see the Dig ital Multip lexed Interfac e (DMI) Tec hnic al Sp ec ific ation, Issue 3.1, Aug ust 1986, selec t c od e 500-029. Ask for the most rec ent version. Less rig orous d efinitions c an b e found in Tab le 4-8 on p ag e 4-22 . G2.2 systems p op ulate the b earer c ap ab ility IE in the following way: nFor c alls from non-ISDN end p oints to ISDN PRI trunks, the b earer c ap ab ility IE is p op ulated from the b earer c ap ab ility c lass of servic e ind ic ated in field s 15 and 16 of proc ed ure 014, word 1 and assig ned to the end p oint in p roc ed ure 000, word 3, field 5. nFor c alls from ISDN end p oints to ISDN PRI trunks, the bearer c ap ability IE is p op ulated b y the end p oint at the time the c all orig inates. Op tion setting s on the ISDN set d etermine the various BC IE c odep oints, suc h as transfer rate and information typ e. G3V2 systems p opulate the BC IE in the following way:
DEFINITY Communications System Generic 2.2 and Generic 3 V2 DS1/CEPT1/ISDN PRI Reference 555-025-107 Issue 1 July 1993 Layers 2 and 3 Page 5-26 ISDN PRI Layer 3 5 nFor c alls from non-ISDN end p oints to ISDN PRI trunks, the b earer c ap ab ility IE, exc ep t for the information typ e c od epoint, is p op ulated automatic ally b ased on the typ e of end p oint. For examp le, if the end p oint is an MPDM set for mod e 0 op eration, the BC IE is p op ulated with mod e 0 c harac teristic s. Two exc ep tions to this rule exist as follows: — A c all from a mod e 2 end point is routed to a p attern c ontaining voic e preferenc es b ut no mod e 2 preferenc es. In this c ase a mod em p ool is inserted and the outg oing ISDN PRI messag e is p opulated b y the BCC and ITC ad ministration of the p referenc e, not the orig inating end p oint. — A c all from a voic e end p oint is routed to a p attern c ontaining p referenc es ad ministered only for d ata (BCCs 1, 2, 3, or 4). In this c ase, the outg oing ISDN PRI message is p op ulated b y the BCC and ITC ad ministration of the p referenc e, not of the orig inating endpoint. nIn G3V2, the information typ e c od ep oint in the BC IE is c od ed from the ad ministered ITC field on the d ata mod ule form. nAs with G2.2, for c alls from ISDN end p oints to ISDN PRI trunks, the b earer c ap ab ility IE is p op ulated b y the end p oint at the time the c all orig inates. Op tion settings on the ISDN set d etermine the various BC IE c od ep oints, suc h as transfer rate and information typ e. NOTE: International d ata c alls req uire the information typ e in the BC IE to b e c od ed as unrestric ted . In G2.2 and G3V2 you c an c ontrol this in ad ministration. Sinc e the ways the DEFINITY systems app ly the bearer c ap ab ility c lass involve using b oth the b earer c ap ab ility IE and the low layer c omp atib ility IE, refer to the sec tion ‘‘Low Layer Comp atibility IE’’ in the sec tion ‘‘User-to-User Information Sig naling’’ for the d etails of how these information elements and the BCCs are used. Calling Party Number IE The DEFINITY systems send the c alling p arty numb er in c od eset 0 in the SETUP messag e. Its p rimary use is to ind ic ate the c alling p artys numb er on the connected partys station display. The number digits field in the calling party numb er is used to send the ad d ress of the c alling p arty. In G2.2, the numb er d ig its field is p op ulated with the 10 dig it numb er formed b y ad d ing the last three or four d ig its of the c alling p artys extension to the value entered in the NPA-NXX field s in p roc edure 354, word 3. In G3V2, the numb er d ig its field is p op ulated from the CPN p refix tab le. At the rec eiving end , the c ontents of the rec eived CPN IE c an be either the calling partys number or the calling partys billing number. If the call is not switc hed throug h the AT&T network, the c ontents of the CPN IE will always b e the c alling p artys numb er as pop ulated from the c alling system. If the c all is
DEFINITY Communications System Generic 2.2 and Generic 3 V2 DS1/CEPT1/ISDN PRI Reference 555-025-107 Issue 1 July 1993 Layers 2 and 3 Page 5-27 ISDN PRI Layer 3 5 switc hed b y AT&T, however, the c alled p arty has four c hoic es as to how to rec eive c alling party numb er or b illing numb er. The AT&T network c alls these op tions features. Options from the AT&T Network When provisioning the AT&T servic e, you must tell the servic e provid ers whic h of these features you want. Following are the features you c an c hoose from: nC PN p re f e rre d . Th is f e a t u re t e l ls t h e 4 ESS t o se n d t h e D EFI N I TY s y st e m the c alling p arty numb er in the CPN IE, if it is availab le. If it is not available, the 4ESS send s the b illing number in the CPN IE. nBN p referred . This feature tells the 4ESS to send the DEFINITY system the billing number in the CPN IE, if it is available. If it is not available, the 4ESS send s the c alling p arty numb er in the CPN IE. nC PN o n l y. Th is f e a t u re t e l ls t h e 4 ESS t o s e n d t h e D EFI N I TY s y st e m t h e c alling p arty numb er in the CPN IE, if it is availab le. If it is not availab le, the 4ESS does not send the CPN IE. nB N o n ly. Th i s f e a t u re t e ll s t h e 4 ESS t o s e n d t h e D EFI N I TY sy s t e m t h e billing number in the CPN IE, if it is available. If it is not available, the 4ESS d oes not send the CPN IE. In ad d ition to these features, on G3V2 systems you c an ord er the req uest op tion from the network. With this op tion the network send s CPN/BN only if req uested b y the G3V2 for a g iven c all. This is imp lemented in the inc oming c all hand ling tab le for the trunk g roup . For examp le, if you subsc rib e to the CPN only feature, y o u c a n t e ll t h e 4 ESS, t h ro u g h t h e se t t in g s in t h e in c o m in g c a l l h a n d l in g t a b l e , t o send the CPN only on c alls of a c ertain servic e typ e (for c all-b y-c all trunk g roup s) or only on DNIS c alls. To have this c ap ab ility, you must ad minister the Per Call CPN/BN field s in the inc oming c all hand ling tab le and also p rovision this op tion f ro m t h e 4 ESS. Fo r d e t a il s o n h o w t o i m p le m e n t t h i s , s e e t h e s e c t io n ‘‘Network Sp ec ific Fac ilities IE in U.S.’’. NOTE: If you p rovision the servic e to always d eliver CPN/BN b ut you also req uest it on a per-call basis, the request will be rejected. For the calling (and connected) party numbers to be supplied across a public network, the DEFINITY system and the far end end p oint must b e on ISDN ac c ess to the p ub lic network. For example, in the U.S. if you rec eive an SDN c all from a far-end switc h that is c onnec ted to a 4ESS with T1.5 ac c ess, you c annot rec eive the c alling p artys numb er in the CPN IE. Thus, you will rec eive the BN in the CPN IE if you sub sc rib e to the BN only, BN p referred or CPN preferred features. At p resent, SDN servic e and ACCUNET Switc hed Dig ital Servic es p rovid e ISDN end-to-end capability in the U.S.
DEFINITY Communications System Generic 2.2 and Generic 3 V2 DS1/CEPT1/ISDN PRI Reference 555-025-107 Issue 1 July 1993 Layers 2 and 3 Page 5-28 ISDN PRI Layer 3 5 Numbering Plan and Type of Number In ad d ition to number d ig its field , whic h c arries the ad dress of the c aller, the c alling p arty numb er IE also c arries information on the numb ering p lan and typ e of numb er. These two field s are p op ulated as follows: The only exc ep tion to this enc od ing is for c ountry p rotoc ol op tion 3 (Japan) in G3V2. In this c ase, b oth the numb ering p lan id entific ation and the typ e of number fields are coded as unknown. All DEFINITY systems acc ept c alling party number IEs regardless of how these two fields are enc oded. Requirements for Sending CPN IE In G2.2 systems, to send the c alling p arty numb er, the NPA-NXX desig nator field in p roc ed ure 354, word 3 must b e ad ministered . This d esig nator must also b e entered in p roc ed ure 000 for the c alling p artys extension. The numb er sent is then always of the form NPA-NXX-extension, a 10-d ig it direc t d istanc e d ial (DDD) numb er. Also, p roc ed ure 100, word 3, field 8 must b e set to 0 or 2 to send the op tional information elements. When set to 2 , the op tional IEs are sent, b ut if the trunk g roup is a DCS trunk g roup on an ISDN fac ility and an ISDN c all from another trunk g roup is routed to it, the DCS name messag e is sup p ressed . In G3V2 systems, to send the c alling p arty numb er IE, the CPN prefix tab le form must b e ad ministered . This tab le allows you to spec ify the numb er to b e p ut in the CPN IE for any given extension. The Send CPN field in the trunk g roup sc reen must also b e ad ministered as y . G3V2 CPN Prefix Table. Following is an example of how to administer the G3V2 CPN Prefix Tab le: Screen 5-1. G3V2 CPN Prefix Table Numbering Plan Identification ISDN/telep hony numb ering p lan (rec ommend ation E.164/E.163) Type of Number National Number CPN PREFIX TABLE Ext Ext CPN Total CPN Len Code Prefix Length 5 65 61948 10 5 66 619494 9 5 67 61949 5 68 61949
DEFINITY Communications System Generic 2.2 and Generic 3 V2 DS1/CEPT1/ISDN PRI Reference 555-025-107 Issue 1 July 1993 Layers 2 and 3 Page 5-29 ISDN PRI Layer 3 5 Tab le 5-3 d esc ribes the ad ministration setting s for the ISDN PRI-sp ec ific field s in this ad ministration form: In G3V2, any numb er of d ig its (from 0 to 15) c an b e sent in the CPN IE b ec ause the CPN p refix tab le allows numb ers of variable length to b e formed . In prac tic e, you should always ad minister the CPN in the form of the p ublic network numb ering p lan for your c ountry. For examp le, if the p ub lic network numb ering p lan is 10 dig its, as in the U.S., and you ad minister the CPN to b e 7 d ig its throug hout your ISDN network, you mig ht rec eive a 7-d ig it CPN over a p ub lic network trunk, whic h would be meaning less. Table 5-3. Field Definitions CPN Prefix Table Field Remarks Ext Len This field and the next c onstitute a key that determines whic h row of the tab le to ap p ly to an extension. Enter the numb er of extension d ig its in the d ial p lan. For examp le, if you are on a five d ig it d ial p lan, enter 5. You c an also use this tab le if you have a mixed numb ering p lan. The sum of this numb er and the numb er of d ig its in the CPN Prefix field must b e a numb er g reater than or eq ual to the numb er in the Total CPN Length field . Ext Cod e This field allows g roup s of extensions to b e ad ministered . If 12 is entered here, for examp le, and 5 was ad ministered in the first field , then all extensions of the form 12XXX will matc h this row. If 12 is ad ministered here and 123 is also administered , then all numb ers of the form 12XXX exc ep t for 123XX will matc h this row. For e xa m p le , if yo u w a n t e d a ll e xt e n s io n s o f t h e f o r m 1 2 XXX e x c e p t f o r 123XX to b e sent with the CPN p refix 30346 and the 123XX extensions to b e sent with the CPN p refix 30353, then you would ad minister b oth 12 and 123 in this field in two different rows. CPN Prefix Enter the d ig its you p rep end to the least sig nific ant d ig its of the extension c od e d ig its to form a CPN of the leng th sp ec ified in the Total CPN Length field. For example, in the sample screen s h o w n a b o ve , i f a n y e xt e n s io n o f t h e f o r m 6 5 XXX p la c e s o r answers a c all, the numb er sent to the other end will be 6 1 9 - 4 8 6 - 5 XXX ( 1 0 d i g it s ) . I n t h e se c o n d ro w t h e t o t a l le n g t h i s 9 d ig its. Sinc e the sum of the Ext Len field and the CPN Prefix field is g reater than the total CPN leng th, the CPN p refix is p rep end ed to the least sig nific ant d igits of the extensions to form a 9 d ig it CPN. For examp le, the extension 66123, when c onverted to the CPN, would b ec ome 619494123. Total CPN Leng th This is the total leng th of the CPN. It c an b e any numb er from 0-15.
DEFINITY Communications System Generic 2.2 and Generic 3 V2 DS1/CEPT1/ISDN PRI Reference 555-025-107 Issue 1 July 1993 Layers 2 and 3 Page 5-30 ISDN PRI Layer 3 5 Calling Party Number Display Requirements In G2.2 systems, the c alling p arty numb er, if sent from the far end , will always be d isp layed . If b oth the c alling p arty numb er and the d isp lay IE are sent from the far end , both will b e d isp layed . In G3V2 systems, the c alling p arty numb er, if sent from the far end , will always b e d isp layed . If b oth the c alling p arty numb er and the d isp lay IE are sent from the far end , both will b e d isp layed . If only the c alling p arty numb er is rec eived , the d isp lay shows Call From and the number. In G3V2 systems, the format of the d isp lay on the c alled p artys terminal d ep end s on the ad ministration setting in the North American Area Code field in the d ial p lan form. If this field ind ic ates an area c od e and the typ e of numb er field in the IE is not international, the numb er will b e d isp layed in the NANP format with hyp hens (for examp le, 303-538-1526). Otherwise, the numb er will b e d isp layed without hyp hens or sp ac es. Also, if the typ e of numb er field in the IE is international, the d isplay will ind icate an international numb er b y displaying INTL in the MISC ID field . These rules assume the c all d oes not travel over DCS trunk g roup s. If the c all is mad e on an ISDN trunk g roup used for DCS, the ISDN PRI d isp lay mig ht b e overridd en b y the DCS d isp lay. Whenever the DCS d isp lay takes p rec ed enc e, the ISDN CPN IE is not d isplayed . See the sec tion ‘‘Disp lay IE’’ for interac tions b etween DCS and ISDN d isp lays. Calling Party Number on Tandem Calls If a c all is tand emed throug h any G3V2 system, CPN will b e p assed if the c all orig inated as an ISDN PRI c all and c ontinued over ISDN PRI trunks. If, however, a c all is tand emed from a non-ISDN trunk to an ISDN trunk, the c alled p arty will d isp lay the trunk g roup name of the inc oming trunk, if ad ministered . Called Party Number IE The DEFINITY systems send the c alled p arty numb er in c od eset 0 in the SETUP messag e. This IE is always sent without any p rereq uisite ad ministration. The c alled p arty numb er IE is not used in ISDN PRI d isp lays. Instead , the c onnec ted numb er IE is d isp layed when the c onnec tion is mad e. The d ialed d ig its ap p ear on the c allers d isp lay as they are being dialed . The c alled p arty numb er IE is, however, p assed to telemarketing app lic ations, suc h as ASAI gateway. On inc oming c alls, G2.2 systems examine the type of number field in the c alled p arty numb er IE to d etermine how to route the c all. G3V2 systems, however, ig nore these field s and route inc oming c alls b ased only on the analysis of the d ig its rec eived . For examp le, these systems must rec eive the p refix 011 to route international c alls c orrec tly.
DEFINITY Communications System Generic 2.2 and Generic 3 V2 DS1/CEPT1/ISDN PRI Reference 555-025-107 Issue 1 July 1993 Layers 2 and 3 Page 5-31 ISDN PRI Layer 3 5 When send ing the c alled p arty numb er IE, G2.2 systems pop ulate the Number Plan ID and Type of Number field s from ad ministration. You ad minister these field s in p roc edure 322, word 1, field s 3 and 4. G3V2 systems, however, p opulate these fields automatic ally as follows: Screen 5-2. G3V2 Called Party Number IE NOTE: Exc ep t for the trunk ac c ess c od e (TAC), the c all typ es ab ove are the c all typ es assigned to a d ialed d ig it string in the AAR and ARS d ig it analysis tab les. NOTE: For Jap an (c ountry op tion 3) the numb er p lan is always enc od ed as unknown. Channel ID IE The c hannel id entific ation information element, whic h is sent in the SETUP messag e and in several other ISDN messag es, is used to assoc iate a c all with its c orresp ond ing B c hannel and c orrespond ing D c hannel messag es. In a FAS interfac e, the interfac e ID c od ep oint in the c hannel ID is imp lied and thus is not sent. In an NFAS arrang ement, however, the interfac e ID must b e p resent. G2.2 systems p op ulate the interfac e ID in p roc ed ure 262, word 1, field 13. In an NFAS arrang ement, G3V2 systems p op ulate the interfac e ID from the sig naling group form. DEFINITY systems also imp lement the p referred /exc lusive c od ep oint in the c hannel ID IE. The c hannel ID information element has a c od ep oint for information ind ic ating whether or not a c hannel is neg otiab le. These two c od ep oints are used to neg otiate a c all to another B c hannel when one is b usy or Call Type Type of Number Number Plan TAC national ISDN/telephony number plan int intl ISDN/telephony number plan fnpa national ISDN/telephony number plan hnpa national ISDN/telephony number plan iop intl ISDN/telephony number plan op national ISDN/telephony number plan svc national ISDN/telephony number plan natl national ISDN/telephony number plan unk unknown ISDN/telephony number plan aar national ISDN/telephony number plan iaar intl ISDN/telephony number plan uaar unknown ISDN/telephony number plan
DEFINITY Communications System Generic 2.2 and Generic 3 V2 DS1/CEPT1/ISDN PRI Reference 555-025-107 Issue 1 July 1993 Layers 2 and 3 Page 5-32 ISDN PRI Layer 3 5 unavailable. In all DEFINITY systems, only c alls on DCS trunk g roup s are c od ed as exc lusive. All others are c oded as preferred. NOTE: For d etails of how c hannel neg otiation works in g lare situations, see the sec tion ‘‘User-Network and Peer Protoc ols’’ earlier in this chapter. The c hannel numb er c od ep oint in the c hannel ID IE id entifies the timeslot the B c hannel for the c all oc c up ies on the interfac e. The c irc uit assig nments in trunk g roup ad ministration map the c irc uit numb er to the timeslot. Thus, on a FAS DS1 interfac e, c irc uits 1-23 c orresp ond to timeslots 1-23. On an NFAS DS1 interfac e, c irc uits 1-24 map to timeslots 1-24. On a FAS CEPT1 interfac e, c irc uits 1-15 map to timeslots 1-15 and c irc uits 17-31 map to timeslots 17-31. On an NFAS CEPT1 interfac e, c irc uits 1-31 map to timeslots 1-31. For all c ountry p rotoc ol op tions exc ep t for op tion 2 (Australia) the value of the c hannel numb er in the c hannel ID IE is the timeslot numb er. In c ountry p rotoc ol op tion 2 on a CEPT1 FAS interfac e, however, c hannel numb ers 1-15 map to timeslots 1-15 b ut c hannel numb ers 16-30 map to timeslots 17-31. This mapp ing is automatic ally c omp ensated for b y the c ountry p rotoc ol op tion 2 software. If you are using an ISDN trac ing tool to d iag nose a p roblem in c ountry op tion 2, however, you mig ht need to c onsid er this mapping. For further information on this sub jec t, see the sec tion ‘‘Fac ility-Assoc iated and Non-Fac ility Assoc iated Sig naling ’’ earlier in this c hap ter. Network Specific Facilities IE in U.S. The network sp ec ific fac ilities (NSF) IE, whic h at present is only used b y p ub lic network applications in the U.S., has the following purposes: nI t t e l ls t h e p u b l ic n e t w o rk s w i t c h , su c h a s t h e 4 ESS o r t h e 5 ESS, w h i c h servic e (suc h as Meg ac om servic e or Ac c unet Switc hed Dig ital Servic es) to ap p ly to the c all. The Facility Coding Value field in the NSF IE c arries this information. nIf the servic e is a p arameterized servic e, it tells the p ub lic network switc h what p arameters to ap p ly to the c all. Presently, WATS (outwats in the ad ministration forms and p roc ed ures) is the only parameterized servic e. Thus, WATS has a fac ility c od ing value, like the other servic es, b ut also has p arameters assoc iated with the servic e. These p arameters are the b and s ap p lied to the servic e. WATS c alls to two d ifferent loc ations mig ht b e c alls to two d ifferent WATS b and s, whic h would c ost d ifferent amounts. nIt tells the p ub lic network switc h, suc h as the 4ESS or DMS100, whic h network feature to ap p ly to the c all. The AT&T network distinguishes b etween servic es and features. The AT&T network features c urrently ap plying to DEFINITY systems are as follows: — C PN p re f e rre d . Th is f e a t u re t e l ls t h e 4 ESS t o s e n d t h e D EFI N I TY system the c alling p arty numb er in the CPN IE, if it is availab le. If it i s n o t a v a il a b l e , t h e 4 ESS s e n d s t h e b il li n g n u m b e r i n t h e C PN I E.
DEFINITY Communications System Generic 2.2 and Generic 3 V2 DS1/CEPT1/ISDN PRI Reference 555-025-107 Issue 1 July 1993 Layers 2 and 3 Page 5-33 ISDN PRI Layer 3 5 — B N p re f e r re d . Th i s f e a t u re t e ll s t h e 4 ESS t o s e n d t h e D EFI N I TY system the b illing numb er in the CPN IE, if it is available. If it is not a va il a b le , t h e 4 ESS s e n d s t h e c a lli n g p a r t y n u m b e r in t h e C PN I E. — C PN o n l y. Th is f e a t u re t e l ls t h e 4 ESS t o s e n d t h e D EFI N I TY s y st e m the c alling p arty numb er in the CPN IE, if it is availab le. If it is not a va il a b le , t h e 4 ESS d o e s n o t s e n d t h e C PN I E. — B N o n ly. Th i s f e a t u re t e ll s t h e 4 ESS t o s e n d t h e D EFI N I TY sy s t e m the b illing number in the CPN IE, if it is availab le. If it is not a va il a b le , t h e 4 ESS d o e s n o t s e n d t h e C PN I E. — Op erator. This feature ap p lies to c alls on trunk g roups c onnec ted to a loc al exc hang e ISDN switc h. If the op erator c od e is in the NSF on an outg oing c all to the LEC, the c aller will rec eive op erator servic e on the c all. — Presub sc rib ed c ommon c arrier op erator. This feature ap p lies to c alls on trunk g roup s c onnec ted to an interexc hang e c arriers ISDN switc h. If the p resub sc rib ed c ommon c arrier operator c od e is in the NSF on an outg oing c all to the toll switc h, the c aller will rec eive op erator servic e on the c all. — Call-assoc iated temp orary sig naling c onnec tion. If the c od e for C A- TSC i s in t h e N SF o n a n o u t g o i n g c a ll t o t h e 4 ESS, a C A- TSC will b e req uested for that D c hannel. nIt tells the loc al exc hang e switc h whic h interexc hang e c arrier to route the c all to (AT&T etc .). This information is c arried in the Network Identification field in the NSF. nOn inc oming c alls to G3V2 systems on call-b y-call servic e selection trunks, it tells the system what typ e of servic e the c all is so that the inc oming c all hand ling tab le c an treat it c orrec tly. G2.2 systems p op ulate the NSF in p roc ed ure 318. The G3V2 systems p op ulate the NSF in the routing pattern form. For example, if a p referenc e is ad ministered for accunet , c alls routed to that p referenc e will have the value 00110 p ut into the Facility Coding Value field in the NSF IE. G2.2 Implementation In the G2.2, you must d efine the NSFs in p roc edure 279, word 1. This ad ministration sup p lies the fac ility c od ing value p ortion of the NSF IE. To ad minister the network id entific ation, you must, for eac h ISDN send ing ind ex, b uild the network id entific ation, c alled the IXC in DEFINITY terminolog y, in p roc ed ure 321, word 1, field s 7 throug h 11. If field 7 is a 2 or 3 , then the IXC assig ned in field s 8 throug h 11 will b e used to p op ulate the network id entifier in the NSF. The c omp lete NSF is then assig ned to a p referenc e in proc ed ure 318, word 1, field 9, whic h is the ISDN send ing ind ex c orrespond ing to the d esired NSF for that p referenc e.
DEFINITY Communications System Generic 2.2 and Generic 3 V2 DS1/CEPT1/ISDN PRI Reference 555-025-107 Issue 1 July 1993 Layers 2 and 3 Page 5-34 ISDN PRI Layer 3 5 G3V2 Implementation G3V2 systems use the following forms and other system p arameters to p op ulate the NSF IE: nRouting pattern form nInc oming c all hand ling tab le in the trunk g roup form nUsag e alloc ation p lan in the trunk g roup form nNetwork fac ilities form NSF Implementation in the Routing Pattern Form. The following list desc ribes how the NSF relates to setting s in the routing p attern form: nFor eac h ISDN PRI p referenc e in a routing p attern, you c an enter the IXC for the interexc hang e c arrier that is c arrying the c all. This p op ulates the network id entific ation c od ep oint of the NSF IE. If the trunk g roup c onnec ts d irec tly to an IXCs switc h, the IXC is not need ed . If the trunk g roup is c onnec ted to a LEC switc h, however, and the c all will eventually b e switc hed to an IXCs switc h, the IXC information will tell the intermed iate switc h to route the c all to the ap p ropriate c arrier. nFor eac h ISDN PRI p referenc e in a routing p attern, you must enter the mnemonic for the servic e that will use that trunk g roup if it is a c all b y c all trunk g roup . This p op ulates the fac ility c od ing value c odep oint in the NSF IE for outg oing c alls over that trunk g roup . If you do not enter the servic e, the fac ility c od ing value in the NSF will not be p opulated . For trunk group s d edic ated to a servic e, this is usually no p roblem b ec ause the NSF is automatic ally p op ulated . For c all b y c all trunk g roup s, however, the NSF must be populated correctly because the trunk group can carry calls of d iffering servic es. The list of valid servic es for this field c an b e found b y d isp laying the network fac ilities form. nIf the servic e/feature mnemonic is outwats-b nd, you must also ad minister the b and numb er (0-255) for the c all. NSF Implementation in the Incoming Call Handling Table. For calls incoming on ISDN PRI trunk g roup s, the system uses the NSF IE to id entify the servic e so that the c all c an b e treated in the inc oming c all hand ling tab le in the trunk g roup form. The mnemonic id entifying the NSF is ad ministered for eac h typ e of servic e that c an be inc oming on the trunk group . When a c all c omes in on that trunk g roup and its NSF matc hes the ad ministered value, that c all is treated in the way d efined on that row of the table. For examp le, an inc oming Meg ac om 800 c all to a g iven rang e of extensions c ould b e routed to a telemarketing ap p lic ation. This tab le ob viously has its g reatest ap p lic ation in c all-b y-c all trunk g roup s. If the servic e typ e of the trunk g roup is not c b c and sp ec ial treatment of c alls on that trunk g roup is not req uired , the tab le d oes not have to b e ad ministered . If you want sp ec ial treatment for c alls on d ed ic ated trunk g roup s, however, you must enter the servic e/feature.