....even though the Config points to the production TAL. I've restarted services, and machines, but TeleFlow still wants to use the 'test' TAL instead of the current one. Any ideas?

Thanks,

So, on the computer that TeleFlow Server is running on, if you open TeleFlow Config right now (close all instances, and re-open), does it have the right .TAL referenced, or not? (I suspect it isn't saving when you click OK)

If that is currently correct, check what is in this registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\enGenic\TeleFlow Server

For string value: APPLISTFILENAME

If it is incorrect, and you correct it in TFConfig, then click OK, then run TFConfig, has it reverted to the 'Test' tal file? If so, you probably have a rights/permissions issue on the computer, and it is not allowing you to save the setting in the registry.

It is correct in the Config util and it is correct in the registry. I have since stopped the TF Server so that the wrong TAL isn't continually used...

OK... that should be impossible; TeleFlow doesn't "remember" anything between runs, and retrieves its values from the registry when started.

If you check the processes in task manager, tfserver.exe isn't running right now, is it? (Be sure to check the "Show processes from all users" checkbox)

Can there be multiple user sessions on this system, such as through RDP or the like?

What happens if you rename your test tal file, to something like test.tal.bak, so that the file no longer exists? If you then try to start TFServer, what is the behavior?

No, tfserver isn't running because I stopped the service - it was not worth it to have TF use the 'old' TAL when phoning a user.

And, yes, we use RDP to access the systems remotely; however, I rebooted the system on the off chance that some random connection were keeping it alive. (Plus my old TAL only had one line in it, so it's not like I had multiple lines to consider.)

I will rename the file and see what happens. Unfortunately, I won't be able to send any calls through the system today due to client actions at an upstream process level. But I'll let you know either tomorrow or Friday if we still see this strange anomaly.