Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

RFC 3261 – Session Initiation Protocol (SIP);

RFC 5341 – The Internet Assigned Number Authority (IANA) Uniform Resource Identifier (URI) Parameter Register

RFC 3265 – Especific Event Notification;

RFC 4028 – SIP Session Timer;

RFC 3262 – Reliability for Provisional Responses in the SIP;

RFC 3550 – RTP: A Transport Protocol for Real-Time Applications

RFC 3711 – The Secure Real-Time Transport Protocol (SRTP);

RFC 2327 – SDP: Session Description Protocol;

RFC 4733 – RTP Payload for DTMF Digits, Telephone Tones and Telephone Signals;

RFC 3264 – An Offer/Answer Model with SDP;

RFC 2959 – Real-Time Transport Protocol (RTP) Management Information Base;;

RFC 3266 – Support for IPv6;

RFC 3551 – RTP Profile for Audio and Video Conferences with Minimal Control;

RFC 6157 – IPv6 Transition in the SIP;

RFC 3389 – RTP Payload for Comfort Noise (CN);

RFC 3515 – SIP Refer Method;

RFC 3486 – Compressing the SIP;

RFC 3891 – SIP Replaces Header;

RFC 3856 – A Presence Event Package for the SIP;

RFC 3263 - SIP: Locating SIP Servers;

RFC 3892 – SIP Referred-by;

RFC 2474 – Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers;

RFC 5389 – Session Traversal Utilities do NAT (STUN);

RFC 2475 – An Architecture for Differentiated Services;

RFC 5766 – Traversal Using Relays around NAT – TURN;

RFC 2597 – Assured Forwarding PHB Group;

RFC 6086 – SIP INFO Method and Package Framework;

RFC 3246 – An Expedited Forwarding PHB;

RFC 3311 – SIP UPDATE Method;

RFC 2507 – IP Header Compression;

RFC 5359 – SIP Service Examples;

RFC 2508 – Compressing IP/UDP/RTP Headers for Low-Speed Serial Links;

RFC 3325 – Private Extensions to the SIP;

RFC 7235 – Hypertext Transfer Protocol (HTTP/1.1): Authentication;

RFC 3323 – A Privacy Mechanism for SIP;

RFC3702 – Authentication, Authorization, and Accounting Requirements for the SIP.

RFC 3581 – A Extension to the SIP for Symmetric Response Routing;

A plataforma pode ser utilizada para trabalhar em múltiplos domínios com modelos de tarifação pós e pré-pago, de forma independente. A condição de multidomínio permite a criação de partições lógicas do sistema segregando assinantes de diferentes clientes corporativos, ou em uma operação privada, de diferentes departamentos/organizações.

...