Radio Shack 43-3704 User Manual Page 5

  • Download
  • Add to my manuals
  • Print
  • Page
    / 8
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 4
Page 5 of 8
8. Provide software maintenance and upgrades as needed.
9. Provide the following information.
a. The Library intends to request Universal Service Administrative Company (USAC)
Schools and Libraries Program discounts commonly known as E-Rate. What is the
vendor’s USAC Service Provider Identification Number (SPIN)?
b. Who manufactures the proposed system?
c. Does the proposer install the product or use business partners?
d. Does the proposer maintain the product or use business partners?
e. Does the proposer maintain a support call-in center for problems?
f. Does the proposer provide on-site assistance if required?
g. Submit three customers that NOLS may contact for references. Customers
organizations of a size and configuration similar to NOLS are preferred, as are
customers who are using a system similar to the one being proposed for NOLS.
Reference information must include company name, name, telephone number and email
address of contact person. Please provide a brief description of the installed system at
each reference site.
E. Technical requirements. Any solution proposed should meet the following technical
requirements.
1. Connectivity across multiple locations
a. Uniform dialing plan to any telephone at any of the Library’s locations.
b. Centralized system administration.
c. Network (telco) services sharing between locations.
d. Capability to provide a variety of interfaces to the PSTN, and choice of analog or IP
phones for endpoints including for users, modems, fax machines, [tele]conference
rooms, etc.
2. Reliability
a. Ability to provide a highly reliable and available system without a significant single
point-of-failure.
b. Ability to provide PSTN access during power outage.
c. Capability to backup voice messaging and configurations.
3. Voice Quality
a. Must be toll quality voice. Latency must not exceed 35 milliseconds in one direction.
QOS must not require infrastructure upgrades.
b. Must not limit current network traffic handling capacity; both internal and between
locations.
4. Capacity and Scalability -- Allows modular, cost-effective growth in both phones and
applications over the next ten years.
5. Support for Open Systems Standards
a. The vendor should be committed to supporting open system industry standards,
such as SIP 1.0/SIP 2.0; H.323; H.248; MGCP Protocol; and G.722, G.711, G.729
codecs etc.
b. IP handsets should use a standard signaling protocol, such as MGCP; and be
compatible with 802.3af PoE (standard), or Class 2 PoE.
Page view 4
1 2 3 4 5 6 7 8

Comments to this Manuals

No comments