1. RPC as Client/Server Framework

2. What is it? Takes care the protocol nastiness, don’t spend your time to create yet another protocol layer. Well established technology Comes from SUN Unix MS Exchange/Outlook and TAPI are based on this Meant to be used for Client/Server architecture Essentially the client runs a procedure or function on the server Works with Windows, Linux and Unix based systems

3. Where could this be used? Virtualization systems – Bunch of virtual clients can communicate to the server which drives the PIKA driver. Windows application could run the Warp as if it was part of it’s system Multi-application access Cloud Resources – Bunch of PCs with PIKA Driver can be seen as just another resource in the system – May provides load balancing between nodes – Nodes can run a thin layer to communicate with main application The Main Application can be used to communicate with different server versions. – AOB/MC 6.5, MC 6.6, etc. – AOH GP 2.6, GP 2.7

4. Benefits Better redundancy failover – 1 active app, others can be on stanby Isolates application from server malfunction – Can continue working and restart gracefully Platform agnostic (OS, AOB, AOH, other vendors) Scalable – Add/remove servers dynamically

5. Cloud resource diagram Application Node

6. Conference recording case CallerApplication Incoming Call Node Resource Callee Transfer call to new node and Establish call with recording to Callee Incoming Caller leg transferred to node resource Database Request for call transfer Make Call Establish conference call and record Record Call Disconnect Call Stop recording Relinquish resources