RestComm/Restcomm-Connect

RouteSelectFailureSpecificInfoImpl toString curley bracket

Opened this issue · 0 comments

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

/kind feature

What happened:
When trying to print a cap message of type (EventReportBCSMRequestImpl) using toString() method, it will print the 'legID' and 'miscCallInfo' in separate parts than the main message part.

What you expected to happen:
The 'leg' id and 'miscCallInfo' should be printed inside the main message part

How to reproduce it (as minimally and precisely as possible):
Just call toString() for any EventReportBCSMRequestImpl message and the issue will raise.

Anything else we need to know?:
After debugging, I found that the problem is in the RouteSelectFailureSpecificInfoImpl.toString() method where a curly bracket '{' printed mistakenly instead of the bracket '['
I can fix this issue directly if you let me do a PR. User name is 'mon205'

Environment:

  • Restcomm Connect version (from startup logs): cap-impl 8.0.0-179
  • Cloud provider or hardware configuration: direct usage of cap-impl libraries
  • OS (e.g. from /etc/os-release): Windows 10
  • Kernel (e.g. uname -a):
  • Deployment method (e.g. docker-compose, with linked docker-compose.yml file,
    or application server info + deployment option):
  • Others: I am using the cap libraries directly (jSS7 jar files).