Using "Kamailio in a mobile world" as a base, I have the following routes to
store information about the current transaction, however, if the transaction is
already cancelled registrations for the user will still trigger `ts_append`,
raising an error as the htable hasn't expired yet.
Is there
follows the rules for Section
> 13, and having two Via hops in one of those is entirely appropriate.
>
> On Fri, Nov 30, 2018 at 02:59:52PM +, Dan Quinney wrote:
>
>> Hi all,
>>
>> I’m having some issues with ACK’s.
>>
>> Specifically, when an
Hi,
When using Kamailio v5.2.0-rc2 (x86_64/linux) 9e729b and setting the below
nathelper module parameters it appears only the first contact is sent a SIP
OPTIONS request.
modparam("nathelper", "natping_interval", 15)
modparam("nathelper", "ping_nated_only", 0)
modparam("nathelper",
Hi all,
I’m having some issues with ACK’s.
Specifically, when an ACK reaches Kamailio from either Asterisk or an endpoint,
Kamailio is adding a second Via header - which isn’t valid as per RFC 3261
(17.1.1.3);
“The ACK MUST contain a single Via header field, and this MUST be equal