Skip to content
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

TROUBLESHOOTING with SayCel App #113

Open
Tcat1 opened this issue Oct 28, 2017 · 6 comments
Open

TROUBLESHOOTING with SayCel App #113

Tcat1 opened this issue Oct 28, 2017 · 6 comments

Comments

@Tcat1
Copy link

Tcat1 commented Oct 28, 2017

Trouble Shooting For SayCel App.
ISSUE Calls are not connecting.
1st Check if local internet backhaul is up, working and connected to Network.
Ways to check backhaul,
Log into bsc and ping saycel.com, if you see no bytes received Backhaul is down
Make an International Call with your local Network Chip, if call cannot connect backhaul is down
2nd If, Internet Backhaul is working check your VOIP accounts.
Log onto Website of your VOIP account,
Check Credit and also check to see if VOIP accounts are connected to BSC.
A page on website of VOIP account will indicated your account is connected to Network normally showing a FREESWITCH protocol.
If you have no credit or you see voip accounts are connected to network, VOIP account is down.
3rd IF VOIP account and Internet Backhaul are both working report issue in TelGram SayCel App Group Chat for further assistance.

@gmarcos87
Copy link
Collaborator

Sounds good, but all these steps are only executable if you are within the GSM network of Saycel or if you have credentials to access services and servers. There is a way to make these checks automatically and accessible via the web. Like https://status.github.com/messages

If you like this this link we can edit this and then add it to Readme.md

@rodrigomonelos
Copy link
Collaborator

rodrigomonelos commented Nov 6, 2017

Sounds good, but all these steps are only executable if you are within the GSM network of Saycel or if you have credentials to access services and servers.

I guess that for the moment (until we work on the suggestion below) we should add a comment explaining that pre-conditions, or who is the person/role that performs this steps. Don't we?

There is a way to make these checks automatically and accessible via the web. Like https://status.github.com/messages

This would be an improvement proposal, right? Creating a tool that gives this info automatically?

If you like this this link we can edit this and then add it to Readme.md

I like very much that HackMD tool

Do you see yourself @gmarcos87 adding below your steps for troublreshooting in case that Thomas reports a case like this one?

@gmarcos87
Copy link
Collaborator

Thomas does not report any particular case, just how to analyze the possible connection problems of the SayCel infrastructure. It is more of a way to rule out problems that are not the application itself and to avoid reporting false errors.

@rodrigomonelos
Copy link
Collaborator

I updated the style on my previous comment, I guess that most of my opinions where lost in between the qoutes.
Lo que te preguntaba en la última frase @gmarcos87 era si vos tenés pasos para agregar, suponiendo la siytuación de que Thomas ejecuta los pasos que describió y no encuentra el problema.

@gmarcos87
Copy link
Collaborator

Me parece que está bien para descartar problemas propios de la configuración de SayCel. No creo necesario agregar nada extra.

@sanchi
Copy link
Collaborator

sanchi commented Nov 17, 2017

not sure this is the right place (should it go into the repository itself as md?), but I'm for now attaching a bit about troubleshooting the WebRTC gateway server part:
debugging_server.txt

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

No branches or pull requests

4 participants