You are correct. This wasn't documented. APP_KEY needs to be the same on both servers. We have now documented it and taken it a step further. The APP_KEY is synced automatically during the HA setup. So no one else runs into this issue.
I would like to keep an eye on this issue. If it repeats itself with any future updates, I'd like to know. We switched from compiling assets on each server to compiling them on GitHub and distributing them via download. It cuts update time significantly and no longer requires as much RAM as...
I’d definitely back up before any major OS update. It's hard to predict what each update will do or whether it might break dependencies. I'd avoid updating PHP. We addressed the vulnerability as soon as it was announced with a coordinated FS PBX update. Some people updated manually too soon...
Reach out to support. We need logs to figure out what's happening. It should be easy to fix.
Quick question, though. Did you set up a caller ID for the extension you are calling from? Or at least the global one?
@Voipy Yes, you are correct. The diversion header is populated correctly where it needs to be.
I followed Voip.ms and Telnyx guides for the diversion header. It puts the dialed number into the diversion header. In your example, it matches number B.
If you are seeing something else provide logs...
FS PBX is integrated with Retell AI. If you are on the latest version, simply add an AI agent under Applications - AI agents after you create one in their portal. It will have an extension in FS PBX, and you can simply route calls to it.