I downloaded the pre-compiled version - 7.0.0 and start it up on CentOS 7. It works fine.
Then I download the latest version - 7.1.0-142 (with sources of the dependencies) to compile. All are success.
But after I updated the folders, files to the jboss and start it up. there's error about ShellExecutor. Do yo have any idea? thanks.

2021-09-01 04:04:47,556 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (main) Error installing to Instantiated: name=ShellExecutor state=Described
java.lang.InstantiationException
at sun.reflect.InstantiationExceptionConstructorAccessorImpl.newInstance(InstantiationExceptionConstructorAccessorImpl.java:48)
at java.lang.reflect.Constructor.newInstance(Constructor.java:527)
at org.jboss.reflect.plugins.introspection.ReflectionUtils.newInstance(ReflectionUtils.java:149)
at org.jboss.reflect.plugins.introspection.ReflectConstructorInfoImpl.newInstance(ReflectConstructorInfoImpl.java:106)
at org.jboss.joinpoint.plugins.BasicConstructorJoinPoint.dispatch(BasicConstructorJoinPoint.java:80)
at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.createTarget(AOPConstructorJoinpoint.java:282)
at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.dispatch(AOPConstructorJoinpoint.java:103)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:241)
at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:109)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:70)
at org.jboss.kernel.plugins.dependency.InstantiateAction.installActionInternal(InstantiateAction.java:66)
at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54)
at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42)
at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:774)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:540)
at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:121)
at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:51)
at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)
at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)
at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
at org.jboss.Main.boot(Main.java:221)
at org.jboss.Main$1.run(Main.java:556)
at java.lang.Thread.run(Thread.java:748)

We need to add an internal statistic counters for message received / sent, dialogs, messages per CAP operations etc like we have for SMSC GW and USSD GW.

For every USSD sent or received either through SMPP or SS7 we should ping the Restcomm statistics server at the end of the day. The integration on the USSD GW side happens through this project https://github.com/RestComm/commons/tree/master/statistics.

hi
i build release folder and it create restcomm-camel-7.1.0-SNAPSHOT.zip
now how can i use it?
please help

We do not have GUI WEB management console for CAMEL GW configuring part. Let's prepare thsi one:
http://localhost:8080/camel-management

We need to add a possibility of sending of empty TC-CONTINUE not only at the state of TCAP dialog initiating. We have code now (CamelGatewaySbb.onResponseEvent()):

if (capDialog.getState() == CAPDialogState.InitialReceived ||
prearrangedEnd != null || xmlCAPDialog.getErrorComponents().size() > 0 || 
xmlCAPDialog.getCAPMessages().size() > 0)
{ <sendig response ...> }

We need to to remove of checking of if CAP messages error messages count is 0.
Zendesk ticket for it was 33733

We have some issues in Javolution 5.5.1 - xml part of it does not properly decode "\n" characters inside a String value: (decimal values like are processed well).

Javolution 6.1 is patched for it. But starting from version 6.0 it has different API interface and swithcing to this version needs the major code update. FastMap is replaced to other class(es) and XML part is also changed. We need to switch to all GWs at the single step because we can not use at the same server both Javolution 5.5 and 6.1.

Before this we need to fix the issue: RestComm/jss7#61

We need to add into release binaries jboss-beans.xml templates for cases:

• META-INF-dialogic
• META-INF-m3ua-dialogic
  The main example is for m3ua case only.

we can provide it in may be "templates/META-INF-templates" folder (subfolders META-INF-dialogic and META-INF-m3ua-dialogic).

We need to make follows:

1. add "appender name="CSVSTATS"" and "category name="org.mobicents.protocols.ss7.oam.common.statistics.CsvStatsPrinter"" into all jboss-log5j.xml templates
2. all jboss-beans.xml -
   <bean name="ShellExecutor" class="org.mobicents.ss7.management.console.ShellServer"> -> <bean name="ShellExecutor" class="org.mobicents.ss7.management.console.ShellServerJboss">
3. GUI - managecampaigns.html - update for configuring of statistic output format
4. java compilation error fixing

Check for more info RestComm/smscgateway#211

We need to specify in the manual (Installation Pre-Requisites) that the only supported JAVA version is JAVA7 (+Oralce/64 is prefered)

When trying to build the gateway, the following warning is thrown

[WARNING] The POM for com.vendor.dialogic:gctapi:jar:6.7.1 is missing, no dependency information available

Which fails the build process.

No possibility of an appliction to initiate any requests itself, so no PUSH mode. PUSH mode can be usefull for "assistRequestInstructions" (SCF can initiate a call by issuing of this invoke) and for "activityTest" operation. PUSH requests from an application for the single dialog can be combined with PULL HTTP requests.

We need to add of non regression CI job for performance

DialogTimeout problem. Now we just ignore any DialogTimeout and keep a Dialog active. We have a risk that if a peer (SSF, SRF) part has been dead without CAMEL GW announsing than this activity will be alive forever (-> resourses will be overloaded).

The regular solution is - using of "activityTest" operation. Now CAP stack supports serializing for it and a CAMEL application. Also we have now "No activity call to HTTP Application" (https://telestax.atlassian.net/browse/CAMELGW-22) when Dialog is active too much time without messageflow

We need to make:

1. add support for sending of activityTest request / receiving of activityTest response
2. send InvokeTimeout announsements for any InvokeTimeout (including activityTest) to a CAMEL application