Am Mittwoch, 28. November 2018, 15:06:03 CET schrieb Patrick Murphy:
> I ran into the exact same issue. DNS resolution is just stuck on A records
> for OPTIONS pings irrespective of DNS options. I can see correct DNS
> resolution with kamcmd dns.lookup but kamcmd dispatcher.list command does
> not
Hello,
what I actually said it was that if you backport to your local git clone
and testing was ok, then you can push it to 5.1 branch by yourself, no
need to wait for me or others to push it. But I can also do it tomorrow.
Cheers,
Daniel
On 28.11.18 15:10, Andreas Granig wrote:
> Hi Daniel,
>
>
Dear Daniel,
Thank you for your answer, the only files we have modified is :
* Rtpproxy /etc/default/rtpproxy
RTPPROXY - config
# Defaults for rtpproxy
# The control socket.
#CONTROL_SOCK="unix:/var/run/rtpproxy/rtpproxy.sock"
# To listen on an UDP socket, uncomment this line:
C
Hi Daniel,
This commit indeed fixed the issue, thanks for pointing it out! From my point
of view, it’s fine backporting it to 5.1 to fix it there as well.
Best,
Andreas
> On 28.11.2018, at 13:45, Daniel-Constantin Mierla wrote:
>
> Hello,
>
> ohh, I was looking at master and the commit I did
I tested this behavior with versions 4.4.5 as well as 5.1.1
From: Patrick Murphy
Sent: Wednesday, November 28, 2018 2:06 PM
To: José Seabra; mico...@gmail.com; Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] Dispatcher with a naptr address as destination
I ran into the exact same issue. DNS resolution is just stuck on A records for
OPTIONS pings irrespective of DNS options. I can see correct DNS resolution
with kamcmd dns.lookup but kamcmd dispatcher.list command does not even list
the gateways which have a NAPTR/SRV DNS name.
Dispatching INVIT
Kamailio v5.2.0 is out – it comes with 6 new modules and a consistent
group of improvements touching more than 100 existing modules.
You can read detailed release notes at:
* https://www.kamailio.org/w/kamailio-v5-2-0-release-notes/
Many thanks to all developers and community members that mad
Hello,
ohh, I was looking at master and the commit I did seemed to be for the
place without a guard on dialog event type.
The master branch has the one you point to already guarded, done with:
-
https://github.com/kamailio/kamailio/commit/6d0f8994611b50faa7ef7d1299acf0c390a2eed1
- https://gi
Hi Daniel,
Unfortunately that doesn’t help. Digging a bit further, it seems that the error
comes from calling check_if_dialog() around line 715 in update_presentity(), so
actually before entering the delete_presentity_if_dialog_id_exists() function.
Andreas
> On 28.11.2018, at 12:51, Daniel-Co
Hello,
you already got some replies, those ERROR messages are because you have
some xlog() statements (or other functions from xlog modules) in your
configuration file. They are not errors from inside the code of Kamailio.
Those error messages are printed because the person that wrote the
kamaili
Hello,
is that contact is some way special? Does it have the sipping_bflag set?
Or are all those contacts not behind NAT and having same branch flags?
Cheers,
Daniel
On 28.11.18 12:38, Dan Quinney wrote:
> Hi,
>
> When using Kamailio v5.2.0-rc2 (x86_64/linux) 9e729b and setting the
> below nathe
Hello,
can you try with the patch from next commit:
-
https://github.com/kamailio/kamailio/commit/55c7f781be7cc40d0cd161640a47244aad60c0e7
Cheers,
Daniel
On 28.11.18 12:34, Andreas Granig wrote:
> Hi Daniel,
>
> I started fresh (never tried this module before), but after googling for the
> e
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", "sipping_bf
Hi Daniel,
I started fresh (never tried this module before), but after googling for the
error, I came across Juha’s post, which sounds quite familiar.
So I’m having a phone subscribing to message-summary of us...@example.org, and
I have a script sending a PUBLISH in behalf of us...@example.org.
Hello,
some clarifications in order to see where to look: you just started to
play fresh with it and get this error? Or an old configuration that used
to work in the past is now throwing the error?
Cheers,
Daniel
On 28.11.18 12:13, Andreas Granig wrote:
> Hi,
>
> Currently playing with presence_
Hi,
Currently playing with presence_mwi in kamailio 5.1, and it appears the issue
reported by Juha two years ago at
https://lists.kamailio.org//pipermail/sr-dev/2016-September/036609.html seems
to have appeared again somewhere along the way.
I’m sending a PUBLISH with message-summary event typ
Hello,
We have a system which using FreeSWITCH for calls and Ejabberd( XMPP) for
chat.Now we want to support SIP SIMPLE as well.But we are not going to move
old users to SIP SIMPLE but only new users will use SIP SIMPLE.This leads
to requirement of having SIP-XMPP gateway for which are are conside
17 matches
Mail list logo
