Hi,
you can see the first error is a database error:
ERROR: db_mysql [km_my_con.c:124]: db_mysql_new_connection(): driver error:
Can't connect to MySQL server on 'server.net1.test' (111)
This error I expected because you have to adapt the access permissions to the
database.
Just check t
Daniel-Constantin Mierla writes:
> > Is it possible to configure Kamailio that wouldn’t send NOTIFY request
> > to watchers when publication status refresh (PUBLISH without XML Body)
> > occur?
> >
>
> no NOTIFY should be sent? Or the NOTIFY in this case should be sent
> without body, just with a
Hello,
On 20/01/16 12:34, Aleš Šturm wrote:
>
> Hi all,
>
>
>
>
>
> I am using Kamailio 4.3 as Presence server and I have a question
> regarding NOTIFY messages sent after publication status refresh. When
> PUA sends refreshing PUBLISH request (before expiration) Kamailio
> sends NOTIFY reques
Hi Phil,
Thanks for quick reply and to point to right direction.
It is working now and i can make calls.As you have asked the
save('location'). Well it was at his default location like
route_request{
>route(REGISTRAR);
> }
> ---
> route[REGISTRAR] {
> if (!is_method("REGISTER")) return;
> if(i
Are you using Kamailio’s usrloc module? If so, at what point do you
save(‘location’)?
From: sr-users [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of
Safdar Khan
Sent: 21 January 2016 12:24
To: Kamailio (SER) - Users Mailing List
Subject: [SR-Users] Kamailio and openLDAP integration
Hi guys,
I have tried to integrate kamailio and ldap.It seems like both are taking
to each other.
Here the purpose of ldap is for back-end support for sip user
authentication rather than kamailio database.However i am able to log in
but could not make call between sip users.I could not figure out w
On 21.01.2016 12:37, Igor Potjevlesch wrote:
And 2 coredumps readable:
Core was generated by `/usr/local/sbin/kamailio -P
/var/run/kamailio.pid -m 256 -M 64'.
Program terminated with signal 11, Segmentation fault.
#0 0x7f13a1550af2 in dtrie_insert (root=0x7f138d7ffb38,
number=0x22ba6c
Hello,
I got several errors this morning on a Kamailio instance.
The first occurred without a complete crash of Kamailio but 4 coredumps have
been created:
BFD: Warning: /core.3818 is truncated: expected core file size >= 342618112,
found: 61579264.
[New Thread 3818]
Cannot access mem
Am 20.01.2016 um 16:02 schrieb Daniel-Constantin Mierla:
> last edition of Kamailio Development Workshop happened about three years
> ago. As I got requests about it from time to time, I thought of trying
> to organize a new edition. Rather short term by now due to various
> constraints, so the pla
Hi,
you can definitely do this with Kamailio. We've made a similar setup
at an MNO, where we had two EPCs and two IMS-Cores which were directly
interconnected (using an Oracle/AcmePacket SBC or directly).
Thanks,
Carsten
2016-01-20 8:32 GMT+01:00 Olle E. Johansson :
>
>> On 19 Jan 2016, at 10:57
OK, thanks for testing -- patch backported to 4.3 branch.
Cheers,
Daniel
On 21/01/16 00:49, Alex Balashov wrote:
> On 01/20/2016 12:35 PM, Daniel-Constantin Mierla wrote:
>
>> Can you check with commit:
>>
>> https://github.com/kamailio/kamailio/commit/0ce66908ee9da74806e2fa506ef98b5f9043e47c
>>
On 21/01/16 08:46, Olle E. Johansson wrote:
>> On 20 Jan 2016, at 09:19, Daniel-Constantin Mierla wrote:
>>
>> Hello,
>>
>> wondering if anyone is using fork=no -- some old docs suggest it is
>> suitable for debugging, but actually kamailio doesn't work properly in
>> this mode, leading to more
12 matches
Mail list logo
