Telecom Tech Source

Below is the video where I have demonstrated how exactly a Peer-to-Peer SIP Call looks like. I also emphasized enough glossary which helps in understanding the basic SIP call flow. Hope this helps! Please provide your comments if any. Thanks, Raj https://telecomtechsource.blogspot.com

As a part of Learning SIP, in the last post I did demonstrate on a Basic Call Flow of SIP. Today, I am going to take you through the SIP System Architecture. SIP is a revolution in this modern world of communications. Rather I would say that SIP alone did not bring this change. That's where I would like to introduce SIP SYSTEM ARCHITECTURE. Each component of this architecture has contributed and made this drastic change in Telecom World. So, why wait! Lets go through the architecture and its components. SIP System Architecture SIP Endpoints: SIP Phones, SIP Soft clients running on PCs, mobiles etc. Proxy: This server accepts INVITE from any SIP endpoints and process the request. This is the server which decides whether the call need to terminated on to another SIP Endpoints (or) to another PBX (or) to PSTN. The routing decision would be taken by the logic written by Administration of this proxy server. It is purely for Session Management.

Alert: If you HATE long posts, stop reading and click here . The Session Initiation Protocol, a VoIP protocol, used for originating and termination of media sessions like voice, video, IM, presence etc. Before we enter into the more technical details of SIP, let's refresh our basic telecom VoIP skills. I'd like to insist here that SIP is a signalling protocol, its NOT a media protocol -- which means it is a set of rules use to control the signaling part of a media session. It doesn't have any control on media. So let's not wait to start the basic call flow of SIP. Key terms: It is important to familiarize with these terms in order to understand basic SIP call flow. Here are few of them: Call flow : It's a flow diagram of SIP messages -- shows an ideal way how a media session carried over two endpoints. Its a must know thing and will be useful for your troubleshooting as well. Endpoint: Any device which is used to originate and terminate

             The Communication Manager is the Private Branch Exchange [PBX] branded by Avaya. You'll find lot more details whenever you do search on Google. So, you do not need me in explaining the same stuff here. But, I am here to explain MY WAY of understanding about Avaya CM. Lets talk about each component of the image in detail.  Here you go! Summary: * CM is running as an application inside the Linux OS (Red Hat Enterprise Linux) * There are other applications in the Linux help for CM not running within CM * CM is different than Server. CM means the call processing software with Linux where as Server means Platform+CM+other applications * Shell prompt: You can not administer CM features etc * Autosat prompt: You can not perform Linux stuff such as busy-out a server, reboot etc Thanks, Raj