[VoiceOps] Session Border Controllers

[Simon Perreault]

Also see RFC 5853.

http://tools.ietf.org/html/rfc5853

Simon

Le 2013-02-19 21:34, Mark R Lindsey a écrit :
> But, Grant, Beware: You're using a term "Session Border Controller" but only talking about the call routing function. When the Big Three (Acme Packet, Metaswitch, and Sonus) use this term, "SBC", they're referring to all of these functions:
>
> 	-- Ability to gracefully single-source and distributed handle attacks from the Internet
>
> 	-- Traffic from numerous VRFs (so that customer A's 10.0.0.1 is not the same as customer B's 10.0.0.1)
>
> 	-- Hosted NAT Traversal
>
> 	-- Transcoding media
>
> 	-- Lawful Intercept hooks
>
> 	-- Demultiplexed SIP trunks (so that each SIP "path" can come from a different IP address or port)
>
> 	-- Constraints like Calls-per-second or Concurrent-calls (so legitimate customers don't cause a failure)
>
> 	-- Failover from one SBC to another
>
> 	-- Distributed SBC models where one box handles signaling and many more handle media
>
> 	-- 802.1q VLAN tagging support
>
> 	-- Support for failover to BroadWorks-style registrar redundancy (where the mated registrar servers have distinct IP addresses)
>
> 	-- SNMP management
>
> 	-- Interworking SIP/UDP and SIP/TCP
>
> 	-- Jumbo SIP (SIP datagrams over 1300 bytes, out of compliance with RFC 3261)
>
> 	-- SIP/TLS and SRTP, and decryption thereof
>
> 	-- Configurable media management (to release media when possible, steer it through the SBC when not)