Alright so this is a weird one. We have a custom bot integration using the Bot Connector framework that receives webhook events from Genesys Cloud when a customer enters a bot flow. This has been working perfectly for 6 months.
Last week we updated our Edge servers from firmware 1.0.0.9823 to 1.0.0.10300. After the firmware update, our bot webhook stopped receiving events for calls that are handled by the Edge (BYOC Premises media). Bot flows on calls handled by cloud media still work fine.
The Bot Connector integration shows as “Active” in Admin > Integrations. The webhook URL is correct and responds to the health check ping. The Architect bot flow has not changed. The only change was the Edge firmware.
Edge diagnostic logs show:
2025-05-12 10:15:33 WARN BotConnectorProxy: Failed to forward webhook event to cloud relay. Connection refused: 127.0.0.1:8443
It looks like the Edge firmware update changed the internal bot connector proxy port. Has anyone seen this after the 10300 firmware update?
Yes! We hit this exact same issue on our Edge servers after the 10300 update. It affected 12 of our 20 Edge appliances across our 800-agent environment.
The firmware update changed the internal bot connector relay service from port 8443 to port 8444. This is documented in the release notes but buried in the “Breaking Changes” section that nobody reads (guilty as charged).
The fix is straightforward but requires Edge console access:
- SSH into each affected Edge server
- Edit
/opt/genesys/edge/config/botconnector.properties
- Change
relay.port=8443 to relay.port=8444
- Restart the Edge media service:
sudo systemctl restart edge-media
Alternatively, if you have not customized the bot connector properties file, delete it entirely. The Edge service will regenerate it with the correct port on the next restart.
The reason only some calls are affected is because only Edge-media calls use the local relay proxy. Cloud-media calls bypass the Edge entirely and go directly from the Genesys Cloud Bot Connector service to your webhook URL.
To add more context on this firmware change, the port migration from 8443 to 8444 was done because the Edge’s internal TLS certificate management service was moved to port 8443 in the 10300 release. The bot connector relay was relocated to avoid the conflict.
From a trunk management perspective, I want to flag that this same firmware update also changed the default SIP OPTIONS ping interval from 30 seconds to 60 seconds. If you have monitoring that alerts on SIP OPTIONS frequency, you might see false alarms after the update.
To check all the port assignments on your updated Edge, run this on the Edge console:
ss -tlnp | grep edge
This shows all listening ports for Edge processes. After the 10300 update, you should see:
- 5060/5061: SIP signaling
- 8444: Bot connector relay (was 8443)
- 8443: TLS certificate manager (new)
- 443: Edge admin web UI
If 8444 is not listening, the bot connector relay service failed to start during the firmware update. Check the logs at /var/log/genesys/edge/botconnector.log for startup errors.