[VOIPSEC] SBC functions

[Christopher A. Martin]

Just a quick blurb with my 2 cents...

MIDCOM is a joke...trust the endpoints...Ha!  :)

Seriously though, SBC's being decomposed like this will serve to provide
a level of scalability to the media endpoints by implementing the
signaling elements much like an SIP Edge Proxy implementation (and they
are typically deployed in mirrored pairs).

These signaling "Directors" will have a knowledge configured in them
about all media endpoints and will also have a perception about the
availability of the remote endpoints, in theory.

That's all for now.
Chris

-----Original Message-----
From: Voipsec-bounces at voipsa.org [mailto:Voipsec-bounces at voipsa.org] On
Behalf Of Nhut Nguyen
Sent: Thursday, June 02, 2005 9:14 AM
To: Voipsec at voipsa.org
Subject: [VOIPSEC] SBC functions

Hello All,

 

In a recent webinar, it was said that ultimately SBC functions will be
decomposed to two parts: media and signaling, with one signaling
function box will control multiple media function boxes, using a MIDCOMM
protocol (e.g. H.248, COPS, SNMP). So what people think about these
questions?

 

1.	What are the good, bad and ugly things about this?
2.	Any potential major performance issues with this architecture?

 

Any thought?

 

Nhut

_______________________________________________
Voipsec mailing list
Voipsec at voipsa.org
http://voipsa.org/mailman/listinfo/voipsec_voipsa.org