date:20180904

Re: [SR-Users] dispatcher probe

2018-09-04 Thread volga629


Hello Mojtaba,
Probe packet is generated by kamailio him self and it not visible in 
REQINIT, at least xlog not showing.


volga629

On Tue, Sep 4, 2018 at 3:23 AM, Mojtaba  wrote:

Hi,
Sure, You could add in REQINIT route block in Kamailio.
With Regads.Mojtaba
On Tue, Sep 4, 2018 at 5:11 AM  wrote:


 Hello Everyone,
 Is possible access OPTIONS packet generated by dispatcher probe ?
 I am trying insert something like this.

 if(is_method("OPTIONS") && $hdr(User-Agent)=~"kamailio") {
 append_hf("X-Node-ID: $avp(node_id)\r\n");
 }


 volga629


 ___
 Kamailio (SER) - Users Mailing List
 sr-users@lists.kamailio.org
 https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users




--
--Mojtaba Esfandiari.S

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users



___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] dispatcher probe

2018-09-04 Thread Federico Cabiddu

Hi,
you can access locally generated packets in
the event_route[tm:local-request].

Cheers,

Federico

On Tue, Sep 4, 2018 at 2:41 AM  wrote:

> Hello Everyone,
> Is possible access OPTIONS packet generated by dispatcher probe ?
> I am trying insert something like this.
>
> if(is_method("OPTIONS") && $hdr(User-Agent)=~"kamailio") {
> append_hf("X-Node-ID: $avp(node_id)\r\n");
> }
>
>
> volga629
>
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Can't connect to local MySQL server (13 "Permission denied")

2018-09-04 Thread David Villasmil

Make sure the password is correct and try with "localhost" and if that
doesn't work, try with 127.0.0.1

On Tue, Sep 4, 2018, 07:35 Henning Westerholt  wrote:

> Am Freitag, 31. August 2018, 21:01:13 CEST schrieb Ginhoux, Patrick:
> > Usually I connect on a command line like this ;
> >
> > su- mysql
> >
> > mysql
> >
> > use siprouter;
> >
> > If now I use
> >
> > mysql -u siprouter -p
> >
> > Enter password:
> >
> > mysql:siprouter:(none)> use siprouter;
> >
> > Database changed
> >
> > So I can connect the local server.
>
> Hello Patrick,
>
> just some ideas to help you troubleshoot the problem:
>
> - maybe there is an issue with the socket file, that kamailio uses the
> wrong
> socket file?
> - maybe kamailio don't have file system access rights to the socket file?
> - maybe there is a mistake in the kamailio cfg or an old cfg file is used?
> - enable mysql server logging and try to spot something in the log during
> the
> kamailio start
>
> Best regards,
>
> Henning
>
> --
> Henning Westerholt
> https://skalatan.de/blog/
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Can't connect to local MySQL server (13 "Permission denied")

2018-09-04 Thread David Villasmil

You should paste your failing cfg line.

On Tue, Sep 4, 2018, 08:39 David Villasmil 
wrote:

> Make sure the password is correct and try with "localhost" and if that
> doesn't work, try with 127.0.0.1
>
> On Tue, Sep 4, 2018, 07:35 Henning Westerholt  wrote:
>
>> Am Freitag, 31. August 2018, 21:01:13 CEST schrieb Ginhoux, Patrick:
>> > Usually I connect on a command line like this ;
>> >
>> > su- mysql
>> >
>> > mysql
>> >
>> > use siprouter;
>> >
>> > If now I use
>> >
>> > mysql -u siprouter -p
>> >
>> > Enter password:
>> >
>> > mysql:siprouter:(none)> use siprouter;
>> >
>> > Database changed
>> >
>> > So I can connect the local server.
>>
>> Hello Patrick,
>>
>> just some ideas to help you troubleshoot the problem:
>>
>> - maybe there is an issue with the socket file, that kamailio uses the
>> wrong
>> socket file?
>> - maybe kamailio don't have file system access rights to the socket file?
>> - maybe there is a mistake in the kamailio cfg or an old cfg file is used?
>> - enable mysql server logging and try to spot something in the log during
>> the
>> kamailio start
>>
>> Best regards,
>>
>> Henning
>>
>> --
>> Henning Westerholt
>> https://skalatan.de/blog/
>>
>> ___
>> Kamailio (SER) - Users Mailing List
>> sr-users@lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>
>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Can't connect to local MySQL server (13 "Permission denied")

2018-09-04 Thread Ginhoux, Patrick

Hi,

 

Looking at your message, I checked again the installation and mainly the 
symlink I had created for Kamailio to get the socket file.

 

For some reason, this link were corrupted. Hereafter what was the issue:

 

The initial symlink for the socket file was : ln -s 
/myqdata/mysiprdb/data/mysiprdb.sock /var/lib/mysql/mysql.sock

But actually a locate command : returns strange

locate *.sock

/myqdata/mysiprdb/data/mysiprdb.sock

/var/lib/gssproxy/default.sock

/var/lib/mysql/mysql.sock

/var/lib/mysql/mysql.sock/mysiprdb.sock

The “/var/lib/mysql/mysql.sock/mysiprdb.sock” doesn’t make sense here.

And the “/var/lib/mysql/mysql.sock” was actually a directoty

[root@in52inmvt2router1 ~]# ll /var/lib/mysql/

total 4

drwx-- 2 root root 4096 Sep  4 10:21 mysql.sock

Removing all of these files/directories, then recreate the symlink have fixed 
the issue.

 

Thanks everybody for your ideas of things to check..

 

Cordialement.

Patrick GINHOUX 

Unisys | +33 1 46 69 52 12 | +33 6 60 32 24 74 | patrick.ginh...@unisys.com

 

De : David Villasmil  
Envoyé : mardi 4 septembre 2018 09:41
À : Kamailio (SER) - Users Mailing List 
Cc : Ginhoux, Patrick 
Objet : Re: [SR-Users] Can't connect to local MySQL server (13 "Permission 
denied")

 

You should paste your failing cfg line.

 

On Tue, Sep 4, 2018, 08:39 David Villasmil mailto:david.villasmil.w...@gmail.com> > wrote:

Make sure the password is correct and try with "localhost" and if that doesn't 
work, try with 127.0.0.1

 

On Tue, Sep 4, 2018, 07:35 Henning Westerholt mailto:h...@kamailio.org> > wrote:

Am Freitag, 31. August 2018, 21:01:13 CEST schrieb Ginhoux, Patrick:
> Usually I connect on a command line like this ;
> 
> su- mysql
> 
> mysql
> 
> use siprouter;
> 
> If now I use
> 
> mysql -u siprouter -p
> 
> Enter password:
> 
> mysql:siprouter:(none)> use siprouter;
> 
> Database changed
> 
> So I can connect the local server.

Hello Patrick,

just some ideas to help you troubleshoot the problem:

- maybe there is an issue with the socket file, that kamailio uses the wrong 
socket file?
- maybe kamailio don't have file system access rights to the socket file?
- maybe there is a mistake in the kamailio cfg or an old cfg file is used?
- enable mysql server logging and try to spot something in the log during the 
kamailio start

Best regards,

Henning

-- 
Henning Westerholt
https://skalatan.de/blog/

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org  
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users



smime.p7s
Description: S/MIME cryptographic signature
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] event_route [tcp:closed] not executed

2018-09-04 Thread Juha Heinanen

Based on comment:

  https://github.com/kamailio/kamailio/issues/171#issuecomment-418175840

I gave event_route [tcp:closed] a try:

event_route [tcp:closed] {  # Handle TCP connection close
xlog("L_INFO", "$proto connection closed ($conid)\n");
}

Nothing comes to syslog when I quit my baresip UA that according to
wireshark closes its TCP connection after un-registration (fin - fin -
ack).

I have not set closed_event param, because according to README, it
defaults to 1.

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Missing ACC record in case of canceled call forking

2018-09-04 Thread Marco Capetta


HiAll,

As additional step I tested the scenario with kamailio v5.1.5 but the 
problem seems still there.


Best regards.
Marco


On 08/28/2018 03:10 PM, Marco Capetta wrote:


Hi All,

I'm facing a strange problem of missing ACC record in case of parallel 
call forking.


The scenario is the following:
 - A subscriber with 1 device registered
 - B subscriber with 2 device registered (B1 and B2)

CASE 1:
 - A calls B
 - B1 and B2 start ringing
 - A hangups the call before B1 or B2 answers
Kamailio generates an ACC record.

CASE 2:
 - A calls B
 - B1 and B2 start ringing
 - B1 rejects the call sending back a 486
 - B2 is still ringing
 - A hangups the call before B2 answers
Kamailio DOESN'T generate an ACC record.



We have Kamailio v5.1.4 with TM module enabled.

ACC configuration is the following:
  modparam("acc", "early_media", 0)
  modparam("acc", "report_ack", 0)
  modparam("acc", "report_cancels", 1)
  modparam("acc", "detect_direction", 1)
  modparam("acc", "db_flag", 1)
  modparam("acc", "db_missed_flag", 2)
  modparam("acc", "failed_transaction_flag", 3)


I increased debug level of TM and ACC modules and I added some debug 
lines as well.
The difference between the two calls is that, after the CANCEL sent by 
A is processed by Kamailio, in CASE 1 I have the following lines:
  Aug 28 14:21:11 spce proxy[13188]: DEBUG: tm [t_hooks.c:258]: 
run_trans_callbacks_internal(): DBG: trans=0x7f5a88049198, callback 
type 512, id 0 entered
  Aug 28 14:21:11 spce proxy[13188]: DEBUG: acc [acc_logic.c:670]: 
tmcb_func(): acc callback called for t(0x7f5a88049198) event type 512, 
reply code 487
  Aug 28 14:21:11 spce proxy[13188]: DEBUG: acc [acc_extra.h:63]: 
free_strar_mem(): Freeing memory, type is 2, message_index 8, index i 0
  Aug 28 14:21:11 spce proxy[13188]: DEBUG: acc [acc_extra.h:63]: 
free_strar_mem(): Freeing memory, type is 2, message_index 8, index i 1
  Aug 28 14:21:11 spce proxy[13188]: DEBUG: acc [acc_extra.h:63]: 
free_strar_mem(): Freeing memory, type is 2, message_index 8, index i 2
  Aug 28 14:21:11 spce proxy[13188]: DEBUG: acc [acc_extra.h:63]: 
free_strar_mem(): Freeing memory, type is 2, message_index 8, index i 3
  Aug 28 14:21:11 spce proxy[13188]: DEBUG: acc [acc_extra.h:63]: 
free_strar_mem(): Freeing memory, type is 2, message_index 8, index i 4


Those debug lines are not printed for CASE 2.



Is there any configuration I'm missing or is it a bug?



Thank you very much for your support.
Marco




___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] event_route [tcp:closed] not executed

2018-09-04 Thread Daniel-Constantin Mierla

Can you list the tcp connections via rpc and see if the one you expect
to be closed is still listed there?

I haven't added the feature and not used it so far, but it might be the
cleanup timer routing for tcp connections that trigger the event route.

Cheers,
Daniel


On 04.09.18 11:07, Juha Heinanen wrote:
> Based on comment:
>
>   https://github.com/kamailio/kamailio/issues/171#issuecomment-418175840
>
> I gave event_route [tcp:closed] a try:
>
> event_route [tcp:closed] {  # Handle TCP connection close
> xlog("L_INFO", "$proto connection closed ($conid)\n");
> }
>
> Nothing comes to syslog when I quit my baresip UA that according to
> wireshark closes its TCP connection after un-registration (fin - fin -
> ack).
>
> I have not set closed_event param, because according to README, it
> defaults to 1.
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference -- www.kamailioworld.com
Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] TOPOH module im REGISTER method.

2018-09-04 Thread Mojtaba

Hello,
I am used topoh module in kamailio, Why this module does not work (No
change ) in Register request Method?
I need to change UA' ip address in Via header in Register request
before forwarded to my network? Does the topoh module used in this
situation?
I have not this issue in INVITE request, I just have this issue in
Register request.
Thanks.
With Regards.Mojtaba

-- 
--Mojtaba Esfandiari.S

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Missing ACC record in case of canceled call forking

2018-09-04 Thread Daniel-Constantin Mierla

Hello,

is flag 3 set for the INVITE transaction?

In the 1st case, is the CANCEL accounted or the INVITE transaction or both?

Cheers,
Daniel


On 04.09.18 11:18, Marco Capetta wrote:
> HiAll,
>
> As additional step I tested the scenario with kamailio v5.1.5 but the
> problem seems still there.
>
> Best regards.
> Marco
>
>
> On 08/28/2018 03:10 PM, Marco Capetta wrote:
>>
>> Hi All,
>>
>> I'm facing a strange problem of missing ACC record in case of
>> parallel call forking.
>>
>> The scenario is the following:
>>  - A subscriber with 1 device registered
>>  - B subscriber with 2 device registered (B1 and B2)
>>
>> CASE 1:
>>  - A calls B
>>  - B1 and B2 start ringing
>>  - A hangups the call before B1 or B2 answers
>> Kamailio generates an ACC record.
>>
>> CASE 2:
>>  - A calls B
>>  - B1 and B2 start ringing
>>  - B1 rejects the call sending back a 486
>>  - B2 is still ringing
>>  - A hangups the call before B2 answers
>> Kamailio DOESN'T generate an ACC record.
>>
>>
>>
>> We have Kamailio v5.1.4 with TM module enabled.
>>
>> ACC configuration is the following:
>>   modparam("acc", "early_media", 0)
>>   modparam("acc", "report_ack", 0)
>>   modparam("acc", "report_cancels", 1)
>>   modparam("acc", "detect_direction", 1)
>>   modparam("acc", "db_flag", 1)
>>   modparam("acc", "db_missed_flag", 2)
>>   modparam("acc", "failed_transaction_flag", 3)
>>
>>
>> I increased debug level of TM and ACC modules and I added some debug
>> lines as well.
>> The difference between the two calls is that, after the CANCEL sent
>> by A is processed by Kamailio, in CASE 1 I have the following lines:
>>   Aug 28 14:21:11 spce proxy[13188]: DEBUG: tm [t_hooks.c:258]:
>> run_trans_callbacks_internal(): DBG: trans=0x7f5a88049198, callback
>> type 512, id 0 entered
>>   Aug 28 14:21:11 spce proxy[13188]: DEBUG: acc [acc_logic.c:670]:
>> tmcb_func(): acc callback called for t(0x7f5a88049198) event type
>> 512, reply code 487
>>   Aug 28 14:21:11 spce proxy[13188]: DEBUG: acc [acc_extra.h:63]:
>> free_strar_mem(): Freeing memory, type is 2, message_index 8, index i 0
>>   Aug 28 14:21:11 spce proxy[13188]: DEBUG: acc [acc_extra.h:63]:
>> free_strar_mem(): Freeing memory, type is 2, message_index 8, index i 1
>>   Aug 28 14:21:11 spce proxy[13188]: DEBUG: acc [acc_extra.h:63]:
>> free_strar_mem(): Freeing memory, type is 2, message_index 8, index i 2
>>   Aug 28 14:21:11 spce proxy[13188]: DEBUG: acc [acc_extra.h:63]:
>> free_strar_mem(): Freeing memory, type is 2, message_index 8, index i 3
>>   Aug 28 14:21:11 spce proxy[13188]: DEBUG: acc [acc_extra.h:63]:
>> free_strar_mem(): Freeing memory, type is 2, message_index 8, index i 4
>>
>> Those debug lines are not printed for CASE 2.
>>
>>
>>
>> Is there any configuration I'm missing or is it a bug?
>>
>>
>>
>> Thank you very much for your support.
>> Marco
>>
>
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference -- www.kamailioworld.com
Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] event_route [tcp:closed] not executed

2018-09-04 Thread Juha Heinanen

Daniel-Constantin Mierla writes:

> Can you list the tcp connections via rpc and see if the one you expect
> to be closed is still listed there?

core.tcp_list after quiting baresip shows that the tcp connection has been
removed, i.e., is not anymore in the list

-- Juha

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] event_route [tcp:closed] not executed

2018-09-04 Thread Daniel-Constantin Mierla



On 04.09.18 11:41, Juha Heinanen wrote:
> Daniel-Constantin Mierla writes:
>
>> Can you list the tcp connections via rpc and see if the one you expect
>> to be closed is still listed there?
> core.tcp_list after quiting baresip shows that the tcp connection has been
> removed, i.e., is not anymore in the list
>
Can you test with latest master and debug=3, then send all debug
messages from tcp connect to disconnect?

I just pushed a commit to add debug messages that can help troubleshoot
if the execution of relevant code in tcpops happens or not.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference -- www.kamailioworld.com
Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] event_route [tcp:closed] not executed

2018-09-04 Thread Juha Heinanen

Daniel-Constantin Mierla writes:

> Can you test with latest master and debug=3, then send all debug
> messages from tcp connect to disconnect?

Below is the debug.  First REGISTER comes at 13:13:26 and un-REGISTER at
13:13:29 followed by tcp connection close.

-- Juha

Sep  4 13:13:26 char /usr/bin/sip-proxy[15893]: DEBUG:  
[core/ip_addr.c:229]: print_ip(): tcpconn_new: new tcp connection: 
192.168.43.107
Sep  4 13:13:26 char /usr/bin/sip-proxy[15893]: DEBUG:  
[core/tcp_main.c:999]: tcpconn_new(): on port 43822, type 2
Sep  4 13:13:26 char /usr/bin/sip-proxy[15893]: DEBUG:  
[core/tcp_main.c:1305]: tcpconn_add(): hashes: 23:2680:2459, 4
Sep  4 13:13:26 char /usr/bin/sip-proxy[15893]: DEBUG:  
[core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0x55561b5d2d40, 69, 2, 
0x7f64144e38b0), fd_no=57
Sep  4 13:13:26 char /usr/bin/sip-proxy[15893]: DEBUG:  
[core/io_wait.h:602]: io_watch_del(): DBG: io_watch_del (0x55561b5d2d40, 69, 
-1, 0x0) fd_no=58 called
Sep  4 13:13:26 char /usr/bin/sip-proxy[15893]: DEBUG:  
[core/tcp_main.c:4196]: handle_tcpconn_ev(): sending to child, events 1
Sep  4 13:13:26 char /usr/bin/sip-proxy[15893]: DEBUG:  
[core/tcp_main.c:3847]: send2child(): checking per-socket generic workers 
(15845/27..15874/34) [tcp:192.168.43.107:5060]
Sep  4 13:13:26 char /usr/bin/sip-proxy[15893]: DEBUG:  
[core/tcp_main.c:3875]: send2child(): selected tcp worker 0 27(15845) for 
activity on [tcp:192.168.43.107:5060], 0x7f64144e38b0
Sep  4 13:13:26 char /usr/bin/sip-proxy[15845]: DEBUG:  
[core/tcp_read.c:1740]: handle_io(): received n=8 con=0x7f64144e38b0, fd=12
Sep  4 13:13:26 char /usr/bin/sip-proxy[15845]: DEBUG:  
[core/tcp_read.c:1540]: tcp_read_req(): content-length=0
Sep  4 13:13:26 char /usr/bin/sip-proxy[15845]: DEBUG:  
[core/receive.c:232]: receive_msg(): --- received sip message - request - 
call-id: [b89bf3310da039ee] - cseq: [59445 REGISTER]
Sep  4 13:13:26 char /usr/bin/sip-proxy[15845]: DEBUG:  
[core/receive.c:287]: receive_msg(): preparing to run routing scripts...
Sep  4 13:13:26 char /usr/bin/sip-proxy[15845]: DEBUG:  
[core/tcp_main.c:2225]: tcpconn_send_put(): send from reader (15845 (27)), 
reusing fd
Sep  4 13:13:26 char /usr/bin/sip-proxy[15845]: DEBUG:  
[core/tcp_main.c:2460]: tcpconn_do_send(): sending...
Sep  4 13:13:26 char /usr/bin/sip-proxy[15845]: DEBUG:  
[core/tcp_main.c:2494]: tcpconn_do_send(): after real write: c= 0x7f64144e38b0 
n=519 fd=12
Sep  4 13:13:26 char /usr/bin/sip-proxy[15845]: DEBUG:  
[core/tcp_main.c:2495]: tcpconn_do_send(): buf=#012SIP/2.0 401 Unauthorized ...
Sep  4 13:13:26 char /usr/bin/sip-proxy[15845]: DEBUG:  
[core/receive.c:449]: receive_msg(): cleaning up
Sep  4 13:13:26 char /usr/bin/sip-proxy[15845]: DEBUG:  
[core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0x55561b61bf40, 12, 2, 
0x7f64144e38b0), fd_no=1
Sep  4 13:13:29 char /usr/bin/sip-proxy[15845]: DEBUG:  
[core/tcp_read.c:1540]: tcp_read_req(): content-length=0
Sep  4 13:13:29 char /usr/bin/sip-proxy[15845]: DEBUG:  
[core/receive.c:232]: receive_msg(): --- received sip message - request - 
call-id: [b89bf3310da039ee] - cseq: [59447 REGISTER]
Sep  4 13:13:29 char /usr/bin/sip-proxy[15845]: DEBUG:  
[core/socket_info.c:559]: grep_sock_info(): checking if host==us: 14==14 && 
[192.168.43.107] == [192.168.43.107]
Sep  4 13:13:29 char /usr/bin/sip-proxy[15845]: DEBUG:  
[core/socket_info.c:566]: grep_sock_info(): checking if port 5060 (advertise 0) 
matches port 5060
Sep  4 13:13:29 char /usr/bin/sip-proxy[15845]: DEBUG:  
[core/tcp_main.c:2225]: tcpconn_send_put(): send from reader (15845 (27)), 
reusing fd
Sep  4 13:13:29 char /usr/bin/sip-proxy[15845]: DEBUG:  
[core/tcp_main.c:2460]: tcpconn_do_send(): sending...
Sep  4 13:13:29 char /usr/bin/sip-proxy[15845]: DEBUG:  
[core/tcp_main.c:2494]: tcpconn_do_send(): after real write: c= 0x7f64144e38b0 
n=417 fd=12
Sep  4 13:13:29 char /usr/bin/sip-proxy[15845]: DEBUG:  
[core/tcp_main.c:2495]: tcpconn_do_send(): buf=#012SIP/2.0 200 OK ...
Sep  4 13:13:29 char /usr/bin/sip-proxy[15845]: DEBUG:  
[core/receive.c:449]: receive_msg(): cleaning up
Sep  4 13:13:29 char /usr/bin/sip-proxy[15845]: DEBUG:  
[core/tcp_read.c:198]: tcp_emit_closed_event(): TCP closed event creation 
triggered (reason: 0)
Sep  4 13:13:29 char /usr/bin/sip-proxy[15845]: DEBUG:  
[core/tcp_read.c:206]: tcp_emit_closed_event(): no callback registering for 
handling TCP closed event
Sep  4 13:13:29 char /usr/bin/sip-proxy[15845]: DEBUG:  
[core/tcp_read.c:315]: tcp_read_data(): EOF on 0x7f64144e38b0, FD 12 
([192.168.43.107]:43822 ->
Sep  4 13:13:29 char /usr/bin/sip-proxy[15845]: DEBUG:  
[core/tcp_read.c:316]: tcp_read_data(): -> [192.168.43.107]:5060)
Sep  4 13:13:29 char /usr/bin/sip-proxy[15845]: DEBUG:  
[core/tcp_read.c:1507]: tcp_read_req(): EOF
Sep  4 13:13:29 char /usr/bin/sip-proxy[15845]: DEBUG:  
[core/io_wait.h:602]: io_watch_del(): DBG: io_watch_del (0x55561b61bf40, 12, 
-1, 0x10) fd_no=2 called
Sep  4 13:13:29 char /usr/bin/sip-proxy[15845]:

[SR-Users] dlg.end_dlg on RTP timeout

2018-09-04 Thread Igor Olhovskiy

Hi all!

Is there any way to end dialog in Kamailio on RTP Timeout event on RTPEngine?

Or only look at logs/redis database with external tool?

Regards, Igor
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] event_route [tcp:closed] not executed

2018-09-04 Thread Juha Heinanen

I had not loaded tcpops module.  Should work after that.  How about
checking that all event routes in config have corresponding modules
loaded?

-- Juha

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] dlg.end_dlg on RTP timeout

2018-09-04 Thread Alex Balashov

There is according the module docs. But there isn't. ;-) 

--
Sent from mobile. Apologies for brevity and errors. 

-Original Message-
From: Igor Olhovskiy 
To: "Kamailio (SER) - Users Mailing List" 
Sent: Tue, 04 Sep 2018 6:48 AM
Subject: [SR-Users] dlg.end_dlg on RTP timeout

Hi all!

Is there any way to end dialog in Kamailio on RTP Timeout event on RTPEngine?

Or only look at logs/redis database with external tool?

Regards, Igor

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] event_route [tcp:closed] not executed

2018-09-04 Thread Juha Heinanen

I loaded tcpops module but still nothing to syslog from:

  event_route [tcp:close]

Debug (below) now shows this:

Sep  4 14:07:52 char /usr/bin/sip-proxy[6487]: DEBUG: tcpops [tcpops.c:233]: 
tcpops_handle_tcp_closed(): received TCP closed event
Sep  4 14:07:52 char /usr/bin/sip-proxy[6487]: DEBUG: tcpops [tcpops.c:207]: 
tcpops_tcp_closed_run_route(): event reason id: 0 rt: 10

-- Juha

--

Sep  4 14:07:41 char /usr/bin/sip-proxy[6487]: DEBUG:  
[core/tcp_main.c:2225]: tcpconn_send_put(): send from reader (6487 (27)), 
reusing fd
Sep  4 14:07:41 char /usr/bin/sip-proxy[6487]: DEBUG:  
[core/tcp_main.c:2460]: tcpconn_do_send(): sending...
Sep  4 14:07:41 char /usr/bin/sip-proxy[6487]: DEBUG:  
[core/tcp_main.c:2494]: tcpconn_do_send(): after real write: c= 0x7f7fad11ed00 
n=779 fd=12
Sep  4 14:07:41 char /usr/bin/sip-proxy[6487]: DEBUG:  
[core/tcp_main.c:2495]: tcpconn_do_send(): buf=#012SIP/2.0 200 OK ...
Sep  4 14:07:41 char /usr/bin/sip-proxy[6487]: DEBUG:  
[core/receive.c:345]: receive_msg(): request-route executed in: 90073 usec
Sep  4 14:07:41 char /usr/bin/sip-proxy[6487]: DEBUG:  
[core/receive.c:449]: receive_msg(): cleaning up
Sep  4 14:07:47 char /usr/bin/sip-proxy[6487]: DEBUG:  
[core/io_wait.h:602]: io_watch_del(): DBG: io_watch_del (0x558dca3d4f40, 12, 
-1, 0x10) fd_no=2 called
Sep  4 14:07:47 char /usr/bin/sip-proxy[6487]: DEBUG:  
[core/tcp_read.c:1661]: release_tcpconn(): releasing con 0x7f7fad11ed00, state 
1, fd=12, id=4 ([192.168.43.107]:44522 -> [192.168.43.107]:5060)
Sep  4 14:07:47 char /usr/bin/sip-proxy[6487]: DEBUG:  
[core/tcp_read.c:1665]: release_tcpconn(): extra_data (nil)
Sep  4 14:07:47 char /usr/bin/sip-proxy[6529]: DEBUG:  
[core/tcp_main.c:3307]: handle_tcp_child(): reader response= 7f7fad11ed00, 1 
from 0
Sep  4 14:07:47 char /usr/bin/sip-proxy[6529]: DEBUG:  
[core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0x558dca38bd40, 68, 2, 
0x7f7fad11ed00), fd_no=56
Sep  4 14:07:47 char /usr/bin/sip-proxy[6529]: DEBUG:  
[core/tcp_main.c:3434]: handle_tcp_child(): CONN_RELEASE  0x7f7fad11ed00 
refcnt= 1
Sep  4 14:07:52 char /usr/bin/sip-proxy[6529]: DEBUG:  
[core/io_wait.h:602]: io_watch_del(): DBG: io_watch_del (0x558dca38bd40, 68, 
-1, 0x0) fd_no=57 called
Sep  4 14:07:52 char /usr/bin/sip-proxy[6529]: DEBUG:  
[core/tcp_main.c:4196]: handle_tcpconn_ev(): sending to child, events 2001
Sep  4 14:07:52 char /usr/bin/sip-proxy[6529]: DEBUG:  
[core/tcp_main.c:3847]: send2child(): checking per-socket generic workers 
(6487/27..6507/34) [tcp:192.168.43.107:5060]
Sep  4 14:07:52 char /usr/bin/sip-proxy[6529]: DEBUG:  
[core/tcp_main.c:3875]: send2child(): selected tcp worker 0 27(6487) for 
activity on [tcp:192.168.43.107:5060], 0x7f7fad11ed00
Sep  4 14:07:52 char /usr/bin/sip-proxy[6487]: DEBUG:  
[core/tcp_read.c:1740]: handle_io(): received n=8 con=0x7f7fad11ed00, fd=12
Sep  4 14:07:52 char /usr/bin/sip-proxy[6487]: DEBUG:  
[core/tcp_read.c:198]: tcp_emit_closed_event(): TCP closed event creation 
triggered (reason: 0)
Sep  4 14:07:52 char /usr/bin/sip-proxy[6487]: DEBUG: tcpops [tcpops.c:233]: 
tcpops_handle_tcp_closed(): received TCP closed event
Sep  4 14:07:52 char /usr/bin/sip-proxy[6487]: DEBUG: tcpops [tcpops.c:207]: 
tcpops_tcp_closed_run_route(): event reason id: 0 rt: 10
Sep  4 14:07:52 char /usr/bin/sip-proxy[6487]: DEBUG:  
[core/action.c:1554]: run_actions(): null action list (rec_level=1)
Sep  4 14:07:52 char /usr/bin/sip-proxy[6487]: DEBUG:  
[core/tcp_read.c:315]: tcp_read_data(): EOF on 0x7f7fad11ed00, FD 12 
([192.168.43.107]:44522 ->
Sep  4 14:07:52 char /usr/bin/sip-proxy[6487]: DEBUG:  
[core/tcp_read.c:316]: tcp_read_data(): -> [192.168.43.107]:5060)
Sep  4 14:07:52 char /usr/bin/sip-proxy[6487]: DEBUG:  
[core/tcp_read.c:1507]: tcp_read_req(): EOF
Sep  4 14:07:52 char /usr/bin/sip-proxy[6487]: DEBUG:  
[core/tcp_read.c:1661]: release_tcpconn(): releasing con 0x7f7fad11ed00, state 
-1, fd=12, id=4 ([192.168.43.107]:44522 -> [192.168.43.107]:5060)
Sep  4 14:07:52 char /usr/bin/sip-proxy[6487]: DEBUG:  
[core/tcp_read.c:1665]: release_tcpconn(): extra_data (nil)
Sep  4 14:07:52 char /usr/bin/sip-proxy[6529]: DEBUG:  
[core/tcp_main.c:3307]: handle_tcp_child(): reader response= 7f7fad11ed00, -1 
from 0


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] event_route [tcp:closed] not executed

2018-09-04 Thread Juha Heinanen

Juha Heinanen writes:

> I loaded tcpops module but still nothing to syslog from:
> 
>   event_route [tcp:close]

I had typo in above: should be closed instead of close.

This again shows that it would be nice if it would be checked that each
event_route has a home.

-- Juha

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] dlg.end_dlg on RTP timeout

2018-09-04 Thread Daniel-Constantin Mierla

Hello,

what do you get from rtpengine on rtp timeout? An RPC call back or an
http request?

Cheers,
Daniel


On 04.09.18 12:48, Igor Olhovskiy wrote:
> Hi all!
>
> Is there any way to end dialog in Kamailio on RTP Timeout event on
> RTPEngine?
>
> Or only look at logs/redis database with external tool?
>
> Regards, Igor
>
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference -- www.kamailioworld.com
Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] dispatcher probe

2018-09-04 Thread volga629


Hello Federico,
Thank you for reply that exactly what I was looking for local route.

The following worked as expected

event_route[tm:local-request] {
   if(is_method("OPTIONS") && $hdr(User-Agent)=~"kamailio") {
   xlog("L_INFO", "Adding X-Node-ID header.\n");
   append_hf("X-Node-ID: $avp(node_id)\r\n");
   }
}


volga629

On Tue, Sep 4, 2018 at 4:00 AM, volga...@networklab.ca wrote:

Hello Mojtaba,
Probe packet is generated by kamailio him self and it not visible in 
REQINIT, at least xlog not showing.


volga629

On Tue, Sep 4, 2018 at 3:23 AM, Mojtaba  wrote:

Hi,
Sure, You could add in REQINIT route block in Kamailio.
With Regads.Mojtaba
On Tue, Sep 4, 2018 at 5:11 AM  wrote:


 Hello Everyone,
 Is possible access OPTIONS packet generated by dispatcher probe ?
 I am trying insert something like this.

 if(is_method("OPTIONS") && $hdr(User-Agent)=~"kamailio") {
 append_hf("X-Node-ID: $avp(node_id)\r\n");
 }


 volga629


 ___
 Kamailio (SER) - Users Mailing List
 sr-users@lists.kamailio.org
 https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users




--
--Mojtaba Esfandiari.S

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users



___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users



___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] event_route [tcp:closed] not executed

2018-09-04 Thread Daniel-Constantin Mierla

On 04.09.18 13:23, Juha Heinanen wrote:
> Juha Heinanen writes:
>
>> I loaded tcpops module but still nothing to syslog from:
>>
>>   event_route [tcp:close]
> I had typo in above: should be closed instead of close.
>
> This again shows that it would be nice if it would be checked that each
> event_route has a home.
>
The event_route was defined for the specific case where its name can be
anything and it is a matter of modules to execute some as they need.

The interpreter which is defined in core has no clue about what names
can be there. The modules cannot complain if they do not find some
event_route blocks that they expect to execute, because if the event
route is not found, then there should be noting executed.

Being open source, of course anything is "possible", but how to do it
and its complexity may require some consistent analysis to see if
affects the flexibility and then expecting relevant development effort
to go in each module dealing with event_route blocks.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference -- www.kamailioworld.com
Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Missing ACC record in case of canceled call forking

2018-09-04 Thread Marco Capetta


Hello,

Yes Flag 3 is set at the very beginning when we start handling the 
received INVITE message.
I checked and it is still active in both the branches of the outgoing 
INVITEs.




In the 1st case the following ACC is generated:
    id: 311
    method: INVITE
  from_tag:
    to_tag:
    callid: 121700311@X.X.X.X
  sip_code: 487
sip_reason: Request terminated
  time: 2018-09-04 11:55:24
time_hires: 1536054924.342



I missed to say in my previous email that in kamailio ACC configuration 
we have also:

  modparam("acc", "acc_prepare_always", 1)


Thanks
Marco



On 09/04/2018 11:39 AM, Daniel-Constantin Mierla wrote:

Hello,

is flag 3 set for the INVITE transaction?

In the 1st case, is the CANCEL accounted or the INVITE transaction or both?

Cheers,
Daniel


On 04.09.18 11:18, Marco Capetta wrote:

HiAll,

As additional step I tested the scenario with kamailio v5.1.5 but the
problem seems still there.

Best regards.
Marco


On 08/28/2018 03:10 PM, Marco Capetta wrote:

Hi All,

I'm facing a strange problem of missing ACC record in case of
parallel call forking.

The scenario is the following:
  - A subscriber with 1 device registered
  - B subscriber with 2 device registered (B1 and B2)

CASE 1:
  - A calls B
  - B1 and B2 start ringing
  - A hangups the call before B1 or B2 answers
Kamailio generates an ACC record.

CASE 2:
  - A calls B
  - B1 and B2 start ringing
  - B1 rejects the call sending back a 486
  - B2 is still ringing
  - A hangups the call before B2 answers
Kamailio DOESN'T generate an ACC record.



We have Kamailio v5.1.4 with TM module enabled.

ACC configuration is the following:
   modparam("acc", "early_media", 0)
   modparam("acc", "report_ack", 0)
   modparam("acc", "report_cancels", 1)
   modparam("acc", "detect_direction", 1)
   modparam("acc", "db_flag", 1)
   modparam("acc", "db_missed_flag", 2)
   modparam("acc", "failed_transaction_flag", 3)


I increased debug level of TM and ACC modules and I added some debug
lines as well.
The difference between the two calls is that, after the CANCEL sent
by A is processed by Kamailio, in CASE 1 I have the following lines:
   Aug 28 14:21:11 spce proxy[13188]: DEBUG: tm [t_hooks.c:258]:
run_trans_callbacks_internal(): DBG: trans=0x7f5a88049198, callback
type 512, id 0 entered
   Aug 28 14:21:11 spce proxy[13188]: DEBUG: acc [acc_logic.c:670]:
tmcb_func(): acc callback called for t(0x7f5a88049198) event type
512, reply code 487
   Aug 28 14:21:11 spce proxy[13188]: DEBUG: acc [acc_extra.h:63]:
free_strar_mem(): Freeing memory, type is 2, message_index 8, index i 0
   Aug 28 14:21:11 spce proxy[13188]: DEBUG: acc [acc_extra.h:63]:
free_strar_mem(): Freeing memory, type is 2, message_index 8, index i 1
   Aug 28 14:21:11 spce proxy[13188]: DEBUG: acc [acc_extra.h:63]:
free_strar_mem(): Freeing memory, type is 2, message_index 8, index i 2
   Aug 28 14:21:11 spce proxy[13188]: DEBUG: acc [acc_extra.h:63]:
free_strar_mem(): Freeing memory, type is 2, message_index 8, index i 3
   Aug 28 14:21:11 spce proxy[13188]: DEBUG: acc [acc_extra.h:63]:
free_strar_mem(): Freeing memory, type is 2, message_index 8, index i 4

Those debug lines are not printed for CASE 2.



Is there any configuration I'm missing or is it a bug?



Thank you very much for your support.
Marco


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


--
*Marco Capetta *
Operations Engineer

Sipwise GmbH  , Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Phone: +43(0)1 301 2044 
Email: mcape...@sipwise.com 
Website: www.sipwise.com 

Particulars according Austrian Companies Code paragraph 14
"Sipwise GmbH" - Europaring F15 - 2345 Brunn am Gebirge
FN:305595f, Commercial Court Vienna, ATU64002206

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Problem with reconnection to database server

2018-09-04 Thread Minh Phan

Hi List,

My Kamailio instance is disconnected from database server (Postgres) quite
often (after running for some days) and it won't manage to reconnect. Any
idea why this happens? Normally it try to reconnect when connection with
the DB is lost, desn't it? Bellow are the related log messages.

Best regards,
Minh Phan


Sep  4 11:31:20 : ERROR:  [db_query.c:235]: db_do_insert_cmd(): error
while submitting query
Sep  4 11:31:20 : ERROR: db_postgres [km_dbase.c:559]:
db_postgres_store_result(): invalid query, execution aborted
Sep  4 11:31:20 : ERROR: db_postgres [km_dbase.c:561]:
db_postgres_store_result(): driver error: PGRES_FATAL_ERROR,
Sep  4 11:31:20 : WARNING: db_postgres [km_dbase.c:609]:
db_postgres_insert(): unexpected result returned
Sep  4 11:31:20 : ERROR: topos [tps_storage.c:599]: tps_db_insert_dialog():
failed to store message
Sep  4 11:31:20 : ERROR: topos [tps_storage.c:412]: tps_storage_record():
failed to store
Sep  4 11:31:20 : WARNING: db_postgres [km_dbase.c:259]:
db_postgres_submit_query(): postgres query command failed, connection
status 1, error [no connection to the server#012]
Sep  4 11:31:20 : WARNING: db_postgres [km_dbase.c:259]:
db_postgres_submit_query(): postgres query command failed, connection
status 1, error [no connection to the server#012]
Sep  4 11:31:20 : WARNING: db_postgres [km_dbase.c:259]:
db_postgres_submit_query(): postgres query command failed, connection
status 1, error [no connection to the server#012]
Sep  4 11:31:20 : ERROR: db_postgres [km_dbase.c:267]:
db_postgres_submit_query(): 0x2b11c92b8b18 PQsendQuery Error:  Query:
select
rectime,a_callid,a_uuid,b_uuid,direction,x_via,x_vbranch,x_rr,y_rr,s_rr,x_uri,x_tag,s_method,s_cseq,a_contact,b_contact,as_contact,bs_contact,a_tag,b_tag
from topos_t where
x_vbranch='z9hG4bK66fa.3f007792.0'
Sep  4 11:31:20 : ERROR:  [db_query.c:132]: db_do_query_internal():
error while submitting query
Sep  4 11:31:20 : ERROR: topos [tps_storage.c:961]: tps_db_load_branch():
failed to query database
Sep  4 11:31:20 : WARNING: topos [tps_storage.c:400]: tps_storage_record():
no local address - do record routing for all initial requests
Sep  4 11:31:20 : WARNING: db_postgres [km_dbase.c:259]:
db_postgres_submit_query(): postgres query command failed, connection
status 1, error [no connection to the server#012]
Sep  4 11:31:20 : WARNING: db_postgres [km_dbase.c:259]:
db_postgres_submit_query(): postgres query command failed, connection
status 1, error [no connection to the server#012]
Sep  4 11:31:20 kamailio[26608]: WARNING: db_postgres [km_dbase.c:259]:
db_postgres_submit_query(): postgres query command failed, connection
status 1, error [no connection to the server#012]
Sep  4 11:31:20 : WARNING: db_postgres [km_dbase.c:259]:
db_postgres_submit_query(): postgres query command failed, connection
status 1, error [no connection to the server#012]
Sep  4 11:31:20 kamailio[26608]: WARNING: db_postgres [km_dbase.c:259]:
db_postgres_submit_query(): postgres query command failed, connection
status 1, error [no connection to the server#012]
Sep  4 11:31:20 : ERROR: db_postgres [km_dbase.c:267]:
db_postgres_submit_query(): 0x2b11c92b8b18 PQsendQuery Error:  Query:
insert into topos_d
(rectime,a_callid,a_uuid,b_uuid,a_contact,b_contact,as_contact,bs_contact,a_tag,b_tag,a_rr,b_rr,s_rr,iflags,a_uri,b_uri,r_uri,a_srcaddr,b_srcaddr,s_method,s_cseq
) values ('2018-09-04 11:31:20','1ff8d1d7606f7416-26611@192.168.70.106
','','','','','','','ae86e22a93159b5c6ac75234cdf26c1b-44e5','','','','',0,'','','','','','OPTIONS','10')
Sep  4 11:31:20 kamailio[26608]: WARNING: db_postgres [km_dbase.c:259]:
db_postgres_submit_query(): postgres query command failed, connection
status 1, error [no connection to the server#012]
Sep  4 11:31:20 : ERROR:  [db_query.c:235]: db_do_insert_cmd(): error
while submitting query
Sep  4 11:31:20 kamailio[26608]: ERROR: db_postgres [km_dbase.c:267]:
db_postgres_submit_query(): 0x2b11c92b8b18 PQsendQuery Error:  Query:
select
rectime,a_callid,a_uuid,b_uuid,direction,x_via,x_vbranch,x_rr,y_rr,s_rr,x_uri,x_tag,s_method,s_cseq,a_contact,b_contact,as_contact,bs_contact,a_tag,b_tag
from topos_t where
x_vbranch='z9hG4bK86fa.424ded00.0'
Sep  4 11:31:20 kamailio[26608]: ERROR:  [db_query.c:132]:
db_do_query_internal(): error while submitting query
Sep  4 11:31:20 : ERROR: db_postgres [km_dbase.c:559]:
db_postgres_store_result(): invalid query, execution aborted
Sep  4 11:31:20 kamailio[26608]: ERROR: topos [tps_storage.c:961]:
tps_db_load_branch(): failed to query database
Sep  4 11:31:20 : ERROR: db_postgres [km_dbase.c:561]:
db_postgres_store_result(): driver error: PGRES_FATAL_ERROR,
Sep  4 11:31:20 : WARNING: db_postgres [km_dbase.c:609]:
db_postgres_insert(): unexpected result returned
Sep  4 11:31:20 : ERROR: topos [tps_storage.c:599]: tps_db_insert_dialog():
failed to store message
Sep  4 11:31:20 : ERROR: topos [tps_storage.c:412]: tps_storage_record():
failed to store
Sep  4 11:

Re: [SR-Users] event_route [tcp:closed] not executed

2018-09-04 Thread Juha Heinanen

Daniel-Constantin Mierla writes:

> The event_route was defined for the specific case where its name can be
> anything and it is a matter of modules to execute some as they need.
> 
> The interpreter which is defined in core has no clue about what names
> can be there. The modules cannot complain if they do not find some
> event_route blocks that they expect to execute, because if the event
> route is not found, then there should be noting executed.

Well, kamailio does not start if config includes call of a function
defined in a module that is not loaded.

Similarly, modules could register their event routes at load, which
would allow the interpreter to detect unknown event routes.

It may be too late to fix this, since too many modules already exists
that define event routes.

-- Juha

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] event_route [tcp:closed] not executed

2018-09-04 Thread Daniel-Constantin Mierla

On 04.09.18 15:46, Juha Heinanen wrote:
> Daniel-Constantin Mierla writes:
>
>> The event_route was defined for the specific case where its name can be
>> anything and it is a matter of modules to execute some as they need.
>>
>> The interpreter which is defined in core has no clue about what names
>> can be there. The modules cannot complain if they do not find some
>> event_route blocks that they expect to execute, because if the event
>> route is not found, then there should be noting executed.
> Well, kamailio does not start if config includes call of a function
> defined in a module that is not loaded.
>
> Similarly, modules could register their event routes at load, which
> would allow the interpreter to detect unknown event routes.
>
> It may be too late to fix this, since too many modules already exists
> that define event routes.
>
The difference here is that event_route blocks are only defined, not
executed from other route blocks.

You can also define a route[name] that is not executed in another blocks
with route(name) and there is nothing happening, because the route block
can be executed also from inside the c code with a value that can be
built at runtime. One can also execute a route with a variable, like
route($var(name)), so there can be no enforcement when a route block
that is not executed statically to stop kamailio start up process.

You can eventually start adding to each module to rise errors if ithey
don't find the expected event_routes, but must be a modparam, because
the behaviour is not to execute event_route blocks if they are not
defined. Something like: if modparam is set and event_route blocks are
not found, rise error. Given that many modules can execute many
event_route blocks in various cases, the modparam has to allow
combinations of when to rise error based on what is expected to execute
and what is defined...

Again, with open source there are always solutions, but someone has to
invest time and find the balance between benefits, complexity and
penalties to performances (in this case would be start up time, which
might not be that critical). Personally I do not see major benefits to
invest a lot if time to update all those modules and take care of all
possible documentation just to cover mistyping cases, but if someone
whats to do it, merging such features can be considered if there is no
major negative impact and they do not change current behaviour.

Cheers,
Daniel

Cheers,
Daniel

-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference -- www.kamailioworld.com
Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Ipv6_to_ipv4

2018-09-04 Thread Karlheinz Knapp

i have tested the sample config from:
https://kb.asipto.com/kamailio:kamailio-mixed-ipv4-ipv6

i found that i can register with v4 to kamailio and to the provider

if i user ipv6 to kamailio and ipv4 to provider i can´t register.

the packet from the provider contain a via entry which is missing from
kamailio to my phone.

Someone have a solution ?
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] DMQ mem leak issues

2018-09-04 Thread Charles Chance

Hi Joel,

I have not had much time recently to find the cause of the issue with
db_mode 1, although I should have some more time over the next couple of
weeks.

Out of interest, what will you be using the database for?

Cheers,

Charles


On Fri, 24 Aug 2018 at 04:00, Joel Serrano  wrote:

> I’m planning to use DMQ + usrloc too! Thanks for sharing the solution!
>
> Do you know if It’s fixed also with db_mode=1?
>
>
> On Thu, Aug 23, 2018 at 13:53 Julien Chavanton 
> wrote:
>
>> Hi, I have glad you guys found a solution.
>>
>> Thanks for sharing it.
>>
>> Regards,
>> Julien
>>
>> On Wed, Aug 22, 2018, 21:43 Rogelio Perez  wrote:
>>
>>> Hi Julien,
>>>
>>> Thanks for checking on this.
>>> I've been working in the background with Charles on this issue and we
>>> think we've found a solution, although the cause isn't clear to me yet.
>>> Following Charles advice we changed the usrloc module parameter db_mode
>>> from 1 (Write-Through) to 2 (Write-Back) and there's been no more memory
>>> leaks incidents since then.
>>> I'll report back if we have any further updates.
>>>
>>> Best,
>>> Rogelio
>>>
>>>
>>> On Wed, Aug 22, 2018 at 11:39 AM Julien Chavanton 
>>> wrote:
>>>
 Hi Rogerio, did you have any luck digging this leak further ?

 On Wed, Aug 8, 2018 at 3:37 AM Charles Chance <
 charles.cha...@sipcentric.com> wrote:

> Hi Rogelio,
>
> I have been running master on a three-node lab (one primary, two
> secondary) for the past 24 hours or so, maintaining 2000 registrations on
> the primary, replicating to both secondaries, and memory usage has 
> remained
> constant throughout.
>
> I will leave it running for another 24 hours to be sure but in the
> meantime, you mentioned you are loading records from DB - which mode are
> you using for writing (write-through or write-back)? Do you experience the
> same symptoms if you disable the database completely on the secondary 
> nodes
> (or just one for testing) and instead, enable sync in dmq_usrloc?
>
> Cheers,
>
> Charles
>
>
> On 7 August 2018 at 16:42, Julien Chavanton 
> wrote:
>
>> I wonder if this could be introduced by a regression or if you are
>> facing a specific edge case
>>
>> I briefly looked at the commits of DMQ and DMQ_USRLOC
>> It seems there was significant work done.
>> I would give a try with 5.0.0 and then we will at least learn that
>> this is not a recent regression.
>>
>> On Mon, Aug 6, 2018 at 1:43 PM, Rogelio Perez 
>> wrote:
>>
>>> Charles, Julien, Daniel,
>>>
>>> The results are pretty much the same, the mem leak is still there
>>> and we need to restart Kamailio when it reaches certain threshold.
>>> https://www.dropbox.com/s/enxx6b7t0c8vl49/Selection_539.png?dl=0
>>>
>>> Is there anything else we can try?
>>> Will a core dump file tell us what's causing it?
>>>
>>> Thanks,
>>> Rogelio
>>>
>>> On Thu, Aug 2, 2018 at 2:57 PM Rogelio Perez 
>>> wrote:
>>>
 Thanks Charles, it's working now.
 I'm deploying to production and confirming results soon.

 Rogelio

>>>
>>>
>>> --
>>> 
>>> Rogelio Perez | engineering | telnyx 
>>> chicago: +1 312 270 8119 | dublin: +353 1 912 6119
>>>
>>>
>>> ___
>>> Kamailio (SER) - Users Mailing List
>>> sr-users@lists.kamailio.org
>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>
>>>
>>
>
>
>
> Sipcentric Ltd. Company registered in England & Wales no. 7365592. 
> Registered
> office: Faraday Wharf, Innovation Birmingham Campus, Holt Street,
> Birmingham Science Park, Birmingham B7 4BB.
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>

>>>
>>> --
>>> 
>>> Rogelio Perez | engineering | telnyx 
>>> chicago: +1 312 270 8119 | dublin: +353 1 912 6119
>>>
>>> ___
>> Kamailio (SER) - Users Mailing List
>> sr-users@lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>


-- 
*Charles Chance*
Managing Director

t. 0330 120 1200m. 07932 063 891

-- 
Sipcentric Ltd.
Company registered in England & Wales no. 
7365592. Registered
office: Faraday Wharf, Innovation 
Birmingham Campus, Holt Street, Birmingham Science Park, Birmingham B7 4BB.
___
Kamailio (SER) - User

Re: [SR-Users] DMQ mem leak issues

2018-09-04 Thread Joel Serrano

Hi Charles,

I'm trying to move _away_ from database for data replication and pass over
to DMQ as much as possible, currently I have db_mode=1 for usrloc so that
is why I asked.

If I understand correctly, on a 2 node cluster, without database for usrloc
and only using DMQ, as long as both nodes don't go down at the same time
you are good... it would be possible to restart the nodes sequentially and
not lose registration info as they would replicate to each other on
startup, right?

Do you see a need for the database (specifically talking about usrloc
replication) other than persistency if *all* nodes in the dmq cluster are
down at the same time?

Thanks,
Joel.

On Tue, Sep 4, 2018 at 11:35 AM, Charles Chance <
charles.cha...@sipcentric.com> wrote:

> Hi Joel,
>
> I have not had much time recently to find the cause of the issue with
> db_mode 1, although I should have some more time over the next couple of
> weeks.
>
> Out of interest, what will you be using the database for?
>
> Cheers,
>
> Charles
>
>
> On Fri, 24 Aug 2018 at 04:00, Joel Serrano  wrote:
>
>> I’m planning to use DMQ + usrloc too! Thanks for sharing the solution!
>>
>> Do you know if It’s fixed also with db_mode=1?
>>
>>
>> On Thu, Aug 23, 2018 at 13:53 Julien Chavanton 
>> wrote:
>>
>>> Hi, I have glad you guys found a solution.
>>>
>>> Thanks for sharing it.
>>>
>>> Regards,
>>> Julien
>>>
>>> On Wed, Aug 22, 2018, 21:43 Rogelio Perez  wrote:
>>>
 Hi Julien,

 Thanks for checking on this.
 I've been working in the background with Charles on this issue and we
 think we've found a solution, although the cause isn't clear to me yet.
 Following Charles advice we changed the usrloc module parameter db_mode
 from 1 (Write-Through) to 2 (Write-Back) and there's been no more memory
 leaks incidents since then.
 I'll report back if we have any further updates.

 Best,
 Rogelio

 On Wed, Aug 22, 2018 at 11:39 AM Julien Chavanton 
 wrote:

> Hi Rogerio, did you have any luck digging this leak further ?
>
> On Wed, Aug 8, 2018 at 3:37 AM Charles Chance <
> charles.cha...@sipcentric.com> wrote:
>
>> Hi Rogelio,
>>
>> I have been running master on a three-node lab (one primary, two
>> secondary) for the past 24 hours or so, maintaining 2000 registrations on
>> the primary, replicating to both secondaries, and memory usage has 
>> remained
>> constant throughout.
>>
>> I will leave it running for another 24 hours to be sure but in the
>> meantime, you mentioned you are loading records from DB - which mode are
>> you using for writing (write-through or write-back)? Do you experience 
>> the
>> same symptoms if you disable the database completely on the secondary 
>> nodes
>> (or just one for testing) and instead, enable sync in dmq_usrloc?
>>
>> Cheers,
>>
>> Charles
>>
>>
>> On 7 August 2018 at 16:42, Julien Chavanton 
>> wrote:
>>
>>> I wonder if this could be introduced by a regression or if you are
>>> facing a specific edge case
>>>
>>> I briefly looked at the commits of DMQ and DMQ_USRLOC
>>> It seems there was significant work done.
>>> I would give a try with 5.0.0 and then we will at least learn that
>>> this is not a recent regression.
>>>
>>> On Mon, Aug 6, 2018 at 1:43 PM, Rogelio Perez 
>>> wrote:
>>>
 Charles, Julien, Daniel,

 The results are pretty much the same, the mem leak is still there
 and we need to restart Kamailio when it reaches certain threshold.
 https://www.dropbox.com/s/enxx6b7t0c8vl49/Selection_539.png?dl=0

 Is there anything else we can try?
 Will a core dump file tell us what's causing it?

 Thanks,
 Rogelio

 On Thu, Aug 2, 2018 at 2:57 PM Rogelio Perez 
 wrote:

> Thanks Charles, it's working now.
> I'm deploying to production and confirming results soon.
>
> Rogelio
>

 --

 Rogelio Perez | engineering | telnyx 
 chicago: +1 312 270 8119 | dublin: +353 1 912 6119

 ___
 Kamailio (SER) - Users Mailing List
 sr-users@lists.kamailio.org
 https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

>>>
>>
>>
>>
>> Sipcentric Ltd. Company registered in England & Wales no. 7365592. 
>> Registered
>> office: Faraday Wharf, Innovation Birmingham Campus, Holt Street,
>> Birmingham Science Park, Birmingham B7 4BB.
>> ___
>> Kamailio (SER) - Users Mailing List
>> sr-users@lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>

Re: [SR-Users] dlg.end_dlg on RTP timeout

2018-09-04 Thread Igor Olhovskiy

As of now - just string in logs )

Regards, Igor
On Sep 4, 2018, 1:52 PM +0200, Daniel-Constantin Mierla , 
wrote:
> Hello,
> what do you get from rtpengine on rtp timeout? An RPC call back or an http 
> request?
> Cheers,
> Daniel
>
> On 04.09.18 12:48, Igor Olhovskiy wrote:
> > Hi all!
> >
> > Is there any way to end dialog in Kamailio on RTP Timeout event on 
> > RTPEngine?
> >
> > Or only look at logs/redis database with external tool?
> >
> > Regards, Igor
> >
> >
> > ___
> > Kamailio (SER) - Users Mailing List
> > sr-users@lists.kamailio.org
> > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
> --
> Daniel-Constantin Mierla -- www.asipto.com
> www.twitter.com/miconda -- www.linkedin.com/in/miconda
> Kamailio World Conference -- www.kamailioworld.com
> Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Problem with reconnection to database server

2018-09-04 Thread Henning Westerholt

Am Dienstag, 4. September 2018, 15:17:20 CEST schrieb Minh Phan:
> My Kamailio instance is disconnected from database server (Postgres) quite
> often (after running for some days) and it won't manage to reconnect. Any
> idea why this happens? Normally it try to reconnect when connection with
> the DB is lost, desn't it? Bellow are the related log messages.

Hello Minh,

yes, normally Kamailio should reconnect to the database when the connection is 
lost.

One reasons that the connection is lost could be a misbehaving firewall or 
simple network stability issues between the Kamailio and the database server.

You can try to enable the tcp_keepalive function, to help to keep the 
connection open:

3.3. tcp_keepalive (integer)   

   Enable the TCP keepalive timer and set the number of seconds the
   connection must be idle before to start sending keepalive packets.
   Defaults to zero, which disables TCP keepalive packets.

   Only supported on platforms which understand and support the
   “TCP_KEEPIDLE” socket option.

Best regards,

Henning


> Sep  4 11:31:20 : ERROR:  [db_query.c:235]: db_do_insert_cmd(): error
> while submitting query
> Sep  4 11:31:20 : ERROR: db_postgres [km_dbase.c:559]:
> db_postgres_store_result(): invalid query, execution aborted
> Sep  4 11:31:20 : ERROR: db_postgres [km_dbase.c:561]:
> db_postgres_store_result(): driver error: PGRES_FATAL_ERROR,
> Sep  4 11:31:20 : WARNING: db_postgres [km_dbase.c:609]:
> db_postgres_insert(): unexpected result returned
> Sep  4 11:31:20 : ERROR: topos [tps_storage.c:599]: tps_db_insert_dialog():
> failed to store message
> Sep  4 11:31:20 : ERROR: topos [tps_storage.c:412]: tps_storage_record():
> failed to store
> Sep  4 11:31:20 : WARNING: db_postgres [km_dbase.c:259]:
> db_postgres_submit_query(): postgres query command failed, connection
> status 1, error [no connection to the server#012]
> Sep  4 11:31:20 : WARNING: db_postgres [km_dbase.c:259]:
> db_postgres_submit_query(): postgres query command failed, connection
> status 1, error [no connection to the server#012]
> Sep  4 11:31:20 : WARNING: db_postgres [km_dbase.c:259]:
> db_postgres_submit_query(): postgres query command failed, connection
> status 1, error [no connection to the server#012]
> Sep  4 11:31:20 : ERROR: db_postgres [km_dbase.c:267]:
> db_postgres_submit_query(): 0x2b11c92b8b18 PQsendQuery Error:  Query:
> select
> rectime,a_callid,a_uuid,b_uuid,direction,x_via,x_vbranch,x_rr,y_rr,s_rr,x_ur
> i,x_tag,s_method,s_cseq,a_contact,b_contact,as_contact,bs_contact,a_tag,b_ta
> g from topos_t where
> x_vbranch='z9hG4bK66fa.3f007792.0'
> Sep  4 11:31:20 : ERROR:  [db_query.c:132]: db_do_query_internal():
> error while submitting query
> Sep  4 11:31:20 : ERROR: topos [tps_storage.c:961]: tps_db_load_branch():
> failed to query database
> Sep  4 11:31:20 : WARNING: topos [tps_storage.c:400]: tps_storage_record():
> no local address - do record routing for all initial requests
> Sep  4 11:31:20 : WARNING: db_postgres [km_dbase.c:259]:
> db_postgres_submit_query(): postgres query command failed, connection
> status 1, error [no connection to the server#012]
> Sep  4 11:31:20 : WARNING: db_postgres [km_dbase.c:259]:
> db_postgres_submit_query(): postgres query command failed, connection
> status 1, error [no connection to the server#012]
> Sep  4 11:31:20 kamailio[26608]: WARNING: db_postgres [km_dbase.c:259]:
> db_postgres_submit_query(): postgres query command failed, connection
> status 1, error [no connection to the server#012]
> Sep  4 11:31:20 : WARNING: db_postgres [km_dbase.c:259]:
> db_postgres_submit_query(): postgres query command failed, connection
> status 1, error [no connection to the server#012]
> Sep  4 11:31:20 kamailio[26608]: WARNING: db_postgres [km_dbase.c:259]:
> db_postgres_submit_query(): postgres query command failed, connection
> status 1, error [no connection to the server#012]
> Sep  4 11:31:20 : ERROR: db_postgres [km_dbase.c:267]:
> db_postgres_submit_query(): 0x2b11c92b8b18 PQsendQuery Error:  Query:
> insert into topos_d
> (rectime,a_callid,a_uuid,b_uuid,a_contact,b_contact,as_contact,bs_contact,a_
> tag,b_tag,a_rr,b_rr,s_rr,iflags,a_uri,b_uri,r_uri,a_srcaddr,b_srcaddr,s_meth
> od,s_cseq ) values ('2018-09-04
> 11:31:20','1ff8d1d7606f7416-26611@192.168.70.106
> ','','','','','','','ae86e22a93159b5c6ac75234cdf26c1b-44e5','','','','',0,'
> ','','','','','OPTIONS','10') Sep  4 11:31:20 kamailio[26608]: WARNING:
> db_postgres [km_dbase.c:259]: db_postgres_submit_query(): postgres query
> command failed, connection status 1, error [no connection to the
> server#012]
> Sep  4 11:31:20 : ERROR:  [db_query.c:235]: db_do_insert_cmd(): error
> while submitting query
> Sep  4 11:31:20 kamailio[26608]: ERROR: db_postgres [km_dbase.c:267]:
> db_postgres_submit_query(): 0x2b11c92b8b18 PQsendQuery Error:  Query:
> select
> rectime,a_callid,a_uuid,b_uuid,direction,x_via,x_vbranch,x_rr,y_rr,s_rr,x_ur
> i,x_tag,s_method,s_cseq,a_contact,b_contact

Re: [SR-Users] Kamailio v5.1.5 Released

2018-09-04 Thread Ben Hood

Hey Daniel,

Just FYI the FreeBSD maintainers have just uprev'ed port to the 5.1.5 upstream.

Cheers,

Ben


> On 22 Aug 2018, at 11:45, Daniel-Constantin Mierla  wrote:
> 
> Hello,
> 
> Kamailio SIP Server v5.1.5 stable release is out.
> 
> This is a maintenance release of the latest stable branch, 5.1, that
> includes fixes since the release of v5.1.4. There is no change to
> database schema or configuration language structure that you have to do
> on previous installations of v5.1.x. Deployments running previous v5.1.x
> versions are strongly recommended to be upgraded to v5.1.5.
> 
> For more details about version 5.1.5 (including links and guidelines to
> download the tarball or from GIT repository), visit:
> 
>  * https://www.kamailio.org/w/2018/08/kamailio-v5-1-5-released/
> 
> RPM, Debian/Ubuntu packages will be available soon as well.
> 
> Many thanks to all contributing and using Kamailio!
> 
> Cheers,
> Daniel
> 
> -- 
> Daniel-Constantin Mierla
> www.twitter.com/miconda -- www.linkedin.com/in/miconda
> Kamailio Advanced Training - www.asipto.com
> Kamailio World Conference - www.kamailioworld.com
> 
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] dlg.end_dlg on RTP timeout

2018-09-04 Thread Richard Fuchs

It does an XMLRPC callback. Currently there's two formats for it, one is 
a sems sbc teardown request (using the from-tag), the other is a generic 
"teardown" command using the call ID.


Cheers

On 2018-09-04 07:52, Daniel-Constantin Mierla wrote:


Hello,

what do you get from rtpengine on rtp timeout? An RPC call back or an 
http request?


Cheers,
Daniel


On 04.09.18 12:48, Igor Olhovskiy wrote:

Hi all!

Is there any way to end dialog in Kamailio on RTP Timeout event on 
RTPEngine?


Or only look at logs/redis database with external tool?

Regards, Igor


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


--
Daniel-Constantin Mierla --www.asipto.com
www.twitter.com/miconda  --www.linkedin.com/in/miconda
Kamailio World Conference --www.kamailioworld.com
Kamailio Advanced Training, Nov 12-14, 2018, in Berlin --www.asipto.com


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] dlg.end_dlg on RTP timeout

2018-09-04 Thread Daniel-Constantin Mierla

Looking quickly at the readme of rtpengine application and digging a bit
with google, it is something like rtpengine has to be started with

-b http(s)://myrpcserver.ip/path -x 1

and then the xmlrpc request is going to be sent to that url, having a
format like:



teardown

_CALLID_VALUE__



Is it right? If yes, then I can try to make a sample config that could
handle it using xmlops, xhttp and jsonrpcs modules.

Cheers,
Daniel


On 05.09.18 08:24, Richard Fuchs wrote:
> It does an XMLRPC callback. Currently there's two formats for it, one
> is a sems sbc teardown request (using the from-tag), the other is a
> generic "teardown" command using the call ID.
>
> Cheers
>
> On 2018-09-04 07:52, Daniel-Constantin Mierla wrote:
>>
>> Hello,
>>
>> what do you get from rtpengine on rtp timeout? An RPC call back or an
>> http request?
>>
>> Cheers,
>> Daniel
>>
>>
>> On 04.09.18 12:48, Igor Olhovskiy wrote:
>>> Hi all!
>>>
>>> Is there any way to end dialog in Kamailio on RTP Timeout event on
>>> RTPEngine?
>>>
>>> Or only look at logs/redis database with external tool?
>>>
>>> Regards, Igor
>>>
>>>
>>> ___
>>> Kamailio (SER) - Users Mailing List
>>> sr-users@lists.kamailio.org
>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>
>> -- 
>> Daniel-Constantin Mierla -- www.asipto.com
>> www.twitter.com/miconda -- www.linkedin.com/in/miconda
>> Kamailio World Conference -- www.kamailioworld.com
>> Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com
>>
>>
>> ___
>> Kamailio (SER) - Users Mailing List
>> sr-users@lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference -- www.kamailioworld.com
Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] dlg.end_dlg on RTP timeout

2018-09-04 Thread Richard Fuchs


Yup that's exactly right.

It would be fairly simple to implement an additional XMLRPC format if 
there's a particular one that's more friendly towards Kamailio.


Cheers

On 2018-09-05 02:42, Daniel-Constantin Mierla wrote:


Looking quickly at the readme of rtpengine application and digging a 
bit with google, it is something like rtpengine has to be started with


-b http(s)://myrpcserver.ip/path -x 1

and then the xmlrpc request is going to be sent to that url, having a 
format like:




teardown

_CALLID_VALUE__



Is it right? If yes, then I can try to make a sample config that could 
handle it using xmlops, xhttp and jsonrpcs modules.


Cheers,
Daniel


On 05.09.18 08:24, Richard Fuchs wrote:
It does an XMLRPC callback. Currently there's two formats for it, one 
is a sems sbc teardown request (using the from-tag), the other is a 
generic "teardown" command using the call ID.


Cheers

On 2018-09-04 07:52, Daniel-Constantin Mierla wrote:


Hello,

what do you get from rtpengine on rtp timeout? An RPC call back or 
an http request?


Cheers,
Daniel


On 04.09.18 12:48, Igor Olhovskiy wrote:

Hi all!

Is there any way to end dialog in Kamailio on RTP Timeout event on 
RTPEngine?


Or only look at logs/redis database with external tool?

Regards, Igor


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


--
Daniel-Constantin Mierla --www.asipto.com
www.twitter.com/miconda  --www.linkedin.com/in/miconda
Kamailio World Conference --www.kamailioworld.com
Kamailio Advanced Training, Nov 12-14, 2018, in Berlin --www.asipto.com


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users



___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


--
Daniel-Constantin Mierla --www.asipto.com
www.twitter.com/miconda  --www.linkedin.com/in/miconda
Kamailio World Conference --www.kamailioworld.com
Kamailio Advanced Training, Nov 12-14, 2018, in Berlin --www.asipto.com
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] dispatcher probe

Re: [SR-Users] dispatcher probe

Re: [SR-Users] Can't connect to local MySQL server (13 "Permission denied")

Re: [SR-Users] Can't connect to local MySQL server (13 "Permission denied")

Re: [SR-Users] Can't connect to local MySQL server (13 "Permission denied")

[SR-Users] event_route [tcp:closed] not executed

[SR-Users] Missing ACC record in case of canceled call forking

Re: [SR-Users] event_route [tcp:closed] not executed

[SR-Users] TOPOH module im REGISTER method.

Re: [SR-Users] Missing ACC record in case of canceled call forking

Re: [SR-Users] event_route [tcp:closed] not executed

Re: [SR-Users] event_route [tcp:closed] not executed

Re: [SR-Users] event_route [tcp:closed] not executed

[SR-Users] dlg.end_dlg on RTP timeout

Re: [SR-Users] event_route [tcp:closed] not executed

Re: [SR-Users] dlg.end_dlg on RTP timeout

Re: [SR-Users] event_route [tcp:closed] not executed

Re: [SR-Users] event_route [tcp:closed] not executed

Re: [SR-Users] dlg.end_dlg on RTP timeout

Re: [SR-Users] dispatcher probe

Re: [SR-Users] event_route [tcp:closed] not executed

Re: [SR-Users] Missing ACC record in case of canceled call forking

[SR-Users] Problem with reconnection to database server

Re: [SR-Users] event_route [tcp:closed] not executed

Re: [SR-Users] event_route [tcp:closed] not executed

[SR-Users] Ipv6_to_ipv4

Re: [SR-Users] DMQ mem leak issues

Re: [SR-Users] DMQ mem leak issues

Re: [SR-Users] dlg.end_dlg on RTP timeout

Re: [SR-Users] Problem with reconnection to database server

Re: [SR-Users] Kamailio v5.1.5 Released

Re: [SR-Users] dlg.end_dlg on RTP timeout

Re: [SR-Users] dlg.end_dlg on RTP timeout

Re: [SR-Users] dlg.end_dlg on RTP timeout

34 matches

Site Navigation

Mail list logo

Footer information