Hello:
I am testing the Kamailio Presence Server. I can see when the presence of
an user agent expires then the server sends an empty NOTIFY without XML
document. Also, when the server receives a SUBSCRIBE it sends a NOTIFY with
XML if the UA is present but it sends an empty NOTIFY when the UA is not
present. However, if the presence server receive a PUBLISH with Expires
header equals cero then it sends a NOTIFY with XML document.
I do not understant why it sends empty NOTIFY messages. Especially if the
user agent is not present.
I tested 4.4.7 version and I can see that it is the best version, because I
tested 5.1.6 and 5.2.0 versions and I could see that they sends empty
NOTIFY messages even the user agent is present.
Then I am using 4.4.7 version, an I am considering as no present when a
NOTIFY message is empty. But I think it is not RFC3856 compliant.
Kamailio presence server es configured like that:
#!ifdef WITH_PRESENCE
# ----- presence params -----
modparam("presence", "db_url", DBURL)
# ----- presence_xml params -----
modparam("presence_xml", "db_url", DBURL)
modparam("presence_xml", "force_active", 1)
#!endif
Can anyone help me?
Thank you very much in advance.
*Eduardo Pascual Gallego*
*Ingeniero de Desarrollo / Development Engineer.*
T. +34 91 807 39 99 · eduardo.pascual(a)nucleocc.com
<https://www.nucleocc.com/>
*Núcleo HQ*
C/Vía de los Poblados, 7
28033 Madrid (Spain)
<https://www.google.es/maps/place/DF+N%C3%BAcleo/@40.4747861,-3.6352894,17z/…>
*Núcleo
USA*
100 Crescent Dr, STE.700
75201 Dallas, Texas (USA)
<https://www.google.es/maps/place/100+Crescent+Ct,+Dallas,+TX+75201,+EE.+UU.…>
*www.nucleocc.com* <https://www.nucleocc.com/>
Este correo electrónico y cualquier fichero adjunto al mismo contienen
información de carácter confidencial exclusivamente dirigida a su
destinatario o destinatarios. En el caso de haber recibido este correo
electrónico por error, le indicamos que no le está permitido por ley la
lectura, copia y uso del mismo . En tal caso, le rogamos notifique lo antes
posible esta circunstancia mediante reenvío a la dirección electrónica del
remitente y destruya el mensaje. Antes de imprimir este correo, piense en
su responsabilidad y compromiso con el medio ambiente.
--
Advertencia | Este
mensaje está destinado únicamente a su destinatario
y puede contener
información CONFIDENCIAL y/o protegida por secreto
profesional cuya revelación
está prohibida por la ley. Si usted no es el
destinatario a quien va dirigido
le informamos que la lectura, la
distribución, el copiado o la revelación de
este mensaje están prohibidos
por la ley. Si ha recibido este mensaje por error
le solicitamos que nos
notifique por e-mail su recepción equivocada y que borre
este mensaje sin
conservar copia, al tiempo que le pedimos disculpas por las
molestias que
le haya ocasionado.
El servicio de
e-mail por internet no garantiza ni
la confidencialidad ni la integridad o la
recepción de los mensajes por lo
que nuestra Firma no asume ninguna
responsabilidad portales circunstancias.
De conformidad con
lo previsto en el REGLAMENTO (UE) 2016/679 DEL
PARLAMENTO
EUROPEO Y DEL CONSEJO de 27 de abril de 2016, a continuación
facilitamos la
información básica en relación con la protección de los
datos personales que
nos sean suministrados:
Responsable: NUCLEO
DE
COMUNICACIONES Y CONTROL, SLU
Finalidad: Cumplimiento
de las relaciones
jurídicas y obligaciones legales asociadas.
Legitimación:
Ejecución
contractual y cumplimiento de nuestras obligaciones.
No se cederán o
transferirán los datos personales a terceros, salvo siguiendo sus
instrucciones
o por obligación legal.
Ejercicio de
derechos de acceso,
rectificación y supresión de los datos, así como el
ejercicio de otros
derechos, tal y como se explica en la información adicional.
Puede
consultar la
información adicional y detallada en el siguiente enlace a
nuestra política de privacidad
y *Tratamiento de Datos
Personales*
<http://www.nucleocc.com/paginas_informativas/proteccin_de_datos_de_carcter_…>*.*
Hi all,
Question. I'm executing uri_param() function to look for our customized
Request-URI parameters generated by our client. However, it keeps saying
the param is not there even though my client logs shows the param was
generated. Below is an example Request-URI from a test call I made:
sips:<some long string>@sjomainkamavip50.fuzemeeting.com:443;FN=
sjomainfn92.a.fuzemeeting.com;BR=sjomainfn91.a.fuzemeeting.com;AK=<some
key>;transport=wss"
And here is my line of code to check it:
if(uri_param("AK") ||uri_param("ak")) {
xlog("L_INFO", "[CSeq $cs] AK value
detected");
} else {
xlog("L_INFO", "[CSeq $cs] AK value not
detected. Aborting call");
drop();
}
Am I misusing this function somehow?
I'm running 5.1.2.
Thanks
Regards,
--
Andy Chen
--
*Confidentiality Notice: The information contained in this e-mail and any
attachments may be confidential. If you are not an intended recipient, you
are hereby notified that any dissemination, distribution or copying of this
e-mail is strictly prohibited. If you have received this e-mail in error,
please notify the sender and permanently delete the e-mail and any
attachments immediately. You should not retain, copy or use this e-mail or
any attachment for any purpose, nor disclose all or any part of the
contents to any other person. Thank you.*
Hi All,
I've Kamailio 5.1 running with Mysql as local DB.
I've configured Siremis as well. I completed accounting configuration as
per the instruction. Now I can see the accounting list, CDR list and as
well as missed calls in Siremis But I can't integrate with free radius
server to trigger the accounting, just like Diameter transaction in IMS.
Kindly advise which doc I should check.
I would like to enable Radius server as an online charging.
Best regards
Yazar
Hey All,
So, I want to use the UAC module to handle Digest Auth to upstream carriers. But, I don’t know which carrier will be selected until another module (dRouting in this case) tells the logic which carrier to use.
I can see in the logs that the uac_auth function can capture the Auth Realm. But, I need to access it from the Kamailio script so that I can lookup the credentials for that realm and then call uac_auth. I’ve tried getting the info from $ar, but that gives me the realm of the inbound request versus the realm of the upstream carrier. Also, I’ve tried using $T_rpl($ar), but that returns 0. Here’s my logic from the Kamailio file:
if(t_check_status("401|407")) {
$var(reply_realm) = $T_rpl($ar);
$var(query)="select auth_username,auth_password from uacreg where realm='" + $var(reply_realm) + "'";
sql_xquery("cb","$var(query)","rb");
xlog("L_DEBUG","[MANAGE_FAILURE: Proxy Auth]: The query is $var(query) auth realm is $var(reply_realm) and the user name is $xavp(rb=>auth_username)");
$avp(auser) = $xavp(rb=>auth_username);
$avp(apass) = $xavp(rb=>auth_password);
uac_auth();
t_relay();
exit;`
}
A snippet of the log file is below:
Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: exec: *** cfgtrace:failure_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=1616 a=63 n=assign
Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: exec: *** cfgtrace:failure_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=1617 a=63 n=assign
Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: exec: *** cfgtrace:failure_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=1618 a=24 n=uac_auth
Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: DEBUG: uac [auth.c:409]: uac_auth(): picked reply is 0x7f900cb7eaf0, code 407
Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: DEBUG: uac [auth.c:225]: get_autenticate_hdr(): looking for header "Proxy-Authenticate"
Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: DEBUG: uac [auth.c:429]: uac_auth(): header found; body=<Digest realm="sip.flowroute.com", nonce="XERJMlxESAbDNCK3INmBfoET1GGxpcyr", qop="auth">
Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: DEBUG: uac [auth_hdr.c:209]: parse_authenticate_body(): <realm>="sip.flowroute.com" state=2
Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: DEBUG: uac [auth_hdr.c:209]: parse_authenticate_body(): <nonce>="XERJMlxESAbDNCK3INmBfoET1GGxpcyr" state=3
Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: DEBUG: uac [auth_hdr.c:209]: parse_authenticate_body(): <qop>="auth" state=1
Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: DEBUG: uac [auth.c:449]: uac_auth(): no credential for realm "sip.flowroute.com"
Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: exec: *** cfgtrace:failure_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=1619 a=24 n=t_relay
Thanks in advance for any help
Mack Hendricks
dSIPRouter
Hello,
I was wondering when the Kamailio Docker image will be updated to use 5.2.1
and be available through the Docker public repository (
https://hub.docker.com/r/kamailio/kamailio)?
Thanks and regards,
Grant
Hello,
Working on sip_trace table produce this error
WARNING: db_mysql [km_res.c:142]: db_mysql_get_columns(): unhandled data type column (Msg_text) type id (250), use DB1_STRING as default
Hi
We are running Kamailio 3.7 on our production servers. The Kamailio process stopped running on one of the 4 servers. Log shows "segfault error".
No core file generated. Any suggestion on how to verify the issue would be appreciated.
kernel: [63574875.776269] kamailio[1558]: segfault at 0 ip 000000000055933a sp 00007fffd4ca6700 error 4 in kamailio[400000+211000]
/usr/sbin/kamailio[1545]: ALERT: <core> [main.c:785]: child process 1558 exited by a signal 11
/usr/sbin/kamailio[1545]: ALERT: <core> [main.c:788]: core was not generated
CRON[21436]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Thanks,
AL
I’m currently and OpenSIPS user and I really want to be able to use their software on OpenWRT, but I have found it really hard to cross-compile. Is there a possibility to run Kamailio as a mid-registrar? For my application this is required, and I haven’t been able to find any information on this.
Hello!
I'm wondering if someone have experience in changing $du on local kamailio
generated packets (like BYE generated at the dialog-timeout) I'm trying to
manipulate in `event_route[tm:local-request]` with no success.
In the end I have it working using the `forward()` function and then using
`exit;` but in this case instead of having 2 BYEs , kamailio sends 4 BYEs
(2 with original $du, 2 with new $du)
this an example :
event_route[tm:local-request] {
if ($rm == "BYE") {
route(SELECT_OUTBOUND_PROXY);
forward();
exit;
}
}
I'm using a kamailio proxy on top with no record-route (we want to have
multiple instances of proxy that can change ip address).
Thanks in advance!
Paolo
