ITalk Project Report

SUPERIOR UNIVERSITY LAHORE
Faculty of Computer Science & IT
Final Year Project

PROJECT REPORT (Part-1)
iTalk
Project ID: [write ID here Issued by FYP Manager]
Project Team
Student Name Student ID Program Contact Number Email Address
WAQAS AHMAD MITE-F17-039 MIT 03214434429 Waqas_4me@hotamil.com
RAHEEL FAZIL MITE-F17-042 MIT 03014828394 Raheel_fazil@hotmail.com
Mr. Amjad Mukhtar

([Designation])
Project Report: iTalk
Project Report
I Talk
Change Record
Author(s) Version Date Notes Supervisor’s Signature
1.0 <Original Draft>
<Changes Based on
Feedback from
Supervisor>
<Changes Based on
Feedback From Faculty>
<Added Project Plan>
<Changes Based on
Feedback from
Supervisor>
Faculty of CS&IT, Superior University Lahore, Pakistan ii

APPROVAL
PROJECT SUPERVISOR
Comments: ___________________________________________________________________
_____________________________________________________________________________
Name:______________________________
Date:_______________________________ Signature:__________________________
PROJECT MANAGER
Comments: ___________________________________________________________________
_____________________________________________________________________________
Date:_______________________________ Signature:__________________________
HEAD OF THE DEPARTMENT

Comments: ___________________________________________________________________
_____________________________________________________________________________
Date:_______________________________ Signature:__________________________
Faculty of CS&IT, Superior University Lahore, Pakistan iii

Dedication
When our final year project was on our head we had so much to think about and
so much to deal with but don’t know from where we had this idea of making this
project. At the time of making this project we were amazed that how would we
accomplished this project, but it’s only done by the continuous support of our
family and teachers who believe that we can do it. Thanks to them and Almighty
ALLAH. We fulfilled our entire task which has been assigned to us.
We worked hard to achieve our goal in beginning it was a huge question of how to
do it and how to conquer this mountain but yes we did it. The project i-Talk solves
all the communication concerned it works by converting analog voice signal into
digitized data packets. The packets are sent out across the internet the same way
as any other IP packets, using the internet’s TCP/IP protocol
Faculty of CS&IT, Superior University Lahore, Pakistan iv

Acknowledgements
We praise to almighty Allah who showers the choicest of his blessing to all those have taken
part in the making of this project.
This project when assigned to us was a big challenge for us to accomplish, because we haven’t
done any project of this kind so far. By the grace of Allah we were to accomplish this task quiet
efficiently that was a great experience for us and it will also help us in our future. We
would like to confiscate this opportunity to do our best to give credit where it is used. First and
foremost to our parents, whose prayers and advices throughout our educational career has
brought us to this in life where we are completing our graduation.
Second thanks goes to our project supervisor Mr. Amjad Mukhrar who helped and guided us in
this project and for his continuous support regarding the various aspects of our project. Last but
not the least Sir Muhammad Aqeel for contiguous guide lines and support.
Faculty of CS&IT, Superior University Lahore, Pakistan v

Executive Summary
The primary goal of this project is to implement VoIP (voice over IP) based communication
system with high performance and cost effective. The main focus of this project is to is handle
incoming calls of the business for sales and after sales support in an efficient manner along with
internal communication. By implementation of Elastix VoIP solution we will be able to receive
all the incoming calls to a single centeral DDIN (Direct Dial In Number). Which would be UAN of
the company. All calls will land to an IVR (interactive voice response) and will be forwarded to
the concern department as selected by the caller. After selection made by caller call will be
queued in the concern department. And will be serve by the first available agent. For quality
assurance purposes all calls will be recorded.
Faculty of CS&IT, Superior University Lahore, Pakistan vi

Table of Contents
Dedication .......................................................................................................................................iv
Acknowledgements..........................................................................................................................v
Executive Summary.........................................................................................................................vi
Table of Contents ........................................................................................................................... vii
List of Figures .................................................................................................................................. ix
List of Tables ....................................................................................................................................x
Chapter 1......................................................................................................................................... 1
Introduction .................................................................................................................................... 1
1.1. Background....................................................................................................................... 2
1.2. Motivations and Challenges ............................................................................................. 3
1.3. Goals and Objectives ........................................................................................................ 3
1.4. System Scop ...................................................................... Error! Bookmark not defined.
1.5. Benefits of VoIP ................................................................. Error! Bookmark not defined.
1.6. Proposed Solution ............................................................................................................ 4
1.7. Project Plan ...................................................................................................................... 5
1.7.1. Work Breakdown Structure .......................................................................................... 5
1.7.2. Roles & Responsibility Matrix ....................................................................................... 5
1.7.3. Gantt Chart ................................................................................................................... 5
1.8. Report Outline .................................................................................................................. 5
Chapter 2......................................................................................................................................... 6
Software Requirement Specifications ............................................................................................ 6
2.1. Introduction....................................................................... Error! Bookmark not defined.
2.1.1. Purpose .......................................................................... Error! Bookmark not defined.
2.1.2. Document Conventions ................................................. Error! Bookmark not defined.
2.1.3. Intended Audience and Reading Suggestions ............... Error! Bookmark not defined.
2.1.4. Product Scope ................................................................ Error! Bookmark not defined.
2.1.5. References ..................................................................... Error! Bookmark not defined.
2.2. Overall Description ............................................................ Error! Bookmark not defined.
2.2.1. Product Perspective....................................................... Error! Bookmark not defined.
2.2.2. Product Functions .......................................................... Error! Bookmark not defined.
2.2.3. User Classes and Characteristics ................................... Error! Bookmark not defined.
2.2.4. Operating Environment ................................................. Error! Bookmark not defined.
2.2.5. Design and Implementation Constraints ................................... Error! Bookmark not defined.
Faculty of CS&IT, Superior University Lahore, Pakistan vii

2.2.6. User Documentation ..................................................... Error! Bookmark not defined.

2.2.7. Assumptions and Dependencies ................................... Error! Bookmark not defined.
2.3. External Interface Requirements ...................................... Error! Bookmark not defined.
2.3.1. User Interfaces............................................................... Error! Bookmark not defined.
2.3.2. Hardware Interfaces ...................................................... Error! Bookmark not defined.
2.3.3. Software Interfaces ....................................................... Error! Bookmark not defined.
2.3.4. Communications Interfaces ........................................... Error! Bookmark not defined.
2.4. System Features ................................................................ Error! Bookmark not defined.
2.4.1. System Feature 1 ........................................................... Error! Bookmark not defined.
2.4.1.1. Description and Priority ............................................. Error! Bookmark not defined.
2.4.1.2. Stimulus/Response Sequences .................................. Error! Bookmark not defined.
2.4.1.3. Functional Requirements ........................................... Error! Bookmark not defined.
2.4.2. System Feature 2 ........................................................... Error! Bookmark not defined.
2.4.2.1. Description and Priority ............................................. Error! Bookmark not defined.
2.4.2.2. Stimulus/Response Sequences .................................. Error! Bookmark not defined.
2.4.2.3. Functional Requirements ........................................... Error! Bookmark not defined.
2.4.3. System Feature 3 (and so on) ........................................ Error! Bookmark not defined.
2.5. Other Nonfunctional Requirements ................................. Error! Bookmark not defined.
2.5.1. Performance Requirements .......................................... Error! Bookmark not defined.
2.5.2. Safety Requirements ..................................................... Error! Bookmark not defined.
2.5.3. Security Requirements .................................................. Error! Bookmark not defined.
2.5.4. Software Quality Attributes ........................................... Error! Bookmark not defined.
2.5.5. Business Rules................................................................ Error! Bookmark not defined.
2.6. Other Requirements.......................................................... Error! Bookmark not defined.
Chapter 3....................................................................................................................................... 13
Use Case Analysis .......................................................................................................................... 13
3.1. Use Case Model .............................................................................................................. 14
3.2. Fully Dressed Use Cases ................................................................................................. 15
Chapter 4....................................................................................................................................... 17
System Design ............................................................................................................................... 17
4.1. Architecture Diagram ..................................................................................................... 18
4.2. Domain Model ................................................................................................................ 18
4.3. Entity Relationship Diagram with data dictionary ......................................................... 18
4.4. Class Diagram ................................................................................................................. 19
4.5. Sequence / Collaboration Diagram ................................................................................ 19
4.6. Operation contracts ....................................................................................................... 19
4.7. Activity Diagram ............................................................................................................. 20
4.8. State Transition Diagram................................................................................................ 20
4.9. Component Diagram ...................................................................................................... 20
4.10. Deployment Diagram.................................................................................................. 21
4.11. Data Flow diagram [only if structured approach is used - Level 0 and 1] .................. 21
Chapter 5....................................................................................................................................... 22
Implementation ............................................................................................................................ 22
5.1. Important Flow Control/Pseudo codes .......................................................................... 23
Faculty of CS&IT, Superior University Lahore, Pakistan viii

5.2. Components, Libraries, Web Services and stubs ........................................................... 23

5.3. Deployment Environment .............................................................................................. 23
5.4. Tools and Techniques ..................................................................................................... 24
5.5. Best Practices / Coding Standards.................................................................................. 24
5.6. Version Control .............................................................................................................. 24
Appendices.................................................................................................................................... 25
Appendix A: Information / Promotional Material ........................................................................ 26
Reference and Bibliography .......................................................................................................... 29
Index.............................................................................................................................................. 31
List of Figures
1.1 Caption of first figure of first chapter 6

1.2 Caption of second figure of first chapter 7
2.1 Caption of first figure of second chapter 14
2.2 Caption of second figure of second chapter 22
2.3 Caption of third figure of second chapter 26
5.1 Caption of first figure of fifth chapter 49
5.2 Caption of second figure of fifth chapter 49
Faculty of CS&IT, Superior University Lahore, Pakistan ix

List of Tables
1.1 label of first table of first chapter 6

1.2 label of second table of first chapter 7
2.1 label of first table of second chapter 14
2.2 label of second table of second chapter 22
2.3 label of third table of second chapter 26
5.1 label of first table of fifth chapter 49
5.2 label of second table of fifth chapter 49
Faculty of CS&IT, Superior University Lahore, Pakistan x

Faculty of CS&IT, Superior University Lahore, Pakistan xi

Chapter 1
Introduction
Chapter 1: Introduction
Voice over IP (Voice over Internet Protocol or "VoIP") technology converts voice calls from analog to digital
to be sent over digital data networks. Voice over IP (VoIP) defines a way to carry voice calls over an IP
network including the digitization and packetization of the voice streams. IP Telephony utilizes the VoIP
standards to create a telephony system where higher-level features such as advanced call routing, voice
mail, contact centers, etc., can be utilized.
Voice over IP is revolutionizing the world of communications. It allows you to make and receive phone calls
over the Internet and IP networks for much cheaper than with the traditional landline phone network. It
also makes your communication experience much richer and nicer with a series of enhanced features and
extended possibilities. Here is what you need to know to get started.
Phone calls from a regular home phone are made using the public switched telephone network (the PSTN).
When you pick up the receiver and hear a dial tone, you have access to a line on the network. The line stays
open between you and the person you are calling until the end of the call VoIP calls don’t use the phone
network. They route calls via the internet. To send voice across the internet, the voice information is coded
into a digital format and transmitted in packets of information in the form of data. The data packets are
then sent across the internet and reassembled into sound at the other end for the receiver to hear.
1.1. Background
Voice communication is a complete method or procedure in which two entities over a distance make
conversation with each other. In early days, voice is transferred from one entity to other, in its original
analog form, with the help of analog devices end to end. To make use of last mile efficiently and to
introduce other services with voice, new architecture was introduced. In this architecture digital devices
were began to use end to end, including voice was also carried to other end in digital form. This digital
supported architecture of voice, introduced new services like CLI (Caller Line Identification) etc.
Up till this architecture, voice was considered as a special service and dedicated circuits were used for
voice service in the provider core. With the continuous increase in the usage of internet, it was getting
Faculty of CS&IT, Superior University Lahore, Pakistan 2

difficult for service providers to maintain two different cores, circuit switch core for voice and packet switch
core for data services.
Evolution takes places in the field of communication, when traditional voice systems analog/digital were
replaced by IP based voice communication. For IP based voice communication model, same packet
switched core is being used as for data service, but to overcome the unacceptable delays in voice
communication in packet switch core, certain QOS is implemented to identify and prioritize voice packets.
This IP based voice communication model is termed as VOIP (Voice over Internet Protocol). This
communication model has new standards and uses its own signaling protocol, which are different from
traditional voice systems. Initially VOIP uses H.323 protocol for its signaling, but this protocol was not much
stable, due to which implementation of VOIP in the industry was denied [6].
With introduction of SIP protocol, VOIP domain gets much disable and traditional analog/digital systems
started to migrate over VOIP. SIP protocol got much popular in industry, due to its stability and additional
features.
1.2. Motivations and Challenges

[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]
1.3. Goals and Objectives

1.3.1 Goal
Lower Costs of Service – Since it is at the top of most lists, let’s start with saving money! The
charge structures for VoIP providers come in many shapes and sizes, however it is not uncommon
for a VoIP phone service to save a business 20 to 40 percent on their monthly phone bill. Many
offer all distance calling programs, so if you have a high amount of long distance calls, your savings
will be higher.
1.3.2 Objectives
1) Users will be able to communicate effectively, speedily and most importantly,
securely there b y enhancing the privacy and confidentiality o f mobile communication.

2) Implementing voice encryption on third generation GSM data which would in turn result
in a better encrypted voice speed and clarity.
3) The configuration and usage of proxy server (SIP / Asterisk) thro ugh defining call
routing and handset registration mechanisms.
4) It will en able the users to communicate with each other in an encrypted fashion.
1.4. System Scope

This system works on the VoIP protocol. The technology establishes call and sends/receives data over
existing internet network using IP protocol. SIP is the application layer protocol, a signaling protocol which
is used for establishing multimedia session over IP network in the internet telephony process.
1.5. Benefits of VoIP

The VoIP system offers UofL many benefits as a replacement for its current telephone technology:
(i) VoIP uses a single communications network for both telephones and computers instead of the
separate phone and computer networks that are prevalent today
(ii) VoIP uses programmable sets that provide new features, applications and capabilities such as
allowing the university to quickly relay alerts or messages to all locations.
(iii) VoIP makes it easy to administer the system and individual features can be configured through a
simple web interface.
(iv) The IP phones can access the university phone directory, allowing users to find the most up
to-date telephone numbers right on their phones.
(v) Using VoIP positions the university for future technologies and future needs of students,
faculty, and staff.
1.6. Proposed Solution

1.7. Project Plan

1.7.1. Work Breakdown Structure

1.7.2. Roles & Responsibility Matrix

1.7.3. Gantt Chart

1.8. Report Outline


Chapter 2
System Requirement &
Specifications

Chapter 2: System Requirement & Specifications
2.1. Hardware Requirements
“Up to 16 sim calls”
CPU Intel® Core™ i3-3210 Processor (3M Cache, 3.20 GHz)
Memory 2 GB
HDD SATA 30GB
Can be Virtualized Yes
NETWORK 100/1000 Mbit/s
“Up to 64 Simultaneous Calls”
CPU Intel® Core™ i3-3210 Processor (3M Cache, 3.20 GHz)
Memory 4 GB
HDD SATA 60GB
Can be Virtualized Yes
NETWORK 100/1000 Mbit/s
“Up to 256 Simultaneous Calls”
CPU Intel® Core™ i7-3770 Processor (8M Cache, up to 3.90 GHz)
Memory 8-10 GB

HDD SATA 100GB
Can be Virtualized Yes, requires v15
NETWORK 1Gbit/10Gbit
“Up to 1,024 Simultaneous Calls”
CPU Intel Xeon CPU - E5405 2.00 Ghz 2.00 Ghz 2 Processors
Memory 16 GB
HDD SATA 500GB
Can be Virtualized Yes, requires v15
NETWORK 1Gbit/10Gbit
2.2 Project Components
2.2.1 Linux
It is an open source Operating system, originally designed for Intel x-86 based PC. It is mostly used as
Operating system for some sort of servers and for Mainframe or supercomputers. Its usage as server and
for scientific purpose is its open source feature due to which, any person can modify its code according to
its needs. Its primary source code after modification can be launched commercially or non-commercially,
but under the licenses of GNU (General Public License).
Linus Operating System was first created by a professor, which was only for the purpose of class based
teaching. That simplified version of Linux was named as MINIX and was only used personally.
After few years in 1991, keeping this basic MINIX personal version in notice, a computer science student

Linus Torvalds in university of Helsinki, developed the first kernel of Linux. It was then licensed under GNU
(General Public License) and was launched with version of 0.0.1.
The GNU (General Public License) was only to ensure that Linux is a free Operating system, with open
source code, allowing modification for any purpose. After this commercialization Linux was began to use
everywhere, from mainframe computers to servers and from servers to mobile applications. Even that
Linux was began to use for the development of protocols used in different technologies.
In start Linux was available only in CLI mode, but after few years of modifications. Its GUI versions are also
available. Linux Operating System was written in C programming and uses GNU (General Public License)
tools, which are freely available to handle any Operating System. Linux then began to use to build the BIOS
of Laptop or Desktop PC, to boot the system even if system has Windows Operating System is being
installed in PC.
Other uses of Linux include, mobile device Operating System and application development. Due to user
friendly behavior, reliability, high security and high availability feature, it allows scientist to develop cloud
computing technology, which was then launched using Linux Operating System in it.
The communication technology is highly dependent on this Operating system as the Operating systems of
communication devices are developed over Linux. The communication protocols are also coded in some
sort of Linux flavor. The popular Web services like Facebook, Twitter, Linked-In, You-Tube and Google all
rely on Linux Operating system [3].
There are multiple flavors of Linux Freely Available, some flavors are available with full features, while
some have few license restrictions for their additional features. List of Linux Flavors are mentioned below:
 Red Hat
 CentOS
 Ubuntu
 Debian
 Fedora
 Gentoo
 Linux Mint
 Kali Linux
 Back Track
Including these mentioned flavors few others may be available. All these flavors are used for different

purpose and are developed by modifying the source code of Linux to add special features. In our project
we are using CentOS, because it was developed to use for the purpose of communication systems.
2.2.3 CentOS
Cento (Community Enterprise Operating System) was released in May, 2004 and is based upon kernel of
Linux, which means that it was derived completely from RHEL (Red Had Enterprise Linux). It is free version
of secure and stable RHEL (Red Had Enterprise Linux), preferred to be used as Operating system for
Servers. In 2006, Tao Linux another flavor of RHEL (Red Had Enterprise Linux), completely merged into
CentOS. All the user of Tao Linux were announced to move to CentOS using “yum update” command.
Later in 2014, RHEL (Red Had Enterprise Linux) announced to sponsor CentOS project, for creating a well-
designed platform according to needs of open source developers. After this sponsor ship CentOS was
available with paid subscription service and this paid subscription includes access to software updates and
technical support at different levels.
CentOS is totally free to use for everyone and if you want free support there are lots of blogs where people
discuss their problems and authentic solutions are presented there [4].
Goals of Open Source CentOS:
 Easily maintained solution creation.
 Everlasting support for Core.
 Free and open business model.
 Open infrastructure.
 Policy for open management.
Processor Architectures Supported by CentOS:

 Supports x86 based processor architectures.
 32-Bits with PAE (Physical Address Extension).
 64-Bits AMD and Intel's EM64T.
 64-Bits Intel Itanium processor (CentOS 3 and Later versions).
 IBM eServers and Z-Series (till CentOS 5).
 Alpha (CentOS 4 only).

2.2.3 Elastic
Elastix is launched as open source platform to build applications for communication. When installed on a
single PC it changes it to act as a communication control server. It was developed in 1999 by mark spencer
for the purpose to implement PBX (Private Branch Exchange) also known as Asterisk. It can also be
customized to build solutions like VoIP gateways and conference control servers. Different organizations
like call centers, carriers, offices and even government agencies are using Asterisk on large scale.
It’s an open source application, Most of the features needed in communication are already built-in it
application, but you want to add some new features, you can easily add them by modifying the source
code in Linux Operating System [5]. Elastix also includes integration with other applications like
 Radius server for the purpose of user authentication and accounting.
 SQL database to maintain call detail records.
 Web applications like PHP and Apache for management through GUI web interface.
2.2.4 Voice over IP (VoIP)
Voice communication is a complete method or procedure in which two entities over a distance make
conversation with each other. In early days, voice is transferred from one entity to other, in its original
analog form, with the help of analog devices end to end. To make use of last mile efficiently and to
introduce other services with voice, new architecture was introduced. In this architecture digital devices
were began to use end to end, including voice was also carried to other end in digital form. This digital
supported architecture of voice, introduced new services like CLI (Caller Line Identification) etc.
Up till this architecture, voice was considered as a special service and dedicated circuits were used for
voice service in the provider core. With the continuous increase in the usage of internet, it was getting
difficult for service providers to maintain two different cores, circuit switch core for voice and packet
switch core for data services.
Evolution takes places in the field of communication, when traditional voice systems analog/digital were
replaced by IP based voice communication. For IP based voice communication model, same packet

switched core is being used as for data service, but to overcome the unacceptable delays in voice
communication in packet switch core, certain QOS is implemented to identify and prioritize voice packets.
This IP based voice communication model is termed as VOIP (Voice over Internet Protocol). This
communication model has new standards and uses its own signaling protocol, which are different from
traditional voice systems. Initially VOIP uses H.323 protocol for its signaling, but this protocol was not
much stable, due to which implementation of VOIP in the industry was denied [6].
With introduction of SIP protocol, VOIP domain gets much disable and traditional analog/digital systems
started to migrate over VOIP. SIP protocol got much popular in industry, due to its stability and additional
features.
2.2.5 Session Initiation Protocol (SIP)

It is a communication enabled protocol used for handling multimedia communication. The common usage
of SIP is in IP telephony for voice and video communication between to end points. It allows us to use data
networks for voice communication enabling voice of IP networks domain [7]. This application layer
protocol is used for the following three purpose in voice domain:
Session creation
Session modification
Session termination
During a complete voice communication between two end point entities SIP behaves in multiple ways,
such as: when number is dialed or call is generated SIP act as a signaling protocol.
When two communication entities are in call, SIP behave as media control protocol, where it is allocating
media to users and monitoring the session for call records. When call is terminated it again behaves as a
signaling protocol [8].

Chapter 3
Use Case Analysis

Chapter 3: System Analysis

[Between 4 to 8 lines describe what is this chapter all about]
3.1. Use Case :1

VoIP on the campus:
• Instead of a traditional (TDM) PBX, a VoIP-based iPBX dispatches all telefphone traffic
• Telephones are connected to the iPBX through the institutional LAN
• Calls destined outside the campus are carried over ISDN30
•Using existing LAN
•Easy to work from home (VPN necessary)

3.2. Use Case : 2

VoIP between locations
Instead of sending calls between different locations of one institution ISDN, this can be done over VoIP
over VPN.
• 2a If the institution has PBXs
•2b If the institution has a iPBX

• Role:
– None
– Optional: consulting
• Impact
– Availability of the network should be high
– Network should be collision free
(so have low latency and jitter)
• Case 2a for institution:
– Investment: 2x gateway
– Maintenance cost (low)
– Savings: inter-location call costs
• Case 2b for institution:
– Savings: inter-location call costs

Chapter 4
System Design

Chapter 4: System Design

4.1. Architecture Diagram

4.2. Domain Model

4.3. Entity Relationship Diagram with data dictionary


4.4. Class Diagram

4.5. Sequence / Collaboration Diagram

4.6. Operation contracts


4.7. Activity Diagram

4.8. State Transition Diagram

4.9. Component Diagram


4.10. Deployment Diagram

4.11. Data Flow diagram [only if structured approach is used - Level 0 and 1]

Chapter 5
Implementation

Chapter 5: Implementation
5.1. Important Flow Control/Pseudo codes

5.2. Components, Libraries, Web Services and stubs

5.3. Deployment Environment


5.4. Tools and Techniques

5.5. Best Practices / Coding Standards

5.6. Version Control


Appendices

Appendix A: Information / Promotional Material

[Between 4 to 8 lines describe what is this appendix all about]
A.1. Broacher
A.2. Flyer
A.3. Standee
A.4. Banner

A.5. First Level heading [16 pt, Calibri, Bold, Left aligned]
A.5.1. Second level heading [14 pt, Calibri, Bold, Left aligned]
A.1.1.1. Third level heading [12 pt, Calibri, Bold, Left aligned]

Appendix [no.]: Appendix Title

A.1. First Level heading [16 pt, Calibri, Bold, Left aligned]
A.1.1. Second level heading [14 pt, Calibri, Bold, Left aligned]
A.1.1.2. Third level heading [12 pt, Calibri, Bold, Left aligned]

Reference and
Bibliography

Reference and Bibliography
[1] M. Sher, M. Rehman, “Title of the Paper” Conference name/Journal Name, Edition, Volume, Issue,
ISBN/ISSN, PP, Publisher/City-Country, Year.
[2] ……

Index

Index
[A]
[B]
[C]



ITalk Project Report

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

ITalk Project Report

Caricato da

Copyright:

Formati disponibili

SUPERIOR UNIVERSITY LAHORE

Faculty of Computer Science & IT

Final Year Project

Project ID: [write ID here Issued by FYP Manager]

Mr. Amjad Mukhtar

Faculty of CS&IT, Superior University Lahore, Pakistan ii

HEAD OF THE DEPARTMENT

Faculty of CS&IT, Superior University Lahore, Pakistan iii

Faculty of CS&IT, Superior University Lahore, Pakistan iv

Faculty of CS&IT, Superior University Lahore, Pakistan v

Faculty of CS&IT, Superior University Lahore, Pakistan vi

Faculty of CS&IT, Superior University Lahore, Pakistan vii

2.2.6. User Documentation ..................................................... Error! Bookmark not defined.

Faculty of CS&IT, Superior University Lahore, Pakistan viii

5.2. Components, Libraries, Web Services and stubs ........................................................... 23

1.1 Caption of first figure of first chapter 6

Faculty of CS&IT, Superior University Lahore, Pakistan ix

1.1 label of first table of first chapter 6

Faculty of CS&IT, Superior University Lahore, Pakistan x

Faculty of CS&IT, Superior University Lahore, Pakistan xi

Faculty of CS&IT, Superior University Lahore, Pakistan 2

1.2. Motivations and Challenges

1.3. Goals and Objectives

Faculty of CS&IT, Superior University Lahore, Pakistan 3

1.4. System Scope

1.5. Benefits of VoIP

1.6. Proposed Solution

Faculty of CS&IT, Superior University Lahore, Pakistan 4

1.7. Project Plan

1.7.1. Work Breakdown Structure

1.7.2. Roles & Responsibility Matrix

1.7.3. Gantt Chart

1.8. Report Outline

Faculty of CS&IT, Superior University Lahore, Pakistan 5

Faculty of CS&IT, Superior University Lahore, Pakistan 6

Chapter 2: System Requirement & Specifications

2.1. Hardware Requirements

“Up to 16 sim calls”

CPU Intel® Core™ i3-3210 Processor (3M Cache, 3.20 GHz)

HDD SATA 30GB

Can be Virtualized Yes

NETWORK 100/1000 Mbit/s

“Up to 64 Simultaneous Calls”

CPU Intel® Core™ i3-3210 Processor (3M Cache, 3.20 GHz)

HDD SATA 60GB

Can be Virtualized Yes

NETWORK 100/1000 Mbit/s

“Up to 256 Simultaneous Calls”

CPU Intel® Core™ i7-3770 Processor (8M Cache, up to 3.90 GHz)

Faculty of CS&IT, Superior University Lahore, Pakistan 7

HDD SATA 100GB

Can be Virtualized Yes, requires v15

“Up to 1,024 Simultaneous Calls”

HDD SATA 500GB

Can be Virtualized Yes, requires v15

2.2 Project Components

Faculty of CS&IT, Superior University Lahore, Pakistan 8

Faculty of CS&IT, Superior University Lahore, Pakistan 9

Processor Architectures Supported by CentOS:

Faculty of CS&IT, Superior University Lahore, Pakistan 10

2.2.4 Voice over IP (VoIP)

Faculty of CS&IT, Superior University Lahore, Pakistan 11

2.2.5 Session Initiation Protocol (SIP)

Faculty of CS&IT, Superior University Lahore, Pakistan 12