I have 2 AES servers that are used for OCS and click to dial. The OCS chat is working fine, but the click to dial is not anymore. When I display IP-Services I see the 2 AES server status as 'in use' and on the AES Server I see the TSAPI connections in the state of 'talking'. Can I rule out the PBX to AES as the issue with this?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
AES/OCS Click to Dial
- Thread starter wpetilli
- Start date
I don't think you can rule that out. OCS is simply sending the commands to your AES to make the call.
- Thread starter
- #3
You might have to do some traces on the OCS side to see what is happening.
These links might help you in troubleshooting both sides:
OCS R2 - OCS R1 -
These links might help you in troubleshooting both sides:
OCS R2 - OCS R1 -
- Thread starter
- #5
Well just a bit of history here.. we were working fine for the longest and this weekend our server teams went through a security remediation and changed every SA password and domain account pw. So the the only thing I see in AES is this enterprise directory section where there is some LDAP password.. not sure what that relates to, but...
On page 32 of the R2 document it talks about the account used Enterprise Directory configuration (basically for LDAP). If they changed the password of that specific account then you will need to update the password in that screen to allow that function to work.
- Thread starter
- #7
- Status
