Once thought impossible is now quite possible with R3 (and higher) in the SV8100. We all know (or should know) that the internal and external page codes were available to be used over CCIS (See P2P CCIS Cheat sheet ).The Combined Paging code was never available until now with this little work around using CM 10-42. Please note that this is not offically supported by NEC as of yet.
This is available for both IP and traditioanl T1 CCIS.
Click here for app note.

So the salesman sold a couple of those cheap 2 button non-display IP phones to the customer for lobby and break room locations. You need to hard configure these phones cause no one will be logging in at them and you’d also like to make sure they work. So how do you manually configure an IP Phone that does not have a display????? Click here to see how.

Here is what I call my Mini-Manual as its too long to be called a Cheat Sheet. Basic CCIS programming so you can connect to any other NEC system that supports Peer 2 Peer CCIS. This includes other SV8100’s and SV8300, NEAX IPS, NEAX IPX, SV8500, and SV7000. Also included are instructions on how to program a bunch of CCIS features commonly used in a CCIS network.
Click here for the cheat sheet.

The General Purpose Relays on the PGD adapters allow you to control external devices off the SV8100 by pushing a feature key on a digital station. Typically the PGD will control a slave relay which in turn controls the larger device (the PGD relay does not allow anything over 24VDC or 500mA).
Common uses include gate openers, security lighting and anything else that needs basic on/off control.
The sheet attached here provides the basics but was for a site where the owner of the system wanted to completely disable External Paging for short periods of time while he shot his TV commercials. By pressing the GPR button on the phone the external page outputs were disabled so that an amplified page would not interrupt the recording of the TV comercial.
here for the cheat sheet.

With the release of R3 there is also the NAT feature supported for IP Phones. It is NOT for CCIS or Netlink only the IP Phones.
In general NAT allows the customer to use there existing public IP address on there network to be shared with the 8100 for IP Phones that are connected across the internet at remote locations. Also with the R3 firmware in the IP phone NAPT can be used at the remote site allowing the 1 public IP address to be shared with one or multiple IP phones as well as toher network equipment.
here for the cheat sheet.

I hate that term twining. It sounds so Avaya. AAHHHH!. Anyway here is the way you go about setting up Mobile Extension to allow internal or trunk calls to a station to ring an off site number. In most cases this will be used with the call forward “Both” feature so the internal and off site number ring at the same time. With R3 and above the incoming caller ID can be passed out to the Mobile Extension as long as this is allowed by the carrier and also calls can forward back to the NEC VM rather than go to the off site VM (cell VM). here for the cheat sheet.