[cisco-voip] How does RIS function

[Wes Sisk]

This is rather detailed information that is not published for a reason - 
namely it is subject to change.  Can you help us to understand your need 
of this information?  Most of the time this information should be 
retrieved using AXL Serviceability interface rather than by any direct 
query to RIS.

Generically the architecture is:
ccm process and ris process run locally on a the same CM node. When ccm 
starts it allocates a shared memory segment.  ccm updates that shared 
memory segment with registration information.  ris reads this shared 
memory segment and makes available to serviceability interfaces.

Beyond that details vary across versions.

/Wes

On Friday, July 31, 2009 7:54:32 AM , Subhrojyoti Banerjee 
<subhrojyoti at hotmail.com> wrote:
> Hi All,
>
> In a cluster where we have 1 PUB and 7 SUB's, how does RIS work? Is it 
> a mesh of information from "All-to-All" or is there a "Primary 
> Provider" to which all other servers connect? Who is the primary 
> provider, and what is the selection criteria? I read something about 
> SSAPI Master and a selection criteria of the highest CTI ID but would 
> like to get that validated. If anyone can throw some light on this it 
> would be fantastic.
>
> In addition is also had few other queries which are co-related-
>
> 1. Where is this RIS database located? Is it in the memory of the 
> respective servers, or is it located on only one server in a cluster 
> and all other servers pull information from it? I don't think this is 
> part of SQL (prior to 5.x) database.
> 2. Where are the dynamic and static tables of RIS stored? Who gets to 
> use the “RIS Cluster TCP port” of 2555 in a cluster and who is the 
> “Primary Collector”? (These things can be found in the Service 
> Parameters page for RIS).
>
>
> Thanks in advance,
>
> Regards,
>
> Subhrojyoti Banerjee
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090731/6cc85c05/attachment.html>