My WebLink
|
Help
|
About
|
Sign Out
Browse
Search
Agmt15 Packet Fusion
RedwoodCity
>
City Clerk
>
Agreements
>
2010-2019
>
2015
>
Agmt15 Packet Fusion
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/7/2015 4:35:42 PM
Creation date
10/7/2015 4:33:32 PM
Metadata
Fields
Template:
Agreement
Contractor Name
Packet Fusion
PROJECT NAME
New Telephone System
RMP File Number
304
Date
10/7/2015
MO Ref
15-160
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
69
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
EXHIBIT "A" SCOPE OF WORK <br /> provider to the PE WAN router and CPE Core Router is saturated. Then, <br /> the WAN provider is forced to shape traffic and drop excess data packets <br /> in favor of higher QoS voice packets before putting traffic into the WAN <br /> link. Voice traffic will be generated and measured during the saturation <br /> test, and Vendor will provide an MOS for the voice traffic under load. <br /> 2.8. For the saturation tests above, PFI will provide all testing methodology, <br /> hardware and software that will be used to generate sufficient traffic to <br /> flood the uplinks from the IDF to the Core in the LAN and between <br /> locations on WAN. These tests shall be conducted after business hours <br /> so that they do not impact business processes. <br /> 2.9. A normal testing session will then be initiated between all end-points using <br /> expected voice and data traffic and should last no less than three days. <br /> 2.10. Testing shall use the G711 CODEC, using a 64KB packet size with a 20 <br /> ms jitter-buffer on the LAN. If the system recommends other "Best <br /> Practices,"then the test should match manufacturer recommendations. <br /> 2.11. Testing shall use the G729 CODEC using a 20 ms sampling rate and 40 <br /> ms jitter-buffer on WAN. If the system recommends other "Best <br /> Practices," then the test should match manufacturer recommendations. <br /> 2.12. Test results shall include: throughput (bandwidth), packet loss, <br /> packet delay (latency), jitter (variable latency), and the minimum <br /> and average MOS that can be expected per LAN/WAN segment. <br /> 2.13. PFI will interpret and summarize the findings and provide a verbal <br /> and written recommendation for any remediation. <br /> 2.14. If the initial test of the network fails and remediation is required, PFI <br /> will retest the network one time with the same process as above, <br /> prior to bringing the new voice system into production. <br /> 2.15. After the initial VoIP Network Readiness Assessment, PFI will be <br /> required to explain and price any additional remediation <br /> recommended in order to achieve the goals above. Once <br /> REDWOOD CITY has implemented the remediation, and the <br /> network has been certified through a follow-up assessment, PFI <br /> and manufacturer are expected to guarantee the installation (other <br /> than WAN carrier quality issues). The following applies if the <br /> installation fails the requirements. <br /> • PFI will have five days to identify the problem. <br /> • REDWOOD CITY (and the WAN provider) will assist in problem <br /> identification/resolution under the direction of PFI. <br /> REV:08-28-15 MLG <br /> Page 14 of 69 <br /> ATTY/AGR.2015.207/Packet Fusion New Telephone System <br />
The URL can be used to link to this page
Your browser does not support the video tag.