Author Message
NobuhiroTentaku
Joined: Jul 7, 2021
Messages: 93
Offline
Dear Sir,

We try to monitor all addresses taken from the provider. However to add listener to virtual extension address causes exception.
Please help and let me know what the problem is.

CTI application start
1) Make provider connection.
2) Get all extension addresses from provider.
3) Then program add CallListener and AddressListener to all addresses one by one as follows:
log.info("connect() addListeners terminal = "+(terms==null? null : terms.length+", "+(terms[0]==null? null : terms[0].getName())));
try {
addres.addCallListener(this);
} catch (TsapiResourceUnavailableException ex_call) {
int errorCode = ex_call.getErrorCode();
int errorType = ex_call.getErrorType();
log.info("addCallListener() TsapiResourceUnavailableException address = "+(address==null? null : addres.getName())+", errorCode = "+errorCode+", errorType = "+errorType);
ex_call.printStackTrace();
}
try {
addres.addAddressListener(this);
} catch (TsapiResourceUnavailableException ex_adr) {
int errorCode = ex_adr.getErrorCode();
int errorType = ex_adr.getErrorType();
log.info("addAddressListener() TsapiResourceUnavailableException address = "+(address==null? null : addres.getName())+", errorCode = "+errorCode+", errorType = "+errorType);
ex_adr.printStackTrace();
}

Here most of addresses have no problem, but all of virtual extension addresses get an exception every time when addres.addCallListener(this) and addres.addAddressListener(this) are executed.
Exception : TsapiResourceUnavailableException address = 5155, errorCode = 41, errorType = 2
Logs and exception stack traces are below:

2022/12/08 17:32:00.607 TerminalServer - connect() addListeners address = 5155
2022/12/08 17:32:00.609 TerminalServer - connect() addListeners terminal = 1, 5155
2022/12/08 17:32:00.649 TerminalServer - addCallListener() TsapiResourceUnavailableException address = 5155, errorCode = 41, errorType = 2

2022/12/08 17:32:00.651 stderr - com.avaya.jtapi.tsapi.TsapiResourceUnavailableException: CSTA Error: 41
2022/12/08 17:32:00.653 stderr - at com.avaya.jtapi.tsapi.tsapiInterface.TSErrorMap.throwCSTAException(TSErrorMap.java:95)
2022/12/08 17:32:00.653 stderr - at com.avaya.jtapi.tsapi.tsapiInterface.TsapiSession.send(TsapiSession.java:579)
2022/12/08 17:32:00.653 stderr - at com.avaya.jtapi.tsapi.tsapiInterface.TsapiSession.send(TsapiSession.java:455)
2022/12/08 17:32:00.653 stderr - at com.avaya.jtapi.tsapi.tsapiInterface.Tsapi.monitorDevice(Tsapi.java:1147)
2022/12/08 17:32:00.653 stderr - at com.avaya.jtapi.tsapi.impl.core.TSDevice.setMonitor(TSDevice.java:2992)
2022/12/08 17:32:00.653 stderr - at com.avaya.jtapi.tsapi.impl.core.TSDevice.setMonitor(TSDevice.java:2899)
2022/12/08 17:32:00.653 stderr - at com.avaya.jtapi.tsapi.impl.core.TSDevice.addAddressCallMonitor(TSDevice.java:821)
2022/12/08 17:32:00.653 stderr - at com.avaya.jtapi.tsapi.impl.core.TSDevice.addAddressCallMonitor(TSDevice.java:676)
2022/12/08 17:32:00.654 stderr - at com.avaya.jtapi.tsapi.impl.TsapiAddress.addCallEventMonitor(TsapiAddress.java:956)
2022/12/08 17:32:00.654 stderr - at com.avaya.jtapi.tsapi.impl.TsapiAddress.addCallListener(TsapiAddress.java:1355)
2022/12/08 17:32:00.654 stderr - at jp.co.daiwa.ctm.cti.agent.telephony.TerminalServer.connect(TerminalServer.java:509)
2022/12/08 17:32:00.654 stderr - at jp.co.daiwa.ctm.cti.agent.action.ConnectProviderAction.executeTemplate(ConnectProviderAction.java:65)
2022/12/08 17:32:00.654 stderr - at jp.co.daiwa.ctm.cti.agent.action.AbstractAction.execute(AbstractAction.java:86)
2022/12/08 17:32:00.654 stderr - at org.apache.struts.chain.commands.servlet.ExecuteAction.execute(ExecuteAction.java:58)
2022/12/08 17:32:00.654 stderr - at org.apache.struts.chain.commands.AbstractExecuteAction.execute(AbstractExecuteAction.java:67)
2022/12/08 17:32:00.655 stderr - at org.apache.struts.chain.commands.ActionCommandBase.execute(ActionCommandBase.java:51)
2022/12/08 17:32:00.655 stderr - at org.apache.commons.chain.impl.ChainBase.execute(ChainBase.java:191)
2022/12/08 17:32:00.655 stderr - at org.apache.commons.chain.generic.LookupCommand.execute(LookupCommand.java:305)
2022/12/08 17:32:00.655 stderr - at org.apache.commons.chain.impl.ChainBase.execute(ChainBase.java:191)
2022/12/08 17:32:00.655 stderr - at org.apache.struts.chain.ComposableRequestProcessor.process(ComposableRequestProcessor.java:283)
2022/12/08 17:32:00.655 stderr - at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1913)
2022/12/08 17:32:00.655 stderr - at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:462)
2022/12/08 17:32:00.655 stderr - at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
2022/12/08 17:32:00.655 stderr - at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
2022/12/08 17:32:00.656 stderr - at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85)
2022/12/08 17:32:00.656 stderr - at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:129)
2022/12/08 17:32:00.656 stderr - at jp.co.daiwa.ctm.cti.agent.filter.ApplicationFilter.doFilter(ApplicationFilter.java:48)
2022/12/08 17:32:00.656 stderr - at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61)
2022/12/08 17:32:00.656 stderr - at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131)
2022/12/08 17:32:00.656 stderr - at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:84)
2022/12/08 17:32:00.656 stderr - at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62)
2022/12/08 17:32:00.656 stderr - at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)
2022/12/08 17:32:00.656 stderr - at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
2022/12/08 17:32:00.657 stderr - at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
2022/12/08 17:32:00.657 stderr - at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131)
2022/12/08 17:32:00.657 stderr - at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57)
2022/12/08 17:32:00.657 stderr - at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
2022/12/08 17:32:00.657 stderr - at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
2022/12/08 17:32:00.657 stderr - at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)
2022/12/08 17:32:00.657 stderr - at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60)
2022/12/08 17:32:00.658 stderr - at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77)
2022/12/08 17:32:00.658 stderr - at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50)
2022/12/08 17:32:00.658 stderr - at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43)
2022/12/08 17:32:00.658 stderr - at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
2022/12/08 17:32:00.659 stderr - at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
2022/12/08 17:32:00.659 stderr - at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
2022/12/08 17:32:00.659 stderr - at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
2022/12/08 17:32:00.659 stderr - at io.undertow.server.handlers.MetricsHandler.handleRequest(MetricsHandler.java:62)
2022/12/08 17:32:00.659 stderr - at io.undertow.servlet.core.MetricsChainHandler.handleRequest(MetricsChainHandler.java:59)
2022/12/08 17:32:00.659 stderr - at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:285)
2022/12/08 17:32:00.659 stderr - at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:264)
2022/12/08 17:32:00.659 stderr - at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
2022/12/08 17:32:00.659 stderr - at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:175)
2022/12/08 17:32:00.659 stderr - at io.undertow.server.Connectors.executeRootHandler(Connectors.java:324)
2022/12/08 17:32:00.660 stderr - at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:803)
2022/12/08 17:32:00.660 stderr - at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
2022/12/08 17:32:00.660 stderr - at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
2022/12/08 17:32:00.660 stderr - at java.base/java.lang.Thread.run(Thread.java:834)

2022/12/08 17:32:00.688 TerminalServer - addAddressListener() TsapiResourceUnavailableException address = 5155, errorCode = 41, errorType = 2
2022/12/08 17:32:00.689 stderr - com.avaya.jtapi.tsapi.TsapiResourceUnavailableException: CSTA Error: 41
2022/12/08 17:32:00.690 stderr - at com.avaya.jtapi.tsapi.tsapiInterface.TSErrorMap.throwCSTAException(TSErrorMap.java:95)
2022/12/08 17:32:00.690 stderr - at com.avaya.jtapi.tsapi.tsapiInterface.TsapiSession.send(TsapiSession.java:579)
2022/12/08 17:32:00.690 stderr - at com.avaya.jtapi.tsapi.tsapiInterface.TsapiSession.send(TsapiSession.java:455)
2022/12/08 17:32:00.690 stderr - at com.avaya.jtapi.tsapi.tsapiInterface.Tsapi.monitorDevice(Tsapi.java:1147)
2022/12/08 17:32:00.690 stderr - at com.avaya.jtapi.tsapi.impl.core.TSDevice.setMonitor(TSDevice.java:2992)
2022/12/08 17:32:00.690 stderr - at com.avaya.jtapi.tsapi.impl.core.TSDevice.setMonitor(TSDevice.java:2899)
2022/12/08 17:32:00.690 stderr - at com.avaya.jtapi.tsapi.impl.core.TSDevice.addAddressMonitor(TSDevice.java:471)
2022/12/08 17:32:00.691 stderr - at com.avaya.jtapi.tsapi.impl.core.TSDevice.addAddressMonitor(TSDevice.java:442)
2022/12/08 17:32:00.691 stderr - at com.avaya.jtapi.tsapi.impl.TsapiAddress.addAddressListener(TsapiAddress.java:1252)
2022/12/08 17:32:00.691 stderr - at jp.co.daiwa.ctm.cti.agent.telephony.TerminalServer.connect(TerminalServer.java:517)
2022/12/08 17:32:00.691 stderr - at jp.co.daiwa.ctm.cti.agent.action.ConnectProviderAction.executeTemplate(ConnectProviderAction.java:65)
2022/12/08 17:32:00.691 stderr - at jp.co.daiwa.ctm.cti.agent.action.AbstractAction.execute(AbstractAction.java:86)
2022/12/08 17:32:00.691 stderr - at org.apache.struts.chain.commands.servlet.ExecuteAction.execute(ExecuteAction.java:58)
2022/12/08 17:32:00.692 stderr - at org.apache.struts.chain.commands.AbstractExecuteAction.execute(AbstractExecuteAction.java:67)
2022/12/08 17:32:00.692 stderr - at org.apache.struts.chain.commands.ActionCommandBase.execute(ActionCommandBase.java:51)
2022/12/08 17:32:00.692 stderr - at org.apache.commons.chain.impl.ChainBase.execute(ChainBase.java:191)
2022/12/08 17:32:00.692 stderr - at org.apache.commons.chain.generic.LookupCommand.execute(LookupCommand.java:305)
2022/12/08 17:32:00.692 stderr - at org.apache.commons.chain.impl.ChainBase.execute(ChainBase.java:191)
2022/12/08 17:32:00.692 stderr - at org.apache.struts.chain.ComposableRequestProcessor.process(ComposableRequestProcessor.java:283)
2022/12/08 17:32:00.692 stderr - at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1913)
2022/12/08 17:32:00.692 stderr - at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:462)
2022/12/08 17:32:00.693 stderr - at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
2022/12/08 17:32:00.693 stderr - at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
2022/12/08 17:32:00.693 stderr - at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85)
2022/12/08 17:32:00.693 stderr - at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:129)
2022/12/08 17:32:00.693 stderr - at jp.co.daiwa.ctm.cti.agent.filter.ApplicationFilter.doFilter(ApplicationFilter.java:48)
2022/12/08 17:32:00.693 stderr - at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61)
2022/12/08 17:32:00.693 stderr - at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131)
2022/12/08 17:32:00.694 stderr - at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:84)
2022/12/08 17:32:00.695 stderr - at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62)
2022/12/08 17:32:00.695 stderr - at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)
2022/12/08 17:32:00.695 stderr - at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
2022/12/08 17:32:00.696 stderr - at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
2022/12/08 17:32:00.696 stderr - at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131)
2022/12/08 17:32:00.696 stderr - at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57)
2022/12/08 17:32:00.696 stderr - at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
2022/12/08 17:32:00.696 stderr - at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
2022/12/08 17:32:00.696 stderr - at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)
2022/12/08 17:32:00.697 stderr - at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60)
2022/12/08 17:32:00.697 stderr - at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77)
2022/12/08 17:32:00.697 stderr - at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50)
2022/12/08 17:32:00.697 stderr - at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43)
2022/12/08 17:32:00.697 stderr - at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
2022/12/08 17:32:00.697 stderr - at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
2022/12/08 17:32:00.697 stderr - at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
2022/12/08 17:32:00.698 stderr - at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
2022/12/08 17:32:00.698 stderr - at io.undertow.server.handlers.MetricsHandler.handleRequest(MetricsHandler.java:62)
2022/12/08 17:32:00.698 stderr - at io.undertow.servlet.core.MetricsChainHandler.handleRequest(MetricsChainHandler.java:59)
2022/12/08 17:32:00.698 stderr - at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:285)
2022/12/08 17:32:00.698 stderr - at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:264)
2022/12/08 17:32:00.698 stderr - at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
2022/12/08 17:32:00.698 stderr - at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:175)
2022/12/08 17:32:00.698 stderr - at io.undertow.server.Connectors.executeRootHandler(Connectors.java:324)
2022/12/08 17:32:00.699 stderr - at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:803)
2022/12/08 17:32:00.699 stderr - at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
2022/12/08 17:32:00.699 stderr - at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
2022/12/08 17:32:00.699 stderr - at java.base/java.lang.Thread.run(Thread.java:834)

Thank you for your help in advance.

Best regards,
JohnBiggs
Joined: Jun 20, 2005
Messages: 1139
Location: Rural, Virginia
Offline
Devices must be registered on Communication Manager in order for a monitor to be established.
Check at the SAT with 'list registered-ip-station XXXX' where XXXX is the station extension.

Are these SIP stations or H.323?
NobuhiroTentaku
Joined: Jul 7, 2021
Messages: 93
Offline
Hi John,

SIP stations.
Thank you very much for your help and quick resoinse.
We are going to check registered-ip-station list probably tomorrow.

Best regards,
MartinFlynn
Joined: Nov 30, 2009
Messages: 1922
Offline
I thought I had replied earlier but apparently not...

According to the TSAPI Programmers Guide, MonitorDevice can cause error 41 under the following circumstances:

GENERIC_SUBSCRIBED_RESOURCE_AVAILABILITY (41)
The request has failed for one of the following reasons:
– A required feature has not been provisioned or enabled. For
example:
? The deviceID corresponds to a station with type “CTI” and
the “CTI Stations” feature is not enabled on
Communication Manager.
? The deviceID corresponds to a non-CTI station
administered without hardware (AWOH) and the “Phantom
Calls” feature is not enabled on Communication Manager.
? The deviceID corresponds to a SIP station, and the “Type
of 3PCC Enabled” administered for the station is not set to
“Avaya”.
? The device ID corresponds to a SIP station, and there is
an off-pbx-telephone station-mapping administered for
deviceID on Communication Manager.
– The TSAPI Service could not acquire the license(s) needed to
satisfy the request.

Make sure to get a copy of "TSAPI for Avaya Communication Manager Programmer's Reference". It is very useful information when dealing with JTAPI.

Martin
NobuhiroTentaku
Joined: Jul 7, 2021
Messages: 93
Offline
Hi Martin,

Thank you very much always for your detailed information and quick response.
We are going to transfer your information above to those who are responsible for configuring CM.

Best regards,
NobuhiroTentaku
Joined: Jul 7, 2021
Messages: 93
Offline
Hi Martin,

Sorry to bother you again.
According to your advice engineers responsible for CM are trying to fix problems.
They check and fix it and we got some improvements. Thank you.
However regarding 2 advices below they do not understand how to change which parameters.
Could you please let us know your suggestion and advice again.

1) The deviceID corresponds to a station with type “CTI” and the “CTI Stations” feature is not enabled on Communication Manager.

2) The deviceID corresponds to a non-CTI station administered without hardware (AWOH) and the “Phantom Calls” feature is not enabled on Communication Manager.

Thank you very much for your help in advance.
Best regards,


MartinFlynn
Joined: Nov 30, 2009
Messages: 1922
Offline
When you configure a Station on Communication Manager, you must configure a Type. Normally this is something like a normal telephone type, e.g. 9621. However, there are some other Types which are for special features (e.g. CTI). As far as I know, these features are quite old and are unlikely to be in use in your system.

Most likely, your problem is due to 3PCC - this happens quite often.

Martin
NobuhiroTentaku
Joined: Jul 7, 2021
Messages: 93
Offline
Hi Martin,

Thank you for your response and advaice.

Best regards,
NobuhiroTentaku
Joined: Jul 7, 2021
Messages: 93
Offline
CM engineers are trying to fix virtual extension and virtual ringer.
There are some questions which we would like to ask you.
1) The parameter 3PCC enable to Avaya is only good for real extension, so 3PCC enable to Avaya cannnot be used for virtual extension. Is this correct?
2) Therefore they set 6408D+ or virtual to type to set up virtual extension and virtual ringer.
Our problems as follows:
2-1) Adding CallListener is failed due to exception.
2-2) Functions of virtual extension and virtual ringer does NOT work as telephone system.
Attached, please find list registered-ip-stations and just look at 5196-5199 setup of virtual extensions.
I really appreciate if you give us advice and / or suggestions to fix problems.

Best regards,
NobuhiroTentaku
Joined: Jul 7, 2021
Messages: 93
Offline
NobuhiroTentaku wrote:CM engineers are trying to fix virtual extension and virtual ringer.
There are some questions which we would like to ask you.
1) The parameter 3PCC enable to Avaya is only good for real extension, so 3PCC enable to Avaya cannnot be used for virtual extension. Is this correct?
2) Therefore they set 6408D+ or virtual to type to set up virtual extension and virtual ringer.
Our problems as follows:
2-1) Adding CallListener is failed due to exception.
2-2) Functions of virtual extension and virtual ringer does NOT work as telephone system.
Attached, please find list registered-ip-stations and just look at 5196-5199 setup of virtual extensions.
I really appreciate if you give us advice and / or suggestions to fix problems.

Best regards,
Filename export-station.xlsx [Disk] Download
JohnBiggs
Joined: Jun 20, 2005
Messages: 1139
Location: Rural, Virginia
Offline
earlier in the thread you mentioned you wer working with SIP stations. Are extensions 5196-5199 SIP stations?

3PCC can be enabled regardless of what is going to register to the extension.
can you explain a bit further what you mean by a 'virtual extension' do you mean a softphone like one-X Communicator or a DMCC application or ?? A similar question for a 'virtual ringer' can you explain a bit more about what you are trying to accomplish with a 'virtual ringer' please?

For item 2-1 (CallListener) can you enable FINEST tracing in DMCC and look at the dmcc-trace log where the listener request is processed and provide the details from the request and response. please see https://www.devconnectprogram.com/site/global/products_resources/avaya_aura_application_enablement_services/support/faq/dmcc/index.gsp?tab=other&accordion=faq-60 for details on enabling tracing.

NobuhiroTentaku
Joined: Jul 7, 2021
Messages: 93
Offline
Hi John,

Attached, please find a diagram file, named ExtensionType.pptx which I got from CM engineers.
In this diagram yellow elipse shows type for the extension. Make sure we are working with SIP stations.
Type "virtual" is set to virtual extension 5198 which is vector-transferred to coverage answer group, virtual ringer 5196 and 5197 without ringing.
Type "6408D+" is set to virtual ringer 5196 and 5197 which are transferred to TeanButton PickupGroup with ringing.
Type "J179" is set to real extension 5003, 5004, 5005 and 5119.
However implementation on the diagram does NOT work as they want.

They want to use virtual extension and virtual ringer instead of real extension. This is because they want to reduce cost, therefore they want to reduce physical equipments.

Regarding "3PCC Enabled" they want to know how to use the parameter "3PCC Enabled"=Avaya for virtual extension/ringing.
Or They want to know other values instead of Avaya for "3PCC Enabled".

Regarding FINEST tracing in DMCC, since they do NOT use DMCC, they wonder that there is another tracing method for SIP? Is tracing in DMCC good for SIP too?

That's all. Based on the attached diagram your advice and suggestion are really appreciated.

Best regards,
NobuhiroTentaku
Joined: Jul 7, 2021
Messages: 93
Offline
NobuhiroTentaku wrote:Hi John,

Attached, please find a diagram file, named ExtensionType.pptx which I got from CM engineers.
In this diagram yellow elipse shows type for the extension. Make sure we are working with SIP stations.
Type "virtual" is set to virtual extension 5198 which is vector-transferred to coverage answer group, virtual ringer 5196 and 5197 without ringing.
Type "6408D+" is set to virtual ringer 5196 and 5197 which are transferred to TeanButton PickupGroup with ringing.
Type "J179" is set to real extension 5003, 5004, 5005 and 5119.
However implementation on the diagram does NOT work as they want.

They want to use virtual extension and virtual ringer instead of real extension. This is because they want to reduce cost, therefore they want to reduce physical equipments.

Regarding "3PCC Enabled" they want to know how to use the parameter "3PCC Enabled"=Avaya for virtual extension/ringing.
Or They want to know other values instead of Avaya for "3PCC Enabled".

Regarding FINEST tracing in DMCC, since they do NOT use DMCC, they wonder that there is another tracing method for SIP? Is tracing in DMCC good for SIP too?

That's all. Based on the attached diagram your advice and suggestion are really appreciated.

Best regards,
  • [Thumb - ExtensionType.png]
[Disk] Download
JohnBiggs
Joined: Jun 20, 2005
Messages: 1139
Location: Rural, Virginia
Offline
the original problem statement referenced x5155 which is not in the diagram.
2022/12/08 17:32:00.607 TerminalServer - connect() addListeners address = 5155

Which stations in the diagram are you having problems establishing monitors on?

5196 and 5197 do not need to be SIP stations, you are better off making them H.323 stations.


Please review this FAQ as it relates to getting CTI to work on Avaya SIP extensions.
https://www.devconnectprogram.com/site/global/products_resources/avaya_aura_application_enablement_services/support/faq/index.gsp?tab=general-services&accordion=faq-76
NobuhiroTentaku
Joined: Jul 7, 2021
Messages: 93
Offline
5155 in the previous log is old and 5196, 5197 and 5198 have the same problem as 5155.

Thank you for your help.

Best regards,
Go to:   
Mobile view