Re: STUN Server vs. NAT Configuration with Kamailio + RTPengine Setup

Henning Westerholt via sr-users <[email protected]>
Newsgroups gmane.comp.voip.ser
Message-ID <VI1PR07MB94581AC2819B14717A937E55BFB62@VI1PR07MB9458.eurprd07.prod.outlook.com>
Hello,

usually, a STUN server is not needed if your clients behave appropriate. Microsip should be fine, if you don't configured something strange.

Regarding test cfg, the default Kamailio configuration should usually work with the appropriate #!defines set.

Cheers,

Henning

> -----Original Message-----
> From: Fernando Lopes via sr-users <[email protected]>
> Sent: Donnerstag, 10. April 2025 15:48
> To: [email protected]
> Cc: Fernando Lopes <[email protected]>
> Subject: [SR-Users] STUN Server vs. NAT Configuration with Kamailio +
> RTPengine Setup
> 
> Previous Thread: https://kamailio.org/mailman3/hyperkitty/list/sr-
> [email protected]/thread/4U545DU5NHHPH23E3H5KVAHZMTVPWOR
> 4/
> 
> Hello everyone,
> 
> Should I use a STUN server, or can I just configure NAT properly?
> 
> Here’s my current setup:
> 
> arduino
> Copy
> Edit
> Router (NAT device)
>    ↓
> Kamailio + RTPengine machine
>    ↓
> Virtual machine running Kubernetes
>    ↓
> Asterisk container
> Kamailio and RTPengine are sitting behind the NAT (the router), and they
> handle SIP and media. Do I need a STUN server in this case, or can I manage
> everything with NAT configuration alone?
> And what is the better approach?
> 
> Any insights or best practices would be appreciated!
> Thank you.
> __________________________________________________________
> Kamailio - Users Mailing List - Non Commercial Discussions -- sr-
> [email protected] To unsubscribe send an email to sr-users-
> [email protected]
> Important: keep the mailing list in the recipients, do not reply only to the
> sender!
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions -- [email protected]
To unsubscribe send an email to [email protected]
Important: keep the mailing list in the recipients, do not reply only to the sender!
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.