# Revisiting Matrix Calls Through STUNner

**URL:** <https://openziti.discourse.group/t/revisiting-matrix-calls-through-stunner/3961>\
**Category:** General Questions\
**Created:** [February 14, 2025, 1:49am UTC](https://openziti.discourse.group/t/revisiting-matrix-calls-through-stunner/3961 "2025-02-14T01:49:29Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![thedarkula](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/thedarkula/32/1459_2.png) [@thedarkula](https://openziti.discourse.group/u/thedarkula)\
**Post date:** [February 14, 2025, 4:52pm UTC](https://openziti.discourse.group/t/revisiting-matrix-calls-through-stunner/3961/3 "2025-02-14T16:52:25Z")

</div>

Pardon, this is coming from a portion of the megathread, here: [Helm Port Mappings - #129 by thedarkula](https://openziti.discourse.group/t/helm-port-mappings/1631/129)

STUNner is a STUN/TURN implementation for kubernetes: [GitHub - l7mp/stunner: A Kubernetes media gateway for WebRTC. Contact: info@l7mp.io](https://github.com/l7mp/stunner)

As far as the logs I mentioned, those are coming from stunner when trying to initiate a matrix video call through element, but the strange IP address also shows up in the ziti router logs.

I was hoping that it was allocated through some ziti magic that I was unfamiliar with.

---

_[View the full topic](https://openziti.discourse.group/t/revisiting-matrix-calls-through-stunner/3961)._