[hydra-dev] Architecture Diagram

[Ken Hunt]

Comments below...
Ken

----- Original Message -----
> From: "Nick Lewis" <Nick.Lewis at atltelecom.com>
> To: hydra-dev at lists.digium.com
> Sent: Monday, June 21, 2010 11:21:25 AM
> Subject: [hydra-dev] Architecture Diagram
> Ken
> 
> Could you please clarify for me a couple of queries regarding the
> Hydra Architecture Diagram
> 
> What is the difference between the "Bridging" channel service and the
> "Routing" telephony service?

I will start by pointing out that these are design concepts subject to change, but here is what we have in mind: 

Routing service - Supports routing a call through the system. For an invite, the Routing Service would identify and locate the destination endpoint(s), or perhaps application to process the call. The Routing Service might also be accessed at the end of a call, or to support a call transfer. Channel Services would register the endpoints that they manage with the Routing Service, so the Routing Service can do lookups between the various Channel Services. 

Bridging Service - Creates bridge objects, which are objects that track relationship among a group of 2 or more connected endpoints. A point-to-point call would result in a bridge with exactly two endpoints. A conference call would manage N endpoints. 
 
> Why are they not media services?

The Routing Service is primarily providing a lookup of registered endpoints, which isn't really a media operation. 

The Bridge objects created by Bridge Service would probably be involved in allocating Media Operations to support the participants in a session, but the media wouldn't necessarily flow through the Bridge. I think it's more likely the Bridge object is forwarding signaling information among the participants of the bridge. 

> 
> -- N_L