microsoftgraph / microsoftgraph/microsoft-graph-comms-samples
Networking Requirements for local debugging (Firewall rules and corporate networks)
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 253
- Forks
- 275
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 1
Description
It is not entirely clear, how the TcpCheck of the Skype Media packages works.
I am unable to debug the local media bots like HueBot locally due to restricted/militarized networking in my corporate network.
I can temporarily circumvent the networking restrictions by tethering via LTE and I can successfully run the bot samples.
Is there any schematic on which ports need to be open (incoming/outgoing) for a bot to work properly.
Are ngrok generated ports required to be available from the bot itself? In general ngrok works fine in my network, but connecting outwards to that tcp port would be a problem if required.
That would enable me to create a ticket with my IT service to poke the necessary holes into our corporate network to facilitate me debugging bots on my machine.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by investigating how TcpCheck in the Skype Media packages establishes connections when running the HueBot and other local bot samples. Document the required incoming and outgoing ports, including whether ngrok-generated ports must be reachable from the bot, so the resulting guidance can be used for a corporate firewall request.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, networking
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100