Skip to content

Check issues at TADHack environment reported by some participants #2498

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ghjansen opened this issue Sep 13, 2017 · 3 comments
Closed

Check issues at TADHack environment reported by some participants #2498

ghjansen opened this issue Sep 13, 2017 · 3 comments
Assignees
Labels

Comments

@ghjansen
Copy link
Contributor

Issues are related to:

  • Record verb not working;
  • Project upload;
  • Missing tabs when opening an existent project.
@ghjansen ghjansen added this to the Video-RCML-Sprint-3 milestone Sep 13, 2017
@ghjansen ghjansen self-assigned this Sep 13, 2017
@ghjansen
Copy link
Contributor Author

Record verb not working;

This seems like a network instability. Restcomm issues the commands normally to XMS, but they are not received from XMS server, even when the firewall is off. Latest tests shown resource working normally, so its apparently stabilized.

Project upload;

The project used during the upload is from a version newer than the ones currently supported by TADHack environment. Project versions supported at TADHack environment are: "rvd714","1.0", "1.1", "1.2", "1.3", "1.4", "1.5", "1.6", "1.7", "1.8","1.9", "1.10" (source)

Missing tabs when opening an existent project.

Remembering opened tabs per project is a resource under development. Check #213 and RestComm/visual-designer#69 for more info.

@ghjansen
Copy link
Contributor Author

Participant still complaining about not being able to access the URL for a recording.

Also, the application that issues the record verb doesn't seems to behave as expected. No beeps were heard by reaching the Record verb.

@ghjansen ghjansen reopened this Sep 18, 2017
@ghjansen
Copy link
Contributor Author

Further investigation from server log showed that Restcomm received BYE message from client's participant in the middle of the call flow, thus breaking resources involved such as the recording file.

Participant was using a Desktop SIP client. Few tests were required using Web Olympus instead, but the participant never reported back.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant