Avaya Support Forums  

Go Back   Avaya Support Forums > Avaya Breeze™ Collaboratory

Reply
 
Thread Tools Search this Thread Display Modes
  #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
  #2  
Old 02-14-2017, 07:29 AM
lucas3 lucas3 is offline
Hot Shot
.
 
Join Date: Nov 2010
Posts: 19
lucas3 has 10 reputation points
Default

Hi jwindb,

I'll follow up with design on this issue and get back with you shortly.
Reply With Quote
  #3  
Old 02-14-2017, 01:18 PM
jwindb jwindb is offline
Member
 
Join Date: Feb 2017
Posts: 3
jwindb has 10 reputation points
Red face

Excellent.

I've discovered that I can ssh into the machine that is actually running the smsxml web service. I can even read the php code.
I cannot, however, gain access to the log directories, as my documentation says I should. They are root only.

I'm beginning to believe that box referred to as our CM, is also the box I would use for OSSI.

ssh cmhost -p 5022

Does that seem correct?

None of my lab credentials work on that host though.
Reply With Quote
  #4  
Old 02-15-2017, 08:09 AM
lucas3 lucas3 is offline
Hot Shot
.
 
Join Date: Nov 2010
Posts: 19
lucas3 has 10 reputation points
Default

The Breeze development team is going to add the universal account (cust#####) to the CM server and change the permissions on the directories in the AES server so you can access the log files. Will send you an email once this is updated.
Reply With Quote
  #5  
Old 02-15-2017, 02:25 PM
lucas3 lucas3 is offline
Hot Shot
.
 
Join Date: Nov 2010
Posts: 19
lucas3 has 10 reputation points
Default

The CM account was provided to you in a separate email. You should now have access to the AES directories /var/log/avaya/aes/apache & /var/log/httpd using the universal cust account.
Reply With Quote
  #6  
Old 02-15-2017, 04:33 PM
jtb1 jtb1 is offline
Aspiring Member
 
Join Date: Feb 2017
Posts: 1
jtb1 has 10 reputation points
Default

mentioned going to the "OAM" pages, but I don't know what that means.

that would be a reference to the web interface on AE Services that you do operations administration and maintenance.
Reply With Quote
Reply

Tags
sms webservices

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 12:42 AM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.