Hi there
I have a Kamailio with TLS/Websocket solution. I'm getting some errors
on log and some users can't connect.
My log:
Mar 18 09:49:15 webrtc /usr/sbin/kamailio[11915]: ERROR: tls
[tls_server.c:192]: tls_complete_init(): tls: ssl bug #1491 workaround:
not enough memory for safe operation: shm=8212904 threshold1=8388608
Mar 18 09:49:15 webrtc /usr/sbin/kamailio[11915]: ERROR: <core>
[core/tcp_read.c:1485]: tcp_read_req(): ERROR: tcp_read_req: error
reading - c: 0x7f6297bd62c0 r: 0x7f6297bd6340
Kamailio is running like:
/usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f
/etc/kamailio/kamailio.cfg -m 128 -M 16 -u kamailio -g kamailio
Kind regards, Javier Valencia.
--
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)
Hello Team,
I need to configure apns sip push in kamailio, I have read it many sites but I don't get proper understanding I read it is done with the help of tsilo module kindly support in it.
Sent with [ProtonMail](https://protonmail.com) Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, February 27, 2020 11:10 AM, master1024 <master1024(a)protonmail.com> wrote:
> Hello,
>
> I need to configure apns push notification in kamailio kindly help. I have a file push.php It is capable to push notification on ios device know i want to implement in kamailio when the user is offline then push notification fire kindly help in this.
>
> Think Out of the Box
>
> Sent with [ProtonMail](https://protonmail.com) Secure Email.
Hello,
do people here have (implemented) special ways to properly start
rtpengine with kernel forwarding after system reboot?
>From rtpengine readme:
"""
A typical start-up sequence including in-kernel forwarding might look
like this:
# this only needs to be one once after system (re-) boot
modprobe xt_RTPENGINE
iptables -I INPUT -p udp -j RTPENGINE --id 0
ip6tables -I INPUT -p udp -j RTPENGINE --id 0
# ensure that the table we want to use doesn't exist - usually needed
after a daemon
# restart, otherwise will error
echo 'del 0' > /proc/rtpengine/control
# start daemon
/usr/sbin/rtpengine --table=0 --interface=10.64.73.31
--interface=2001:db8::4f3:3d \
--listen-ng=127.0.0.1:2223 --tos=184 --pidfile=/run/rtpengine.pid
--no-fallback
"""
I was relying on shell scripts executed on boot time, but now that
systemd is more common, I am looking to see what are
"standard"/"recommended" ways for running additional scripts besides the
start/stop daemon, which makes it also easier to build packages not
worrying about the type of OS and how it can run scripts at startup.
Systemd seems to have the "ExecStartPre" option, is it what people use
to ensure the rtpengine kernel module is loaded and iptables rule exists?
Any systemd-specific wayt to run a script only once after system boot? I
have seen workarounds on the net for creating like a rc.local service,
but they didn't look to be systemd-native, ...
Not strictly related, but if someone is aware or had some experiences
with, I am curious if "echo 'del 0' > /proc/rtpengine/control" is
really needed because on a system where I forgot to have it in the
scripts (well, was commented), I haven't noticed any issues after
rtpengine restarts.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com
Hello Team,
I want to configure ios push notification in kamailio, if it is possible kindly support me in deep, because I am new in kamailio.
Sent with [ProtonMail](https://protonmail.com) Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Monday, March 16, 2020 1:24 PM, master1024 <master1024(a)protonmail.com> wrote:
> Hello Team,
>
> I want to implement apns push notification on messages and calling in kamailio kindly support me. I am Beginner in kamailio.
>
> Sent with [ProtonMail](https://protonmail.com) Secure Email.
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Thursday, March 5, 2020 10:18 AM, master1024 <master1024(a)protonmail.com> wrote:
>
>> Hello Team,
>> Kindly support in the same.
>>
>> Sent with [ProtonMail](https://protonmail.com) Secure Email.
>>
>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>> On Wednesday, March 4, 2020 11:18 AM, master1024 <master1024(a)protonmail.com> wrote:
>>
>>> Hello Team,
>>>
>>> I need to configure apns Push Notification in kamailio kindly support in it. I read from the site https://medium.com/@denys.pozniak/apple-push-notification-with-kamailio-eec… but I don't understand properly because here is missing push.php, I have another push.php and it is able to push notification on ios device but I need to understand how to integrate that push.php with kamailio, I need that when user is offline during call or message then push notification will fire from php script and application will wake up via push notification.
>>>
>>> Sent with [ProtonMail](https://protonmail.com) Secure Email.
>>>
>>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>>> On Tuesday, March 3, 2020 12:06 PM, master1024 <master1024(a)protonmail.com> wrote:
>>>
>>>> Hello Team,
>>>> I already read this and attempt to implement that but $sht is creating problem for me. and it is not working for me.
>>>>
>>>> Sent with [ProtonMail](https://protonmail.com) Secure Email.
>>>>
>>>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>>>> On Monday, March 2, 2020 11:14 PM, M S <shaheryarkh(a)gmail.com> wrote:
>>>>
>>>>> Here is a good starting point for you. Adapt and extend as needed in your setup.
>>>>>
>>>>> https://medium.com/@denys.pozniak/apple-push-notification-with-kamailio-eec…
>>>>>
>>>>> Hope this helps.
>>>>>
>>>>> On Mon, 2 Mar 2020, 12:39 master1024, <master1024(a)protonmail.com> wrote:
>>>>>
>>>>>> Hello Team,
>>>>>> Kindly explain your 1st step, The IOS app must what what kind of parameters and how many parameters we needed ???
>>>>>>
>>>>>> Sent with [ProtonMail](https://protonmail.com) Secure Email.
>>>>>>
>>>>>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>>>>>> On Thursday, February 27, 2020 6:38 PM, M S <shaheryarkh(a)gmail.com> wrote:
>>>>>>
>>>>>>> Push notification setup is long and complex but generally has following process. Don't forget to read documentation of relevant kamailio modules for proper use.
>>>>>>>
>>>>>>> 1. The iOS app must send push notification parameters in SIP request e.g. SIP Register. In kamailio, when this request is received, you must extract them and save them in some db backend, e.g. MySQL, Redis etc.
>>>>>>>
>>>>>>> 2. For each income call, check if destination is offline and push parameters stored in db. If so, then you suspend the INVITE transaction using ASYNC or TSILO module and store transaction information in db.
>>>>>>>
>>>>>>> 3. Then using the push parameters stored in db, you send the push notification to device using CURL or HTTP client modules etc.
>>>>>>>
>>>>>>> 4. When device receives push notification, it must come online and send SIP register with push parameters. Kamailio again stores push parameters and checks if an INVITE transaction is waiting for the device. Retrieve the transaction, restore it and forward call to the device.
>>>>>>>
>>>>>>> 5. If device does not comes online upon receiving push notification and call times out or caller hangs up the call then you need to clean up transaction data stored in db. Similarly, you need to setup mechanism to purge push notification data after some time e.g. 7 or 10 days to ensure device push parameters remain up to date etc.
>>>>>>>
>>>>>>> The iOS apps now need to implement CallKit for push notification capable calls, that adds some serious difficultly in processing such calls since they show fake call screen before the actual call is received by app and if callee is too quick to respond to call (answer or reject) then kamailio will never know and still send the real call (step 4 above) later on, so you will need to manage that too.
>>>>>>>
>>>>>>> Hope this helps.
>>>>>>>
>>>>>>> On Thu, 27 Feb 2020, 13:25 master1024, <master1024(a)protonmail.com> wrote:
>>>>>>>
>>>>>>>> Sent with [ProtonMail](https://protonmail.com) Secure Email.
>>>>>>>>
>>>>>>>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>>>>>>>> On Thursday, February 27, 2020 5:52 PM, master1024 <master1024(a)protonmail.com> wrote:
>>>>>>>>
>>>>>>>>> Hello Team,
>>>>>>>>>
>>>>>>>>> I need to configure apns sip push notification in kamailio, I have read it many sites but I don't get proper understanding I read it is done with the help of tsilo module kindly support in it.
>>>>>>>>>
>>>>>>>>> Sent with [ProtonMail](https://protonmail.com) Secure Email.
>>>>>>>>>
>>>>>>>>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>>>>>>>>> On Thursday, February 27, 2020 11:10 AM, master1024 <master1024(a)protonmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hello,
>>>>>>>>>>
>>>>>>>>>> I need to configure apns push notification in kamailio kindly help. I have a file push.php It is capable to push notification on ios device know i want to implement in kamailio when the user is offline then push notification fire kindly help in this.
>>>>>>>>>>
>>>>>>>>>> Think Out of the Box
>>>>>>>>>>
>>>>>>>>>> Sent with [ProtonMail](https://protonmail.com) Secure Email.
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Kamailio (SER) - Users Mailing List
>>>>>>>> sr-users(a)lists.kamailio.org
>>>>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Hello,
Kamailio SIP Server v5.3.3 stable release is out.
This is a maintenance release of the latest stable branch, 5.3, that
includes fixes since the release of v5.3.2. There is no change to
database schema or configuration language structure that you have to do
on previous installations of v5.3.x. Deployments running previous v5.3.x
versions are strongly recommended to be upgraded to v5.3.3.
For more details about version 5.3.3 (including links and guidelines to
download the tarball or from GIT repository), visit:
* https://www.kamailio.org/w/2020/03/kamailio-v5-3-3-released/
RPM, Debian/Ubuntu packages will be available soon as well.
Many thanks to all contributing and using Kamailio!
Special circumstances are now everywhere word wide, impacting all of us,
therefore we wish a smooth time during this crisis and to stay healthy
to all our developers, supporters and community members along with
their beloved ones!
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Source:
https://www.kamailioworld.com/k08/2020/03/kamailio-world-2020-event-cancell…
It is probably no much of a surprise that the next Kamailio World
Conference and the NG-Emergency track cannot be organized any more
during April 27-29, 2020. We are trying to find out the best
alternatives for later in the year, when we hope the situation will be
back to normal and people will be again in mood for social interaction.
Being one of proposed alternatives, because we discussed a lot during
the last several days with the people involved in organizing the event
as well as its active community, we want to make it clear right now that
we do not plan to switch to an online version (i.e., video conferencing)
at the same dates. With the current situation out there, it is very
likely that the level of stress everywhere will be high during the next
6 weeks till the initial planned dates, so putting together the
infrastructure for video conferencing, synchronizing with the speakers
and participants will just add to it, therefore it is better that
everyone is focusing on taking care of the beloved ones and how to deal
the best with the daily constraints during this interval.
All the payments received for participating at or supporting Kamailio
World 2020 will be refunded. If you are among them, thank you once more!
We will contact you very soon with the relevant details.
Keep also an eye on the event website for updates related to what is
going to be next related to the conference!
We hope the evolution will turn into a positive perspective very soon
and the crisis is going to end rapidly, so everyone can return to the
usual activities! Moreover, we wish you and the beloved ones a smooth
time during this exceptional situation and to stay healthy!
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Hello,
I am considering to release Kamailio v5.3.3 next week, either on Monday
(March 16) or Tuesday (March 17). As usual, if any of you are aware of
issues not reported on the tracker yet or knows fixes not backported to
branch 5.3, reported them as soon as possible to take care of them.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com
K reported during about 90 sec period that it is out of shared memory:
Feb 28 09:47:28 rox1 /usr/bin/sip-proxy[19725]: ERROR: tm
[t_hooks.c:136]: insert_tmcb(): out of shm. mem
Feb 28 09:47:28 rox1 /usr/bin/sip-proxy[19725]: ERROR: acc
[acc_logic.c:394]: acc_onreq(): cannot register additional callbacks
Feb 28 09:47:28 rox1 /usr/bin/sip-proxy[19725]: ERROR: <core>
[core/sip_msg_clone.c:499]: sip_msg_shm_clone(): could not allocate
shared memory from shm pool
Feb 28 09:47:28 rox1 /usr/bin/sip-proxy[19725]: ERROR: tm
[t_lookup.c:1293]: new_t(): out of mem:
Feb 28 09:47:28 rox1 /usr/bin/sip-proxy[19725]: ERROR: tm
[t_lookup.c:1439]: t_newtran(): new_t failed
...
Feb 28 09:47:29 rox1 /usr/bin/sip-proxy[19725]: ERROR: <core>
[core/mem/q_malloc.c:297]: qm_find_free(): qm_find_free(0x7f1f2a506000,
1232); Free fragment not found!
Feb 28 09:47:29 rox1 /usr/bin/sip-proxy[19725]: ERROR: <core>
[core/mem/q_malloc.c:434]: qm_malloc(): qm_malloc(0x7f1f2a506000, 1232);
Free fragment not found!
Feb 28 09:47:29 rox1 /usr/bin/sip-proxy[19725]: ERROR: tm
[t_reply.c:1957]: relay_reply(): cannot alloc reply shmem
Feb 28 09:47:29 rox1 /usr/bin/sip-proxy[19725]: ERROR: <core>
[core/sip_msg_clone.c:499]: sip_msg_shm_clone(): could not allocate
shared memory from shm pool
Feb 28 09:47:29 rox1 /usr/bin/sip-proxy[19725]: ERROR: acc
[acc_logic.c:562]: acc_onreply(): failed to clone the request - acc aborted
...
Feb 28 09:48:51 rox1 /usr/bin/sip-proxy[19724]: ERROR: <core>
[core/mem/q_malloc.c:297]: qm_find_free(): qm_find_free(0x7f1f2a506000,
5728); Free fragment not found!
Feb 28 09:48:51 rox1 /usr/bin/sip-proxy[19724]: ERROR: <core>
[core/mem/q_malloc.c:434]: qm_malloc(): qm_malloc(0x7f1f2a506000, 5728);
Free fragment not found!
Feb 28 09:48:51 rox1 /usr/bin/sip-proxy[19724]: ERROR: tm
[t_lookup.c:1293]: new_t(): out of mem:
Feb 28 09:48:51 rox1 /usr/bin/sip-proxy[19724]: ERROR: tm
[t_lookup.c:1439]: t_newtran(): new_t failed
And after that period it started working normally again and
core.shmmem showed:
{
total: 134217728
free: 124173808
used: 9530960
real_used: 10043920
max_used: 134217728
fragments: 349
}
As can be seen, shm had been full, but normally only about 10% of it
is in use.
Syslog does not show any traffic spikes or other unusual activity before
the memory got full.
Any ideas what could cause such a high memory usage or could there be
a bug in shm management?
-- Juha
Any idea where this kind of error message could come from:
Mar 12 07:16:17 rox2 /usr/bin/sip-proxy[32058]: CRITICAL: <core>
[core/pass_fd.c:277]: receive_fd(): EOF on 61
Mar 12 07:16:17 rox2 /usr/bin/sip-proxy[32058]: ERROR: <core>
[core/io_wait.h:607]: io_watch_del(): trying to delete already erased
entry 61 in the hash(-1, 0, 0x7f689c16a868) flags 0)
Mar 12 07:16:17 rox2 /usr/bin/sip-proxy[32058]: ERROR: <core>
[core/io_wait.h:607]: io_watch_del(): trying to delete already erased
entry 64 in the hash(-1, 0, 0x7f68c063b0f0) flags 0)
Mar 12 07:16:17 rox2 /usr/bin/sip-proxy[32058]: CRITICAL: <core>
[core/pass_fd.c:191]: send_fd(): sendmsg failed sending 79 on 64: Broken
pipe (32)
Mar 12 07:16:17 rox2 /usr/bin/sip-proxy[32058]: ERROR: <core>
[core/tcp_main.c:4225]: send2child(): send_fd failed for 0x7f689c18a0b0
(flags 0x4018), fd 79
Debug does not give any hints.
-- Juha