View Single Post
  #1  
Old 02-13-2017, 11:20 AM
jwindb jwindb is offline
Member
 
Join Date: Feb 2017
Posts: 3
jwindb has 10 reputation points
Angry SMS Svc Web Services in our Collaboratory

We have a lab, Lab174.

I have downloaded the "SMS Web Services SDK"
and am following the instructions to connect using the sample application.
"Avaya Aura Application Enablement Services Web Services Programmer's Guide".

The sample app class is called "SMSXMLTest.java"

In order to get java to talk to the host, I downloaded the "aes-labUseOnly" certificate, and them used that as the hostname (the certificate required it), bu putting the ip address of the host in my /etc/hosts file.
I have verified that I can programmatically download the wsdl, so that's clear.

I'm unclear what to use for the values is smsxml.properties
sms.root
cm.login
sm.password

Especially as within the test, the string cm.login comes in the form:
loginid@cmaddress[ort]


My web service url ends up as :
https://aes-labUseOnly/smsxml/System...entService.php
aes-labUseOnly is in my hosts file as 10.0.0.17
I've been using our cust#####@dev-174.collaboratory.avaya.com

Best I have ever gotten is OSSI connection errors.

I need to know what I ought be using for the properties, how to verify that our lab service is actually installed correctly (the documentation mentions looking in the logs, but doesn't bother to say how to get to them), also mentioned going to the "OAM" pages, but I don't know what that means.
Reply With Quote