[SR-Users] Re: DMQ read message too large

-- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com > -----Original Message----- > From: Calvin E. via sr-users sr-users@lists.kamailio.org > Sent: Sonntag, 30. März 2025 17:40 > To: Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org > Cc: Calvin E. calvine@gmail.com > Subject: [SR-Users] Re: DMQ read message too large > > Any guidance on using TCP for DMQ, or the maximum recommended htable > size when using DMQ replication? > > On Fri, Mar 21, 2025 at 3:30 PM Calvin E. calvine@gmail.com wrote: > > > > I see msg_recv_max_size defaults to 32767. I don't mind increasing > > this, but what is sane for DMQ htable replication? > > > > On Fri, Mar 21, 2025 at 3:09 PM Calvin E. calvine@gmail.com wrote: > > > > > > We are seeing errors like this when synchronizing htables over DMQ: > > > > > > ERROR: <core> [core/udp_server.c:677]: udp_rcv_loop(): read message > > > too large: 60793 > > > > > > We have no issues with other UDP fragments caused by STIR/SHAKEN > > > headers. Our socket buffers are sufficiently large (SO_RCVBUF is > > > initially 26214400). Does DMQ have a receive message size limit less > > > than what it can send? > > > > > > Is DMQ intended for htables under a certain total size? > > > > > > We tried to configure DMQ to use a TCP listener with ;transport=tcp > > > on the notification and server address, but the DMQ traffic was > > > still sent as UDP. The example in the documentation shows TLS, but > > > we haven't tried that. > > > > > > -Calvin E. > __________________________________________________________ > Kamailio - Users Mailing List - Non Commercial Discussions -- sr- > users@lists.kamailio.org To unsubscribe send an email to sr-users- > leave@lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only to the > sender!