Standard RFC documents
You can read on this page what kind of standard protocols needed to use to make VoIP calls. You find bellow RFC documents what defines these protocols.
-
RFC 3265:
Session Initiation Protocol (SIP) - Specific Event NotificationThis document describes an extension to the Session Initiation Protocol (SIP). The purpose of this extension is to provide an extensible framework by which SIP nodes can request notification from remote nodes indicating that certain events have occurred. Learn more...
-
RFC 3489:
STUN - Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs)This document defines STUN protocol. STUN is a lightweight protocol that allows applications to discover the presence and types of NATs and firewalls between them and the public Internet. Learn more...
-
RFC 3725:
Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP)This document discusses best current practices for the usage of SIP for third party call control. Third party call control refers to the ability of one entity to create a call in which communication is actually between other parties. Learn more...
-
RFC 3842:
A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP)This document describes a Session Initiation Protocol (SIP) event package to carry message waiting status and message summaries from a messaging system to an interested User Agent. Learn more...
-
RFC 3856:
A Presence Event Package for the Session Initiation Protocol (SIP)This document describes the usage of the Session Initiation Protocol (SIP) for subscriptions and notifications of presence. Presence is defined as the willingness and ability of a user to communicate with other users on the network. Learn more...
-
RFC 3920:
Extensible Messaging and Presence Protocol (XMPP): CoreThis memo defines the core features of the Extensible Messaging and Presence Protocol (XMPP), a protocol for streaming Extensible Markup Language (XML) elements in order to exchange structured information in close to real time between any two network endpoints. Learn more...
More information