@miconda To answer a few other questions:
1. I always set `$http_req(suspend) = 1` on async HTTP client transactions;
2. There are no `event_routes` anywhere;
3. The flow is complex, though. After this async HTTP query, there is another
_synchronous_ HTTP query using the normal `http_client` mo
Hi, thank you very much for investigating this!
Unfortunately, the causes of the crash do not appear to arise dependably; as
luck has it, there hasn't been one in the days since I submitted this issue.
So, all I can do is cherry-pick this patch into the source and hope for the
best.
I will be
The 53-nightly release does fix the issue.
However, related: is it intentional that `apt-get upgrade` doesn't show an
available upgrade to the nightly release ?
```
$ apt-cache policy kamailio
kamailio:
Installed: 5.3.3+bionic
Candidate: 5.3.3+bionic
Version table:
*** 5.3.3+bionic 100
This is cool! much needed improvement. As always, great work @miconda !
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/commit/f917318c1e5fefa4106eaaf46123506d77dc02ba#commitcomment-385706
I think I found something that could have been caused the issue, respectively
setting the AVPs lists from transaction in the process context inside the http
async callback function. It was done for the case when transaction was
suspended and no cleaned up, living further in the context of the pr
Module: kamailio
Branch: master
Commit: 1bc3bbd010705ee247345c1ed9b36210bb8d9ed1
URL:
https://github.com/kamailio/kamailio/commit/1bc3bbd010705ee247345c1ed9b36210bb8d9ed1
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date: 2020-04-17T19:04:16+02:00
http_async_client: do
@abalashov have you checked if you set suspend field always? any new crash?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2286#issuecomment-615355471__
Module: kamailio
Branch: master
Commit: f917318c1e5fefa4106eaaf46123506d77dc02ba
URL:
https://github.com/kamailio/kamailio/commit/f917318c1e5fefa4106eaaf46123506d77dc02ba
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date: 2020-04-17T18:44:06+02:00
presence: functions to
Current stable release support using only one (first by ordering) NAPTR DNS
record.
I didn't find any ideas how to configure possibility for use all supported
NAPTR / SRV records. This pull request resolve this issue.
General issue:
PreConditions:
# host -t naptr voip.somehost.com
voip.somehost
Module: kamailio
Branch: master
Commit: c26f40bc0c0a410ece7203c680b57a5c587ec1aa
URL:
https://github.com/kamailio/kamailio/commit/c26f40bc0c0a410ece7203c680b57a5c587ec1aa
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date: 2020-04-17T12:57:26+02:00
tls: renamed tls hooks
Thanks, it will be merged!
Have you seen my comment on your previous PR:
* https://github.com/kamailio/kamailio/pull/2268#issuecomment-609935161
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/
It doesn’t make a lot of sense to see looping calls “connected”. If they
connect, then they’re not looping, unless there is some counter somewhere
that answers the call when it sees a loop.
That’s very weird.
Use sngrep and trace on ALL interfaces.
On Fri, 17 Apr 2020 at 11:46, Pavithra M wrote
Hi,
In Wireshark , I couldn't able to see the looping packets .In debug logs of
pcscf , I am able to see the looping occurs . But how then the call gets
connected . That's where I am struck .
On Fri, Apr 17, 2020, 4:11 PM David Villasmil <
david.villasmil.w...@gmail.com> wrote:
> You need to trac
You need to trace sip. There’s a loop somewhere. Use tshark (wireshark) or
sngrep or ngrep, or some similar network tracing tool.
On Fri, 17 Apr 2020 at 11:34, Pavithra M wrote:
> Hi ,
>
> I am getting the call connected and got 200 ok from the client . But the
> INVITE packet goes multiple time
Hi ,
I am getting the call connected and got 200 ok from the client . But the
INVITE packet goes multiple times between terminating pcscf and s-cscf and
gives too many hops error .Even After that call goes perfectly fine with
200 ok message.
What would be the reason . I am not getting any errors i
Hi,
Do anybody have worked orchestrating kamailio as an IMS server through osm
by launching vnfs in openstack . If so kindly reply me as I need some
inputs on that.
___
Kamailio (SER) - Development Mailing List
sr-dev@lists.kamailio.org
https://lists.kama
> Thanks for this contribution!
>
> However, wouldn't it be better to use `parse_sip_msg_uri()` so `_m->new_uri`
> or ` _m->first_line.u.request.uri` is parsed in the `_m->parsed_uri` field
> and then just build the AoR using `_m->parsed_uri.user` and
> `_m->parsed_uri.host`?
Thanks for the su
Closed #2288.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2288#event-3243597966___
Kamailio (SER) - Development Mailing List
sr-dev@l
https://kamailio.sipwise.com/view/kam51/job/kamailiodev-nightly-binaries/architecture=amd64,distribution=bionic/1641/consoleText
```
Get: 30 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 openssl
amd64 1.1.1-1ubuntu2.1~18.04.5 [613 kB]
```
Fixes in place and seems to work fine again.
Triggered builds for kamailio-[dev|5.3|5.2]-nightly to get some debs using the
security repositories included.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2288#issuecomment-615
Yes, confirmed. There was a mistake with the internal Sipwise and Github repos
and some commits were lost:
https://github.com/sipwise/kamailio-deb-jenkins/commit/1e06bfc19870db27477ec28c5a91521c625c54e7
https://github.com/sipwise/kamailio-deb-jenkins/commit/1e40ff9960baff7f0a4aab4f5b8326c8e516dec
* New Feature
* Changes Tested Locally
This sel variable allows a kam script to get access to not just the peer
certificate (at index 0), but when a certificate is successfully verified, the
entire chain of certificates that were used to verify the peer certificate (at
index 1, 2, 3, etc).
Thi
22 matches
Mail list logo
