Hello Danial,
Thanks once again for your reply and sorry for late reply from my side.
>From below point No. 2, I just want to understand that "Is Kamailio process
DTMF or not".
Now we are working on a modal where Kamailio will be used as Proxy and
Freeswitch as Media server. I am able
for kamailio, rtpengine, asterisk and clients on locahost. Docker is on
Linux and Windows.
I have configured onreply route, not sure if it is a right way, but looks
like it works as I need.
if (ds_is_from_list()) {
remove_hf("Record-Route");
append_hf("Record-Route: \r\n");
}
пн, 10
pipelimit is how I'd go about it.
On 8/10/20 3:57 PM, Ameed Jamous wrote:
Dear all,
I wanted to confirm, which is the best way to implement CPS limits per
source IP in kamilio in 2020? PIKE module or Rate Limit module or both
combined.
Thanks in advance for your support.
--
AJ
Dear all,
I wanted to confirm, which is the best way to implement CPS limits per
source IP in kamilio in 2020? PIKE module or Rate Limit module or both
combined.
Thanks in advance for your support.
--
AJ
___
Kamailio (SER) - Users Mailing List
Daniel-Constantin Mierla writes:
> The DNS NAPTR is also turned off by default, which should be on, based
> on RFC, iirc, but that adds extra DNS query and slows down everything as
> most of services I saw so far do no relay on NAPTR.
It is OK to have NAPTR lookup off by default, but if it is
It worked. Thanks so much.
Is there any way I can help to correct documentation ?
On Mon, Aug 10, 2020 at 8:28 PM Daniel-Constantin Mierla
wrote:
> Hello,
>
> the documentation is somehow incorrect, the function is exported with two
> parameters, the second being named owner. By name, I assume
What is the point of dns_naptr_ignore_rfc default value:
dns_naptr_ignore_rfc
If the DNS lookup should ignore the remote side's protocol preferences,
as indicated by the Order field in the NAPTR records and mandated by RFC
2915.
dns_naptr_ignore_rfc = yes | no (default yes)
In my (and RFC
On 10.08.20 17:08, Juha Heinanen wrote:
> Daniel-Constantin Mierla writes:
>
>> The DNS NAPTR is also turned off by default, which should be on, based
>> on RFC, iirc, but that adds extra DNS query and slows down everything as
>> most of services I saw so far do no relay on NAPTR.
> It is OK to
Hello,
the documentation is somehow incorrect, the function is exported with
two parameters, the second being named owner. By name, I assume it has
the purpose as described in the section:
-
https://kamailio.org/docs/modules/5.4.x/modules/keepalive.html#dev-add_destination
So try to provide a
I have not developed that feature, but many options are not following
the recommendations from RFCs with their default values, but more what
was the common practice/best supported at that time (e.g., auto-switch
protocol to tcp/tls on mtu size).
The DNS NAPTR is also turned off by default, which
Why do you want to do this?
—
Sent from mobile, with due apologies for brevity and errors.
> On Aug 10, 2020, at 6:35 AM, Aidar Kamalov wrote:
>
>
> Hello,
>
> I have kamailio with only one interface. Is it possible to set one RR - lan
> ip address to INVITEs (to dispatcher list members)
Hello,
I have kamailio with only one interface. Is it possible to set one RR - lan
ip address to INVITEs (to dispatcher list members) and 127.0.0.1 to replies
200OK (to softphone)?
I can't use record_route() function in onreply route because: Command
cannot be used in the block.
--
Aydar A.
Indeed, calling this function from a branch_route works fine.
The only thing i noticed is the following messages in the log file:
*uac [replace.c:396]: replace_uri(): Already called uac_replace for this
dialoguac [replace.c:405]: replace_uri(): Deleted <_uac_tonew> var in
dialoguac
13 matches
Mail list logo
