microsoftgraph / microsoftgraph/microsoft-graph-comms-samples
[PolicyRecordingBot] - When running locally, call never connects
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 253
- Forks
- 275
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 1
Description
I'm attempting to debug the Policy Recording Bot by running it locally, but when making a call, it rings a few times then the user sees "Forwarding to Voicemail", and a few seconds later the message "Sorry, we couldn't connect you". The call ends, and it does not go to voicemail.
While the call is establishing, I see multiple requests to OnIncomingRequestAsync and OnNotificationRequestAsync happening successfully, which leads me to believe that the issue is with the media port.
My local media port is 8445, and I'm using ngrok to attempt to tunnel traffic to this port.


To troubleshoot, I've tried connecting to the public and local media ports, and they each seem to be open:

Also, it looks like localhost:8445 is being reached. Each time I make a call, the Connections count for the media tunnel increases (highlighted in screenshot).

I've seen other people asking about similar issues here, but none of the proposed solutions in those threads has worked for me. Any help or troubleshooting guidance will be much appreciated.
Trace messages from while a call is establishing are attached:
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 with the attached PolicyRecordingBot-trace.log and the OnIncomingRequestAsync and OnNotificationRequestAsync activity described in the issue. Reproduce the local call through the ngrok tunnel on port 8445, then compare media-port behavior with the call flow. Done means identifying why the call fails to connect or documenting the missing configuration and a verified fix.
Written by the indexing model from the issue text.
Assessment
- Domain
- audio-video-rtc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100