Is there a document on how to setup CM and the AES to use the Telephony, SMS and User web services? What specifically I am looking for is what users need to be setup where and what should their permissions be? I create a user on CM called ctiuser and gave them 'susers' rights and that works for SMS transactions using ctiuser@192.168.15.129 in the header of the web Service.

The issue I am having now is that the Telephony and User web services are returning and error

startSession: SwitchNotReachableException for switch 192.168.15.129

If I read further down I see

<ns4:hostname xmlns:ns4="http://xml.apache.org/axis/">aessim</ns4:hostname>

So is the Telephony and User web services using the AESSIM CTI setup in the AES?

Request:<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ses="http://xml.avaya.com/ws/session" xmlns:tel="http://TelephonyService.ws.avaya.com">

   <soapenv:Header>

      <ses:sessionID>-1</ses:sessionID>

   </soapenv:Header>

   <soapenv:Body>

      <tel:attach></tel:attach>

   </soapenv:Body>

</soapenv:Envelope>

Response

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

   <soapenv:Header>

      <ns1:sessionID soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next" soapenv:mustUnderstand="0" xmlns:ns1="http://xml.avaya.com/ws/session">-4936483567300967922</ns1:sessionID>

   </soapenv:Header>

   <soapenv:Body>

      <soapenv:Fault>

         <faultcode>soapenv:Server.generalException</faultcode>

         <faultstring>startSession: SwitchNotReachableException for switch 192.168.15.129</faultstring>

         <detail>

            <ns1:SwitchNotReachableException xmlns:ns1="http://basictelephony.api.avaya.com">

               <subErrorCode>0</subErrorCode>

            </ns1:SwitchNotReachableException>

            <ns2:exceptionName xmlns:ns2="http://xml.apache.org/axis/">com.avaya.api.basictelephony.SwitchNotReachableException</ns2:exceptionName>

            <ns3:stackTrace xmlns:ns3="http://xml.apache.org/axis/">startSession: SwitchNotReachableException for switch 192.168.15.129

	at com.avaya.ws.TelephonyService.helpers.TelephonyServiceImpl.startSession(TelephonyServiceImpl.java:219)

	at com.avaya.ws.TelephonyService.TelephonyServiceImpl.startSession(TelephonyServiceImpl.java:559)

	at com.avaya.ws.TelephonyService.TelephonyServiceImpl.checkSession(TelephonyServiceImpl.java:491)

	at com.avaya.ws.TelephonyService.TelephonyServiceImpl.attach(TelephonyServiceImpl.java:192)

	at com.avaya.ws.TelephonyService.TelephonyServiceSoapBindingImpl.attach(TelephonyServiceSoapBindingImpl.java:54)

	at com.avaya.ws.TelephonyService.TelephonyServiceSoapBindingSkeleton.attach(TelephonyServiceSoapBindingSkeleton.java:321)

	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

	at java.lang.reflect.Method.invoke(Method.java:597)

	at org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCProvider.java:397)

	at org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:186)

	at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323)

	at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)

	at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)

	at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)

	at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:454)

	at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)

	at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:699)

	at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)

	at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)

	at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)

	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)

	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)

	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)

	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)

	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)

	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)

	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)

	at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)

	at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)

	at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:774)

	at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:703)

	at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:896)

	at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)

	at java.lang.Thread.run(Thread.java:619)</ns3:stackTrace>

            <ns4:hostname xmlns:ns4="http://xml.apache.org/axis/">aessim</ns4:hostname>

         </detail>

      </soapenv:Fault>

   </soapenv:Body>

</soapenv:Envelope>

The User Service has been removed from AE Services.

The Telephony Web Service (TWS) uses JTAPI which in turn uses TSAPI.

TSAPI is dependent on the switch connections configured in AE Services.

In this case it looks like the TWS is indicating that the switch connection provisioned with IP 192.168.15.129 is out of service.

Did you change the IP addresses of your AE Services and CM so it worked in your local environment. If so it would appear that the switch connection CLAN/PROCR IP address was not changed.

Even if you didn't change the IP addresses, I would investigate the state of the switch connection via AE Services web based management interface

From a browser set the address to the IP of AE Services (192.168.15.128)
login with the default credentials (craft/craft01)
select Communication Manager Interface
select switch connections
select cmsim
click edit PE/CLAN IPs
verify the proper IP for Communication Manager's processor Ethernet IP is set.

I did not change the IP from the base install. I did do a

status aesvcs link

on the CM and see

the IP of 192.168.15.128 and data in the Msgs Sent and Msgs Rcvd SEE ATTACHED

Is there a config file on the AES that I have to change to set up the TSAPI links? I remember doing that on a customer machine before.

On BDE they are pre-configured... see the edit on my earlier post for how to take a look at that configuration. There is a number of connected links (should be 1) and if you drill down, you should see the status of all connected links.

your .png file would seem to show the switch connection as operational however.

let me ask the person who handles the TWS service to take a look and see if he sees the problem here.

Have you tried using "cmsim" as the switch name instead of the IP address? Mine says Switch Not Reachable if I use IP instead of switch name.

Thanks for looking into this Craig,

TSAPI uses the switch name, not an IP. I suspect jeffreyn has been using SMS where the IP is used, leading to the confusion.

Thanks guys that works great.

I also wanted to add to the thread that the user is different as well, when using the Telephony Web Services vs the SMS Web Services.

I created a super user in CM called ctiuser, which works for the SMS WS but not for the Telephony WS.

If using the Telephony WS you have to use the CT user aessim with the password Aessim12# that was created on the install. You could add other CT users in the AES if you wanted to but the default works.

SMS is (largely) a proxy through to Communication Manager. The user you provide to SMS is authenticated by Communication Manager. TWS is a AE Services web service, that reforms your requests into JTAPI/TSAPI. The TWS user is authenticated by AE Services against CT Users in its local databases. You could setup a single authentication LDAP server and home both servers to that, however in the BDE environment each server has a separate login/password, so you learn that they are separate users and where they come from. I could have used the same login/password for both users, however IMHO that would have led to a different confusion.

You can create new users on AE Services using the web management interface's User Management -> User Admin-> Add User page. Once that is done you use Security -> Security Database -> CTI Users to set the user you created to have 'CT User' permissions. To keep things simple aessim has 'Unrestricted Access' CT User privileges, however in some environments a CT User may be restricted in what devices it can monitor/manipulate, and that is when all the capabilities of the Security Database (SDB) come into play. :wink: