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
When PlayCollect fires OF event, it creates a response containing an error message.
This format is wrong and do not follow the standards.
For this reason, we get an exception on RestComm side (because it expects to parse the response code):
13:29:14,300 ERROR org.mobicents.servlet.restcomm.mgcp.IvrEndpoint null: java.lang.NumberFormatException: null
at java.lang.Integer.parseInt(Integer.java:454) [rt.jar:1.7.0_79]
at java.lang.Integer.parseInt(Integer.java:527) [rt.jar:1.7.0_79]
at org.mobicents.servlet.restcomm.mgcp.IvrEndpoint.notification(IvrEndpoint.java:167) [restcomm.mgcp-7.6.0.873.jar:]
at org.mobicents.servlet.restcomm.mgcp.IvrEndpoint.onReceive(IvrEndpoint.java:125) [restcomm.mgcp-7.6.0.873.jar:]
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:
…aying next, previous or current announcement.
patches #167 Operation Failed (of) events now containa reason code (rc) instead of logging the exception message.
When PlayCollect fires OF event, it creates a response containing an error message.
This format is wrong and do not follow the standards.
For this reason, we get an exception on RestComm side (because it expects to parse the response code):
The text was updated successfully, but these errors were encountered: