Introduction

A brief introduction highlighting the preamble of the project, emphasising the

requirements to be addressed in the feasibility study.

Cost Benefit Analysis

An analysis of costs and benefits of a mobile access system, the requirements
outline 3 key areas for costs. These are:

Operational costs, maintenance costs, setup costs.

Analyse these costs, would generally cover some common areas such as:

Setup (Deployment) costs

Installation, training, hosting, hardware, software costs. Thus in your research

look for what items will appear on the inventory of costs for a mobile access
facility. Show cost estimates for the items you have identified, check up a few
websites for cost estimates.

Maintenance costs

These will be as a consequence of your setup costs. What items need to be

maintained? Hardware, software updates etc.

Operations cost

Cost of operating a mobile access facility, may include license, labour costs,
support, insurance, generally what the accountants refer to as recurring costs.

Benefits

Restate the benefits as outlined in the introduction of the case. A table will be
useful in addressing the tangible and intangible benefits to the different
categories of users. Thus in your research look for related information on
tangible and intangible benefits from using a Mobile access system.

Technical Requirements
Here you should be researching technical requirements of mobile access
systems, these can be found from websites of network service providers, reading
white papers from their websites and studying case studies.

A few useful websites include:

http://docs.sun.com/source/817-6257/02analyz.html

http://www.cisco.com/en/US/docs/wireless/technology/mobile/access/mobileacce
ss.html

http://www.mediapro.com.sg/products_SipVoip.htm
http://computer.howstuffworks.com/modem1.htm,

Also use related textbooks on mobile computing, William stallings and jochen
schuller come to mind immediately.

This list is by no means exhaustive, by all means search through for as many as
you would deem appropriate, the internet is an endless resource and textbooks
on mobile computing as a complement.

Address the usage requirements of your various categories of users, a table will
help break this down addressing areas mentioned in stage 2 of your coursework.

You may also need a table to address the technical requirements for each user
category with regard to appropriate devices, number of users, bandwidth
requirements, level of security etc.

Also highlight conflicts that may arise from the technical requirements and
security challenges.

Design
There are 2 key areas mentioned here:

Your cell size and cell overlaps showing coverage (for the museum), you may
choose to draw this or research an appropriate diagram but it must be a realistic
one that addresses the requirements as accurately as possible. Thus
researching some cell coverage diagrams for mobile solutions will be well worth
it to give you a clear idea of what you are looking for. Also refer to your slides on
cellular systems where cells are discussed to help you in this regard. A cellular
map is what is required here as your deliverable.

Your network topology must show the wireless infrastructure as well as an

indication of how the fixed network part integrates with the wireless part. A
network diagram on the fixed part will include servers, workstations/desktops,
printers, switches, routers. Also make provision for wireless implementation
within the fixed network. Study carefully the requirements in the specifications
and endeavour to address them in as much detail as possible. The wireless part
of your network supports mobility within the museum complex, your wireless
access point(s), base (transceiver) station(s), wireless access devices etc must
be clear in your infrastructure diagram.

Devices
Devices required for constructing the network will include:

Routers, switches, cables, repeaters, modems, base station etc.

Additionally list devices needed to connect to (access) the network:

Computers (desktops/laptops), security cameras, PDAs etc.

Previous Contents Index Next

Sun Java System Portal Server Mobile Access 6 2005Q1 Deployment Planning Guide

Chapter 2
Analyzing Your Mobile Access Requirements
This chapter describes how to analyze your organization’s needs and requirements that affect
the design of your Mobile Access software deployment.
This chapter contains the following sections:
• Identifying and Evaluating Your Business and Technical Requirements
• Mapping Mobile Portal Features to Your Business Needs

Identifying and Evaluating Your Business and

Technical Requirements
To identify and analyze your Mobile Access business and technical requirements, consider
what your needs are from a high-level perspective.
To guide your deployment planning, this topic provides questions in the following areas:
• Business Objectives
• Technical Goals
• User Behaviors and Patterns
• Performance and Capacity
• Front-End Systems
• Growth Projections
• Authentication and Secure Access
• Channels
• Quality Goals
Some questions in these areas will not apply to your mobile portal design, and in some cases,
you will identify and have to address issues that are not presented here.
Business Objectives
The business goals of providing mobile access affect deployment decisions. If you do not
understand your objectives, you can easily make erroneous assumptions that could affect the
success of your deployment.
Use these questions to help you identify your business objectives:
• What are the business goals of providing mobile access to your portal? For
example, do you want to enhance customer service? Increase employee
productivity? Reduce the cost of doing business?
• What are the business goals of providing voice access to your portal?
• Who is your target audience?
• What services or functions will the mobile portal deliver to users?
• How will your target audience benefit from mobile access?
• What are the key priorities for providing mobile access? If you plan to
deploy your mobile portal in phases, identify key priorities for each phase.
Technical Goals
The reasons you are offering mobile access to your portal have a direct affect on planning
your deployment. You must define target population, performance standards, and other
factors related to your goals.
Use these questions to help you identify the goals of your mobile portal:
• What are the goals of providing mobile access? For example, do you want
to deliver a service? Do you want to provide information?
• What applications will the mobile portal deliver?
• What is your target population?
• What performance standard is necessary? Does it differ from your portal
performance?
• What transaction volume do you expect? What transaction volume do you
expect during peak use?
• What response time is acceptable during peak use?
• What level of concurrency, the number of users who can be connected at
any given time, is necessary?
• Will your mobile portal be deployed in one phase, or many phases?
Describe each phase and what will change from phase to phase.
User Behaviors and Patterns
Study the people who will use your mobile portal. Consider factors such as when they will
access the portal using a mobile device and how they have used predecessor access methods.
If your organization’s experience cannot provide these patterns, you can study the experience
of other organizations and estimate them.
Use these questions to help you understand mobile users:
• Is mobile portal use likely to increase over time? Or stay stable?
• How fast will your mobile user base grow?
• How have your users used applications that the mobile portal will deliver
to them?
• What mobile portal channels do you expect users to use regularly?
• What expectations about your mobile portal content do your users have?
How have they used predecessor Web-based information or other
resources that your mobile portal will offer?
Performance and Capacity
The performance that your portal must deliver directly affects your deployment requirements.
Scalability, capacity, and high availability are some of the standards you need to consider.
Use these questions to help you evaluate performance requirements for your portal:
• What performance requirements exist?
• What high availability requirements exist?
• What response times are acceptable? How do the response times of your
stand-alone systems compare with response time requirements of your
portal?
• If you size your portal infrastructure for good response times during
regular hours, can you tolerate a possible degradation in performance
during peak load times?
• How many concurrent sessions, or connected users, are likely during peak
use? (Count only users who are active. Do not include users who are, for
example, away on vacation, on leave, or sleeping.)
• What is the above-normal peak time? How does this information affect
your peak concurrent user estimate?
• What sort of user activity occurs during peak periods? Logins or reloads?
• How long do you expect the typical user to be connected, or have a valid
portal session open? What use statistics do you have for existing
applications? Do you have Web traffic analysis figures for an existing
portal?
Front-End Systems
Analyze the front-end systems that will be used for access to your mobile portal. This enables
you to identify how your users will connect to your portal and what kinds of browsers they
will use. These factors will affect your deployment decisions.
Use these questions to help you understand your front-end systems:
• How will mobile users access your portal? What types of devices will they
use?
• What browser features do your users have? Do they have Java™
applications? Is JavaScript™ technology enabled? Is cookie support
enabled? Are tables supported?
• Is voice access needed?
Growth Projections
In addition to determining what capacity you need today, assess what capacity you’ll need in
the future, within a time frame that you can plan for. Growth expectations and changes in
how your portal is used are factors you need to accommodate growth.
Use these questions to help you set growth projections for your mobile portal:
• What is the projected growth for the portal? How fast will the growth
occur?
• Where is your mobile portal available? What are the trends for use of
mobile devices in those countries?
• How will your business objectives change in the next two or three years?
• What plans do you have for future content?
Authentication and Secure Access
Determine whether security is needed for your mobile portal. If so, you must assess what
kind is appropriate.
Use these questions to help you identify security requirements for your mobile portal:
• Is SSL required for authentication to the portal?
• Is SSL required for any other part of the portal?
• Is a gateway needed?
• What are your security policies?
• Do you use the Identity Server software to provide single sign-on to your
portal? Will your single sign-on requirements change for mobile access?
Should your mobile portal users be able to sign on automatically?
Channels
The channels your portal site offers have an affect on your deployment decisions. How your
users use mobile devices to use channels and their content are among the factors to define.
Use these questions to help you assess channel requirements for your mobile portal:
• How many channels are you likely to provide to mobile device users?
• What portal channels do you expect mobile users to use regularly?
• Will you provide new content or re-work existing content?
Quality Goals
To identify and establish quality goals for your Mobile Accesss software deployment,
consider what measures will allow you to deliver the quality that your mobile portal must
offer.
Use these questions to help you set quality goals for your mobile portal:
• Do you want to provide all existing Portal Server software users mobile
access to your portal within a certain time frame, such as 12 months?
• Have you completed plans for a test environment that replicates your
production environment?
• How much time will you need for various test phases, including unit
testing, functional testing, end-to-end testing, user acceptance testing,
and the like?
• Will you test each mobile device you plan to support?
• Should you maintain existing mobile portal services during your mobile
portal deployment?
• What performance and reliability expectations do you have? Have you
established baseline measurements that you can track as you move to a
production environment?
• What user interface standards do you have for various mobile devices?
• Can you maintain a completely functioning network infrastructure
throughout the transition period from your test environment to your
production environment?
• Can you eliminate single points of failure for the portal system by
developing an architecture that includes redundant portal servers,
gateways, and directory replicas and masters at various service layers?
 • What change control procedures will you follow?

Mapping Mobile Portal Features to Your Business

Needs
This section describes specific technology features of Mobile Access to help you determine
which technologies are most important for your organization. Review these features while
keeping in mind your organization’s short-, mid-, and long-term plans.
To assist you in developing a deployment plan in a timely and cost effective manner, this
topic describes the following features:
• Dynamic Rendering Engine
• VoiceXML Support
• JSR 188 (CC/PP)Secure Remote Access
• Secure Remote Access
Dynamic Rendering Engine
The dynamic rendering engine in Mobile Access software enables content, applications and
services to be delivered dynamically to a mobile device in the correct markup language. The
markup languages supported are XHTML, cHTML, HDML, HTML and WML.
This enables you to implement multi-device deployment scenarios.
VoiceXML Support
Mobile Access software provides the framework required to deploy VoiceXML applications.
A voiceXML application can be deployed to users who are either on a land-based or mobile
phone.
Voice-enabling enterprise applications such as email or calendar are useful ways to reuse
enterprise information and content. Various voice engines and developer tools from third
party vendors can be used with the Mobile Access software.
JSR 188 (CC/PP)
Mobile Access software implements the composite capability and preference profiles
(CC/PP) specification. Portal Server software can use this implementation to adapt content
and pass on delivery context information to channels that would adapt their behavior
accordingly.
This specification provides developers with a standard set of APIs for processing delivery
context information compatible with the majority of Web access mechanisms that deliver
context negotiations.
Writing device-independent code that can deliver content to a multitude of Web access
mechanisms helps reduce costs and avoids proliferating proprietary and potentially
incompatible implementations.
Secure Remote Access
The Mobile Access product supports Sun Java™ System Portal Server Secure Remote
Access software, which provides proxy, URL rewriting, and VPN-on-demand capabilities.
The Secure Remote Access gateway sits in the DMZ in front of the corporate firewall and
provides security from outside connections to resources available behind the firewall.
The gateway provides proxy server and URL rewriting capabilities for content and
applications. It also supports URL obfuscation.

Previous Contents Index Next

Part No: 819-1372 . Copyright 2005 Sun Microsystems, Inc. All rights reserved.
Home Skip to content Skip to navigation Skip to footer

Cisco.com Worldwide Home

Products & Services Support How to Buy Training & Events Partners
(menu) (menu) (menu) (menu) (menu)
Guest

Top of Form

Search

Search

cisco.com en US f Guest

Bottom of Form

Log In

Account

Register

My Cisco

My Cisco

My Cisco

Now you can add and remove modules to My Cisco!

Click to open.

Easily access your personalized content anywhere on Cisco using My Cisco.

Click to open

Worldwide

Log In
Account

Register

Cisco 5500 Series Wireless Controllers

Mobile Access Indoor Wireless Solution and Cisco WLANs

Hierarchical
Navigation Table Of Downloads
HOME Contents Mobile Access Indoor Wireless Solution and
PRODUCTS & White
SERVICES Paper: Cisco WLANs
WIRELESS Mobile
CISCO 5500 Access
SERIES WIRELESS Indoor
CONTROLLERS Wireless Solution and Cisco WLANs
PRODUCT Contents
LITERATURE Introduction
WHITE PAPERS Solution Overview
Mobile Access Co-existence of Signaling on the CAT-5e/6 Cable
Indoor Wireless Co-existence of PoE on the CAT-5e/6 Cable
Solution and Cisco Testing to Identify Co-existence Issues
WLANs Maximum Cable Length
Ethernet Compliance per 802.3 specifications
Top of Form Product Safety and Compliance
Feedback: Help us Cisco Device Compatibility
help you Additional Reference Material

Please rate this

document. White Paper: Mobile Access Indoor
Wireless Solution and Cisco WLANs
Excelle
nt Published: September, 2010
Contents
Good Introduction
Solution Overview
Co-existence of Signaling on the CAT-5e/6 Cable
Averag Co-existence of Signaling on the CAT-5e/6 Cable
e Co-existence of PoE on the CAT-5e/6 Cable
Testing to Identify Co-existence Issues
Fair Additional Reference Material
Introduction
The purpose of the paper is to show that the Mobile Access
Poor
access pod and the Cisco Aironet access point can share the
same Cisco WLAN infrastructure including the CAT-5e/6 cable
This document solved
run while each solution maintains complete functional
my problem.
performance.
 This document so Mobile Access is a Cisco Developer Networks partner with
Cisco Systems and the MobileAccessVE solution is available
through SolutionsPlus. The MobileAccessVE solution cost-
effectively provides in building cellular coverage over
Yes
category 5/6 cables. The solution components primarily
consist of the Control Unit (VCU) which is a Head-End
No element that interfaces with the Service Provider's RF
capacity source and Access Pods (VAP) which provide indoor
Just distributed RF cellular coverage. CAT-5e/6 Ethernet cable
Browsing distributes analog signals from the VCU to the VAP and vice-
versa. The VAP radiates the service provider signals at the
Suggestions to service providers licensed radio frequency. The
improve this MobileAccessVE Element Management System (EMS) which is
document. integrated with the VCU provides remote monitoring and
management.
Solution Overview
Mobile Access's solution uses Ethernet CAT-5e/6 cabling to
provide in-building cellular signal distribution. The
MobileAccessVE solution can reuse the same CAT-5e/6 used
by Cisco Aironet Access Points concurrently.
(512 character limit)
The solution can be configured to operate in any the
108 frequency used by the cellular provider. The Wi-Fi signal is
transferred in different frequency bands from the cellular
If you have provided a
frequencies. They do not interfere with each other when in
suggestion, please the air or on wire.
enter your full nameThe following picture shows a Cisco switch, an Aironet AP and
and e-mail address.the MobileAccessVE solution co-existent on the same CAT-
This information is 5e/6 cable run while simultaneously maintaining full Ethernet
optional and allows capabilities.
us
to contact you if
necessary.

Name:

E-mail:
Mobile Access In

http://w w w .cisc

293
Cabling notes:
• Ethernet LAN packet signals passed over Ethernet cable
 feedback2techdo frequencies between 0 MHz and 125 MHz.
• Cellular signals are converted for transmission over the
Ethernet cable to frequencies at 160 MHz and above.
• This configuration allows Ethernet cabling to be passive
to cellular and Wi-Fi.
right
• The separation of the analog cellular signals by the
Ethernet cable pairs from the Ethernet LAN traffic signals
false
provides the LAN traffic full bandwidth capabilities.
• PoE is transparent between the two technologies. Even if
Products White P
the MobileAccessVE devices are powered off; the Cisco AP
will remain fully functional. Similarly if the ethernet solution is
cisco.com#Produ switched off; the MobileAccessVE solution continues to
operate.
external_docbas • The MA Controller pictured above shows that two cellular
services(Example Cell and PCS) can be brought into the
CCIM-TD controller. There are 12 UTP ports than can transport those
two cellular services to 12 MA VAPs and those 12 UTP ports
UNKNOWN
are paired to/from 12 Cisco switch ports.
Co-existence of Signaling on the CAT-5e/6 Cable
On the Ethernet port signaling side of the Mobile Access VCU
UNKNOWN
the cellular traffic is transmitted onto the cable at a different
frequency than the frequency used for the LAN packets to
and from the Aironet AP to prevent interference with each
Bottom of Form other. The VCU and VAP devices transmit analog radio signals
over the CAT-5e/6 cable by down-shifting the cellular
frequencies to intermediate frequencies. Since the frequency
range used of cellular traffic is different from Ethernet traffic;
there is no cross talk or harmonic inference between the two
technologies. The cellular frequencies are 140-220 MHz,
while the Ethernet spectrum is 0-125 MHz. The
MobileAccessVE device performance is not influenced by the
presence or absence of Cisco switches or APs. The
MobileAccessVE devices that share the same cable run as the
Cisco devices are not influenced by the power state(on/off) of
the Cisco devices. The MobileAccessVE devices are passive
with concern to Ethernet connectivity. The RJ-45 ports on the
VCU are strictly pass-through. They are not programmable in
the sense of switch ports on a Cisco switch.
Co-existence of PoE on the CAT-5e/6 Cable
The amount of power that a switch provides at the power
sourcing port depends on the switch or line card of the
switch. It also depends on the model of the switch or line card
and the power supplies of the switch. Cisco switches then
negotiate the amount of power to provide to the endpoint
using the Cisco Discovery Protocol (CDP). A Cisco switch
provides power to the Aironet AP. The VCU provides power to
the Mobile Access VAP. The ability to provide power to
Aironet AP from the CAT-5e/6 cable that is also powering the
VAP is done using different wire pairing within the CAT-5e/6
cable for each AP. CAT-5e/6 cable has four pairs of wire. The
Cisco switch provides power on pairs 1-2 and 3-6 for the
Aironet AP per 802.af type A standards. The MobileAccessVE
provides power separately for the VAP on pairs 4-5 and 7-8.
Therefore, Aironet AP and the VAP have unique power
sources. The MobileAccessVE and VAP pass the power from
the Cisco switch through to the AP passively. This separate,
independent supply of power on the CAT-5e/6 cables
provides the VAP full service functionality and the Aironet AP
full 802.11n performance.
Testing to Identify Co-existence Issues
Cisco engineers tested the following items to identify co-
existence issues:
• Maximum Ethernet Cable Length
• Ethernet compliance per 802.3 specifications
• Product Safety and Compliance
• Cisco device Interoperability
Maximum Cable Length
The highest length of CAT-5e/6 cable that is recommended
for a gigabit Ethernet run is a total of 100 meters. It is
recommended that only CAT-5e or better be used in any
portion of the run. A run is defined as the total CAT-5e/6
cable connections between the PoE switch port to the final
Ethernet client device. All connections to MobileAccessVE
Controller (VCU) and the MobileAccessVE Access Pod (VAP)
add into that total run length. This is because to the gigabit
Ethernet signals, the VCU and VAP are passive, pass-through
devices. Therefore, in considering the maximum run length,
there will be a minimum of three CAT-5e/6 cables involved.
Cisco ran exhaustive tests with cable lengths well beyond
100 meters to substantiate the 100 meter specification when
any devices are connected to the VE system and any
medium- to good-quality CAT5e/6 cable is used.
There is no difference in Wi-Fi or Cellular performance
whether short or long CAT5e/6 cables are used. Also, gigabit
Ethernet performance (throughput, packet error rate) was
tested rigorously and no negative effects were observed-the
VE system is truly transparent to gigabit Ethernet operation.
Packet error rates were studied with various Ethernet
protocols, encryption types, packet sizes and data rates.
Packets sizes varied from runt to jumbo. The protocols
included TCP, UDP, DHCP, CDP, LWAPP, CAPWAP, EAP-TLS,
Cisco LEAP and Cisco VPN. This provided a broad but
common list of data protocols, security and authentication
protocols and encryption schemes. It certainly is not a
complete list but certainly indicates that no type of protocol
and encryption incurred a packet error rate higher than
another protocol.
Ethernet Compliance per 802.3 specifications
The MobileAccessVE system was examined against 802.3
(Ethernet) physical layer specifications using engineering
laboratory equipment. A complete Ethernet compliance test
suite was run on the VE system and examined such
parameters as constellation error, return loss, and pulse
mask. The system exhibits a small amount of parametric
degradation, equivalent to the effect of a short length of
Ethernet cable about 10-15 meters in length.
Product Safety and Compliance
During the tests, Cisco also verified product safety and
regulatory compliance, and inspected the entire set of
certifications and test reports associated with the
MobileAccessVE system.
Cisco Device Compatibility
Cisco has tested the MobileAccessVE system with the entire
portfolio of Aironet Wi-Fi Access Points, and with the CAT3k
and CAT4k line of Ethernet switches. PoE functionality per
802.3af/at and compatibility with the Cisco Discovery
Protocol (CDP) for enhanced PoE was verified. Note: PoE
compatibility could be an issue with legacy EOL'd Cisco
access points since those products were designed before the
802.3af PoE standard was ratified.
The system works assuming the 802.3af/at Type A PoE
injection convention is used. Any Ethernet client equipment
which operates outside of the 802.3af standard or with the
Type B methodology may require a special adaptor (supplied
by Mobile Access) to reconfigure the PoE to a Type A
equivalent. The adaptor solution ensures that customers will
be able to deploy the VE system in any current or legacy
Ethernet network.
Additional Reference Material
Design Zone for Mobility:
http://www.cisco.com/en/US/netsol/ns820/networking_solutio
ns_program_home.html
 PoE information:
http://www.cisco.com/en/US/docs/wireless/technology/poe/tec
hnical/reference/Power.html
Cisco and the Cisco Logo are trademarks of Cisco Systems,
Inc. and/or its affiliates in the U.S. and other countries. A
listing of Cisco's trademarks can be found at
www.cisco.com/go/trademarks. Third party trademarks
mentioned are the property of their respective owners. The
use of the word partner does not imply a partnership
relationship between Cisco and any other company. (1005R)
© 2010 Cisco Systems, Inc. All rights reserved.

Borderless Networks

Product Portfolio

Architecture

Services

Solutions

Industries

Solutions For

Enterprise

Small Business

Service Provider

Home

Industries

Contacts

Contact Cisco

Find a Partner

Support

Downloads

Documentation
Communities

Collaboration

Developer Network

Learning Network

Support (NetPro)

About Cisco

Investor Relations

Corporate Social Responsibility

Environmental Sustainability

Human Network

Career Opportunities

Offers

Special Offers

Financing Options

Collaboration

Conferencing

Customer Care

Enterprise Social Software

IP Communications

Messaging

Mobile Applications

Telepresence

Solutions For

Enterprise

Small Business

Service Provider

Home

Industries
Contacts

Contact Cisco

Find a Partner

Support

Downloads

Documentation

Communities

Collaboration

Developer Network

Learning Network

Support (NetPro)

About Cisco

Investor Relations

Corporate Social Responsibility

Environmental Sustainability

Human Network

Career Opportunities

Offers

Special Offers

Financing Options

Data Center and Virtualization

Products and Solutions

Case Studies

Design Zone

Technology Partnerships

Data Center Services

Solutions For

Enterprise
Small Business

Service Provider

Home

Industries

Contacts

Contact Cisco

Find a Partner

Support

Downloads

Documentation

Communities

Collaboration

Developer Network

Learning Network

Support (NetPro)

About Cisco

Investor Relations

Corporate Social Responsibility

Environmental Sustainability

Human Network

Career Opportunities

Offers

Special Offers

Financing Options

Borderless Networks

Product Portfolio

Architecture

Services
Solutions

Industries

Solutions For

Enterprise

Small Business

Service Provider

Home

Industries

Contacts

Contact Cisco

Find a Partner

Support

Downloads

Documentation

Communities

Collaboration

Developer Network

Learning Network

Support (NetPro)

About Cisco

Investor Relations

Corporate Social Responsibility

Environmental Sustainability

Human Network

Career Opportunities

Offers

Special Offers

Financing Options
Contacts | Feedback | Help | Site Map |

Terms & Conditions | Privacy Statement | Cookie Policy | Trademarks

D-Link DVG-1402S 4-ports VoIP Gateway

Top of Form
Using your existing broadband connection, the DVG-1402S connects
to your cable or DSL modem. Connect up to two regular phones to
the DVG-1402S, and with an appropriate Internet phone service plan,
you are ready to make VoIP calls. With the DVG-1402S, calling over
the Internet is simple and works just like a regular telephone. The
DVG-1402S is compatible with several convenient call features such
as caller ID, voicemail, call waiting, and three way calling.
Bottom of Form

Linksys WAG54GP2 Wireless-G ADSL Router with 2 phone port

- 2 FXS, QoS
- ADSL Modem built-in
- 4-ports switch

Linksys PAP2T VoIP phone Adapter

- 2 FXS ports for SIP Service

Linksys Sipura SPA-3102 VoIP phone Adapter

- 1 FXS and 1 FXO, ATA Solution with a PSTN Gateway

Linksys Sipura SPA-9000 IP PBX VoIP System

- IP Telephony System
- Full Featured IP PBX System for the Small Business and
Home Office
- Initial support of 4 Linksys IP Phones per SPA9000 is
upgradeable to 16 with a easy to install license key
- Powerful self-configuration capabilities enabled with
Linksys IP Phones
 Linksys Sipura SPA-400
- Internet Telephony Gateway with 4 FXO Ports
- Advanced Multi-Port PSTN Gateway Solution for the
Linksys Voice System
- Functions as an Analog Line Gateway for a Linksys Voice
System VoIP Network
- Integrated Voicemail Application Server with up to 32
Voicemail Accounts
- Perfectly Suited to Connect up to 4 Analog Lines
- Enables Linksys Voice System Users to Leave and
Playback Voicemail Messages
- Designed only to be deployed with the Linksys SPA9000
- Easy installation support using the SPA9000 Setup Wizard
(download available on SPA9000 product page)

Linksys Sipura SPA-921 SIP VoIP Phone

- One independently configurable line appearances / extensions
- High resolution pixel-based display
- Speakerphone

Linksys Sipura SPA-941 SIP VoIP Phone

- Two or four independently configurable line appearances / extensions
- High resolution pixel-based display
- Speakerphone

Linksys Sipura SPA-942 SIP VoIP Phone with PoE

- Two or four independently configurable line appearances / extensions
- High resolution pixel-based display
- Speakerphone

Linksys Sipura SPA-962 SIP VoIP Phone with Color LCD

- 6-Line IP Telephone with 2 Port Ethernet Switch, PoE, and Color
Display
Enhances Business Communication Requirements with Color
- Full featured six line business class IP Phone supporting Power
over Ethernet 802.3af
- Connect directly to an Internet Telephone Service Provider or
connect to an IP PBX
- Dual switched Ethernet ports, Speakerphone, Caller ID, Call
Hold, Conferencing, and more
- Appealing Four Inch, True Color Liquid Crystal Display (LCD)