Hello,
I use TWS MakeCall to stimulate a "Hunt Group Busy Activation" we are working on AES 6.2. I get a beep on my phone but I get no response to my request from AES server.

makeCall - originatingExtension=10793, destinationNumber=*600001
FEATURE ACCESS CODE =*60
Hunt-Group =0001

I have this error after time out
Didn't receive alerting or failed event

-------------- cat ws-telsvc-api.log.0
2013-05-20 15.02.53,506 com.avaya.ws.TelephonyService.TelephonyServiceImpl attach
FINE: attach: entered - sessionID=2282058671807484652
2013-05-20 15.02.53,506 com.avaya.ws.TelephonyService.TelephonyServiceImpl attach
FINE: attach: completed
2013-05-20 15.02.53,518 com.avaya.ws.TelephonyService.TelephonyServiceImpl makeCall
FINE: makeCall: entered - sessionID=2282058671807484652, originator=10793, destination=*600001

----------------- cat ws-telsvc-trace.log.0
2013-05-20 15.02.53,518 com.avaya.ws.TelephonyService.helpers.TelephonyServiceImpl makeCall
FINE: makeCall - originatingExtension=10793, destinationNumber=*600001
2013-05-20 15.03.09,101 com.avaya.basictelephony.BasicTelCallMonitor waitForAlert
WARNING: Didn't receive alerting or failed event

------------- catalina.out
com.avaya.basictelephony.TimeoutException: Didn't receive alerting or failed event
at com.avaya.basictelephony.BasicTelCallMonitor.waitForAlert(BasicTelCallMonitor.java:195)
at com.avaya.basictelephony.BasicTelSvcImpl.makeCall(BasicTelSvcImpl.java:285)
at com.avaya.ws.TelephonyService.helpers.TelephonyServiceImpl.makeCall(TelephonyServiceImpl.java:293)
at com.avaya.ws.TelephonyService.TelephonyServiceImpl.makeCall(TelephonyServiceImpl.java:273)
at com.avaya.ws.TelephonyService.TelephonyServiceSoapBindingImpl.makeCall(TelephonyServiceSoapBindingImpl.java:76)
at com.avaya.ws.TelephonyService.TelephonyServiceSoapBindingSkeleton.makeCall(TelephonyServiceSoapBindingSkeleton.java:327)
at sun.reflect.GeneratedMethodAccessor79.invoke(Unknown Source)
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:776)
at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:705)
at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:898)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
at java.lang.Thread.run(Thread.java:619)


Regards.

I have not worked with that feature on Communication Manager before. Is it working without Telephony Web Service in the picture? Can you make a call from one extension to another with the telephony web service?

Keep in mind that TWS is very basic and it will tell the CM to dial digits and a response only tells you that the call was attempted and doesn't say anything about the result of the call. Since this is a Feature Access call the CM allows for the user to enter a hunt group number. This isn't an alerting situation.

You could perform a second call to the hunt group extension itself to see if it's busy. Your application should receive an InvalidPartyException if the destination is busy. This was you could be for sure that the hunt group busy was activated.

Successfully activating Hunt Group Make Busy provides confirmation tone to the activator. I doubt TWS handles this class of call flow nicely. While I don't have an environment whereby I can activate HGMB, I tried with Send All Calls activation and see the same behavior. There basically is not a CTI event that occurs for tones like confirm, denial, intercept, reorder as it applies to feature activation/deactivation.

Thank you for your answers,
Between two EXT TWS make_call works very well. and i have tested successfully also Hunt Group Make Busy in AES WEB interface (TSAPI Test).
I think that TWS make_call restart TSAPI service when I try to send it via SOAP XML request.

Additional log
---------------- cat catalina.out log -----------------------------

@2013-05-21 13:43:22,206 CEST||INFO|com.avaya.jtapi.tsapi.tsapiInterface.TSInvokeID||GetEventThread|File=TSInvokeID.java,Line=51|Handling INVOKE ID 23 for TSProvider[#593]@110384a|||||||aes.domain.org|####
@2013-05-21 13:43:22,206 CEST||INFO|com.avaya.jtapi.tsapi.impl.core.SysStatHandler||GetEventThread|File=TSProviderImpl.java,Line=3897|Event monitoring was ended successfully|||||||aes.domain.org|####
@2013-05-21 13:43:22,206 CEST||INFO|com.avaya.jtapi.tsapi.impl.core.SysStatHandler||GetEventThread|File=TSProviderImpl.java,Line=3897|Event monitoring was ended successfully|||||||aes.domain.org|####
@2013-05-21 13:43:22,206 CEST||INFO|com.avaya.jtapi.tsapi.tsapiInterface.TSInvokeID||GetEventThread|File=TSInvokeID.java,Line=55|DONE handling INVOKE ID 23 for TSProvider[#593]@110384a|||||||aes.domain.org|####
@2013-05-21 13:43:22,206 CEST||INFO|com.avaya.jtapi.tsapi.tsapiInterface.TSInvokeID||GetEventThread|File=TSInvokeID.java,Line=55|DONE handling INVOKE ID 23 for TSProvider[#593]@110384a|||||||aes.domain.org|####

@2013-05-21 13:43:22,206 CEST||INFO|com.avaya.jtapi.tsapi.tsapiInterface.TsapiSession||TP-Processor7|File=TsapiSession.java,Line=636|Sent InvokeID 24 for TSProvider[#593]@110384a|||||||aes.domain.org|####
@2013-05-21 13:43:22,206 CEST||INFO|com.avaya.jtapi.tsapi.tsapiInterface.TsapiSession||TP-Processor7|File=TsapiSession.java,Line=636|Sent InvokeID 24 for TSProvider[#593]@110384a|||||||aes.domain.org|####

@2013-05-21 13:43:22,210 CEST||INFO|com.avaya.jtapi.tsapi.tsapiInterface.TsapiSession||GetEventThread|File=TsapiSession.java,Line=730|Received invokeID 24 for TSProvider[#593]@110384a|||||||aes.domain.org|####
@2013-05-21 13:43:22,210 CEST||INFO|com.avaya.jtapi.tsapi.tsapiInterface.TsapiSession||GetEventThread|File=TsapiSession.java,Line=730|Received invokeID 24 for TSProvider[#593]@110384a|||||||aes.domain.org|####

@2013-05-21 13:43:22,210 CEST||INFO|com.avaya.jtapi.tsapi.tsapiInterface.TSInvokeID||GetEventThread|File=TSInvokeID.java,Line=51|Handling INVOKE ID 24 for TSProvider[#593]@110384a|||||||aes.domain.org|####

@2013-05-21 13:43:22,210 CEST||INFO|com.avaya.jtapi.tsapi.tsapiInterface.TSInvokeID||GetEventThread|File=TSInvokeID.java,Line=55|DONE handling INVOKE ID 24 for TSProvider[#593]@110384a|||||||aes.domain.org|####
@2013-05-21 13:43:22,210 CEST||INFO|com.avaya.jtapi.tsapi.tsapiInterface.TSInvokeID||GetEventThread|File=TSInvokeID.java,Line=55|DONE handling INVOKE ID 24 for TSProvider[#593]@110384a|||||||aes.domain.org|####

@2013-05-21 13:43:22,210 CEST||INFO|com.avaya.jtapi.tsapi.tsapiInterface.Tsapi||TP-Processor7|File=Tsapi.java,Line=979|tsapi.shutdown() called (inService = true) for TSProvider[#593]@110384a|||||||aes.domain.org|####
@2013-05-21 13:43:22,210 CEST||INFO|com.avaya.jtapi.tsapi.tsapiInterface.Tsapi||TP-Processor7|File=Tsapi.java,Line=979|tsapi.shutdown() called (inService = true) for TSProvider[#593]@110384a|||||||aes.domain.org|####

@2013-05-21 13:43:22,210 CEST||INFO|com.avaya.jtapi.tsapi.tsapiInterface.TsapiSession||TP-Processor7|File=TsapiSession.java,Line=636|Sent InvokeID 25 for TSProvider[#593]@110384a|||||||aes.domain.org|####
@2013-05-21 13:43:22,210 CEST||INFO|com.avaya.jtapi.tsapi.tsapiInterface.TsapiSession||TP-Processor7|File=TsapiSession.java,Line=636|Sent InvokeID 25 for TSProvider[#593]@110384a|||||||aes.domain.org|####
@2013-05-21 13:43:22,211 CEST||INFO|com.avaya.jtapi.tsapi.impl.core.TSProviderImpl||TP-Processor7|File=TSProviderImpl.java,Line=1408|TSProvider.shutdown - Done|||||||aes.domain.org|####
@2013-05-21 13:43:22,211 CEST||INFO|com.avaya.jtapi.tsapi.impl.core.TSProviderImpl||TP-Processor7|File=TSProviderImpl.java,Line=1408|TSProvider.shutdown - Done|||||||aes.domain.org|####

@2013-05-21 13:43:22,212 CEST||INFO|com.avaya.jtapi.tsapi.impl.core.TSProviderImpl||TP-Processor7|File=TSProviderImpl.java,Line=1343|TSProvider.shutdown - attempting shutdown|||||||aes.domain.org|####
@2013-05-21 13:43:22,212 CEST||INFO|com.avaya.jtapi.tsapi.impl.core.TSProviderImpl||TP-Processor7|File=TSProviderImpl.java,Line=1343|TSProvider.shutdown - attempting shutdown|||||||aes.domain.org|####

@2013-05-21 13:43:22,213 CEST||INFO|com.avaya.jtapi.tsapi.impl.core.TSProviderImpl||TP-Processor7|File=TSProviderImpl.java,Line=1357|TSProvider.shutdown - Starting|||||||aes.domain.org|####
@2013-05-21 13:43:22,213 CEST||INFO|com.avaya.jtapi.tsapi.impl.core.TSProviderImpl||TP-Processor7|File=TSProviderImpl.java,Line=1357|TSProvider.shutdown - Starting|||||||aes.domain.org|####

I used the TelSvcGuiClient that comes with the TWS SDK (6.2) to run a test. I have a registered station and I logged in an agent which is in skill 1 (hunt group 1). I put the agent ready and called the skill. My agent rang. I then hung up and put the agent ready.

I used the TelSvcGuiClient to call *800001 (*80 is my FAC). When I run the CM SAT command "ch hunt help" (where help is esc + h) it tells me to enter a number from 1-8000. This tells me I need to send a 4 digit hunt group, so 0001. If it says to enter 1-99 then I would send 01.

When I make that call I get three beeps to confirm that it's activated. I then call the skill group from another extension and it rings as that was the only agent in that skill and it's now not taking calls.

So the only indication I get is that beep on the phone, and the only way to see what is happening in your case is to take a look at the TSAPI logs as well. Please open a ticket with Devconnect to proceed. As a registered member we can only handle Tier 1-2 type questions at no cost and this has become a Tier 3-4 question. We have pay per hour support to handle this type of request. Once you open a ticket we can give you more information.

Edit: Paragraph 3 in my response should be more clear in that it is the hunt group that keeps ringing. The agent doesn't get a call since it's not available.