Avaya Workplace app Contact Service Problem / Your contacts may not be up to date

[rgunther]

Hey Guys... using avaya IP500 R11.0.4. Remote workers use Avaya Workplace app with VPN back to LAN where IP Office is located. We use "

http://192.168.x.x"

as the URL for Avaya workplace app to connect to the IPO. All calling features seem are working properly, but the application has an error that says "Contact Service Problem - Your Contacts may not be up to date", and we do not have the system contacts. Any idea's what needs to be setup? Thanks

 

[rgunther]

So when I manually change the "Phone Service" Server address to the IP address rather than the auto-populated FQDN, the Contacts and presence starts working again. If I change it back to the FQDN, then the presence and contacts breaks. Anyone have any ideas why this would be?

 

[critchey]

Do you have splitDNS setup? Your FQDN needs to resolve to your external IP when outside your network (DNS A record through provider) but it needs to resolve to your internal IP when on your internal network. This requires you to edit the DNS record on the internal DNS server and point both the client PC and IPO to this DNS server.

The truth is just an excuse for lack of imagination.

 

[derfloh]

You have to ensure that the VPN clients get the LAN DNS Server populated.

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