Professional Documents
Culture Documents
Submitted by: Chirag Golechha Gaurav Jain Neha Agarwal Priyanka Mahajan Shikha Vijay
Submitted to: Department of Computer Engineering University College of Engineering, RTU, Kota
Unified communication
NEED
To integrate different communication medium over one interface. To minimize communication response time or delay. One can send a message on one medium and receive the same message on another medium. Less bills to worry as all services from a single provider through a single number. To maximize work time.
Implementation architecture
STEPS OF IMPLEMENTATION
1. Establishment of SIP Proxy Server (openSIPS).
1.1 Configuration of User agent server. 1.2 Configuration of Proxy server. 1.3 Configuration of Redirect server. 1.4 Configuration of Location server.
1.VoIP Service
2.Mail Exchange Service
For VoIP service steps of implementation are :1. Configuration of scripting and routing. 2. Adding authentication. 3. Establishing a GUI for openSIPS.
4. Connecting to PSTN.
5. Integration of media services.
abc@rediffmail.com
Outgoing mail
Sent Mail
Web Browser
The main components of mail exchange service are:1. Fetch Mail :- Open source software used to retrive email from a remote POP3, IMAP mail server to mail transfer agent. 2. Mail Transfer agent (Postfix with SASL):- It handles receiving mails addressed directly to our machine, and sending it to the correct users mailbox, and sending mail out of the machine. SASL stands for simple authentication security layer. 3. Dovecot (IMAP and POP3 Server) :- It provides a way for mail user agents to access their mails. 4. Sqirrelmail :- It is a web mail package. 5. Browser interface
AUTHENTICATION
To authenticate SIP requests and save data such as location and alias tables we have to perform database based authentication using AUTH_DB module and to provide MySQL support we have to use DB_MySql module. The AUTH_DB module exports two functions:
When Open SIPS receives the REGISTER message, it checks for the existence of the Authorize header. If it is not found, it will challenge UAC for the credentials and exit. After being challenged, the UAC should send a REGISTER message with an Authorize header field.
The first INVITE with a reply containing a message, 407 Proxy Authentication Required. This message has the Authorize header field, containing information about the digest authentication, such as realm and nonce UAC replies with a new INVITE. Now, the Authorize header field contains the digest calculated using the username, password, realm, and nonce calculated using the MD5 algorithm.
DIGEST authentication
The digest scheme is a simple challenge-response mechanism. It challenges the UA using a nonce value. A valid response includes a checksum with all the parameters. Thus the password is never transmitted in plain text.
Client Interface
It offers follwing features: Voice call Video call Instant messaging Mail access