[SR-Users] out of shm without any visible reason

K reported during about 90 sec period that it is out of shared memory: Feb 28 09:47:28 rox1 /usr/bin/sip-proxy[19725]: ERROR: tm [t_hooks.c:136]: insert_tmcb(): out of shm. mem Feb 28 09:47:28 rox1 /usr/bin/sip-proxy[19725]: ERROR: acc [acc_logic.c:394]: acc_onreq(): cannot register additional

Re: [SR-Users] out of shm without any visible reason

The times we've seen this is when transactions are waiting on something so they pile up consuming shared memory. Do you have any database lookups or calls out to external services or scripts? Long timeouts can also contribute if something stops responding because transactions are waiting for a

Re: [SR-Users] How to detect NAT during authenticated registration of clients which adjust the headers

But why it becomes a problem? It looks like client reloves NAT issue on his side. So during the call of this user you will send request to the proper destination address anyway. On Fri, 28 Feb 2020, 18:03 David Villasmil, wrote: > Can you paste the challenge and responses? > > On Fri, 28 Feb

Re: [SR-Users] How to detect NAT during authenticated registration of clients which adjust the headers

Can you paste the challenge and responses? On Fri, 28 Feb 2020 at 14:50, Awal Junanto wrote: > I added a call to add_uri_param("nat=yes") before auth_challenge("$fd", > "0"), but couldn't see any difference in the actual SIP messages. The > challenge (and the response) didn't contain that newly

Re: [SR-Users] How to detect NAT during authenticated registration of clients which adjust the headers

I added a call to add_uri_param("nat=yes") before auth_challenge("$fd", "0"), but couldn't see any difference in the actual SIP messages. The challenge (and the response) didn't contain that newly added keyword. Or am I missing something here? On Fri, 28 Feb 2020 at 13:58, David Villasmil <

Re: [SR-Users] How to detect NAT during authenticated registration of clients which adjust the headers

There probably is a better way of doing this, but maybe you can store the fact that the first register came from a natted device in the locations table (or a hash). Or maybe add a parameter when challenging where you state the client is natting? Something like this

Re: [SR-Users] dlg.end_dlg on RTP timeout

> On 13-Feb-2020, at 7:00 PM, Daniel-Constantin Mierla > wrote: > > The xmlrpc module has its own callback, you should not use the one from xhttp > module, see: > > - > https://kamailio.org/docs/modules/5.3.x/modules/xmlrpc.html#xmlrpc.pevent_callback > >

[SR-Users] How to detect NAT during authenticated registration of clients which adjust the headers

Hi, We are building a service where we need to detect NAT when the clients register to our server. We are struggling in analyzing NAT status of some clients which modify their IP addresses/ports in the headers according to the value of "received" parameter sent during "401 Unauthorized" response.

Re: [SR-Users] I need to configure apns push notification in kamailio

I am new in kamailio, So kindly provide me some examples of configuration files and step by step guide of this. kindly find the attachment of my configuration file and guide me according to this. Sent with [ProtonMail](https://protonmail.com) Secure Email. ‐‐‐ Original Message ‐‐‐ On