Hi
We are receiving 2 to 3 contact headers in the 200 OK response of the
registration request. It appears that the `user_location` is updating
multiple contact headers for the same extension due to network
disconnections. Please suggest a solution to avoid duplicates in the
`user_location`
Hi,
We are using kamailio and freeswitch, So when we make a call from A to B
the call is going via "kamailio -> freeswitch" and "freeswitch ->
kamailio". Please suggest me how i can set "set_dialog_profile" for both
legs with unique value in kamailio config file.
Thanks.
their exact role is
> not mentioned.
> If this is the case, you could do some kamcmd ul.dump on both registrars.
> Also the DMQ traffic can be traced by tcpdump etc.
>
> You may also want to validate the DMQ bus, "the way each node learns about
> the other ones."
>
> On Th
Hi,
There are two proxy servers and two registrar servers with DMQ enabled, and
we have upgraded the proxy servers to 5.7.4 and the registrar servers to
5.5.5.
Kamailio proxy version 5.7.4
Kamailio registrar version: 5.5.5
Following the upgrade of the proxy server to 5.7.4, calls are not
me DB script adaptions.
>>
>>
>>
>> Cheers,
>>
>>
>>
>> Henning
>>
>>
>>
>> *From:* satyaprakash ch via sr-users
>> *Sent:* Dienstag, 16. April 2024 14:39
>> *To:* Kamailio (SER) - Users Mailing List
>> *
HI
I currently have two proxy servers running in my environment, and I want to
upgrade Kamailio from version 5.4.7 to 5.6.
Can I recompile the Kamailio service before restarting it without downtime
? Will there be any impact on my production environment if I recompile
Kamailio to the newer
Hi,
The kamailio version we are using is "5.5.5", We are facing a kamailio
crash issue recently and it has generated the core-dump. Based on the
core-dump analysis we could see that "*si_desc = "udp receiver
child=3" *getting
crashed. We could see the below error in the core-dump trace,
#22
Hi,
We're encountering a CPU load of approximately 90% on the Kamailio proxy
server. Additionally, there's an error logged indicating a lost connection
to MySQL. Could this indicate a problem with the configuration file or is
it related to MySQL itself? Your guidance would be appreciated.
MySQL
Hi,
Does the below link issue is improved in updated version of Kamailio,
Or kindly anyone help on this 412 issue?
Link - https://github.com/kamailio/kamailio/issues/2048
Thanks.
__
Kamailio - Users Mailing List - Non Commercial
Hi,
Please anyone can reply on the issue of 412 conditional request failed.
On Thu, Jan 18, 2024 at 6:49 PM satyaprakash ch <
chiramchetty.satyaprak...@gmail.com> wrote:
> Hi
>
> There were two PUBLISH requests were sent by the Kamailio Proxy server to
> the Kamailio Presence server.
>
>
Hi
There were two PUBLISH requests were sent by the Kamailio Proxy server to
the Kamailio Presence server.
Processing of the first PUBLISH request resulted in the presentity table
being updated - the "etag" changed from "a.1705053846.16611.21.1" to
"a.1705053846.16613.23.2"
Processing of the
uld be my first checks.
>
> Specifically - "ds_probing_threshold" and the "ds_inactive_threshold"
> params (first takes it out after x failed, second adds it back in after x
> successful.) We would need to see the kamailio version, dispatcher params
> and the d
HI,
Scenario:
We possess 2 proxies and 2 registrar servers equipped with dmq
functionality. Unexpectedly, one of the Proxy IP addresses was marked as
inactive (FLAG: IP) in the dispatcher list, causing the proxy to cease
responding. Simultaneously, Kamailio logs stopped recording any activity.
.html#sanity.f.sanit
> >> > y_check
> >> > - 4.1. sanity_check([msg_checks [, uri_checks]])
> >> > - This function makes a row of sanity checks over the given SIP
> request...
> >> >
> >> > It seems simple: che
io.org/docs/modules/5.5.x/modules/sanity.html#sanity.f.sanit
>> > y_check
>> > - 4.1. sanity_check([msg_checks [, uri_checks]])
>> > - This function makes a row of sanity checks over the given SIP
>> request...
>> >
>> > It seems simple: check
dd the Call-ID to the log message, and then
> also
> > capture (tshark/tcpdump) traffic for subsequent analysis.
> >
> > James
> >
> > On Mon, 16 Oct 2023 at 16:52, satyaprakash ch via sr-users > us...@lists.kamailio.org> wrote:
> > >
> &g
e need to do to resolve this?
>
> Waiting for your reply.
>
>
> On Mon, Oct 9, 2023 at 11:45 AM satyaprakash ch <
> chiramchetty.satyaprak...@gmail.com> wrote:
>
> Hi,
>
> Thanks for the reply,
>
> What if we would get a negative value, Do we need
Hi,
Any reply would be appreciated.
On Mon, Oct 16, 2023 at 10:10 PM satyaprakash ch <
chiramchetty.satyaprak...@gmail.com> wrote:
> Hi,
>
> We possess a code within Kamailio, which specifically handles malformed
> SIP responses. Below is the code snippet:
>
>
>
>
>
> *reply_routeCopy code
Hi,
We possess a code within Kamailio, which specifically handles malformed SIP
responses. Below is the code snippet:
*reply_routeCopy code if(!sanity_check("17604", "6")) { xlog("Malformed SIP
response from $si:$sp\n"); drop;*
Additionally, we have Kamailio drop request statistics as
aprak...@gmail.com> wrote:
>
> Hi,
>
> Thanks for the reply,
>
> What if we would get a negative value, Do we need to change any code level,
> Will you please suggest what we need to do to resolve this?
>
>
>
> On Wed, Sep 27, 2023 at 9:26 PM Patrick Karton
> wrote:
;
>> Probably because you are returning negative value in this failure_route
>> ------
>> *De :* satyaprakash ch via sr-users
>> *Envoyé :* mercredi 27 septembre 2023 06:45
>> *À :* Kamailio (SER) - Users Mailing List
>> *Cc :* satyapraka
ive value in this failure_route
> --
> *De :* satyaprakash ch via sr-users
> *Envoyé :* mercredi 27 septembre 2023 06:45
> *À :* Kamailio (SER) - Users Mailing List
> *Cc :* satyaprakash ch
> *Objet :* [SR-Users] ERROR: run_top_route
>
> Hi,
>
> We a
Hi,
We are having an error in the Kamailio logs which we need to resolve this
issue,
ERROR is ::* /usr/local/sbin/kamailio[10149]: ERROR: tm [t_reply.c:1081]:
run_failure_handlers(): error running run_top_route for failure handler.*
We are getting this error at the time of the 3xx response,
23 matches
Mail list logo
