You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
07:27:20,722 ERROR [org.restcomm.connect.telephony.Call] (RestComm-akka.actor.default-dispatcher-25) No transition could be found from a(n) completed state to a(n) failed state.: org.restcomm.connect.commons.fsm.TransitionNotFoundException: No transition could be found from a(n) completed state to a(n) failed state.
at org.restcomm.connect.commons.fsm.FiniteStateMachine.transition(FiniteStateMachine.java:60) [restcomm-connect.commons-8.0.0.1102.jar:8.0.0.1102]
at org.restcomm.connect.telephony.Call.onReceive(Call.java:447) [restcomm-connect.telephony-8.0.0.1102.jar:8.0.0.1102]
at akka.actor.UntypedActor$$anonfun$receive$1.applyOrElse(UntypedActor.scala:159) [akka-actor_2.10-2.1.2.jar:]
at akka.actor.ActorCell.receiveMessage(ActorCell.scala:425) [akka-actor_2.10-2.1.2.jar:]
at akka.actor.ActorCell.invoke(ActorCell.scala:386) [akka-actor_2.10-2.1.2.jar:]
at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:230) [akka-actor_2.10-2.1.2.jar:]
at akka.dispatch.Mailbox.run(Mailbox.scala:212) [akka-actor_2.10-2.1.2.jar:]
at akka.dispatch.ForkJoinExecutorConfigurator$MailboxExecutionTask.exec(AbstractDispatcher.scala:506) [akka-actor_2.10-2.1.2.jar:]
at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:262) [scala-library-2.10.1.jar:]
at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:975) [scala-library-2.10.1.jar:]
at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1478) [scala-library-2.10.1.jar:]
at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:104) [scala-library-2.10.1.jar:]
The text was updated successfully, but these errors were encountered:
* master:
Changed version to 8.1.0-SNAPSHOT
Restcomm load test scripts, change conference RCML app to use Play instead of Say so we don't get error from TTS service in case of excesive TTS requests
fix#1670fix#1669
* master: (21 commits)
added sender email
send notification only when call is hangingup due to disk cache failure
removed error from msg
changed notification type
readded tostring
made statment like before
made statment like it was before
called super method
added notification for disk errors and improved log level
changes log level and replace log position for disk cache errors
Changed version to 8.1.0-SNAPSHOT
Restcomm load test scripts, change conference RCML app to use Play instead of Say so we don't get error from TTS service in case of excesive TTS requests
UI improvements for drop-area in AdminUI/apps view
Fixed broken 'status_callback' in AdminUI incoming number form
Fixed broken application link in Incoming number details
fix#1670fix#1669
Implement Register Number and Register Client
Implement Logs - Messages, Recordings, Transcriptions & Notifications
Implement Logs - Calls
Implement Numbers / Clients details & Other fixes
...
The text was updated successfully, but these errors were encountered: