Hello,
I'm trying to periodically get all registered contacts from the Kamailio
memory in the json format.
JSONRPCS module have 3 different types of transport to get this data. I
just wonder what will be the safest transport for the Kamailio to get all
this data? Because all this data it's not so
You could use an htable and wait for the ACK to dlg_bye the caller.
Or you could try rewriting the response and sending dlg_bye to the callee,
just seems less predictable in terms of what can happen.
On Mon, Oct 5, 2020 at 2:47 PM Julien Chavanton
wrote:
> Indeed, the call must be
Hi Aymeric,
Thanks for your reply. Yes, as you said I get the below warning when I
start Linphone. But the port is actually not used by any other application.
And one more thing is, I see this error only in case of enabling TCP
transport and not in UDP. So does that mean, linphone works only with
Hi,
I'm answering as the author of libosip & libeXosip ;)
Linphone, in your case is based on eXosip.
Linphone removed eXosip2 years ago and thus, you use
a very old linphone and very old eXosip2 version..
Anyway, whatever versions of eXosip2, it needs to be used that way:
ctx = eXosip_malloc
Thank you people. It seems an easy approach using htable.
I was wondering that this is not compliant with RFC 3261, since a proxy
should not change sip responses.
In fact not only I should change the sip response but I should send a BYE
on behalf of the UAC. It seems like a B2BUA
Em sáb, 3 de
Hi!
Thanks for your interest in sip_reg and sip_monitor!
sip_reg.c is a very old tool in libeXosip. It's runs as a daemon, in
background so..., to REGISTER a Contact header.
This Contact header can be a long term static URI, or anything to test.
It will reject any incoming call.
It will log into
Hi Aymeric,
Can you please send a link to git repo with this tool?
Thanks
On Sat, Oct 3, 2020 at 9:05 PM Aymeric Moizard wrote:
> Hi,
>
> In libeXosip, latest release or git, I have made a new tool named
> "sip_monitor".
>
> The dependencies are libosip and c-ares.
>
> The tool can build
Hi Daniel,
Just for clarification. This case is about data from non-kamailio xcap server
to be handled in a self-written Kamailio module (Railway specific
functionality) during call setup, where we would appreciate the module-API
services of the xcap_client module.
Currently discussing it
Hello,
thanks for this info, knowing more testing tools is useful. I noticed a
second tool coming with libeXosip, namely sip_reg. The help message
seems to be similar with sip_monitor, what is the difference between the
two?
Cheers,
Daniel
On 03.10.20 18:04, Aymeric Moizard wrote:
> Hi,
>
> In
Not an expert here. But many moons ago, I was playing with pjsip and got
the same. You must create the socket first, make sure the ip assigned is
correct.
On Mon, 5 Oct 2020 at 06:47, Pavithra Mohanraja
wrote:
> Hi Jan,
> Sorry for the delayed response. I guess the issue is because of UDP
>
Hi Henning,
I can't see any differences. When I'm waiting some time f.ex. 30 seconds
between stop and start, everything work. In debug log only the senden
host is skipped, as expected.
What is also strange is, that if I kill Kamailio with kill -9
Kamailio is restarting immediately and all
Hello,
database would be perfect, but the file is ok as well.
Right now, I have accounting in syslog only and I think this is because
they are just transaction logs, ie.
acc_log_request(): ACC: transaction answered:
timestamp=1601877602;method=BYE
I got also some missed calls, but no answered
Hello,
do you want dialog-based cdrs to both database and syslog? Or just to
database, but you get them in syslog only?
Cheers,
Daniel
On 04.10.20 11:08, Jan Rozhon wrote:
>
> Guys thank you, by trial and error, I got the solution to logging to
> syslog. On this one particular machine, I also
13 matches
Mail list logo
