Hi everybody,
I'm just testing Kamailio 5.4.1 with dialog replication over DMQ. This
seems to work very good. Dialogs are replicated without problems.
When I'm restarting one node I would have expected, that all dialogs are
synced again, just like in dmq_usrloc.
But this does not happen. After a restart the nodes dialog-list is empty.
Did I miss somethin? Is there a special parameter that I have to set?
BR, Björn
--
Björn Klasen, Specialist
TNG Stadtnetz GmbH, Network Management (VoIP)
Projensdorfer Straße 324
24106 Kiel
Germany
T +49 431/ 530530
F +49 431/ 7097-555
mailto: bklasen(a)tng.de
http://www.tng.de
Register: Amtsgericht Kiel HRB 6002 KI
Executive board (Geschäftsführung): Dr.-Ing. Volkmar Hausberg,
Sven Schade, Carsten Tolkmit, Dr. Sven Willert
Tax-Id (Steuernr.): 2029047020, VAT-Id (USt-Id): DE225201428
Hi All,
I am facing an issue in understanding how the min_se should be working in
kamailio. As per the SST documentation, it seems like if the min_se is
configured as 500, then any value of Session-Expires OR MIN-SE if lower
than 500, can be responded to by a 422.
However, I strangely see the reverse happening. To investigate further, I
looked in to the ki_sst_check_min() code in the master, and these seems
like a potential issue.
Ref Code: Inside ki_sst_check_min(), there is an if condition like below:
if (sst_min_se < MIN(minse, se.interval)) {
However, shouldn't it be the other way around? ie
if (sst_min_se > MIN(minse, se.interval)) {
because we need to send 422 if the received value(in INVITE etc) is
smaller than the sst configure min_se value?
I also found a different documentation, at
https://git.sgu.ru/oldssu/ex-opensips/blob/cb9df8d59dbb254a9d862569fd5d11f6…
where
the check is as below?
if (sst_min_se > MIN(minse, se.interval)) {
Can someone confirm if this is broken, or my understanding is incorrect?
Regards,
Harneet
--
"Once you eliminate the impossible, whatever remains, no matter how
improbable, must be the truth" - Sir Arthur Conan Doyle
On Mon, May 07, 2018 at 04:44:14PM +0200, Daniel Tryba wrote:
> Sure. Attached. Problem appears to be that the topos query can't find
> callid-totag (from the response).
>
> I'll try the same scenario with the mysql backend to see if it behaves
> different.
Config works fine with mysql as topos backend. So the bug is restricted
to topos-redis.
Hi,
We’re still using kamailio 4.4 but we’ll be migrating to 5.0 soon.
Cool so it will be fixed when we migrate !
Thanks,
Andreas
From: sr-users [mailto:sr-users-bounces@lists.kamailio.org] On Behalf Of Federico Cabiddu
Sent: vendredi 12 mai 2017 11:56
To: Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] t_drop_replies not working with t_suspend in failure route
Hi,
which version are you using?
A similar case had been reported some months ago and it should be fixed in 5.0.
Regards,
Federico
On Fri, May 12, 2017 at 11:44 AM, Huber Andreas <andreas.huber(a)nagra.com<mailto:andreas.huber@nagra.com>> wrote:
Hello,
We have a use case where we suspend a transaction in a failure_route to give UEs that might be woken by a push notification more time to REGISTER and join the INVITE.
We’d like to drop the previous branches in this case. I tried using t_drop_replies() but it has no effect.
The doc states that t_drop_replies() is only working if a new branch is added. And from my understanding t_suspend() adds a new branch.
But is it possible that t_drop_replies() cannot be used with t_suspend()? Or am I missing something?
Kind Regards,
Andreas
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Hello everybody!
i am trying a setup of kamailio like sbc for ms teams,
I currently have the following scenario:
TLS Connection OK
Out Call ok (except BYE 481 on reply)
my problem is in incoming calls
microsoft only supports srtp
and my pbx (freeswitch based) only works with rtp,
now i was reading that you need to use rtpengine to manage srtp to rtp,
unfortunately it seems that rtpengine has become very difficult to build
especially with recent os,
I was wondering if it is possible to have an alternative to rtpengine for
managing the srtp (rtpproxy does not seem to work)
has anyone managed to get a working setup?
in case it is possible to send a configuration template?
Thanks You !!!
Davide
Hi,
I was wondering what is the recommended approach to implement a failover on several destination SIP servers:
1) using DNS SRV records
2) using dispatcher list
3) combination of both.
Thanks,
AL
Hello Members,
Kamailio acc module is not inserting cdr into MySQL DB, sometimes it works
and sometimes didn't, the number of parameters/values are similar in failed
as well success scenario. I also check with tcpdump for MySQL requests,
unfortunately, Kamailio didn't issue insert query toward DB server, so it
is clear to me that the MySQL server is nothing to do with failed queries.
Please guide me on what I should do to find and fix the issue.
Kamailio Installed version :
kamailio -v
version: kamailio 5.4.1 (x86_64/linux) 2ca223
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: 2ca223
compiled on 12:51:24 Sep 21 2020 with gcc 6.3.0
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_logic.c:691]: tmcb_func(): acc callback called for t(0x7fe29b2a7870)
event type 512, reply code 200
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_logic.c:413]: should_acc_reply(): probing acc state - code: 200 flags:
0x6
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_logic.c:446]: should_acc_reply(): acc is on
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 6, index i 0
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 6, index i 1
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 6, index i 2
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 6, index i 4
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 6, index i 5
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 6, index i 6
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 6, index i 7
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 6, index i 8
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 6, index i 9
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 6, index i 10
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 6, index i 11
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 6, index i 12
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 6, index i 13
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 6, index i 16
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 6, index i 17
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 6, index i 19
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 6, index i 20
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 6, index i 22
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 6, index i 26
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 6, index i 28
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 6, index i 29
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 6, index i 32
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 6, index i 33
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: tm
[t_hooks.c:256]: run_trans_callbacks_internal(): DBG: trans=0x7fe29b2a7870,
callback type 512, id 0 entered
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 3, index i 0
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 3, index i 1
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 3, index i 2
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 3, index i 3
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 3, index i 4
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 3, index i 5
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 3, index i 8
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 3, index i 9
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 3, index i 11
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 3, index i 12
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 3, index i 14
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 3, index i 18
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 3, index i 20
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 3, index i 21
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 3, index i 24
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 3, index i 25
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: ERROR: acc
[acc_cdr.c:267]: db_write_cdr(): failed to insert into database
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 3, index i 0
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 3, index i 1
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 3, index i 2
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 3, index i 3
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 3, index i 4
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 3, index i 5
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 3, index i 8
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 3, index i 9
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 3, index i 11
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 3, index i 12
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 3, index i 14
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 3, index i 18
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 3, index i 20
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 3, index i 21
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 3, index i 24
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc
[acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2,
message_index 3, index i 25
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: ERROR: acc
[acc_cdr.c:682]: cdr_on_end_confirmed(): failed to write cdr!
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: tm
[t_reply.c:1758]: cleanup_uac_timers(): RETR/FR timers reset
Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103682]: DEBUG: tm
[timer.c:634]: wait_handler(): finished transaction: 0x7fe29727ba88
(p:0x7fe294d27288/n:0x7fe294d27288)
--
Regards
M Arqum
Hi there!
Go ahead I apologize for my English.
I have a Kamailio 5.4 with the DISPATCHER module and UAC enabled (for
remote REGISTER), the DISPATCHER has several SETIDs, and they have one
or more Asterisk balanced behind it.
In Kamalio script, when an endpoint does REGISTER, I enable the REGISTER
of the UAC module. And when it expires or expires=0 I disable the
REGISTER in the UAC module.
In the UACREG table in the database, L_UUID (unique key), L_USERNAME,
R_USERNAME, and AUTH_USERNAME have the same value. For example CST100EXT100.
Knowing that the DISPATCHER and UAC modules have no relationship, but
that when a SETID has several balanced Asterisks, how can I make the UAC
module send the REGISTER to all the Asterisks of a SETID?
Clarifications;
1.- I cannot update the Asterisk, which are currently in version 11.
They do not support PATH.
2.- I can modify the content of the UACREG table so that l_uuid has a
suffix '_X'.
3.- Call jsonrpc_exec several times to enable the REGISTER in the UAC
module.
(diff emulated)
< jsonrpc_exec ('{"id": 1, "jsonrpc": "2.0", "method": "uac.reg_enable",
"params": ["l_uuid", "s: $ au"]}') ;
> jsonrpc_exec ('{"id": 1, "jsonrpc": "2.0", "method":
"uac.reg_enable", "params": ["l_uuid", "s: $ au_1"]}') ;
> jsonrpc_exec ('{"id": 1, "jsonrpc": "2.0", "method":
"uac.reg_enable", "params": ["l_uuid", "s: $ au_2"]}') ;
> jsonrpc_exec ('{"id": 1, "jsonrpc": "2.0", "method":
"uac.reg_enable", "params": ["l_uuid", "s: $ au_3"]}') ;
But I want to know if there is any more elegant way to do this.
Cheers, JV
--
Logo <http://www.voiper.es/>
Javier Valencia | CTO
Centro de Negocios Martín Buendía
Camino de las Cañadas, nº 1C, Portal 1, 2ºG
29649 Mijas (Málaga)
# 951562080 (T) <tel:951562080> | 687486759 (M) <tel:687486759>
# www.voiper.es <http://www.voiper.es/>
------------------------------------------------------------------------
AVISO LEGAL
-----------
Este mensaje contiene información confidencial destinada para ser leída
exclusivamente por el destinatario. Queda prohibida la reproducción,
publicación, divulgación, total o parcial del mensaje así como el uso no
autorizados por el emisor. En caso de recibir el mensaje por error, se ruega
su comunicación al remitente lo antes posible. Por favor, indique
inmediatamente si usted o su empresa no aceptan comunicaciones de este tipo
por Internet.
Las opiniones, conclusiones y demás información incluida en este mensaje que
no esté relacionada con asuntos profesionales de SMART RECARGAS, S.L, se
entenderá que nunca se ha dado, ni está respaldado por el mismo.
Responsable del Tratamiento de Datos
------------------------------------
SMART RECARGAS , SL
Camino de las Cañadas, 1C PORTAL 1 2º G
29651 MIJAS COSTA (MALAGA)
Is it possible to send arbitrary text messages triggered by an external
application (evapi/http) to registered SIP clients via websocket?
The following doesn't seem to do anything.
KSR.corex.send_data("sip:user@example.com", "Message at $Ts");
--
--
This message contains confidential information and is intended only for the
individual named. If you are not the named addressee, you should not
disseminate, distribute or copy this email. Please notify the sender
immediately by email if you have received this email by mistake and delete
this email from your system. Email transmission cannot be guaranteed to be
secure or error-free, as information could be intercepted, corrupted, lost,
destroyed, arrive late or incomplete, or contain viruses. The sender,
therefore, does not accept liability for any errors or omissions in the
contents of this message which arise as a result of email transmission. If
verification is required, please request a hard-copy version.
Hi there,
I was wondering if there's a way to log various core error events in some
DB.
For example, below error occurred
Jan 29 11:43:56 kamailio[11076]: {1 11440 INVITE
28b653bd-8f62-4085-a5ef-f2a4ac0f393d } ERROR: <core>
[core/parser/sdp/sdp_helpr_funcs.c:499]: extract_mediaip(): no `IP[4|6]'
address in `c=' field
Jan 29 11:43:56 kamailio[11076]: {1 11440 INVITE
28b653bd-8f62-4085-a5ef-f2a4ac0f393d } ERROR: <core>
[core/parser/sdp/sdp.c:430]: parse_sdp_session(): can't extract common
media IP from the message
Thanks in advance. Regards,
--Sergiu
