- Go to TSMSAPI configuration file and look for below key,
- Make sure value of ConsiderAgentIdAsSkill is configured to true.
- After any modifications done in configuration file, a restart of the TSMSAPI service is required.
The issue is observed in the TSMSAPI log file when a request made to get agent details.
As the error message from AES web service SMS API clearly says, the agent id record is not in the CM dial plan.
This implies the agentId “469” parameter that is been passed with the GetAgent method call is invalid.
To verify this, login to CM using putty. Run command “display dialplan analysis”, below screen will be shown.
Check if the dial-plan is correct. If we want to take this as an example,
To solve this issue, there are only two approaches, they are,
This error will be seen if the TSMSAPI application and AES SMS API website are trying to communicate with different protocols.
This occurs when TSMAPI is not configured properly.
The issue occurs due to the transport layer level configuration mismatch between two machines (TSMSAPI hosted machine and AES hosted machine).
The first thing to check is what transport layer security system is enabled in hosting machine.
If not sure how to check, please follow instructions as below,
The machine hosting TSMSAPI application must be at-least configured for ssl3 or Tls.
Avaya AES web services support only TSL1.0 or below. So, please make sure you have not configured either TLS1.1 or TLS1.2 as a value for configuration key “Sslversion” in the TSMSAPI applications configuration file (key and value shown below). Allowed values are Tls or Ssl3.
<!--Tls,Ssl3--> <add key="SslVersion" value="Tls"/>
This must resolve the issue.
This issue is possible to occur when path to Avaya's SMS API web service certification file path is been configured incorrectly.
Follow below two steps to solve this issue.
<add key="CertificateFile" value="D:\Products\MyBucket\TSMSAPI\smsxml.cer"/>
Issue Description: Error message from SMS API while making API calls.
Resolution: TSMSAPI will check for secondary AES URL configured when the primary is not reachable, the application will log this error message when the AES SMS API secondary URL is not configured in the applications config file or if it is configured incorrectly.
Please check if the below config key is present in the TSMSAPI applications configuration file if not present go ahead and add this config key.
If it is already configured, verify whether the configured AES SMSAPI service URL is up and running. To verify, copy the URL and paste it in browser address, on run below screen will appear which confirms service is running and reachable.
The above configuration must resolve this issue.
Issue Description: General error message from Avaya’s SMSAPI while querying for certain requests.
Troubleshooting Steps: This error occurs when AES is down or there are no more connections left in CM to serve the new request from SMSAPI. Follow below guidelines as troubleshooting steps,
This particular error occurs only when SMSAPI's connection type is configured to "CM".
This particular issue occurs when SMSAPI application tries to query a command called list.
example: list skill, list agents. Please note: error with code starting with "failed: xxx" will be generally from Avaya's SMSAPI web-service standard error code with message.
As error message implies, this issue clearly says that the user account used in SMSAPI doesn't have access to list command.
As a resolution step, Login to CM in browser and check type of user account that is being used in SMSAPI application.
If user type is "Unprivileged Administrator" then we will get this error. To eliminate this , we must use "Privileged Administrator" .
Below are some screenshots for better understanding.