[cisco-voip] Expressway Clustering...

[russon81]

Another thing, the clustering is kind of funky, so you need to make sure they are listed in the same order on both nodes.  Sent from my T-Mobile 5G Device
-------- Original message --------From: Brian V <bvanbens at gmail.com> Date: 5/12/22  3:24 PM  (GMT-08:00) To: Jonathan Charles <jonvoip at gmail.com> Cc: cisco-voip at puck.nether.net Subject: Re: [cisco-voip] Expressway Clustering... A few thoughts.Clustering does require H323 to be enabled.Check DNS resolution if Expressway-E,  you can statically define name resolution for peers in the case where the defined DNS might not be able to resolve the peers "inside" addressOn Thu, May 12, 2022 at 4:19 PM Jonathan Charles <jonvoip at gmail.com> wrote:Howdy! We are seeing an error on our Expressway E nodes right after we form a cluster.The cluster is up and fully operational, however, we get:Peer Not RespondingA peer address for the LocalZone local zone is down and unreachable.It then tells you to check the zones page and verify the failing peer address...There are no zones configured, as of yet... just the DefaultZone and it has no option for peers to be configured.The LocalZone also has no peer configuration as an option.Any ideas?Thanks!Jonathan
_______________________________________________
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/20220512/fcce11aa/attachment.htm>