Page 1210 of 1814 MCDN End to End Transparency553-2901-301 Standard 9.00 January 2002Feature interactions with NMS-MC using the QSIG transportInteractions specific to NMS-MC using the QSIG transport are discussed inthe following section. Refer toNetwork ACD: Description and Operation(553-3671-120) for information on generic NACD feature interactions.NACD and NAS encapsulation within QSIGFor ACD and attendant Message Centers that are NACD or NAS, the ACDagents and attendants may reside at different nodes. With packagingrequirements satisfied at the node where the MC call is presented, either theNACD agents or the NAS attendants are treated as a Message Center.If the Message Center is an attendant, the NMS-MC feature operationremains the same as for a simple NMS-MC set. If the attendant NMS-MC hasa specific ICI key defined, when a message Waiting call terminates to theattendant NMC-MC, the ICI lamp changes to lit to indicate a NMS-MC call.As for MCDN, it is not recommended to use NACD or NAS as a NMS-MCunless the message data base can be made available to all agents or attendantsat different nodes.Feature packagingMEET requires these packages:• Multi-purpose Serial Data Link (MSDL) package 222• QM reference signaling point Interface (QSIG) package 263• QSIG Generic Functional protocol (QSIGGF) package 305• MCDN End to End Transparency (MEET) package 348Depending on the application, other packages are also required.For the QSIG ISDN PRI interface, the following packages are also required:• ISDN Signaling (ISDN) package 145• Advanced ISDN Network Services (NTWK) package 148• 1.5 Mb Primary Rate Access (PRA) package 146, or• 2.0 Mb Primary Rate Interface (PRI2) package 154, or• International Primary Rate Interface (IPRA) package 202
