2650 Valley View Lane

Building 1, Suite 200

Dallas, TX 75234-6273

214.241.2151

(Statement of Work) (uMobility Deployment and Support)Document Name

2009 Varaha Systems, Inc. All Rights Reserved.

This document is the confidential property of Varaha Systems, Inc. No part of this document may be reproduced or transmitted in any form or by any means, electronic or otherwise, including photocopying, reprinting, scanning, or recording, for any purpose, without the express written permission of Varaha Systems, Inc.

Trademarks

uMobility is a trademark of Varaha Systems, Inc. All other company, brand, product or service names mentioned herein are the trademarks or registered trademarks of their respective owners.

Disclaimer

Information in this document is subject to change without notice and should not be construed as a commitment on the part of Varaha Systems, Inc. Varaha Systems, Inc. does not assume any responsibility or make any warranty against errors that may appear in this document.

Varaha Systems, Incorporated

2650 Valley View LaneBuilding 1, Suite 200Dallas, Texas 75234

Tel: +1-972-241-2151Fax: +1-972-243-1505E-mail: info@varaha.comVisit us at: http://www.varaha.com

Change History

Date

Rev.

Change Author

Summary of Change

Approved (Yes/No)

Xx/xx/xx

1.0

Table of Contents

1Statement of Work for 5

1.1Introduction5

1.2Project Summary5

1.2.1The Solution: uMobility6

1.2.2Solution Components6

1.2.3uMobility Functionality13

1.2.4uMobility End User Call Features14

1.2.5uMobility End User Mobility Features16

1.3Project Scheduling17

1.4Review and Planning17

1.4.1Software Licensed.17

1.4.2Software License(s)18

1.4.3Deployment Checklist and Documentation18

1.4.4Resource requirements, Task assignments19

1.5Solution Design19

1.5.1Kick off the project19

1.5.2Review IP-Telephony network/topology19

1.5.3Identify server hardware20

1.5.4Identify uMobility Topology21

Supported Third Party switches21

1.5.5Smart Phone Requirements25

1.6Implementation25

1.6.1Verify Site Survey Information26

1.6.2Hardware Installation and Commissioning26

1.6.3Install CentOS26

1.6.4Install uMC software27

1.6.5Configure uMC27

1.6.6Configure Softswitch or PBX27

1.6.7Test and Acceptance Plan Execution27

1.6.8User Provisioning27

1.6.9Test Acceptance Plan (TAP) Execution28

1.7Normal Operation Handover28

1.7.1Deliver documentation28

1.7.2Train administrator28

1.7.3Train users29

2Pricing30

2.1Assumptions and Limitations30

2.2Completion of Services31

2.3Agreement between and the Enterprise32

3Appendix A – service responsibilities33

Phase 1: Acceptance of SOW33

Phase 2: Solution Design33

Phase 3: Implementation & Cutover34

Phase 4: Project Acceptance36

4Appendix B : Related forms37

4.1Site Locations and Contact Information37

4.2Services Completion Checklist – PSID# uMobility Deployment37

5Appendix C – Change Request Form39

Statement of Work for

This Statement of Work (SOW) outlines the responsibilities, deliverables and acceptance criteria for the services that the vendor will perform for (“Customer”) as it pertains to (“End User”). This is described below in the Project Summary. Four appendices are included:

Appendix A – Service Responsibilities

Appendix B – Related Forms

Appendix C – Change Request Form

Introduction

Here, the product on offer is a comprehensive Fixed Mobile Convergence (FMC) solution – uMobility for businesses and ties the critical business processes to mobiles. Patented uMobility technology is unique in supporting both voice, data and business process integration, convergence infrastructure today. It is a deployable solution by wireless, wireline and enterprise customers independent of wireless carriers. uMobility solution increases productivity, visibility and cost control while providing one number, one login on one device with better speed, coverage and reach.

Project Summary

Businesses worldwide are looking to leverage alternate access such as Wi-Fi or 3G data networks for cost savings, offloading traffic, increasing in-building coverage at low cost and provide better user experience.

Numerous point solutions have emerged promoting collaboration and “unified communications”, but these solutions increase expenses and complexities while often preventing the fastest, most reliable form of communication – voice - from occurring, resulting in business process delays.

Forrester study of internal communication challenges at 67 enterprises discovered that business process delays occur with high frequency because of the frequent inability to quickly reach decision makers. In 27% of the companies surveyed, regular delays occurred weekly or daily, while an additional 51% reported project delays arising a few times per quarter. Most notably, work on critical projects came to a halt in 25 percent of the companies surveyed because decision makers could not be reached.

Clearly, the ability to reach co-workers and customers has a direct impact on costs, customer care/satisfaction and an organization’s overall success in terms of revenue and profitability.

The Solution: uMobility

uMobility addresses the need for better coverage, off loading, and business communication integration with potential spectrum usage and cost savings, to minimize business process delays and to increase productivity when employees use a cell phone at the office or at home.

uMobility lets employees make/receive IP-PBX or Hosted PBX phone calls directly from their smart phone while improving cell phone coverage inside buildings. The solution converts in-building cell phone calls to Voice over IP (VoIP) and routes the calls over the in-building Wi-Fi network, providing several compelling benefits:

· No cellular minutes is used when a cell phone is used with uMobility at the office or home, so typically 30% - 50% less cell minutes are used each month.

· International travelers can experience substantial cost savings using uMobility to bypass expensive foreign cellular networks via Wi-Fi connectivity providing better revenue opportunity to mobile operator.

· The quality of cell phone conversations is improved because the in-building Wi-Fi signal is considerably stronger than the external cellular network signal.

· As the business number also now becomes available on the cellular phone, additional data traffic related to business processes can be driven over cellular data and Wi-Fi access while off loaded to generate additional revenue.

Solution Components

uMobility is a software solution that consists of two primary components: the uMobility Controller (uMC) and the uMobility smart phone client.

The uMC is the heart of the system. It resides at the service provider facilities and communicates with the IP-PBX/softswitch over the LAN or WAN. The uMC also communicates with the uMobility smart phone client (which is installed on end-user smart phones) over Wi-Fi and cellular networks.

uMobility continuously monitors both the Wi-Fi and cellular networks and lets users move seamlessly back-and-forth between the networks when they are talking on their smart phone. When users initiate a call from their smart phone, they can decide if callers will see their enterprise number (or home number, depending on the type of uMobility service) or their native cell phone number.

Likewise, when people dial an uMobility user’s office (or home) number, uMobility makes sure that the call rings the user’s smart phone – no matter where the user is located.

uMobility works with single mode (cellular only) and dual mode (cellular and Wi-Fi) smart phones. The solution works independently of the user’s physical location.

uMobility Controller (uMC)

The uMC is software that runs on inexpensive, off-the-shelf Intel server hardware. Appendix A contains the uMC hardware requirements.

Administration software (uMobility, Operations and Metrics or uMOM) provides an end user interface to the uMC. The uMOM allows the System Administrator (SysAdmin) to perform all necessary OAM&P (Operations, Administration, Maintenance and Provisioning) functions for the uMobility solution.

In an enterprise configuration, the uMC resides in the enterprise network and communicates with the IP-PBX via the industry-standard Session Initiation Protocol (SIP). The system is typically maintained by the PBX administrator or an enterprise IT professional. The enterprise Wi-Fi network routers and Access Points (AP) must be provisioned and deployed for voice services to ensure maximum performance.

uMC Enterprise Configuration

For smaller deployments, a standard Intel Pentium 4 (or Xeon) processor in a 1U configuration is recommended. For larger deployments, a Linux BladeServer cluster is required. Sample specification with salient attributes is given in the table below.

(Over 10K users) (Under 10K users)

Processor

X86 processor (e.g. Pentium 4, Xeon, or AMDxxx) running at least 2.5 GHz

Hard Disk Space

100 GB

RAM

4 GB

Network Interface Card

At least 1 GbE for systems larger than 25 users

Operating System

Linux - CentOS 5.4

uMobility Smart Phone Client

The uMobility smart phone client is client application software that runs on a number of popular smart phones, such as devices from Apple, BlackBerry, Android, Windows Phone and Nokia/Symbian. The software provides the end user interface between the smart phone and the uMC. Communication between the client and uMC is via SIP. Appendix A contains the client hardware requirements and technical specifications for the client software.

After the end user is provisioned in the uMobility uMC, an email or SMS message is sent to the user’s smart phone with a link to install the software. The user simply clicks on the link provided and the client software is automatically installed on the user’s cell phone “over the air”.

Apple (iPhone, iPod Touch, iPad)

The Apple device client software for uMobility runs on every Apple device available (except the iPod Touch 1st generation, which has no port for a headset). The client software is an application that takes full advantage of the iOS4’s ability to provide background processing; this means that while in a valid Wi-Fi network, inbound calls to the uMobility number will be answered via the uMobility client software over Wi-Fi, providing better in-building coverage upon answering the inbound call.

The Panel Menu across the bottom provides access to Options, Call Logs, the iPhone’s Contacts, the Keypad and one touch dialing of the voice mailbox.

The top of the screen provides the user information on the status of the application (e.g., Registered means the client has successfully registered with the uMobility Controller in the IT of service providers’ network).

Research in Motion BlackBerry

The uMobility client software works on a number of dual mode BlackBerry models that work on the GSM network. The uMobility client, upon the user’s direction, takes over the phone function of the device, allowing uMobility the opportunity to provide service over the best network available no matter where the user is at the time.

Android

Android is the name of the smart phone operating system provided by Google. A number of manufacturers (e.g., Motorola, LG, Samsung, and HTC) make devices based upon the Android OS. uMobility actually uses the native dialer of the Android device, allowing the user interface to appear the same for cellular as well as uMobility calls. For uMobility calls, the uMobility smart phone application grabs the dialed digits and routes them to the appropriate network for processing.

Windows Mobile

The Windows Mobile client provides an attractive Graphical User Interface (GUI) for the uMobility end user. Option Tabs along the bottom of the screen let the user quickly move between major features, while large, easy-to-read buttons provide access to commonly-used phone functions.

(Message Waiting Indicator) (Dial Pad) (3 Line Text Display AreaAnswer/Call ButtonuMobility Network Selector/Indicator ButtonCellular Network Selector/Indicator ButtonBackspace ButtonRelease (End Call) ButtonuMobility Option TabsuMobility Call MenuDial PaduMobility File MenuKeyboardMinimize ButtonBluetooth Hands-Free ConnectionuMobility User NameMissed Call IndicatorDial PadAnswer/Call Button)

Symbian/Nokia

The uMobility Symbian/Nokia client runs on most Nokia smart phones. The Symbian client uses the native Symbian/Nokia user interface so there is no “learning curve” for an end user to learn how to use the client – uMobility calls are made and received the exact same way as standard cellular calls.

A handy indicator is displayed along the top of the screen to let the end user know if the current network being used by uMobility is the Wi-Fi ( ) or cellular () network. A message waiting indicator is also displayed when new voice mail is received to provide quick access to the office voice mail system.

(Message Waiting Indicator) (Network Indicator)

Virtual Private Networks (VPN)

uMobility works with the VPN client software provided by the respective phone manufacture. If the business uses a VPN aggregator from any popular manufacture (e.g., Cisco, Nortel, Juniper, etc.), once that VPN connection is established back to the home office, the uMobility client software will use that secure tunnel for all traffic, from initial registration to the end of the call.

uMobility Functionality

Basic Dialing

Consider a call that originates from the uMobility-enabled smart phone in the cellular domain. For example, a uMobility user is driving in the car on the way to the office and originates a call from the smart phone.

When the desired number is dialed, the uMobility client communicates with the uMC which in turn communicates with the office IP-PBX/softswitch to set up the call. The uMC then instructs the IP-PBX /softswitch to dial the called number. The number is dialed and the called party sees the caller’s office number as the incoming Caller ID.

Let’s continue this scenario and assume that the call is still in progress as the uMobility user parks the car and walks toward the office building. The client software is always searching for, and communicating with, any Wi-Fi APs that have been pre-registered (trusted) with the uMobility client. This is done to determine if the Wi-Fi signal strength and other parameters are suitable for quality voice communications over the Wi-Fi network.

If the Wi-Fi signal is poor at the user’s smart phone, then the call is kept in the cellular domain. But now, let’s assume that the user has walked within range of the office Wi-Fi network and the uMC determines that the Wi-Fi quality is strong enough to handle the call. The uMC works with the IP-PBX/softswitch to instantly “hand-off” the call from the cellular domain to the Wi-Fi network. The call remains anchored at the IP-PBX/softswitch and the uMC has done its job by handing off (HO) the call from the cellular network to the enterprise Wi-Fi network.

The uMC does one more important job. As the user enters the office and walks around the building, the UMC keeps a diligent watch and may hand off the call back to the cellular network if Wi-Fi coverage becomes insufficient, to ensure the call stays connected and with high voice quality.

Interaction with the IP-PBX/Softswitch

The uMC communicates with the IP-PBX/softswitch via SIP. Both line side and trunk side SIP configurations are supported. If carrier as IMS deployed, uMobility can also communicate with CSCF over SIP. In the absence of IMS deployment, uMobility connects with the cellular network over POTS interface(s).

The importance of the uMobility line-side implementation cannot be overemphasized. The line-side implementation allows seamless delivery of IP-PBX/softswitch features directly to the end user’s smart phone, including MWI (Message Waiting Indicator).

uMobility also leverages existing dialing plans, voice mail, and other features of the IP-PBX/softswitch to extend those features to the smart phone. For example, users can 4-digit dial co-workers from their smart phone and they can also be reached on their smart phone via 4-digit dialing – anytime, anywhere regardless if the network of choice is Wi-Fi or cellular.

An important concept to understand is that when uMobility is running, all calls to and from the smart phone are always controlled by the IP-PBX/softswitch. However, the uMC is also in the signaling path of the calls to offer specific uMobility features such as single-number reach, network hand-off, device mobility, etc. A summary of uMobility features is provided in the section entitled uMobility End User Features.

uMC Standards Compliance

• SIP RFC 3261

• SIP Event Notification – RFC 3266

• SIP Info – RFC 2976

• SIP RFC 3455 – Private Header (P-Header) Extensions to the Session Initiation Protocol for the 3rd-Generation Partnership Project (3GPP)

In general, uMobility can be deployed in various configurations depending on the network topology, number of users, desired capacity, number of PBX/softswitches, and end-user partitioning. For example, consideration for the following is required:

· Single country or multiple countries

· Single or multiple site

· Simplex or redundant

· Number of PBX/Softswitches to be supported and per uMobility Controller

· Number of users based on the hardware selected

· uMC deployed in public or private network

· uMobility to work with/without VPN

Interaction with Wi-Fi and Cellular Networks

With uMobility, users are free to move virtually anywhere while they are talking on their cell phone. uMobility automatically ensures that the best available network signal - Wi-Fi or cellular - is always used so the call will continue uninterrupted, no matter where the user is located.

When a Wi-Fi network is used inside a building, the voice quality will be better because the Wi-Fi signal is typically much stronger inside a building compared to the comparable cellular network signal. Also, with a Wi-Fi network, no cell phone plan minutes are used because the signal is converted to VoIP at the smart phone.

uMobility always automatically tries to use a properly configured Wi-Fi network for communication. If the Wi-Fi network is unavailable, then the cellular network is automatically selected. Either way, uMobility monitors both networks, displaying the status of each.

Being able to manually select a network allows end users to make a call using their office telephone number or their native cell phone number. For example, when calling a family member, a user may want to manually select the cellular network (even if they are in a strong Wi-Fi zone) so that the called party will see the caller’s familiar cell phone number when they receive the call. Alternately, if calling a business contact, users will probably want to use their uMobility number. See the next section for more on the uMobility feature Preferred Call Routing to learn more about this capability.

uMobility End User Call Features

This section outlines some of the many IP PBX or softswitch features that can be delivered to the smart phone with the uMobility solution.

Call History

Users can access their call history from uMobility. This feature displays a list of received, dialed and missed calls. Users can re-dial any number from the call history list.

Call Hold

During a conversation, a call may be placed on hold. While a call is on hold, the user may set-up a conference call (depending on the capabilities of the cellular provider or PBX/softswitch), transfer the call to another party or call another party.

Call Transfer

The Call Transfer feature lets a user perform a blind or announced transfer to another internal extension or external number. This feature is dependent upon the IP PBX providing the feature.

Call Waiting

The Call Waiting feature notifies users of a new, incoming call when a call is already in progress.

Consultation Hold

This feature lets a user dial another number after a call is in progress. When the other number is dialed, the current call is automatically placed on hold.

Contact Dialing

The Contact Dialing features lets users dial a contact directly from the smart phone’s contact list.

Do Not Disturb (DND)

This feature lets users forward all their incoming calls to voice mail. When this feature is on, the smart phone will not ring when a call is received and the call will immediately go to voice mail. This feature can even be set during a call so that the active call will not be disturbed.

Extension Dialing

This uMobility feature lets users call co-workers anytime, anywhere from their smart phone by simply dialing their four-digit extension (or whatever number of digits is supported by the associated PBX/softswitch).

Last Number Redial

This feature lets users instantly re-dial the last number they dialed.

Voice Mail

uMobility provides direct access to the IP-PBX/softswitch voice mail system from the user’s smart phone. Similarly a message waiting indicator is displayed on uMobility when a message is left at the PBX number.

Message Waiting Indicator (MWI)

This feature displays a mailbox icon on the smart phone to indicate to the user that a new voice mail message has been received. With a data plan from the cellular provider, MWI can be delivered via the cellular network for messages waiting back at the home office’s voice mail system.

Missed Call Indication

uMobility provides on-screen indication of missed calls and allows users to quickly access and dial the phone number that is associated with a missed call.

Selective Network Dialing

When a user makes a call, they can use this feature to either dial the number using their cell phone caller ID or their uMobility (office or home) caller ID. For example, a doctor can return a call to a patient from his/her cell phone while out of the office using the uMobility (office) number without having to expose his/her personal cell phone number to the patient.

Speed Dialing

This feature lets users dial an entire number (or sequence of numbers) by simply tapping a single digit on the smart phone.

Shared Line Appearances

This feature lets an incoming call (e.g., a call to the main business number or support number) simultaneously ring a uMobility-enabled smart phone along with the desk or home phone. This feature is obtained from the call control node (PBX or soft switch) in the network.

uMobility End User Mobility Features

Best Network Choice - Hand-Offs

uMobility monitors both the cellular and Wi-Fi networks and allows users to move back-and-forth between the networks when they are talking on their smart phone without interrupting the conversation and without requiring any action or decision on the user’s part. uMobility automatically selects the best network for high-quality voice communication. uMobility does not require each Wi-Fi access point to be manually configured for network hand-offs and the Wi-Fi network does not have to environment-mapped (which typically, is a time-consuming exercise).

Single Number Reach (SNR)

Some users, in particular highly-mobile sales people, prefer to have one phone and one voice mailbox versus trying to juggle between several devices and several voice mailboxes while on the road. The uMobility Single Number Reach (SNR) feature lets users assign their office phone number (or home phone number, depending on the type of uMobility service) to their smart phone to ensure that they can be reached anytime, anywhere via onenumber.

Dual Number Privacy

uMobility lets users have two numbers on their smart phone: the native cellular number and the uMobility number. This provides users with the flexibility to give out their native cell phone number to friends and family and only use their uMobility (office) number to their business contacts. This feature is excellent for professionals who do not want to give out their personal cell phone number to anyone outside their circle of friends and family. For example, clients or office staff can dial the office number to reach the employee’s cell phone, while friends and family can reach the same device via the personal cell phone number.

Preferred Call Routing

Preferred Call Routing (PCR) allows the user to tag a phone number to determine which phone number (personality) to use every time with that number. An example would be a worker and their spouse each having cellular service from the same provider. There is no point taking a call between spouses across the enterprise network when using the cellular network make this type of call free. A number tagged through PCR is recognized by the client software and is placed over the cellular network every time without further instruction from the user.

Device Mobility

Device Mobility is a uMobility feature that lets users move the current, active call from the smart phone to their office phone (or other device), without interrupting the conversation. This powerful feature also lets users fetch the call back to the smart phone, if desired.

Campus Alert

This feature allows the SysAdmin to send a message to a sub-set or the entire uMobility user community and anyone else desired that is provisioned on the system. The SysAdmin types in the text string (e.g., “Storm warning, stay in the building under further notice”) and with one keystroke sends the message to be received on the uMobility-enabled smart phones as well as those user who are not smart phone users via their email accounts or SMS to standard cellular phones. This feature is available for an addition charge and is part of the MESA (Mobile Environment Services Architecture) family of applications.

Presence

Presence allows the user to set up Buddy Lists of uMobility users and get and have their respective status displayed on their buddy list phones. This feature makes it easier to know how best to reach a person based upon their present status and location. This feature is available for an addition charge and is part of the MESA (Mobile Environment Services Architecture) family of applications.

Device Power Management

uMobility includes patent-pending power management software that automatically turns Wi-Fi or the cellular radio signal on/off, as needed, to communicate. This feature extends the smart phone battery life between charges. This feature is only required in WM smartphones.

Project Scheduling

This project is scheduled to start (TBD), with the anticipated Completion Date (“Completion Date”) of (TBD). For purposes of this SOW, the project shall be deemed complete when the enterprise has completed the services as described in Services Description and fulfilled its obligations as specifically set forth in Appendix A (Responsibilities) and the system is functioning substantially in accordance with manufacturer’s published specifications for the newly purchased functionality.

Review and Planning

Review the overall project for all the following:

Software Licensed.

· uMobility Controller software and support software.

· uMobility Client software that operates in conjunction with the uMobility Controller software as listed in the Application note on uMobility supported devices published from time to time but no later than quarterly basis with updates.

Both software items are provided as Executable code. Typically the software download links are sent to the customer with the licenses and access to operations and support portal that includes secure login credentials and directions to use the portal. If the customer does not have access to the portal and if it is required then it can be given at this time as well.

Software License(s)

You should receive licenses for deployment upon commercial agreement and issuance of the purchase order. The licenses should be perpetual after purchase with support renewal period as per your contract.

Deployment Checklist and Documentation

Below is the checklist that the customer or uMobility supplier is recommended to fill out to begin the actual installation of the product. The checklist can be modified or included as part of the project plan as necessary. The devices chosen for deployment should be procured as necessary. It is recommended that a check of the current version of firmware is done on the device and upgrade, if uMobility supports newer version.

Item

Discussion

Completed/Open

Introductions

Who are the key resources such as project manager, marketing, testers, IT, System Admin resources, etc.

Review Customer Portal

Document repository for customer to gain UG, technical guides, etc.

Review Operations Portal

Enter problem reports; upload log files from test results, etc.

3rd party software

If the customer needs access to server OS (CENTOS), advise customer to obtain software from Third Party Site.,

FTP site information

FTP site for uMC software and related clients can be reached by clicking on the following link.

Project Plan

Provide and review project plan boilerplate; intent is that customer will update and return to enterprise to drive resource and scheduling on both sides.

Review Site Survey

Make sure network diagram, phones, numbering plan, port availability (SBC) etc. are reviewed, understood and configuration changes are planned for deployment by the customer.

Test and Acceptance Plan (TAP)

Review TAP and ask customer if there are additional requirements for specific changes/tests at this time or if another meeting is required to obtain input.

Debugging Support

Method and procedure review for identified bugs, response times, contacts and escalation procedures.

TAC Support Group contact Information

Besides the operations Portal… The TAC can be reached via email at Support@varaha.com. The email will be received by TAC Support group where a Support Engineer will respond to the request. Support can also be contacted directly 24/7 by calling the Support number at 972.755.1855.

After the review the deployment project plan and milestones are mutually agreed by the parties. The project plan and milestones template is included by reference herein. The project plan may not be fully completed by the time planning stage is complete but all the necessary information as listed in the Customer_Profile.xls should be obtained to minimize the delay on the start of the deployment.

Resource requirements, Task assignments

Also the key resources and contacts are identified and the following template is completed between the parties as part of the process.

The resource requirements and task assignments are included in the project plan included herein by reference. The file format is easily modifiable and serves as guidelines. The actual network should be evaluated for exact resource planning.

Solution DesignKick off the project

The project kickoff reviews the project plan sign off with all stakeholders and is chaired by a project manager.

The design phase involves collection and organization of network, user, desired devices and uMobility solution information as input to the procurement process, to complete the site survey which is used for uMobility configuration, and driving other operation processes such as requests for power, space and network access.

Review IP-Telephony network/topology

Review of current network topology and any planned changes to the network is required. The scope of the network should include all the locations or types of locations, that the end-customer is likely to operate from, as well as the network where the uMobility controller will be deployed.

This includes answering the following questions:

1. Is there a detailed network diagram with IP address, locations

2. What types of access are required by users?

a. What types of direct access are required?

i. From Public locations such as hot spots

ii. From Private, leased access such as end-customer premises

b. What types of network security are required?

c. Identify security protocols and devices.

d. What types of remote access by the enterprise, partner, and administrators are available?

3. Based on the access required, are there ports and access that must be requested?

a. Review uMobility deployment port details to ensure correct SBC/Firewall configuration.

4. Is there a managed Wi-Fi infrastructure available? Or, does the end-customer provide Wi-Fi service?

a. Gather Wi-Fi voice readiness details from your supplier.

5. What devices or end-points are to be supported?

The outcome of this review is:

1. Detailed network topology

2. Identification of use cases by the end-customer including types of access and resulting SBC/Firewall configuration.

a. Requests for network port access with corresponding entries in the project plan based on the uMobility deployment requirements and use case scenarios.

3. Identification of remote access of uMobility system by support personnel from Enterprise, Partner or administrator.

4. Requests for network access for concerned personnel with corresponding entries in the project plan

The review should be planned for duration of 1 day with appropriate follow up to complete the actions through conference calls.

Identify server hardware

Based on the number of subscribers, call profile and the network topology as provided by the customer, the class and capability of the hardware can be determined.

The outcome of this activity is:

1. Determination of the class of hardware and processing power required.

2. Based on customer desire or existing vendor relationship, selection of hardware models and options

3. Identification of space requirements and requests for the same with corresponding entries in the project plan

4. Identification of power requirements and requests for the same with corresponding entries in the project plan

5. Identification of hardware location and requests for the same with corresponding entries in the project plan

Dell R815 or equivalent for uMC for up to 1,000 users with 10% on an active call is highly recommended.

Identify uMobility TopologySupported Third Party switches

The following list indicates supported PBX Solutions and you need to make sure the switch you have is listed in here:

SOFT

SWITCH

Manufacturer

System

Trunk side

Line side

Broadsoft

Broadworks

X

Broadsoft

M6

X

Cedar point

Safari C3

Metaswitch

Metaswitch

Nortel

MCS 5200, CS2K

X (CS2K)

Taqua

MobileWorks

Veraz

Veraz

X

PBX

Asterisk

Asterisk

Avaya

CM/SES

X

Cisco

LinksysOne, CUCM

X

Mitel

3300

NEC

SV8100, SV8500

Nortel/ Avaya

BCM, MCS 5100, CS1K

Pingtel/ Nortel

SIPX

Toshiba

CIX

Vertical

Televantage,XIP, WAVE

X

Note that the complete switch functionality is not supported in the clients. Also there may be exceptions in the supported functionality based on the capability and connectivity of the switch as noted in the table. uMobility is also available with other switches and the functionality may vary with the IP-PBX. Please consult your supplier or concerned personnel to receive the functionality changes as applicable with your PBX.

The following are the features users can utilize with uMobility and SV8x00 series platform on the different device OS families.

Feature Name or Description

Nokia

Apple

Windows Phone

BlackBerry

Android

uMobility Features

Dual Mode Operations

(uMobility features and services in both Wi-Fi and Cellular Domain)

Yes

Yes

Yes

Yes

Yes

Handoff Operations (HO)

Yes

Yes (user managed handoff for Wi-Fi to Cell)

Yes

Yes

Yes

Single Number Reach (SNR)

Yes

Yes

Yes

Yes

Yes

Over-the-Air (OTA) Client Delivery

Over-the-Air (OTA) Configuration Delivery

Yes

Yes

No (Apple AppStore)

Yes

Yes

Yes

Yes

Yes

Yes

Yes

BASIC TELEPHONY

(PBX/CM dependent)

Enterprise Dialing (ED)

Yes

Yes

Yes

Yes

Yes

Call Forward All (CFA)

Yes

Yes

Yes

Yes

Yes

Call Forward Busy (CFB)

Yes

Yes

Yes

Yes

Yes

Call Forward No Answer (CFNA)

Yes

Yes

Yes

Yes

Yes

Call Hold and Resume

Yes

Yes

Yes

Yes

Yes

Call Waiting

Yes

Yes

Yes

Yes

Yes

uMobility enabled device can participate in conference call (cannot initiate conferencing functionality i.e., 3-way conference)

Yes

Yes

Yes

Yes

Yes

Calling Line Identification

(Calling Name)

Yes

Yes

Yes

Yes

Yes

Abbreviated extension dialing

Yes

Yes

Yes

Yes

Yes

Mid-call DTMF

Yes

Yes

Yes

Yes

Yes

Feature Name or Description

Nokia

Apple

Windows Phone

BlackBerry

Android

BASIC TELEPHONY

(Device dependent)

Speed dial

No

Yes

Yes

No (POR)

Yes

Missed call indication

Yes (both Wi-Fi and Cellular)

Yes in Wi-Fi

Yes (both Wi-Fi and Cellular)

Yes in (both Wi-Fi and Cellular)

Yes (both Wi-Fi and Cellular)

Call Logs

Yes

Yes

Yes

Yes

Yes

Contact Dialing

Yes

Yes

Yes

Yes

Yes

Mute/Unmute

Yes

Yes

Yes

Yes

Yes

Speakerphone

Yes

Yes

Yes

Yes

Yes

Volume Control

Yes

Yes

Yes

Yes

Yes

Do Not Disturb (DND)

Yes (both Wi-Fi and Cellular)

Yes in Wi-Fi

Yes (both Wi-Fi and Cellular)

Yes

Yes (both Wi-Fi and Cellular)

Bluetooth

Best Effort

No (POR)

Best Effort

No (POR)

Best Effort

PRESENTATION

(SV8x00 and Sphericall)

Blind Call Transfer

Yes

Yes

Yes

No (POR)

Yes

Consultative Call Transfer

No

No

No

No

No

Two Calls Per Line (Items are grayed – only available on Sphericall)

Yes

Yes

Yes

Yes

Yes

VOICEMAIL

Message Waiting Indicator (MWI)

Yes

(Cellular Data Network dependent)

Yes

(Cellular Data Network dependent)

Yes

(Cellular Data Network dependent)

Yes

(Cellular Data Network dependent)

Yes

(Cellular Data Network dependent)

The outcome of this activity is:

1. Network map from the previous section with the locations identified for the uMobility Controller deployments

a. With redundancy

b. IP connectivity and associated PBX/Softswitch

c. Identify space for the server hardware.

d. Identify power position for the server hardware.

e. Identify position in the network for uMC server – where it will be plugged into a switch/router.

f. Identify IP-Address(es) for the uMC server(s)

g. Identify uMC software release

Smart Phone Requirements

The customer is expected to review and capture the following information about the clients:

· Identify uMobility client release for each type of phone devices

· Capture device information for the client software if applicable

Apple

The Apple iPhone models supported are presently Generation 2 (3G), 3 (3G S) and iPhone 4 & 4S devices running the 4.0 operating system and higher. The iPod Touch, Generation 2 (e.g., headset jack) is supported running the 4.0 operating system or higher. The iPad is supported running 3.2 OS or higher.

Android

The Android phones are supported from a number of manufacturers, including Motorola, Samsung, LG and HTC. Particular models include the Hero, Fascinate, Incredible, Droid, Moment, etc. OS version 2.1 or higher is recommended for best performance.

BlackBerry

GSM models such as the Bold 9700, Bold 9000, Curve 8900, Curve 8520 and 9300 (OS7) are supported. Many cellular-only models (e.g., Curve 8300) can be supported in single mode (cellular) only.

Upon completion of planning any procurement and resourcing task should be completed before starting implementation.

uMobility also supports Nokia and WM 6.x clients. Inquire about the supported devices on these OSes.

Implementation

After the completion of planning phase and collection of pertinent information capture, it is recommended to review the details with Customer in a conference call to kick off implementation of uMobility. The remaining activities are performed by a skilled and certified enterprise personnel onsite with the assistance of the customer resources.

Verify Site Survey Information

The site survey is the document that is intended to capture all the above information necessary to efficiently deploy uMobility in your network.

The following is a description of the approach to collecting the information and the type of people that will be needed to collect the information for a successful installation of uMobility.

A review of the customer completed site survey based on the review of the site survey, Customer will:

1. Identify the appropriate uMC software release and document in the site survey

2. Identify the appropriate uMobility client release for each type of phone devices and document in the site survey

Hardware Installation and Commissioning

This document assumes that the customer has procured the hardware based on the specification provided as the result of the site survey and network design. The supplier has delivered and commissioned the hardware as per network connectivity specifications from the hardware supplier. The servers can be installed from the console or over the network.

Install CentOS

CentOS is a core version of Linux. The CentOS version is provided publicly. An image of the OS with required components on the public domain is available to all consumers. The links for the same are accessible from the uMobility Operations and Support portal.

The direction for OS installation is provided with the release software. The effort can take one day if hardware is installed and ready. Upon installation the acceptance test must include network connectivity and reachability testing to softswitch/PBX, firewall, DMZ nodes and internal applications servers. uMobility is tested on CENTOS 5.x,32-Bit OS.

Install uMC software

The order fulfillment will provide applicable uMobility Controller load with the releases of the client loads. The steps to install the software are provided with the software. This effort takes no longer than one day. A crafts person familiar with the LINUX or CentOS operating system can get the installation done in 4 hours or less. The installation procedure is given in the uMobility System Administration Guide.

Configure uMC

The uMC configuration includes installing valid license, configuring IP address, domain and other network information into the controller, configure and test the redundancy of the platform. The configuration steps are included in the uMobility System Administration Guide.

Configure Softswitch or PBX

You need to make sure that the uMobility users are first configured and active in the softswitch or PBX that you are connecting to from uMobility to provide calling services. The users should be configured on the SIP line side or trunk interface for the solution to work appropriately. If you are adding new users for uMobility then refer to the guide on how to provision or configure users on the PBX provided by your supplier.

You will also need to configure SIP trunk for displaying caller ID pass through for single number reach feature implementation. You may need to refer to the SIP trunk Configuration Guide for caller ID Pass through for actual procedure. For a craftsperson familiar with the call server this activity may take up to two (2) days to implement, configure and test the SIP trunk. Similarly, the customer may choose to connect to the call server over SIP trunk instead of SIP line interface. In such case the uMobility should be configured accordingly and the call server must be configured with the necessary SIP trunks.

uMobility will require additional SIP licenses as Reserve Users and defined in Huntgroup for providing FMC features.

Test and Acceptance Plan Execution

Add three users on uMC manually to test the uMobility installation first. Then refer to your finalized test and acceptance plan based on the provided Test and Acceptance (TAP) document. When the users are provisioning into the system, it automatically triggers the over-the-air software installation procedure. This will trigger software installation for the devices. The typical parameters needed to provision the users are described in the uMobility System Administration Guide.

First run the sanity check-list provided in the TAP document. Once the sanity check list is successfully executed then execute the test cases in the TAP document and clearly mark the observed behavior if it is different from the expected behavior as noted in the TAP document. Based on the results modify the uMobility configuration parameter or add any related information in uMobility until you are satisfied with the performance. Refine/tune configuration parameters such as handoff-triggers based on the results observed during this testing for individual APs. Admin can submit executed and signed TAP and his acceptance of product, with respect to deployment; TAP is considered signed off at this time.

User Provisioning

Once the system is performing to your satisfaction you can add the users manually or prepare a csv format file for bulk provisioning. You can also choose to build an interface using SQL scripts to add/delete and modify the users and their provisioning profile through a programmatic interface. The programmatic interface implementation is separately scoped by your supplier or IT team. Contact the enterprise for information for interface specification if needed.

When the users are provisioning into the system, it automatically triggers the over-the-air software installation procedure. This will trigger software installation for the devices. The typical parameters needed to provision the users are described in the uMobility System Administration Guide.

Test Acceptance Plan (TAP) Execution

The execution of TAP includes the following tasks:

· "Run sanity check-list, acceptance test plan"

· Refine/Tune configuration parameters

· Wi-Fi acceptance

· "Setting up Wi-Fi access points in the phone – they’ll need this for home/hot-spot, etc."

· Enabling Wi-Fi access points to work with uMobility.

TAP is executed by the person onsite and then either the results are reviewed or use case scenarios are executed with the customer personnel as desired by the customer. The results are published and normal operation handover process is started with the customer. It is expected that customer will not plan any network upgrades or changes after successful execution of the TAP and the normal operation handover to customer is completed.

Normal Operation HandoverDeliver documentation

A final copy of the documents is created and delivered with the installation specific information for future use and reference by customers, supplier support organization as well as the enterprise. The documentation includes:

· uMobility System Administration Guide

· uMobility Client user guides that may be modified with the customer specific branding information.

· Completed site-survey

· System backup in a redundant electronic storage

· Completed Test and Acceptance Plan

Train administrator

The purpose of this training is to provide education, information, and practice regarding the uMobility market, technology, and solution to all who work with uMobility – sales to marketing to implementation engineers and it is applicable for service provider market. The enterprise provides two (2) day classes for networking crafts persons and one (1) day classes to sales and marketing.

The second day of training is geared to hands on review of the administration of the solution with focus on the provisioning of users, maintenance of the system with backup/restore, gathering logs, and analysis of CDRs.

Train users

Although uMobility interface is easy to use and intuitive, the users in companies may need to be trained on uMobility operations similar to the cell phone usage similar to the getting started guide. A typical training for users include:

· Usability aspects of uMobility.

· Setting up Wi-Fi access points in the phone – they’ll need this for home/hot-spot, etc.

· Enabling Wi-Fi access points to work with uMobility.

· How to verify if their phone is correctly setup for a Wi-Fi network.

During this time supplier or support team will monitor the normal network operation, assist customer personnel for the normal operational items and train the personnel on the system as needed for smooth transition.

Pricing

In consideration for the Equipment and Services specified in the attached Equipment and/or Services lists, «SOLDTONAME» shall remit the total Sale Price of $0.00 plus applicable sales tax. Payment shall be due as indicated in the following Payment Schedule:

Services: $ 00

100% of Service Price ($0.00) due upon Acceptance of project.

Part Number

Description

Qty

MSRP Price

Ext MSRP

Associate Price

Ext Price

0300809

uMobility Commissioning

0

$xxxxx.00

$0.00

.90

$0.00

0300807

uMobility PS Domestic

0

$xxx.00

$0.00

.90

$0.00

Total Price:

$.00

$.00

This price is based on the customers current discount pricing structure as of creation date of this SOW. Customers discount is subject to change and that change will be reflected in this documented pricing.

Unless otherwise agreed to by the parties in writing, the above payments shall be due on a per System, per site, per event basis. All Change Orders shall be invoiced upon Cutover. Prices stated in this SOW are effective for 30 days from the date specified below in the footer. THE ABOVE SALE PRICE EXCLUDES SALES TAX. SALES TAX (IF APPLICABLE) WILL BE INVOICED IN ADDITION TO THE SALE PRICE.

Assumptions and Limitations

Associate and the enterprise agree that any deviation from the following assumptions may result in an adjustment in the rate(s)/price(s):

The terms and conditions of the SOW and the Agreement prevail regardless of any conflicting terms on any Associate Purchase Order, other correspondence and any and all verbal communications. All Purchase Orders are subject to acceptance and approval by the enterprise..

Delays caused by lack of completed site preparation or failure to meet any responsibilities as specified on the part of the Associate, will be billed at prevailing time and materials rates plus expenses.

Services required by the Associate to be performed outside of normal business hours (8 a.m. to 5 p.m. Monday through Friday local time, excluding holidays observedby the enterprise), unless otherwise planned for and noted, shall incur additional charges in accordance with will be billed at prevailing labor rates.

Changes to this SOW and subsequent implementation plan shall only be binding upon the parties when agreed to in writing by both parties and may result in costs additional to the prices in this SOW. Such changes may affect the project scope and timeline and will therefore constitute a new agreement.

The Associate’s network architecture design shall not change between the date of Associate’s execution of this SOW and the completion of all Services contemplated hereunder.

The Associate is responsible for any facility issues that may arise (i.e. bad or incorrect cabling, not meeting cable plant, environmental or power specifications, lack of rack space, etc.) and will correct any issues as quickly as possible. The Associate may contract with the enterprise for resolution of these issues.

The Associate is responsible for ordering and verifying availability of any required Telco circuits.

Associate will schedule and inform users of any required systems outage.

The enterprise requires a minimum lead-time of fourteen (14) calendar days from Associate’s execution of the SOW to begin work. It will make commercially reasonable efforts to meet the requested installation date.

The enterprise shall require a schedule extension of thirty (30) calendar days for any personnel change requests made by Associate.

Associate acknowledges that the following services are not covered under this SOW:

Support or replacement of Product that is altered, modified, mishandled, destroyed, or damaged by natural causes or damaged due to a negligent or willful act or omission by Associate or use by Associate other than as specified in the applicable or manufacturer-supplied documentation.

Services, software, or hardware required for software or hardware problem resolution resulting from third-party products or unforeseen circumstances.

Any hardware upgrades required to run new or updated software.

Any additional network audit, network assessment, network design, consulting, and/or training services that are offered under a separate Statement of Work.

Completion of Services

Upon completion of all work, the enterprise shall submit to the Associate a Services Completion Checklist (See Appendix B) for their review and signature. Associate shall ensure that the proper personnel are scheduled to review each completed Service or Deliverable upon receipt of this notification. The assigned Associate personnel shall indicate their acceptance of the Service or Deliverable by signing the Services Completion Checklist within five (5) days from the presentation of the completed Service or Deliverable. Services and Deliverables will be deemed accepted if the assigned Associate representative fails to respond within this five-day period. If a Service or Deliverable is not complete for any reason, Associate shall provide written notification to the enterprise. It shall have ten (10) days after the receipt of such notice from the Associate to correct the error, given it is within it’s scope to do so. Such time period to correct the error may be extended by mutual consent.

Equipment List

No equipment is provided under this Statement of Work

Agreement between and the Enterprise

This Statement of Work is governed by, incorporated into, and made part of the Master Purchase Agreement ("MPA") # _____ between and <«SOLDTONAME»>, having its principal place of business at ; as of the date last written below ("Effective Date").

This SOW defines additional provisions for applicable Hardware/Software and/or Services (“Products”) that the Enterprise shall sell and/or license to Associate under the terms of the MPA and as specifically defined in the related Equipment List, Services List. The terms of this SOW are limited to the scope of the related Equipment List, Services List, and shall not be applicable to any other attachments or exhibits, which may be executed and attached to the MPA.

IN WITNESS WHEREOF, the duly authorized representatives of the parties hereto have caused this SOW to be duly executed.

By: ____________________________by: ____________________________

Name:___________________________Name:___________________________

Title: ____________________________Title: ____________________________

Date: ____________________________Date: ____________________________

Appendix A – service responsibilities

«SOLDTONAME» (“Associate”) and Enterprise agree to the following specific responsibilities required for this project.

Phase 1: Acceptance of SOW

Phase 1 is the planning phase and the table shows the expected activities and responsibilities are listed below.

Category

Task

Description

Responsibility

Planning

Planning and Agreement

Discusses project requirements and activities on both sides. The kickoff list and the documentation is reviewed and modified by both parties.

enterprise Customer

Project kick off and review (Remote)

Deliverables – Product, Documentation, Support

enterprise Customer

Acceptance of SOW

NEC shall be responsible for the following:

Provide and sign contract documents.

Associate shall be responsible for the following:

Review and sign provided contract documents.

Phase 2: Solution Design

The solution design prepares the customer for making decisions to add another network appliance, security details and other such related tasks. The enterprise participates in the project planning and network planning as applicable, where as associate is responsible for all activities here working with the customer.

Category

Task

Description

Responsibility

Implementation

Deployment project plan/milestones (Remote)

Define milestones to deploy uMobility Product

enterprise Customer

Solution Design (Remote)

enterprise Customer

Procure server hardware, and phone devices

Customer

Identify space for the server hardware.

Customer

Identify power position for the server hardware.

Customer

Identify position in the network for uMC server – where it will be plugged into a switch/router

Customer

Identify IP-Address(es) for the uMC server(s)

Customer

Complete site-survey document for the IP-Telephony network information, user details, Wi-Fi details, etc

Customer

Phase 3: Implementation & Cutover

The enterprise shall be responsible for the following:

1.

1.

1. As outlined in this SOW and accompanying project plan documentation.

Category

Task

Description

Responsibility

Implementation

Identify uMC software release

enterprise

Identify uMobility client release for each type of phone devices

enterprise

Mount the server hardware in the rack/other space

Customer

Connect network, mouse, keyboard, monitor cables to the server hardware

enterprise

Install uMC software

enterprise

Check network connectivity from another computer to the uMC server

This ensures that there are no SBC/Firewall issues to connect to PBX, MG and remote sites as applicable.

enterprise

Add users or Trunk, as the case may be, on the call manager

Add SIP users in uMC and connects them to PBX and ensures basic call capabilities.

enterprise

Configure uMC based on the information captured in site-survey

enterprise

Add users on uMC which will trigger software installation for the devices (5 users)

enterprise

Install client s/w on devices (5 users)

The five devices are used to test the solution deployment and Wi-Fi readiness.

enterprise

Verification

Execute the test plan identified in the TAP document

Ensure the configuration works for all customer desired functionality.

enterprise

Run sanity check-list, acceptance test plan

uMobility Testing

enterprise

Refine/Tune configuration parameters

Tune any parameters based on the customer expectation.

enterprise

Wi-Fi acceptance

Wi-Fi Survey (200,000 SQ. FT)

enterprise

Setting up Wi-Fi access points in the phone – they’ll need this for home/hot-spot, etc.

This applies to five user devices.

enterprise

Enabling Wi-Fi access points to work with uMobility.

Voice readiness report verification

enterprise

Cutover

Documentation

Product user guides, Release Notes, Project Plan, TAP, Site-Survey are delivered

enterprise

Training

Administrators are trained to manage users and software upgrades on an ongoing basis. Users are made familiar with the features and use of uMobility.

enterprise Customer

Cutover the network to administrator

Customer personnel start maintaining uMobility.

enterprise Customer

Monitor the network for a day or agreed length of time

Support any end user queries and deployment.

enterprise Customer

Usage and Normal Operation monitoring

Support regular administrative task questions.

enterprise

Note that the standard service package includes 200,000 SQ.FT. of built out area in the current SOW. If the area serviced is larger than a day should be added per each additional 200,000 SQ. FT of area. Also in the facilities with use of heavy machinery, Wi-Fi upgrade is typically required after initial readiness survey. The other factors that may affect time are:

3. the number of buildings and

4. the distance among the buildings.

Reasonable provisions should be added for travel time from among buildings in the SOW.

Similarly if the customer expects the enterprise to provide all user devices then additional 5 minutes per user must be added. Therefore approximately 80 user devices can be added per day.

Phase 4: Project Acceptance

The enterprise shall be responsible for the following:

2.

Give Services Completion checklist to Customer to sign.

Resolve non-conforming issues identified by Customer in writing prior to Cutover.

Upon signoff of SOW, invoice remaining 100% of Service Price.

Customer shall be responsible for the following:

Sign Services Completion checklist. The System shall be accepted, for purposes of this SOW, 15 days after the Cutover Date, unless Customer gives a written notice prior to the Acceptance Date detailing how System does not conform to requirements of this SOW.

Submit payment for 100% of the Service Price.

Appendix B : Related forms

Site Locations and Contact Information

As applicable, following is a listing of installation sites identified by Associate for this SOW:

Street

City

State

ZIP

It is critical for success of your project that you have all the resources identified for the project available and reachable. The following table guides you through the information to plan and involve the right resources from the beginning of the project. Your organizational process may require a different list so do not hesitate to modify the list as necessary. Do not forget to share the list with the supplier of the uMobility products. You can also request the same contact information from the supplier in return. This is also part of the customer profile described above.

Customer/Company Name

Location/Address

IT/Engineering Contact Information

Name, Email, Phone number

Networking Engineering

Security (SBC) Engineering

Provisioning Engineering

Support Engineering

Hardware Engineering

Power planning and site engineering

Marketing/Sales Contact Information

Name, Email, Phone number

Documentation Prime

Market communication Prime

User Training/Documentation Prime

End customer support prime

Executive sponsor Contact information

Name, Email, Phone number

Services Completion Checklist – PSID# uMobility Deployment

The enterprise will submit this checklist to Associate for signature to indicate acceptance of this installation. The system shall be accepted, for purposes of this SOW, 15 days after the Cutover Date (the "Acceptance Date"), unless Associate gives written notice prior to the Acceptance Date detailing how the System does not conform to the requirements of this SOW.

IMPLEMENTATION TASK

COMPLETED?

1. uMobility Deployment.

|_|

Acceptance Acknowledged:

By:

Printed Name:

Title:

Date:

Appendix C – Change Request Form

Original Purchase Order #:______________________________________________________

Original Purchase Order Amount:_________________________________________________

New Purchase Order Amount:____________________________________________________

1. Change request explanation

____________________________________________________________

____________________________________________________________

1. Change request Parts

This request is foradditional parts / refunded parts (Circle one)

Part Number

Description

Qty

MSRP Price

Ext MSRP

Associate Price

Ext Price

$

$

$

$

$

$

$

$

$

$

$

$

$

$

$

$

Totals:

$

$

$

$

1. explanation

____________________________________________________________

____________________________________________________________

1. Change request Parts

This request is for additional parts / refunded parts (Circle one)

1. Signatures

The Enterprise

Signature:

Signature:

Printed Name:

Printed Name:

Title

Title:

Date:

Date:

Server(s)

Wi-Fi Network

IP Network

Telephony Network

Cellular Network

Title: uMobility Deployment and support (Statement of Work)

Confidential

2003-2012 Varaha Systems, Inc.

Page 30 of 40

THIS DOCUMENT AND THE DATA DISCLOSED HEREIN OR HEREWITH IS PROPRIETARY AND IS NOT TO BE REPRODUCED, USED OR DISCLOSED IN WHOLE OR IN PART TO ANYONE WITHOUT THE WRITTEN PERMISSION OF VARAHA SYSTEMS. COPYRIGHT, © Varaha Systems 2008

Dialpad

pad

Display Area

Network

connectivity:

1) Registered,

2) Enterprise

or 3) Cell

Network

information

message

Panel Menu

Dial pad (displays dialed

digits from the keypad)

Network connectivity:

1) C for Cellular

Network,

2) E – registered to the

Enterprise via the

cellular data network,

3) W - registered to the

Enterprise using the Wi-

Fi network

Device info (e.g.,

time, date)

Call Logs

W

C