14 Sep
2020
14 Sep
'20
1:37 p.m.
Hmm...interesting.
Is there logging which states the fallback is issued? If so, can someone
share?
Thanks.
On Mon, Sep 14, 2020 at 1:28 PM Richard Fuchs <rfuchs(a)sipwise.com> wrote:
On 14/09/2020 13.14, Andrew Chen wrote:
--
Andy Chen
Sr. Telephony Lead Engineer
415 516 5535 (M)
achen@ <achen(a)thinkingphones.com>fuze.com
--
*Confidentiality Notice: The information contained in this e-mail and any
attachments may be confidential. If you are not an intended recipient, you
are hereby notified that any dissemination, distribution or copying of this
e-mail is strictly prohibited. If you have received this e-mail in error,
please notify the sender and permanently delete the e-mail and any
attachments immediately. You should not retain, copy or use this e-mail or
any attachment for any purpose, nor disclose all or any part of the
contents to any other person. Thank you.*
Btw Richard Fuchs, to follow up on your comment,
we have a load
generator running sipp which is non-SRTP traffic.
As for the fallback, how does that work exactly? We tried the
following today and it seems to have helped:
- Removed "--table" startup param in systems file
- Uncommented "no-fallback = false" in rtpengine.conf
- Set "table=-1" in rtpengine.conf
Is there anything else I'm missing that controls the fallback?
Userspace fallback is always available, even if `no-fallback` is set
(which is relevant during startup only). If a packet is not handled by
the kernel module for whatever reason, it's always automatically passed
on to the daemon to be handled (except when explicitly instructed to
drop a packet, e.g. through `strict-source`). In this sense, you get the
same behaviour as if `table = -1` is used.
Cheers
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users