gregarican
IS-IT--Management
I know this might be in the category of hen's teeth, but if I would've read this a week ago I would've saved a few hours of frustration.
Although the published TSAPI port that Merlin CTI uses is listed as TCP 450, there are secondary ports that are spawned for accessing the TServer (TCP 1121 for example). If you have a newer Windows based TServer an enabled Windows Firewall will block remote clients from opening the initial CTI stream. I spent so much time tracing the traffic and seeing the remote clients login, only to have the sessions fail with an ACS Universal Failure -9 error, meaning an unspecified condition that TServer can't determine what the heck happened!
After disabling the Windows Firewall (never a good idea in practicality) things are working fine. I thought opening TCP 450 and even adding TCP 1121 to the white list was good enough. Apparently not :-/
Although the published TSAPI port that Merlin CTI uses is listed as TCP 450, there are secondary ports that are spawned for accessing the TServer (TCP 1121 for example). If you have a newer Windows based TServer an enabled Windows Firewall will block remote clients from opening the initial CTI stream. I spent so much time tracing the traffic and seeing the remote clients login, only to have the sessions fail with an ACS Universal Failure -9 error, meaning an unspecified condition that TServer can't determine what the heck happened!
After disabling the Windows Firewall (never a good idea in practicality) things are working fine. I thought opening TCP 450 and even adding TCP 1121 to the white list was good enough. Apparently not :-/
