I have tried to use the SMS Interactive Test utility that comes with the SMS SDK, but I haven't yet found a username/password that works. I'm accessing the tool as such:
http://209.201.33.48/sms/sms_test.php

But when I enter any of the user accounts that I'm familiar with (aesadmin, craft, avaya) I get the same error, which is:
"Fault: Connection Failed: "

For example, I've tried:
OSSI Login ID = craft@localhost:80
Password = crftpw
SMS Host = http://localhost
Model = Station
Operation = list
Objectname = [blank]
Qualifier = count 5
Fields = *

Any help would be greatly appreciated.

Thanks, Art

Hi Art,

The "Fault: Connection Failed: " error message does not necessarily mean that the user credentials are invalid. This message typically indicates that SMS can not make a connection to CM on the port and protocol that are specified in the SMS configuration file. I am not sure what version of CM and AES that you are using, but you will want to ensure that CM is listening on the port that SMS is trying to use. A simple test to verify if CM is listening is to use an SSH and/or a Telnet client to connect on CM's TUI port (It is always best to do so on the actual AES server to also verify connectivity). Try these two commands:

>ssh -p5022 -lcraft <cm-ip-address>
>telnet <cm-ip-address> 5023

If CM responds with a login/password prompt, then you know what protocol and corresponding ports are available for SMS to use (you also verify that your username/password are correct at this time). To configure SMS to use one protocol or the other, first verify the version of AES you are using. Logon to your AES server and su root/sroot:

>swversion

Check if you are using AES 3.x
***********************************************************************
Application Enablement Services
***********************************************************************
Version: r3-1-3-build-48-3-0

or AES 4.x

***********************************************************************
Application Enablement Services
***********************************************************************
Version: r4-0-1-bld-51-0

If you are using AES 3.x then the only protocol available for SMS is Telnet. If you are using AES 4.x then you can choose between Telnet or SSH for added security.

>vi /opt/mvap/web/sms/saw.ini

And configure your SMS installation appropriately (Note the default Protocol has changed between SMS releases 3.x and 4.x):

AES 3.x - Telnet
CMPort=5023
ProxyOptions=-n

AES 4.x- Telnet
CMPort=5023
ProxyOptions=-n -T

AES 4.x- SSH
CMPort=5022
ProxyOptions=-n


There is also a documented incompatibility between SMS 3.x and CM 4.x so you will also want to verify that this is not the situation for you. There is a workaround for this so please respond to this thread if you need assistance with this. Also, if you happen to find that one of the TUI ports on CM are not open and you need it to be, please respond in this thread for further instruction.

I also apologize for not being able to respond to your other thread in a timely manner, however this may be your real issue. Please let me know if this works for you.

Thanks,

Tony

Thanks for the help. I'm not sure what is wrong, but I can't telnet to port 5023 or 5024. Error is:
[aessim:/opt/mvap/web/sms]telnet localhost 5023
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused

The result is the same if I use full IP instead of localhost.

swversion is as follows:
Version: r3-1-2-build-46-5-0
Server Type: OTHER
Offer Type: SWONLY

Also, I don't know the password for root and I've searched everywhere for what it could be with no luck. The person who installed AES also has no idea what it could be? So how DOES one know what the root password is? I can't find it documented anywhere?

So it looks like my problem is that SMS is not available because port 5023/5024 is/are not open. So what enables that? I guess I assumed that it would be open as part of the install of AES?

Thanks again!
Art

Okay, I was pointing to the AES server IP address, not the CM IP address. So now I do get a proper response from telnet to port 5023 on CM server. But now when I try the test utility I get the following error:
Fault: XML error on line 1 col 0 byte 0 syntax error

Here are my current values in the utility:
OSSI Login ID = craft@209.201.33.47:5023
Password = crftpw   
SMS Host = http://209.201.33.47:5023
Model = Station
Operation = list   
Objectname [empty]
Qualifier = count 5   
Fields = *

Is this thing documented anywhere?
Thanks, Art

Have you downloaded the SMS SDK? It has fairly good documentation.

SMS Host = http://209.201.33.47:5023

Should be left as default:
SMS Host = http://<localhost>;

Tony

Okay, big step forward! In the test utility I changed
SMS Host = http://209.201.33.47:5023
to:
SMS Host = http://localhost

And then it worked!! But this is for the test utility (sms_test.php). So now I'm trying to duplicate this in my C# app and I still have the same error. Here are my current values for Credentials and Url:
sms.Credentials = new NetworkCredential("craft@209.201.33.47", "crftpw");
sms.PreAuthenticate = true;
sms.Url = "http://209.201.33.48/sms/SystemManagementService.php";

Note that the AES server is running on 209.201.33.48 and the CM server is running on 209.201.33.47. So i must have these values messed up somehow. Can you help?

Thanks, Art

I am doing the sms_test on AES 4.0 and the data that i use are as follows:
OSSI Login ID: tadmin@180.174.128.1:5022
Password:partner01
SMS Host:http://localhost
Model: Station
Model = Station
Operation = list
Objectname = [blank]
Qualifier = count 5
Fields = *

And the answer is as follow

Session ID: 34431b460382cb74a070ecf10e129012
Responce:
class stdClass {

var $result_code = 0;

var $result_data = '';

var $message_text = '';

}

This answer can be seen as a test successful????


Thanks, Arturo

Hi Arturo,

A result_code of 0 would indicate that no errors occurred during the request, however I would have expected to see some data in the result_data if you have stations administered on that CM. Can you manually login to SAT on your CM with the user you provided SMS and verify that a list station count 5 returns a proper list of data? Also, you may want experiment with some other models and commands.

Thanks,
Tony

Thanks Tony

Already execute the command from the terminal sat, and it gives me information. I understand that the sms_test have to send me this same information. Think you set something missing in the AES or PBX?

The configuration in saw.ini is as follow

[ACP]
Name=
ProxyHost=localhost
ProxyPort=4001
ProxyPortRange=16
CMHost=180.174.128.1
CMPort=5022
ProxyFile=proxyhost
ProxyOptions=-n
OSSI_ResponseTimeout=10

Arturo

Your default configurations seem to be OK and the fact that you are getting a successful result code lead me to believe that you are making a connection to CM. Have tried any other SMS commands ie:list AARAnalysis , list COR, display Station? You may also want to try s'tatus logins' from SAT to verify that SMS has successful logged in to CM.

Tony

Arturo,

I believe the problem is steaming from the /opt/mvap/web/saw.ini configuration file. If you see something similar to the following in /var/log/error_log you will need to check the configurations in your saw.ini file:

[client x.x.x.x] PHP_DEBUG: Sun Jun 22 04:02:30 2008: Opening DB for:station in read-write mode
[client x.x.x.x] PHP_DEBUG: Sun Jun 22 04:02:30 2008: PHP Notice/Warning(2): dba_open(data/station.db,wl): No such handler: gdbm in /opt/mvap/web/sms/include/DBConnector.class.php at line 56.
[client x.x.x.x] PHP_ERR: Sun Jun 22 04:02:30 2008: DB inaccessible for: station

Please verify that the saw.ini file includes the following connection line exactly as it appears (and remember this file is case sensitive):

[General]
connection=OSSI
?
?
?

Thanks,
Tony