SMS Test on Avaya CM

There will be some moments where SMS SOAP Faults (article here) within tomcat logs may seem obfuscated, not usable, or they may be missing information. 

Overview

Here, we will see how these errors are generated by replicating the command that generated an error.

Also, if you input incorrect credentials on the CM setup, it will give you this pop up.

Steps

1. Navigate to the SMS test page using your preferred browser
   

   https://<ip_address_of_AES>/sms/sms_test.php

   
   
   
   
2. Follow the steps below to test your SMS
   

   • Connection Information
     
     
     
     

     1. "CM Login ID"
        1. Put in the CM Server User, CM Server IP address, and SMS port
           •  E.g.

             • chronicall@<CMServerIPAddress>:5022

           • The default port is 5022, but it can be modified
             • If modified, this port can be found within the AES Web client under AE Services > SMS > SMS Properties > Default CM Admin Port
           • The CM Server User and CM Server IP address are the same ones used in the Communications Manager menu within Chronicall
             
             
             
             
     2. "Password"
        1. Place the password that you use to connect to the CM server
           1. The Password should be the same one used in the "CM Server Password" setting of the Communications Manager menu within Chronicall
     3. "SMS Host"
        1. Should be automatically filled in but is the AES Server IP Address
           1. Also found in the "AES Server IP Address" setting of the Communications Manager menu within Chronicall

   • Request Parameters
     
     
     
     

     • Mimic what Chronicall was trying to do with its request, in this case, list station count 1
       1.  Model
          
          1. Type in "Station"
       2. Operation
          1. Type in "list"

   • Last Request Response
     
     
     
     

     1. Response
        • The results will be presented here
          • If successful, we should yield all stations available to the PBX
          • If not, we will have errors.