Hello everyone,
I'm beginner in Kamailio, I want to connect my asterisk Server with
Kamailio. Can you please help me in this context. I shall be very thankful
to you.
Regards,
Rohit Kumar
On Thu, Dec 31, 2020, 16:31 <sr-users-request(a)lists.kamailio.org> wrote:
> Send sr-users mailing list submissions to
> sr-users(a)lists.kamailio.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
> or, via email, send a message with subject or body 'help' to
> sr-users-request(a)lists.kamailio.org
>
> You can reach the person managing the list at
> sr-users-owner(a)lists.kamailio.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of sr-users digest..."
>
>
> Today's Topics:
>
> 1. using kamailio 5.4 with the websocket or xmlhttprequest
> (Daniel Hermann N'don)
> 2. Re: using kamailio 5.4 with the websocket or xmlhttprequest
> (Antony Stone)
> 3. Re: using kamailio 5.4 with the websocket or xmlhttprequest
> (Daniel Hermann N'don)
> 4. Using a specific log level for "script" ? (Chaigneau, Nicolas)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 30 Dec 2020 14:15:19 +0000
> From: Daniel Hermann N'don <danielhermann.ndon(a)outlook.com>
> To: "sr-users(a)lists.kamailio.org" <sr-users(a)lists.kamailio.org>
> Subject: [SR-Users] using kamailio 5.4 with the websocket or
> xmlhttprequest
> Message-ID:
> <
> MWHPR05MB291167705F86195717CA7E3181D70(a)MWHPR05MB2911.namprd05.prod.outlook.com
> >
>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hello everyone, I'm a beginner in kamailio technology, and I would like to
> know how to communicate with kamailio from the web.
>
Hello,
Is it possible to set a specific log level for the Kamailio script ?
I've seen that the < debugger > module allows to do that with modules or < core > :
https://kamailio.org/docs/modules/5.4.x/modules/debugger.html#dbg.p.mod_lev…
So I've tried to do :
modparam("debugger", "mod_level_mode", 1)
modparam("debugger", "mod_hash_size", 5)
modparam("debugger", "mod_level", "my_module=3") // this works
modparam("debugger", "mod_level", "core=3") // also works
modparam("debugger", "mod_level", "script=3") // nope...
But it doesn't seem to work for < script >... :/
Regards,
Nicolas.
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Hello!
Could somebody explain how the parameters *publ_cache=2* and
*subs_db_mode* depend
on each other?
Do I understand correctly that only the following modes of *subs_db_mode* are
allowed 0,1,2?
*subs_db_mode:0 - This disables database completely. Only memory will be
used. Subscriptions will not survive restart. Use this value if you need a
really fast presence module and subscription persistence is not necessary
or is provided by other means.1 - Write-Through scheme. Subscriptions are
updated synchronously in database and in memory(used for read operations).
Use this scheme if speed is not top priority, but it's important that no
subscriptions will be lost during crash or reboot or if you have an
external application that reads the state of the subscriptions from
database and they need to be updated synchronously.2 - Write-Back scheme.
This is a combination of previous two schemes. All changes are made to
memory and database synchronization is done in the timer. The timer deletes
all expired contacts and flushes all modified or new subscriptions to
database. Use this scheme if you encounter high-load peaks and want them to
process as fast as possible. Latency of this mode is much lower than
latency of mode 1, but slightly higher than latency of mode 0. To control
the interval at which data is flushed to database, set the db_update_period
parameter.3 - DB-Only scheme. No memory cache is kept, all operations being
directly performed with the database. The timer deletes all expired
subscriptions from database. The mode is useful if you configure more
servers sharing the same DB without any replication at SIP level. The mode
may be slower due the high number of DB operation.*
--
BR,
Denys Pozniak
Hello everyone! I faced some unfortunately issue with presence module. Let me
describe setup scheme a bit: I'm publishing dialog states via pua_dialoginfo
from one kamailio server(for calls proccessing itself) to another one
kamailio(standalone kamailio just for handling presence,blf,mwi etc)
So, about issue, let's say we have device A which has outgoing subscription
to extension which belongs to device B and device C(both devices has same
extension but different usernames, webrtc+sip phone, effectively its the
same Phone, I'm using pubruri_avps to change entities from usernames to
extension) . And, in some cases,for examle, when thirtparty is making call
to this extension(B,C devices) and making CANCEL after couple seconds - I
see the PUBLISH from callserver to presence server with state "terminated',
I see 200ok response.. but presence server isn't sending NOTIFY to device A
about state "terminated", everything is good with "trying" and "early"
states...
That problem is happening 1 of 50 tries.. I've tried a lot of things to fix
that - still are not succeed.
p.s. everything is good from logs/sip point of view... And also, when I
disable the webrtc device - I'm not able to reproduce that issue anymore.
Looks like something wrong with case, when you have multiple different
username behind the same presentity.
Maybe someone had same issue and may help me. Thanks!
--
Sent from: http://sip-router.1086192.n5.nabble.com/Users-f3.html
Hello,
I'm working with IMS network and VoLTE related services. My problem is
that I would like to use Kamailio as a presence watcher but I haven't
managed to make it happen yet. The approach would be that once
Kamailio gets 3rd party registration from S-CSCF the Kamailio would
send SUBSCRIBE back to S-CSCF to subscribe the presence of
subscription. Once a subscription place or get calls the status of
subscription would be updated to Kamailio and to the database where it
can be fetched. I have checked presence and pua modules, but haven't
found a way to make it work as expected.
Is there way to do that or is this totally incompatible approach to do that?
Best Regards,
Jukka Heikkilä
jutsco(a)gmail.com
Hi,
What is the recommended practice for implementing a self-sustained Presence
server from my current Kamailio configuration? That is I want the Presence
module to be fed status updates as Kamailio is routing calls and handling
registrations. So when a user registers, his phone is ringing, he is on
the phone, etc.., the Presence module gets notified and can update its
subscribers accordingly. Must I add snippets of codes to all of these
events and generate local Publish messages, or is there a better way?
I'm using the latest version 5.4.x.
Regards,
Michel Pelletier
Hi there!
When I start my webrtc kamailio suddenly stops.
I can see this on syslog:
Dec 28 16:08:53 webrtc /usr/sbin/kamailio[803]: CRITICAL: <core>
[core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed
pointer (0x7f55756c2ab8), called from tls: tls_init.c:
ser_free(323), first free tls: tls_init.c: ser_malloc(293) - ignoring
Dec 28 16:08:53 webrtc /usr/sbin/kamailio[803]: CRITICAL: <core>
[core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed
pointer (0x7f55756c3138), called from tls: tls_init.c:
ser_free(323), first free tls: tls_init.c: ser_malloc(293) - ignoring
... omit vervose ...
Dec 28 16:08:53 webrtc /usr/sbin/kamailio[803]: CRITICAL: <core>
[core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed
pointer (0x7f55756c1f38), called from tls: tls_init.c:
ser_free(323), first free tls: tls_init.c: ser_free(323) - ignoring
...omit verbose ...
Dec 28 16:08:53 webrtc /usr/sbin/kamailio[803]: CRITICAL: <core>
[core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed
pointer (0x7f557569f250), called from tls: tls_init.c:
ser_free(323), first free tls: tls_init.c: ser_realloc(299) - ignoring
Dec 28 16:08:53 webrtc /usr/sbin/kamailio[803]: CRITICAL: <core>
[core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed
pointer (0x7f557565cf60), called from tls: tls_init.c:
ser_free(323), first free tls: tls_init.c: ser_malloc(293) - ignoring
Dec 28 16:08:53 webrtc /usr/sbin/kamailio[803]: INFO: <core>
[core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized
OS info:
root@webrtc:/etc/kamailio# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 10 (buster)
Release: 10
Codename: buster
root@webrtc:/etc/kamailio# free -m
total used free shared
buff/cache available
Mem: 16041 134 15551 108 356 15524
Swap: 974 0 974
Kamailio version:
version: kamailio 5.4.3 (x86_64/linux)
flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS,
DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC,
Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX,
FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR,
USE_DST_BLACKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED
ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE
1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: unknown
compiled with gcc 8.3.0
Kamailio params:
SHM_MEMORY=512
PKG_MEMORY=32
SSL info:
root@webrtc:/etc/kamailio# apt show openssl
Package: openssl
Version: 1.1.1d-0+deb10u4
Priority: optional
Section: utils
Maintainer: Debian OpenSSL Team
<pkg-openssl-devel(a)lists.alioth.debian.org>
Installed-Size: 1.495 kB
Depends: libc6 (>= 2.15), libssl1.1 (>= 1.1.1)
Suggests: ca-certificates
Homepage: https://www.openssl.org/
Download-Size: 843 kB
APT-Manual-Installed: no
APT-Sources: http://security.debian.org/debian-security
buster/updates/main amd64 Packages
Description: juego de herramientas Secure Sockets Layer - utilidad
criptográfica
Este paquete forma parte de la implementación del proyecto OpenSSL
de los
protocolos criptográficos SSL y TLS para la comunicación segura a
través de
Internet.
.
Contiene el binario de propósito general para la línea de órdenes
/usr/bin/openssl,
útil para operaciones criptográficas como:
* creación de parámetros clave RSA, DH y DSA;
* creación de certificados X.509, CSR y CRL;
* calcular resúmenes de mensajes;
* cifrado y descifrado con cifras;
* probar clientes y servidores SSL/TLS;
* gestión de correo firmado o cifrado S/MIME.
Should I use another version of openssl, or maybe use gnutls?
Regards,
Javier Valencia
Hi,
What is the recommended practice for implementing a self-sustained Presence
server from my current Kamailio configuration. That is I want the Presence
module to be fed status updates from the same Kamailio that is routing the
calls. So when a user registers, his phone is ringing, he is busy, on the
phone, etc.., the Presence module gets notified and can update subscribers
accordingly. Must I add snippets of codes to all of these events and
generate local Publish messages, or is there a better way?
I'm using the latest version 5.4.x.
Regards,
Michel Pelletier
Hello,
I am redirecting the agents/reps to their asterisk server based on the
hostname which they connect, and, i wonder if it's possible to read from db
instead of the file cause it's getting big ;)
# Dispatch requests
route[DISPATCH] {
switch ($fd){
case "oro.streamlinepbx.nl":
if (!ds_select_dst("1", "4")) {
send_reply(503, "Service
Unavailable $fd");
exit;
}
break;
case "oro3.streamlinepbx.nl":
if (!ds_select_dst("2", "4")) {
send_reply(503, "Service
Unavailable $fd");
exit;
}
break;
............
default:
log("unknow destination?");
send_reply(503, "No service defined");
xlog("--- SCRIPT: going to <$ru> via <$du>
...Exiting");
exit;
}
xlog("--- SCRIPT: going to <$ru> via <$du> (attrs:
$xavp(_dsdst_=>attrs))\n");
t_on_failure("RTF_DISPATCH");
route(RELAY);
exit;
}
Thanks,
A year that was very tough for the entire world is getting close to its
end, no doubt that was the most challenging in our life so far for many
of us, however, with a distributed, friendly and collaborative
community, Kamailio project continued to develop consistently, bringing
out a new major release. I trust it helped people and companies world
wide to to connect with the dear ones and build a better way of living.
The season holidays are ahead, time to rest a bit, spend time with
family and friends, being online or face to face. As usual, I take this
chance to express my thanks and greetings to all the friends,
developers, supporting companies and community members that made 2020
another great year for Kamailio project.
Enjoy the holidays! Merry Christmas!
Daniel
* Santa is flying Kamailio! *
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
