Calls between Publisher and Subscriber

[tziupa]

Hi all!,
This is my first message, hope to be lucky!

I have a Callmanager Cluster with two servers in the same group (Callmanager version: 4.3).
For load balancing purposes I defined two device pools with inverted server priority each other. This way, phones register equally on both servers and all of them can correctly get to PSTN through the gateway. By the way phones registered on one server can't make calls to phones registered on the other server.
Both device pools parameters are indentical with the only exception of the Callmanager Group with inverted priority with respect to the other Callmanager group.
When I try to make a call between phne registered on different servers I hear a fastbusy tone.

I hope the issue explanation is clear, maybe some of you already encountered such a problem.

Thanks to all!

 

[whykap]

If you cannot make calls from phones between servers then you have a database replication issue. Try a cluster reboot, starting with the publisher first, once it's completely up and running, reboot the sub.
I would also run the dbhelper tool on the pub (it's a downloadable plug in) which will tell you your replication status.

Be aware, as best practice per cisco, the publisher should have no devices registered to it at any point unless there is a failover situation. The publisher should be dedicated to database handling and replication.

 

[tziupa]

Hello whykap,

Many thanks for your kind answer. I'll try a cluster reboot and analyze possible db issues with dbhelper.
If the Publisher shouldn't have any phones registered to it, this means that load balance could be possible (following Cisco best practices) only between subscribers?

Bye,

Enrico.

 

[whykap]

Load balancing is possible with a pub as well so that's not your issue. It's a db replication issue or you have a configuration issue somewhere.
What I am saying is by best practices you should not be using your pub for load balancing. If you want to do it properly add another sub.

 

[tziupa]

Hello again whykap! I solved by simply rebooting the Publisher... I'm glad of having this problem sorted out but I'm not really satisfied of the way it has been solved, I'm just looking for what it could be the issue... Before restarting the server i checked all region configuration and database replication status with dbhelper and everything seemed to be ok...


Anyway, thank you very much,
Bye!

Enrico