Hello everyone,
I'm trying to use BLF with the config here (except with SQlite):
http://kb.asipto.com/kamailio:presence:k43-blf
BLF seems to work perfectly except after the call is ended I get
"sqlite commit failed: database is locked" error messages as seen
here:
http://pastebin.com/xVijj98H
BLF is then broken at this point.
kamailio -v
version: kamailio 4.3.5 (x86_64/linux) 950657
flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS,
USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM,
SHM_MMAP, PKG_MALLOC, DBG_QM_MALLOC, USE_FUTEX,
FAST_LOCK-ADAPTIVE_WAIT, USE_PTHREAD_MUTEX, USE_DNS_CACHE,
USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: 950657
compiled on 01:33:01 Mar 29 2016 with x86_64-openwrt-linux-gnu-gcc 4.8.3
Has anyone ever seen this before?
Thanks!
--
Kristian Kielhofner
hi ，
I want to use kamailio as a proxy ;
/ gateway1 ----->pstn
/
1、 call from backend server ---> kamailio ----->gateway2 -----> pstn
\
\ gateway3 ------->pstn
2、caller and callee number translation ;
Could you please give me some suggest;
Wade
From China
liwei(a)neulinx.com
Happy New Year!
I've just upgraded my Kamailio (build from master@c7e411e) instance to Fedora
23 from Fedora 22. I've built the packages specifically for Fedora 23 with
the following current sources:
openssl-1.0.2e-3.fc23.x86_64
openssl-libs-1.0.2e-3.fc23.x86_64
openssl version reports...
OpenSSL 1.0.2e-fips 3 Dec 2015
Even so, the following error occurs. It seems like Kamailio having trouble
detecting that I'm using running with the same version that I have installed,
and the same version that I have compiled against.
tls [tls_init.c:557]: init_tls_h(): ERROR: tls: init_tls_h: installed openssl
library version is too different from the library the Kamailio tls module was
compiled with: installed "OpenSSL 1.0.0-fips 29 Mar 2010" (0x10000003),
compiled "OpenSSL 1.0.2d-fips 9 Jul 2015" (0x1000204f).
Please make sure a
compatible version is used (tls_force_run in kamailio.cfg will override this
check)
CRITICAL: <core> [main.c:2558]: main(): could not initialize tls, exiting...
Any pointers? -A
--
Anthony - https://messinet.com/ - https://messinet.com/~amessina/gallery
8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E
Hello, *Olle!*
*Thanks for your help in this case, and don't worry about the time
(actually I wasn't even expecting to get an answer today).*
*I know the max_contacts parameter. But the problem is that if I set the
max_contacts to 2, when the user tries to register again, he gets an error
message 503. The point is that I want to get the user registered, and
replace the oldest location entry for the newest one.*
*Bruno Emer*
Mobile: +55 11 96540-0044
email: brunoemer(a)gmail.com
2016-04-01 16:31 GMT-03:00 Bruno Emer <brunoemer(a)gmail.com>:
> Hello all.
>
> I have problem here and I tried to find a solution and search over
> internet, but without success.
>
> My scenario is the following: I have an application that must be
> registered in Kamailio when a user logs in the web interface, so he can get
> calls (something like a web softphone using webrtc). At this point, we are
> OK, and everything is working fine.
>
> To get these register functions I am using the parameter "save("location",
> "0x04")" as described in the REGISTRAR module documentation, so if a user
> logs in another web browser or computer, only the last one will continue
> registered and all calls will be forwarded to him.
>
> The point is that now we are creating a phone app that will do almost the
> same thing as the web interface, allowing users to receive calls using the
> mobile device, and here is my problem: I want to allow my users to be
> registered on two devices at the same time, but if a user logs into another
> device, I don't want to reply with a 503. I want to allow the user to
> register again, deregistering the oldest contact.
>
> I saw that there is a module named "ims_usrloc_scscf" and on its
> description it says "implemented overwrite oldest contact behaviour", but
> I couldn't find any documentation about it.
>
> So, is there a way to get this working today?
>
>
> *Bruno Emer*
>
> Mobile: +55 11 96540-0044
> email: brunoemer(a)gmail.com
>
Hello all.
I have problem here and I tried to find a solution and search over
internet, but without success.
My scenario is the following: I have an application that must be registered
in Kamailio when a user logs in the web interface, so he can get calls
(something like a web softphone using webrtc). At this point, we are OK,
and everything is working fine.
To get these register functions I am using the parameter "save("location",
"0x04")" as described in the REGISTRAR module documentation, so if a user
logs in another web browser or computer, only the last one will continue
registered and all calls will be forwarded to him.
The point is that now we are creating a phone app that will do almost the
same thing as the web interface, allowing users to receive calls using the
mobile device, and here is my problem: I want to allow my users to be
registered on two devices at the same time, but if a user logs into another
device, I don't want to reply with a 503. I want to allow the user to
register again, deregistering the oldest contact.
I saw that there is a module named "ims_usrloc_scscf" and on its
description it says "implemented overwrite oldest contact behaviour", but I
couldn't find any documentation about it.
So, is there a way to get this working today?
*Bruno Emer*
Mobile: +55 11 96540-0044
email: brunoemer(a)gmail.com
For immediate release:
ATLANTA, GA (1 April 2016)--Alex J. Balashov, a self-styled
businessman based in Atlanta, Georgia, USA, has a plan to "Make
Kamailio Great Again".
"Evariste Systems is huge. My name is on the building," said
Balashov of his iconic VoIP consulting brand.
"And you know what, I have been very successful. Everybody loves me."
Balashov has capitalised on a contentious election cycle marked by
deep political polarisation, growing income inequality and geopolitical
challenges such as global terrorism. And his sharp message of alarm
about the declining influence of the Kamailio SIP server project has
resonated with increasing numbers in the CxO suite, vaulting him to
the lead in the race for the IETF SIP Working Group nomination,
according to recent polls of primary voters.
He has been quick to tout his competitive credentials in a tough
global open-source ecosystem. At a recent colloqium on unified
communications, he asked:
"When was the last time anybody saw us beating, let's say, OpenSIPS
in Git commits? They kill us. I beat OpenSIPS all the time. All the
time."
As Balashov sees it, a major cause of the beleaguered Kamailio
project's woes lies in its liberal patch acceptance policy and
lax scrutiny of third-party contributions:
"When GitHub sends its people, they're not sending their best.
They're not sending you. They're not sending you. They're sending
people that have lots of problems, and they're bringing those
problems. They're bringing drugs. They're bringing crime. They're
rapists. And some, I assume, are good people."
He has proposed a controversial solution that has drawn ire from
liberal ranks in the open-source community, but has also attracted
applause and standing ovations at his speaking engagements:
"We have to have a firewall around the Kamailio source code. We
have to have an access control list. And in that firewall, we're
going to have a big fat door where commits and pull requests can
come into the master branch, but they have to come in legally.
The firewall will go up, and GitHub will start behaving."
Balashov's firewall proposal has been met with scorn from critics who
deride it as impractical and quixotic. In particular, commentators
have raised questions about funding and resources as well as GitHub's
willingness to entertain a boundary around a project in its vicinity.
Balashov isn't concerned, however:
"I will build a great firewall--and nobody builds firewalls better
than me, believe me--and I'll build them very inexpensively. I will
build a great, great stateful packet inspection wall on our border
with GitHub, and I will make GitHub pay for that wall. Mark my words."
He has also been rebuked by rival IETF leadership candidates for his
often acerbic Twitter remarks directed at Lennart Poettering and the
developers of "firewalld". As he sees it, however, the network effects
of social media are a strength: "My Twitter has become so powerful
that I can actually make my enemies tell the truth." He scoffed at
the suggestion that his characterisations of industry actors behind
the RedHat-led "systemd" movement are misleading:
"RedHat was the worst Steward of Linux in the history of the kernel.
There has never been a Steward so bad as RedHat. The source code
blew up around us. We lost everything, including all synergies.
There wasn't one good thing that came out of that administration or
them being Stewards of Linux."
Balashov's idiosyncratic campaign is not standing still. He has proven
to be a capable populist, adapting rapidly to an evolving sense of the
kinds of pronouncements that activate his swelling crowds of devotees.
Along the way, he has deftly deflected calls to subject his policy
proposals to expert review.
"I know what I'm doing, and I listen to a lot of people, I talk to
a lot of people, and at the appropriate time I'll tell you who
the people are. But I speak to a lot of people, but my primary
consultant is myself, and I have a good instinct for this stuff."
At a recent gathering of SIP stack interoperability specialists,
Balashov the latest pillar of his platform to "Make Kamailio Great
Again", in view of growing security vulnerabilities in the latest
Kamailio modules:
"Alex J. Balashov is calling for a total and complete shutdown of
commits entering the master branch from the territory of the European
Union until our project's representatives can figure out what's going
on. According to Netcraft, among others, there are a lot of buffer
overflows in Kamailio by large segments of the EU population."
Hi,
I'm seeing a difference in timestamp for acc modules recorderd INVITES
and the dialog start event.
This is the log entry:
Apr 1 12:55:59 host /usr/sbin/kamailio[15642]: INFO: <script>:
5d3ff3407b9761b24c4f75195c6ccb1d@192.168.10.245:5060 - dialog:start
And this has been added by ACC in the database:
INVITE
as2880319e
56FE53B9-49E3774-3E86ED1B
5d3ff3407b9761b24c4f75195c6ccb1d@192.168.10.245:50...
200
OK
2016-04-01 12:56:01
Why are these two seconds apart? Shouldn't the acc module record the
same dialog start event time as the start of a dialog? When I look at
the value of DLG_lifetime this confirms my findings, as it results in:
dialog_time = TS - dlg_start
When looking at the database BYE-time - INVITE time, the call is two
seconds shorter.
Any insight would be appreciated!
Cheers,
Dirk
Hello,
I installed Kamailio 4.3 on debian wheezy machine using debian package from https://www.kamailio.org/wiki/packages/debsThe installation went fine, but I'm unable to start kamailio. It seems that Kamailio is having issue locating the issues.Kamailio installed all the modules in location '/usr/lib/x86_64-linux-gnu/kamailio/modules', when building from source, it usedto copy modules in '/usr/lib/kamailio/modules'.Any suggestions on how can I fix it?
Thanks,Nitesh
Hi, all
Not a Kamailio-related question, but.
I want to form SIP-packets with info I need and receive answers.
At first iteration in would be PUBLISH (with XML info) messages (PUBLISH -
200 OK) sent to Kamailio.
I want to use Python (more preferable) or Lua (less preferable). Is there
any lib I can create messages with, or forget and just use plain text + UDP
socket?
--
Best regards,
Igor
