database replication in cluster

[karthik ratna]

hi all,

i was confused about pub and sub replications

for example , i have one pub and 2 sub

when i need to add new IP phone ,   is it possible to add in sub or i must need to add in pub

As pub has read/write permissions , where has sub has ready only

as for my understanding , when we add new ip phone to pub ,it replicated to sub using IDS , and as phone get configuration files form tftp , in tftp we have ips of cm group  , so when it it is registered to sub ip ,  in phone cofiguration page it shows registered with sub ip

so total cluster will know about that phone

Is my thinking is correct ?

please guide me , i was very new to this world

Thanks for helping in advance

karthik

[Joseph Martini · Accepted solution]

Here's a good document on replication: https://supportforums.cisco.com/docs/DOC-13672.

As for your question you can add phones from the subscriber.  What will happen when you add a phone is a change notification is triggered which will reach the publisher, updated it's database, and then a database update notification is sent to the subscribers to update their databases to match the publisher.  In newer versions of call manager user facing features as you'll see in the above document such as CFA and MWI can be updated in the subscribers database even when the publisher is down.  However in normal operation change notifications cause the publisher to update and then the updated database entry is propagated to the subscribers.

[karthik ratna]

hi joemar,

thanks for your quick response

when database is replicated to sub , so when we add phone to one of the sub , is their any possible to check the added phone from another sub ?

when we make the call from one phone to another phone in another phone , signaling will pass from pub or sub-sub ?

Thanks

Karthik

[Joseph Martini]

You can check that the phone added on one subscriber was added to the other from the command line with "run sql select * from device where name like 'SEP'" so that the local database is queried and you should see the phone returned. 

When you make a call from one phoneA registered to subA to another phoneB registered with subB, the signaling is from phoneA to subA then from subA to subB, then from subB to phoneB.  Signaling typically only travels through servers that the devices are registered to.  If nothing is registered to the publisher the signaling usually won't go through the publisher.  One thing to remember is that route lists register too, and signaling can go through other servers depending on H323 gateway dial peer configuration.