AWS Deployment with Secondary

[davea2]

Hi

Setting up a deployment in AWS with Primary and Secondary.
Primary and secondary are in different AZs but in the same VPC, so different subnets.
The subnets 192.168.x.x etc are visible to each other as if a VPN exists.
pri and Sec on different public IPs, different FQDNs but same domain.

A few things I notice and am not sure of how to proceed.

The Websocket link between the 2 uses the LAN address so 192.168.75.x connects to 192.168.76.x
That works but the I cannot 'see' the secondary via manager as it's looking for 192.168.76.x and I don't have a VPN to the cloud VPC
A more worrying issue though is the 46xxsettings file which will show:-

SET FQDN_IP_MAP "pri.xxxxxx.co.uk=18.xxx.xxx.105,sec.xxxxx.co.uk=192.168.76.xxx"

So if the Primary falls over, the handsets are going to try to connect to 192.168.76.xxx which obviously they cannot.

If I try to set up the Websocket by using the public IP addresses (I know this is not right, just testing, although the security group block all public IPs apart from the Primary, secondary and my own) the SCN link will not establish. The 2 of them can ping each other OK though.
One positive about using public IPs though is that Manager can see both systems

The FQDNs are publicly resolvable and UCC certs in place on both system

Any help??

Many thanks!

dave

 

[derfloh]

Did you configure network Topology on the secondary server?

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[davea2]

Yes, all configured.
I must have missed something somewhere though but can't see it

 

[davea2]

I have just changed the line type to proprietary instead on websocket and the SCN cam straight up
Even using the public IPs