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,
- requested agentId is 469
- But in the CM dialplan we don’t see any dialplan as such. i.e. number starting with 4 and having total length 3. According to the above CM screen, Number starting with 4 must be of total length 5, else it will be considered as invalid.
To solve this issue, there are only two approaches, they are,
- Change or Add a new dialplan.
- Pass correct agentId to SMSAPI application.