NEC SL2100 Communication SystemQuick Install Guide – SL2100 SLNet rev1.0 9Conditions1. SLNet is not supported through NAT, only Point-to-Point connection such as a VPN, MPLS, or otherPoint-to-Point circuit.2. SLNet is only for networking SL2100 systems together.3. Hold, Transfer, and Park recall timers will follow the timer of the system where the call is on hold (Trunkand Station). For example, a user in Site A calls a user in Site B. Site B answers the call and places thecall on hold. The hold recall time is based on Site A because the call on hold is in Site A and not site B.4. The allowing or denying of Class of Service features in an SLNet Network must be performed networkwide. For example, if users in Class of Service 1 at site 1 want to block the Camp On feature a changewill have to be made in Class of Service 1 of all systems in the network.5. When a terminal or trunk is placed on hold, the Music on Hold comes from the system where theterminal or trunk resides.6. When Multiple Voice Mails are installed in the network, each site must have a unique Voice Mail pilotnumber. The pilot number assigned must be within the routable extension number range in all sitesthroughout the network.7. When each site has its own Voice Mail system, a user in one location cannot call the Voice Mail pilotnumber that resides in another system.8. When each site has its own Voice Mail system, a Voice Mail Message Line key (Program 15-07 : key 77)cannot be programmed for an extension in a Remote system.9. Virtual Loopback trunks are not supported across SLNet10. SMDR information is collected in the system where the trunk resides. If a user in Site A accesses a COtrunk out of Site B, this call is reported in Site B's SMDR and not in Site A's SMDR.11. When a networked internal call forwards to Voice Mail (Centralized or Individual Voice Mail) the user willnot be able to perform any dialing options to dial out of the mailbox. The associated dial action tablecannot be accessed unless the call originates from a CO trunk12. Built-in Automated Attendant and Centralized Voice Mail cannot be used in the same system13. Calls (Intercom or Trunk) routed across the SLNet network cannot be answered by the Built-InAutomated Attendant14. Directory Dialing will not list extension numbers in remote SLNet systems15. An operator extension (Program 20-17) cannot be assigned to an extension in a Remote SLNet system.The operator for each site must reside in their own local system16. Mobile Extension is not supported for calls across the SLNet network17. When transferring a caller to a remote SLNet extension via the press of a DSS key on a 60 button DSSconsole, without pressing Transfer first, you must press the DSS key twice to complete the transfer.