Hi,

When I to access the AES Web Service using sms_test.php script on the AES, it works perfectly. The following is the error_log when I try the script:

PHP_DEBUG: Mon Nov 19 13:37:12 2007: ==========> OSSIConnector::dtor() invoked; disconnecting
PHP_DEBUG: Mon Nov 19 13:43:14 2007: SOAP_WebService instantiated
PHP_DEBUG: Mon Nov 19 13:43:14 2007: Constructing model
PHP_DEBUG: Mon Nov 19 13:43:14 2007: Establishing OSSI connector
PHP_INFO: Mon Nov 19 13:43:14 2007: VDN model acquiring read-only connection
PHP_DEBUG: Mon Nov 19 13:43:14 2007: Connecting to proxy for host 10.10.8.202:5023 at localhost:4006
PHP_DEBUG: Mon Nov 19 13:43:14 2007: Sending to proxy: re41374f578f31f6bd8e22adeb795460eSMS!svcvdn!*******!!10.10.8.202!5023
PHP_DEBUG: Mon Nov 19 13:43:14 2007: Waiting for connector handshaking response
PHP_DEBUG: Mon Nov 19 13:43:15 2007: Response Received: 0
PHP_INFO: Mon Nov 19 13:43:15 2007: VDN model releasing connection
PHP_DEBUG: Mon Nov 19 13:43:15 2007: Closing Socket Connection to ossicm

However, when I try the C# sample code in the other thread, I get the following error:


PHP_DEBUG: Mon Nov 19 13:48:28 2007: ==========> OSSIConnector::dtor() invoked; disconnecting
PHP_DEBUG: Mon Nov 19 13:53:39 2007: SOAP_WebService instantiated
PHP_DEBUG: Mon Nov 19 13:53:39 2007: PHP Notice/Warning (2): session_write_close(): The session id contains invalid characters, valid characters are only a-z,
A-Z and 0-9 in /opt/mvap/web/sms/include/SMSSession.class.php at line 99.
PHP_DEBUG: Mon Nov 19 13:53:39 2007: PHP Notice/Warning (2): session_write_close(): Failed to write session data (files). Please verify that the current setti
ng of session.save_path is correct (/opt/mvap/web/sms/templates_c/) in /opt/mvap/web/sms/include/SMSSession.class.php at line 99.
PHP_DEBUG: Mon Nov 19 13:53:39 2007: Constructing model
PHP_DEBUG: Mon Nov 19 13:53:39 2007: Establishing OSSI connector
PHP_INFO: Mon Nov 19 13:53:39 2007: VDN model acquiring read-only connection
PHP_DEBUG: Mon Nov 19 13:53:39 2007: Connecting to proxy for host 10.10.8.202:5023 at localhost:4006
PHP_DEBUG: Mon Nov 19 13:53:39 2007: Sending to proxy: rSMS!!!10.10.8.202!5023
PHP_DEBUG: Mon Nov 19 13:53:39 2007: Waiting for connector handshaking response
PHP_DEBUG: Mon Nov 19 13:53:39 2007: Response Received: 1
PHP_DEBUG: Mon Nov 19 13:53:39 2007: Closing Socket
PHP_DEBUG: Mon Nov 19 13:53:39 2007: OSSI Connector Failed with params: array (! 'Host' => 'localhost',! 'Port' => '4001',! 'Login' => NULL,! 'Writable' =
> false,! 'SocketFailure' => NULL,! 'OSSIFailure' => NULL,! 'LogonRequired' => true,! 'ServerStatus' => 'active',!)
PHP_ERR: Mon Nov 19 13:53:39 2007: Connection could not be established for list VDN operation.
PHP_DEBUG: Mon Nov 19 13:53:39 2007: PHP Notice/Warning (2): session_write_close(): The session id contains invalid characters, valid characters are only a-z,
A-Z and 0-9 in /opt/mvap/web/sms/include/SMSSession.class.php at line 99.
PHP_DEBUG: Mon Nov 19 13:53:39 2007: PHP Notice/Warning (2): session_write_close(): Failed to write session data (files). Please verify that the current setti
ng of session.save_path is correct (/opt/mvap/web/sms/templates_c/) in /opt/mvap/web/sms/include/SMSSession.class.php at line 99.
PHP_DEBUG: Mon Nov 19 13:53:40 2007: ==========> OSSIConnector::dtor() invoked; disconnecting
[Mon Nov 19 13:59:03 2007] [error] [client 10.10.5.169] File does not exist: /opt/mvap/web/sms/SystemManagementService.php/wsdl
PHP_DEBUG: Mon Nov 19 13:59:07 2007: SOAP_WebService instantiated
PHP_DEBUG: Mon Nov 19 13:59:07 2007: Web service getting wsdl

Does anyone ever encounter the same problem?

Bill,

I believe there are a couple of things wrong:

First, it looks like your connection to CM is failing because you failed to include valid credentials in the SOAP request:

-----------------
Sending to proxy: rSMS!!!10.10.8.202!5023
PHP_DEBUG: Mon Nov 19 13:53:39 2007: OSSI Connector Failed with params: array (? 'Login' => NULL,)
-----------------

A valid request would log something like this:
PHP_DEBUG: Mon Nov 19 15:48:36 2007: Sending to proxy: rSMS!craft!******!!apollo-srv1!5023

Second, is the session ID is not set properly. This is not your fault because the Session ID is not set in the sample application that is posted on the forum. I have written a sample C# app at this thread https://devconnect.avaya.com/secure/forum/d_forum_3.jsp?t=1313&f=29 (SessionID value in SMS) but it will only work with a Web Reference to a 4.0 SMS WSDL. Note, the 3.x SMS server will still be able to handle the SOAP request if you generate you code with a 4.0 SMS WSDL. You can get the 4.0 SMS WSDL by downloading the 4.0 SMS SDK at "Avaya Product Information / Documentation / SDKs."

I suggest that you use the 4.0 WSDL to generate your web reference since I have noticed some irregularities between .NET and the 3.x SMS WSDL which have been rectified in the SMS 4.0 WSDL (mainly that SMS 3.x returns a string for the sessionID instead of the long that is specified in the WSDL).

Please let me know if you have any questions about this or need further assistance!

--Tony

Hi,Greway

It is still failed after I add the sessionid when links to real AES.
the sms_test.php is ok.
But the same code works properly when links to virtual AES.

Version:
mvap-sms-3.0.1-28

Real AES Ver: mvap-sms-3.1.0-28
Virtual AES Ver: mvap-sms-3.1.704.14-1

Connection Failed

Hi Bill,

I believe I know why you are seeing the 'Connection Failed' error messages on your real AES server. Microsoft .Net has a preauthenticate property that you can set in the SOAP request which is "supposed" to send the user credentials on the initial HTTP post. I am not sure why, but after running some packet traces this does not seem to be happening when you set preuthenticate=true. SMS has addressed this issue in AES 3.1.2 and greater, which is why your virtual environment succeeds! I would suggest upgrading to AES release 3.1.2 or greater if possible. If you must remain on this load of AES you will need to manually set the Authentication Credentials in the HTTP header so that the initial SOAP request contains the Authentication Credentials. Sorry for any inconvenience, please let me know if you have anymore questions.

Thanks,
--Tony

Hi Tony,

Becuase our production system is very important, there will be very high risk to update the AES to ver4.0.

We tried to set the Authentication Credentials in SOAPHeader , but it is still failed.

Could you give sample code of .NET ?
Thanks
Bill

And we tried to run the java client in SDK, but it failed too.

Hi Bill,

Sorry for the delayed response. I have not had time to look into writing a .Net code sample for you yet, but I will work on trying to get one up soon. In the meantime, I did not have any issues using the SMSTest Java/Axis program included in the SMS SDK. The authorization credentials are set in the initial request in the SDK therefore passing along the correct login information to SMS. What version of the SMS SDK are you using?

--Tony

Hi Tony,

Thank you very much .

We had researched a method to change or list the CM property.
Though it is stupid ,but can work correctly.


Our SDK version is the wsdl of the AES Server.
http://server/sms/SystemManagementService.php?wsdl

Below is detial version of our AES :
$ swversion -a
***********************************************************************
Application Enablement Services
***********************************************************************
Version: r3-1-0-build-33-1-0
Server Type: IBMX306
Offer Type: TURNKEY


***********************************************************************
Operating System Version
Linux 2.4.21-32.EL


***********************************************************************
***********************************************************************
Application Enablement Server RPMs Installed on disk for release r3-1-0-build-33-1-0:
aesvcs-alarming-3.1.0-1.12
aesvcs-config-samp-3.1.637-2
aesvcs-config-security-3.1.637-12
mvap-linuxconfig-3.1.637-9
mvap-cusldap-1.0-20
mvap-sms-3.1.0-28
mvap-DLG-3.1-101
mvap-install-scripts-hooks-3.1.637-15
mvap-services-3.1.637-3
mvap-telephonysvc-3.1.637-1
mvap-tomcatconfig-3.1.637-6
mvap-platform-3.1.637-1
mvap-transport-3.1-101
mvap-cmapi-3.1.637-1
mvap-callcontrol-3.1-101
mvap-common-utils-3.1.637-4
mvap-userservice-3.1-5
cs-samp-1.0.0-8
cs-syslogreader-1.0.0-1.7
cs-security-1.0.0-8
cs-lifecycle-1.0.1-0.21


**********************************************************************
Third Party RPMs Installed on disk for release r3-1-0-build-33-1-0:
avaya-coreservices-axis-1.1-13
avaya-coreservices-tomcat-5.0.28-0.0
ethereal-0.10.11-1.EL3.1
jdk-1.5.0_02-fcs
libpcap-0.7.2-7.E3.5
net-snmp-5.0.9-2.30E.15
net-snmp-libs-5.0.9-2.30E.15
openldap-clients-2.1.22-8
openldap-2.1.22-8
openldap-servers-2.1.22-8
httpd-2.0.46-46.ent
mod_ssl-2.0.46-46.ent
e1000-5.2.30-1
libxml2-2.5.10-7
curl-7.10.6-6.rhel3
gdb-6.3.0.0-0.30.1
tripwire-2.3.1-20.fdr.1
php-pear-4.3.2-14.sms
php-4.3.2-23.ent
openssl-0.9.7a-33.15
sahpi-01_01B-1.14