Hello,
preparing of v5.0.1 will start very soon, if anyone needs to push
commits to the branch 5.0 after 12:00UTC, then write first to sr-dev
mailing list on sync on #kamailio IRC channel. Once the announcement of
the release is out, the backports can be done again directly.
Cheers,
Daniel
On 04
Daniel,
+1 to what Olle said! I have been able to produce pretty consistently a
segfault in a total dev environment evapi / uac_req but it could be
something totally crazy I'm doing, I'll get you a bit more solid info on
the exact issue in the early am here, as well as make sure that the issue
Hey Daniel,
Indeed, call comes in over tcp and goes out over udp. They claim that it
is not RFC compatible to add the i.
Thanks,
DanB
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://li
Hello,
tell them to read again the RFC3261, respectively the Via grammar:
Via = ( "Via" / "v" ) HCOLON via-parm *(COMMA via-parm)
via-parm = sent-protocol LWS sent-by *( SEMI via-params )
via-params= via-ttl / via-maddr
/ via-received / via-b
Hello,
On 03.04.17 22:53, 노형균 wrote:
> Hello all, I’m having problem again.
> After solving DBENGINE=MYSQL, I’ve been asked to type password but still get
> this message.
> I’ve tried to install mysql-server but it showed the same.
when you install mysql-server you have to set the password, not
Hello,
On 03.04.17 22:15, 노형균 wrote:
> Hello all, I’m newbie to Kamailio and I’m having problem with installation.
> I tried to install Kamailio through
>
> '/usr/local/sbin/kamdbctl create’ but it showed error that database engine
> not specified.
>
> When I checked the kamctlrc file, the DBENG
Hello,
On 03.04.17 16:11, Yasin CANER wrote:
>
> Hello,
>
> I want to active ka_timer that means SIP session refreshing/timer.
> kamailio dialog module handles with OPtions methods. is there a way to
> handle it with re-invite or Update methods or is there another module
> to do it.
>
the ka_tim
Given that packaging there is not controlled by the kamailio project,
building from sources can be an option -- I guess that guidelines from
next link are more or less the same:
- http://kamailio.org/docs/tutorials/5.0.x/kamailio-install-guide-git/
Also, you can build the deb packages yourself,
Hello,
execution of event routes for kemi was added. You have to use master
branch for now.
Anyhow, I expect that maybe some functions from this modules were not
yet exported to kemi -- if you give the list of the functions you use in
your config from this modules, I will add them.
Cheers,
Danie
Hello,
nathelper module does ping OPTIONS only for UDP.
For tcp/tls, there is transport layer keepalive:
- https://www.kamailio.org/wiki/cookbooks/5.0.x/core#tcp_keepalive
What is the problem you are trying to solve with this? Maybe there are
some other options for it.
Cheers,
Daniel
On 31.
Hello,
On 31.03.17 09:53, narayan panigrahi wrote:
>
> Hi All,
>
>
> I have a architecture of pjsip,kamailio,freeswitch and one external
> server.
>
> When kamailio is receiving "407"-proxy authentication required from
> the external server it sends to freeswitch and received "407" from
> freeswi
Hello,
apparently the /var/run/kamailio folder was not created by the init.d
script for rpm, as it is done in the deb specs. I updated it and
triggered a rebuild of rpms, available at:
https://build.opensuse.org/package/show/home:kamailio:v5.0.x-rpms/kamailio50
Try to upgrade and then see if it
Hi,
I have downloaded and installed only the new rpm :
kamailio-5.0.0-10.1.x86_64.rpm. Is it enough ?
Then I try to start Kamailio that fails :
[root@vm-vse02-siprouter2 kamailio]# service kamailio start
Starting kamailio (via systemctl): Job for kamailio.service failed. See
'systemctl
Hello,
is kamailio already running there?
Cheers,
Daniel
On 05.04.17 14:12, Ginhoux, Patrick wrote:
>
> Hi,
>
>
>
> I have downloaded and installed only the new rpm :
> kamailio-5.0.0-10.1.x86_64.rpm. Is it enough ?
>
> Then I try to start Kamailio that fails :
>
>
>
> [root@vm-vse02-siprou
Hello,
Thanks for this feedback.
Here the description of the issue I am trying to solve.
I use already tcp_keepalive.
Call flow is:
UACs --> Nat device --> Kamailio
Transport protocol is TLS.
Kamailio sends TCPs keepalive (tcp_keepalive option) to the softphone
located behind the nat devices
Hi,
Message resend due to size exceeded.
Yes, it is running that is something I don’t understand how it can start with
this error:
[root@vm-vse02-siprouter2 ~]# ps -ef |grep kam
kamailio 1225 1 0 14:03 ?00:00:00 /usr/sbin/kamailio -P
/var/run/kamailio/kamailio.pid -m
Hi,
Yes, it is running that is something I don’t understand how it can start with
this error:
[root@vm-vse02-siprouter2 ~]# ps -ef |grep kam
kamailio 1225 1 0 14:03 ?00:00:00 /usr/sbin/kamailio -P
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kamailio
kamailio
Hello,
if kamailio is already running, you have to do a restart:
service kamailio restart
Cheers,
Daniel
On 05.04.17 14:38, Ginhoux, Patrick wrote:
>
> Hi,
>
>
>
> Message resend due to size exceeded.
>
>
>
>
>
> Yes, it is running that is something I don’t understand how it can
> star
Hello,
if it happens also between INVITE and 200ok or between 200ok and the
ACK, then very likely sending the OPTIONS will not help. Probably the
far end routers have a broken implementation of NAT.
Is this happening only for a specific group of users, or happens
randomly for different users?
Ch
Hi,
Actually I discovered that kamailio is running after I break the ‘service
Kamailio start’ command because of no response.
So I kill the Kamailio processes, check that it is not running anymore. In this
case the start command is sufficient.
Below the action I do:
[root@vm-vse02
> On 6/04/2017, at 12:25 AM, Abdoul Osséni wrote:
> I have always this issue with NAT devices using VSS-Monitoring protocol.
>
> A network capture shows:
> - Kamailio sends a tcp keepalive
> - The NAT device sends a tck keepalive ACK to Kamailio with a new filed :
> vss-monitoring
>
>
Thanks.
This is a network capture taken on Kamailio server that showing VSS
Monitoring ethernet.
---
This is not a LAN network. UAC is on Internet behind a NAT device so I
can't capture the traffic in the network.
According your message, you think UAC send close notify alerts even during
during t
Hi,
New update.
I attempt to stop kamailio with the ‘service kamailio stop command’ but it
doesn’t stop:
[root@vm-vse02-siprouter2 ~]# ps -ef |grep kam
kamailio 1157 1 0 15:10 ?00:00:00 /usr/sbin/kamailio -P
/var/run/kamailio/kamailio.pid -m 1024 -M 8 -u kamailio -g kam
On Wed, Apr 05, 2017 at 02:25:29PM +0200, Abdoul Osséni wrote:
> The advantage of the SIP ping options is a bidirectional traffic through
> NAT. I think in this case, my issue will be solved.
Due to some limitations of the nat helper pinger (3 backends, one should
ping at hh:mm:00, the other at hh
Hello,
the log messages show only that kamailio is already running.
If you do only 'service kamailio stop' what happens?
The new init.d script is creating /var/run/kamailio if it doesn't exist
and sets chown to it. So not really affecting how kamailio is stopped or
started.
Cheers,
Daniel
On 0
Hi,
Nothing happens after the ‘service kamailio stop’; kamailio is still running
(same pid) ((as detaillled below).
Cordialement
Patrick GINHOUX
De : Daniel-Constantin Mierla [mailto:mico...@gmail.com]
Envoyé : mercredi 5 avril 2017 15:44
À : Ginhoux, Patrick
Cc : Kamailio (SER) - U
On 04/04/2017 09:33 PM, Anthony Joseph Messina wrote:
After more digging, I see (from the Asterisk perspective) that after a certain
amount of time, the "RTCP report" size gets smaller and this is the point at
which the audio from Asterisk back to the softphone is dropped. Again, this
audio dro
Hello,
On 05.04.17 15:46, Ginhoux, Patrick wrote:
>
> Hi,
>
>
>
> Nothing happens after the ‘service kamailio stop’; kamailio is still
> running (same pid) ((as detaillled below).
>
>
>
can you run in terminal and give the output of the next command?
killproc -h
It seems that some versions
Hello,
Kamailio SIP Server v5.0.1 stable release is out!
This is a maintenance release of the latest stable branch, 5.0, that
includes fixes since the release of v5.0.0. There is no change to
database schema or configuration language structure that you have to do
on previous installations of v5.0
Hi,
The killproc command doesn’t exist :
[root@vm-vse02-siprouter2 ~]# killproc -h
-bash: killproc: command not found
To help the debug, I added ‘echo’ command at the case statement in the
/etc/init.d/Kamailio script :
# See how we were called.
case "$1" in
start|debug)
> On 6/04/2017, at 1:12 AM, Abdoul Osséni wrote:
>
> Thanks.
>
> This is a network capture taken on Kamailio server that showing VSS
> Monitoring ethernet.
Perhaps your service provider is adding it or something then, but that would be
very unusual. I would have a chat with your network team
Hello,
killproc might be only in opensuse as standalone tool and the other rpms
have it in init.d lib functions...
Can you install the rpms for kamailio 5.0.1? They are already built:
https://build.opensuse.org/package/show/home:kamailio:v5.0.x-rpms/kamailio50
I tried to force the pid file path
Hi,
I’m going to install the kamailio 5.0.1 .
One question before:
Can you tell me if it included the patch for the htable (issue
“ht_db_load_table(): key type must be string (type=6)”) ?
Cordialement
Patrick GINHOUX
De : Daniel-Constantin Mierla [mailto:mico...@gmail.com]
En
Hello,
yes, the patch for htable should be in 5.0.1.
Cheers,
Daniel
On 05.04.17 17:14, Ginhoux, Patrick wrote:
>
> Hi,
>
>
>
> I’m going to install the kamailio 5.0.1 .
>
>
>
> One question before:
>
>
>
> Can you tell me if it included the patch for the htable (issue
> “ht_db_load_table(
Hi,
Kamailio 5.0.1 is now installed,
The start and then the stop command works fine now. Kamailio is correctly
stopped.
I also tested a reboot, and saw kamailio started with success. A new attempt to
stop it is also successful.
So I can tell that this issue is closed; the fifo fi
On Wednesday, April 5, 2017 8:55:36 AM CDT Richard Fuchs wrote:
> On 04/04/2017 09:33 PM, Anthony Joseph Messina wrote:
> > After more digging, I see (from the Asterisk perspective) that after a
> > certain amount of time, the "RTCP report" size gets smaller and this is
> > the point at which the a
On 05/04/17 02:53 PM, Anthony Joseph Messina wrote:
On Wednesday, April 5, 2017 8:55:36 AM CDT Richard Fuchs wrote:
On 04/04/2017 09:33 PM, Anthony Joseph Messina wrote:
After more digging, I see (from the Asterisk perspective) that after a
certain amount of time, the "RTCP report" size gets sm
On Wednesday, April 5, 2017 2:24:12 PM CDT Richard Fuchs wrote:
> On 05/04/17 02:53 PM, Anthony Joseph Messina wrote:
> > On Wednesday, April 5, 2017 8:55:36 AM CDT Richard Fuchs wrote:
> >> On 04/04/2017 09:33 PM, Anthony Joseph Messina wrote:
> >>> After more digging, I see (from the Asterisk per
On Wednesday, April 5, 2017 2:54:08 PM CDT Anthony Joseph Messina wrote:
> Signed by
> amess...@messinet.com,webmas...@messinet.com,ad...@messinet.com. Show
> Details
> On Wednesday, April 5, 2017 2:24:12 PM CDT Richard Fuchs wrote:
> > On 05/04/17 02:53 PM, Anthony Joseph Messina wrote:
> > >
39 matches
Mail list logo
