from:"Hamid Hashmi"

Re: [SR-Users] kamailio-5.2.0 Crash - udp_send failed

2020-12-07 Thread Hamid Hashmi

00\000\000\000\000\006\000\000\000\000\000\000\000\250u\302\226\255\177\000\000\266\210\241\226\255\177",
 '\000' , 
"\341o%\374\177\000\000\060=\362\225\255\177\000\000\020\342o%\374\177\000\000\370\001\363\225\255\177\000\000\070\365\330\003\000\000\000\000\000\342o%\374\177\000\000\350*Ö"...
option_index = 0
long_options = {{name = 0x7e424f "help", has_arg = 0, flag = 0x0, val = 
104}, {name = 0x7df854 "version", has_arg = 0, flag = 0x0, val = 118}, {name = 
0x7e4254 "alias", has_arg = 1,
flag = 0x0, val = 1024}, {name = 0x7e425a "subst", has_arg = 1, 
flag = 0x0, val = 1025}, {name = 0x7e4260 "substdef", has_arg = 1, flag = 0x0, 
val = 1026}, {
name = 0x7e4269 "substdefs", has_arg = 1, flag = 0x0, val = 1027}, 
{name = 0x7e4273 "server-id", has_arg = 1, flag = 0x0, val = 1028}, {name = 
0x7e427d "loadmodule", has_arg = 1,
flag = 0x0, val = 1029}, {name = 0x7e4288 "modparam", has_arg = 1, 
flag = 0x0, val = 1030}, {name = 0x7e4291 "log-engine", has_arg = 1, flag = 
0x0, val = 1031}, {
name = 0x7e429c "debug", has_arg = 1, flag = 0x0, val = 1032}, 
{name = 0x0, has_arg = 0, flag = 0x0, val = 0}}
__FUNCTION__ = "main"
(gdb)

I observed that service crash on Signal 11 and when service starts again it 
immediately crashes on Sig 6. After that service remains up for some time. 
Moreover, there are many following errors of udp_send_failed and tcp_read error.


#0  0x7f668aa94013 in recvfrom () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#1  0x006638d0 in udp_rcv_loop () at core/udp_server.c:460
len = 638
buf = "SUBSCRIBE tel:+923492324215 SIP/2.0\r\nFrom: 
;tag=2869510412\r\nTo: \r\nCSeq: 
722026762 SUBSCRIBE\r\nCall-ID: 2869510410_3596082716@10.100.217.241\r\nVia: 
SIP/2.0/UDP 10.100"...
tmp = 0xdf831260 
from = 0x7f666ac86e78
fromlen = 16

and


#0  0x7f668aa94013 in recvfrom () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#1  0x006638d0 in udp_rcv_loop () at core/udp_server.c:460
len = 952
buf = "REGISTER sip:ims.mnc006.mcc410.3gppnetwork.org SIP/2.0\r\nVia: 
SIP/2.0/UDP 10.100.213.50;rport;branch=z9hG4bKL60mek0i6jXu6V\r\nFrom: 
;tag=jYbVBQiAfL1"...
tmp = 0xdf831260 
from = 0x7f666ac86e78
fromlen = 16
ri = {src_ip = {af = 2, len = 4, u = {addrl = {140072621270026, 
140723275665552}, addr32 = {852845578, 32613, 2967179408, 32764}, addr16 = 
{25610, 13013, 32613,
0, 37008, 45275, 32764, 0}, addr = 
"\nd\325\062e\177\000\000\220\220۰\374\177\000"}}, dst_ip = {af = 2, len = 4, u 
= {addrl = {3839926538, 0},
  addr32 = {3839926538, 0, 0, 0}, addr16 = {41226, 58592, 0, 0, 0, 
0, 0, 0}, addr = "\n\241\340\344", '\000' }}, src_port = 5060,
  dst_port = 5060, proto_reserved1 = 0, proto_reserved2 = 0, src_su = 
{s = {sa_family = 2, sa_data = 
"\023\304\nd\325\062\000\000\000\000\000\000\000"}, sin = {
  sin_family = 2, sin_port = 50195, sin_addr = {s_addr = 
852845578}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {sin6_family = 
2, sin6_port = 50195,
  sin6_flowinfo = 852845578, sin6_addr = {__in6_u = {__u6_addr8 = 
'\000' , __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 
= {0, 0, 0,
0}}}, sin6_scope_id = 0}}, bind_address = 0x7f666aa23d78, 
proto = 1 '\001'}
evp = {data = 0x0, rcv = 0x0, dst = 0x0}
printbuf = "P\221۰\374\177\000\000\005\364<\337e\177\000\000 
\221۰\374\177\000\000\265˧\337e\177\000\000\340\223۰\374\177\000\000L\221۰\374\177\000\000\340\223۰\004\000\000\000\360\005|\000\016\000\000\000n\365\023o\016\000\000\000\177$\000\000\000\000\000\000P\221۰\374\177\000\000(6\373\337e\177\000\000`\211A\000\000\000\000\000`\227۰\374\177",
 '\000' , "\020\222۰\374\177\000\000\035\261]", '\000' 
, 
"\300\022\262\000\000\000\000\000I/e\025\000\000\000\000`\211A\000\000\000\000\000`\227۰\374\177",
 '\000' , "\222"...
i = -537187496
j = 32613
l = 32613
__FUNCTION__ = "udp_rcv_loop"
#2  0x00424c4c in main_loop () at main.c:1628

This VM PCSCF node is created on OpenStack.


Regards

Hamid R. Hashmi



From: Daniel-Constantin Mierla 
Sent: Monday, December 7, 2020 5:53 PM
To: Kamailio (SER) - Users Mailing List ; Hamid 
Hashmi ; Henning Westerholt 
Subject: Re: [SR-Users] kamailio-5.2.0 Crash - udp_send failed


Hello,


get also the output of "bt full" from gdb.


I see you use ims moudules, they are known to have some limitations for various 
settings. Is this something that you can reproduce, o

Re: [SR-Users] kamailio-5.2.0 Crash - udp_send failed

2020-12-06 Thread Hamid Hashmi

Hello

I have updated Kamailio from 5.2.0 to 5.4.2 but the service is still crashing 
with sig 11 and sig 6. Please find the attached 'bt full' traces.

Sig 11:

Core was generated by `/usr/local/sbin/kamailio -f 
/usr/local/etc/kamailio_pcscf/kamailio.cfg -P /var/'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x006a16fc in timer_list_expire (t=1339518316, h=0x7facee484fd0, 
slow_l=0x7facee488208, slow_mark=7936) at core/timer.c:846
846 _timer_rm_list(tl); /* detach */
(gdb) bt
#0  0x006a16fc in timer_list_expire (t=1339518316, h=0x7facee484fd0, 
slow_l=0x7facee488208, slow_mark=7936) at core/timer.c:846
#1  0x006a1c19 in timer_handler () at core/timer.c:922
#2  0x006a20ba in timer_main () at core/timer.c:961
#3  0x0042ac0a in main_loop () at main.c:1753
#4  0x0043400c in main (argc=13, argv=0x7ffc256fe358) at main.c:2856

Sig 6:

Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/local/sbin/kamailio -f 
/usr/local/etc/kamailio_pcscf/kamailio.cfg -P /var/'.
Program terminated with signal SIGABRT, Aborted.
#0  0x7fad95f56c37 in raise () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0  0x7fad95f56c37 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7fad95f5a028 in abort () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x0041e39d in sig_alarm_abort (signo=14) at main.c:687
#3  
#4  0x7fad960183c7 in syscall () from /lib/x86_64-linux-gnu/libc.so.6
#5  0x7fad6f5c024b in futex_get (lock=0x7facee70baa0) at 
../../core/mem/../futexlock.h:121
#6  0x7fad6f5c2167 in get_peer_by_fqdn (fqdn=0x7faceeb377b0) at 
peermanager.c:240
#7  0x7fad6f5e6c31 in get_first_connected_route 
(cdp_session=0x7faceeb37768, r=0x7facee70a220, app_id=16777236, 
vendor_id=10415) at routing.c:110
#8  0x7fad6f5ea8b2 in get_routing_peer (cdp_session=0x7faceeb37768, 
m=0x7facef617fb0) at routing.c:272
#9  0x7fad6f5ac72d in AAASendMessage (message=0x7facef617fb0, 
callback_f=0x0, callback_param=0x0) at diameter_comm.c:137
#10 0x7fad6ef05dbb in rx_send_str (rx_session_id=0x7facf0849d50) at 
rx_str.c:157
#11 0x7fad6eeb25c4 in callback_dialog (dlg=0x7facf0036d70, type=8192, 
params=0x7fad72b2a1c0 ) at ims_qos_mod.c:453
#12 0x7fad728973af in run_dlg_callbacks (type=8192, dlg=0x7facf0036d70, 
req=0x0, rpl=0x0, dir=0, dlg_data=0x0) at dlg_cb.c:274
#13 0x7fad728d5315 in destroy_dlg (dlg=0x7facf0036d70) at dlg_hash.c:219
#14 0x7fad728d5b1b in destroy_dlg_table () at dlg_hash.c:291
#15 0x7fad7290b71e in mod_destroy () at ims_dialog.c:627
#16 0x00616ae1 in destroy_modules () at core/sr_module.c:746
#17 0x0041ce17 in cleanup (show_status=1) at main.c:563
#18 0x0041e6ef in shutdown_children (sig=15, show_status=1) at 
main.c:706
#19 0x00421755 in handle_sigs () at main.c:806
#20 0x0042bc85 in main_loop () at main.c:1817
#21 0x0043400c in main (argc=13, argv=0x7ffc256fe358) at main.c:2856

PS: I am using ubuntu 14.04.


Regards

Hamid R. Hashmi


From: Henning Westerholt 
Sent: Saturday, September 26, 2020 12:04 PM
To: Kamailio (SER) - Users Mailing List 
Cc: Hamid Hashmi 
Subject: Re: kamailio-5.2.0 Crash - udp_send failed

Hello,

you are using a old and non released dev version of kamailio. These are meant 
only for development purposes.

Please update to a proper version (like the latest one based on 5.3 or 5.4 
branch.

Then try to reproduce the bug again and report on the list or by creating an 
issue.

Cheers,

Henning


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


From: sr-users  on behalf of Hamid Hashmi 

Sent: Friday, September 25, 2020 9:28:07 PM
To: sr-users@lists.kamailio.org 
Subject: [SR-Users] kamailio-5.2.0 Crash - udp_send failed

I am using "kamailio 5.2.0-dev6 (x86_64/linux) 48ed62-dirty" what could be the 
reason of the crash

its usually crash with the following logs


Sep 25 16:58:41 pcscf [Proxy-CSCF][20771]: ERROR:  
[core/udp_server.c:596]: udp_send(): 
sendto(sock,0x7f36eee8c560,418,0,10.100.227.202:5060,16): Invalid argument(22)
Sep 25 16:58:41 pcscf [Proxy-CSCF][20771]: CRITICAL:  
[core/udp_server.c:601]: udp_send(): invalid sendtoparameters#012one possible 
reason is the server is bound to localhost and#012attempts to send to the net
Sep 25 16:58:41 pcscf [Proxy-CSCF][20771]: ERROR: tm 
[../../core/forward.h:219]: msg_send_buffer(): udp_send failed
Sep 25 16:58:41 pcscf [Proxy-CSCF][20771]: WARNING: tm [t_reply.c:1581]: 
t_retransmit_reply(): send pr buffer failed
Sep 25 16:58:41 pcscf [Proxy-CSCF][20756]: ERROR:  
[core/udp_server.c:596]: udp_send(): 
sendto(sock,0x7f36ef8eb948,358,0,10.100.177.91:5060,16): Invalid argument(22)
Sep 25 16:58:41 pcscf [Proxy-CSCF][20756]: CRITICAL:  
[core/udp_server.c:601]: udp

[SR-Users] [Mod: CDP] TCP Zero Window Error

2020-11-26 Thread Hamid Hashmi

Dear Users

I have been facing a diameter peer disconnection issue between I-CSCF and HSS. 
after taking traces on both sides, I saw a lot of TCP Zero Window packets from 
HSS towards I-CSCF and after that HSS disconnects with the following errors in 
the log.

Nov 26 20:30:25 PROD-HSS-STANDBY [HSS][16401]: ERROR: cdp 
[peerstatemachine.c:157]: sm_process(): sm_process(): In state Closed invalid 
event Timeout
Nov 26 20:31:25 PROD-HSS-STANDBY [HSS][16401]: ERROR: cdp 
[peerstatemachine.c:157]: sm_process(): sm_process(): In state Closed invalid 
event Timeout
Nov 26 20:32:25 PROD-HSS-STANDBY [HSS][16401]: ERROR: cdp 
[peerstatemachine.c:157]: sm_process(): sm_process(): In state Closed invalid 
event Timeout
Nov 26 20:33:04 PROD-HSS-STANDBY systemd[1]: Stopping LSB: Start the Kamailio 
SIP proxy server...
Nov 26 20:33:04 PROD-HSS-STANDBY kamailio_hss[18098]: Stopping Kamailio SIP 
Server: kamailio_hss:.
Nov 26 20:33:04 PROD-HSS-STANDBY systemd[1]: kamailio_hss.service: Succeeded.
Nov 26 20:33:04 PROD-HSS-STANDBY systemd[1]: Stopped LSB: Start the Kamailio 
SIP proxy server.
Nov 26 20:33:04 PROD-HSS-STANDBY [HSS][16274]: CRITICAL: cdp 
[diameter_peer.c:423]: diameter_peer_destroy(): destroy_diameter_peer(): Bye 
Bye from C Diameter Peer test
Nov 26 20:33:07 PROD-HSS-STANDBY systemd[1]: Starting LSB: Start the Kamailio 
SIP proxy server...
Nov 26 20:33:07 PROD-HSS-STANDBY kamailio_hss[18138]: Starting Kamailio SIP 
Server: kamailio_hss:loading modules under config path: 
/usr/local/lib64/kamailio/modules/:/usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/:/usr/local/lib/kamailio/modules/
Nov 26 20:33:07 PROD-HSS-STANDBY kamailio_hss[18138]: Listening on
Nov 26 20:33:07 PROD-HSS-STANDBY kamailio_hss[18138]:  udp: 
10.161.224.81 [10.161.224.81]:8080
Nov 26 20:33:07 PROD-HSS-STANDBY kamailio_hss[18138]:  tcp: 
127.0.0.1 [127.0.0.1]:5090
Nov 26 20:33:07 PROD-HSS-STANDBY kamailio_hss[18138]:  tcp: 
10.161.224.81 [10.161.224.81]:8080
Nov 26 20:33:07 PROD-HSS-STANDBY kamailio_hss[18138]: Aliases:
Nov 26 20:33:07 PROD-HSS-STANDBY [HSS][18155]: WARNING: sl 
[../../modules/tm/tm_load.h:149]: load_tm_api(): Cannot import load_tm function 
from tm module
Nov 26 20:33:07 PROD-HSS-STANDBY [HSS][18155]: WARNING: sl 
[../../modules/tm/tm_load.h:149]: load_tm_api(): Cannot import load_tm function 
from tm module
Nov 26 20:33:07 PROD-HSS-STANDBY [HSS][18281]: WARNING: cdp [tcp_accept.c:120]: 
create_socket(): create_socket(): Trying to open/bind/listen on 10.161.224.81 
port 3868
Nov 26 20:33:07 PROD-HSS-STANDBY [HSS][18281]: WARNING: cdp [tcp_accept.c:145]: 
create_socket(): create_socket(): Successful socket open/bind/listen on 
10.161.224.81 port 3868
Nov 26 20:33:07 PROD-HSS-STANDBY kamailio_hss[18138]: .
Nov 26 20:33:07 PROD-HSS-STANDBY systemd[1]: Started LSB: Start the Kamailio 
SIP proxy server.
Nov 26 20:38:44 PROD-HSS-STANDBY [HSS][18282]: WARNING: cdp 
[peermanager.c:310]: peer_timer(): Inactivity on peer 
[icscfcdp2.ims.mnc006.mcc410.3gppnetwork.org] and no DWA, Closing peer...
Nov 26 20:39:01 PROD-HSS-STANDBY systemd[1]: Starting Clean php session files...
Nov 26 20:39:01 PROD-HSS-STANDBY systemd[1]: phpsessionclean.service: Succeeded.
Nov 26 20:39:01 PROD-HSS-STANDBY systemd[1]: Started Clean php session files.
Nov 26 20:39:20 PROD-HSS-STANDBY [HSS][18282]: ERROR: cdp 
[peerstatemachine.c:157]: sm_process(): sm_process(): In state Closed invalid 
event Timeout


I am using the following Kamailio version

Distributor ID: Debian
Description:Debian GNU/Linux 10 (buster)
Release:10
Codename:   buster

Version: kamailio 5.2.8 (x86_64/linux) 5a7f5b
Default config: /usr/local/etc/kamailio/kamailio.cfg
Default paths to modules: /usr/local/lib64/kamailio/modules
Compile 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, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, 
FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, 
USE_DST_BLACKLIST, HAVE_RESOLV_RES
MAX_RECV_BUFFER_SIZE=262144
MAX_URI_SIZE=1024
BUF_SIZE=65535
DEFAULT PKG_SIZE=8MB
DEFAULT SHM_SIZE=64MB
ADAPTIVE_WAIT_LOOPS=1024
TCP poll methods: poll, epoll_lt, epoll_et, sigio_rt, select
Source code revision ID: 5a7f5b
Compiled with: gcc 8.3.0
Compiled on: 04:34:39 Nov 19 2020

How I can resolve TCP Zero Window Error? I have already tried increasing CDP 
worker threads, TCP read and write buffers etc.



Regards

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

[SR-Users] How to increase private & shared memory in kamailio Container?

2020-10-16 Thread Hamid Hashmi

Dear Users

How can I increase private memory in the Kamailio container?

the service was started with the following command

docker run -d --restart unless-stopped --network host -v 
/root/volumes/scscf/:/etc/kamailio --name scscf -e IP=10.161.224.90 -e 
INT_IP=10.161.224.90 10.161.224.196:5000/kamailio-ngvoice

PS: I don't have a docker file to build the image again.

Regards

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

[SR-Users] kamailio-5.2.0 Crash - udp_send failed

2020-09-25 Thread Hamid Hashmi

I am using "kamailio 5.2.0-dev6 (x86_64/linux) 48ed62-dirty" what could be the 
reason of the crash

its usually crash with the following logs


Sep 25 16:58:41 pcscf [Proxy-CSCF][20771]: ERROR:  
[core/udp_server.c:596]: udp_send(): 
sendto(sock,0x7f36eee8c560,418,0,10.100.227.202:5060,16): Invalid argument(22)
Sep 25 16:58:41 pcscf [Proxy-CSCF][20771]: CRITICAL:  
[core/udp_server.c:601]: udp_send(): invalid sendtoparameters#012one possible 
reason is the server is bound to localhost and#012attempts to send to the net
Sep 25 16:58:41 pcscf [Proxy-CSCF][20771]: ERROR: tm 
[../../core/forward.h:219]: msg_send_buffer(): udp_send failed
Sep 25 16:58:41 pcscf [Proxy-CSCF][20771]: WARNING: tm [t_reply.c:1581]: 
t_retransmit_reply(): send pr buffer failed
Sep 25 16:58:41 pcscf [Proxy-CSCF][20756]: ERROR:  
[core/udp_server.c:596]: udp_send(): 
sendto(sock,0x7f36ef8eb948,358,0,10.100.177.91:5060,16): Invalid argument(22)
Sep 25 16:58:41 pcscf [Proxy-CSCF][20756]: CRITICAL:  
[core/udp_server.c:601]: udp_send(): invalid sendtoparameters#012one possible 
reason is the server is bound to localhost and#012attempts to send to the net
Sep 25 16:58:41 pcscf [Proxy-CSCF][20756]: ERROR: sl 
[../../core/forward.h:219]: msg_send_buffer(): udp_send failed
Sep 25 16:58:41 pcscf [Proxy-CSCF][20744]: ERROR:  
[core/udp_server.c:596]: udp_send(): 
sendto(sock,0x7f36ef8b4a80,358,0,10.100.72.230:5060,16): Invalid argument(22)
Sep 25 16:58:41 pcscf [Proxy-CSCF][20744]: CRITICAL:  
[core/udp_server.c:601]: udp_send(): invalid sendtoparameters#012one possible 
reason is the server is bound to localhost and#012attempts to send to the net
Sep 25 16:58:41 pcscf [Proxy-CSCF][20744]: ERROR: sl 
[../../core/forward.h:219]: msg_send_buffer(): udp_send failed
Sep 25 16:58:41 pcscf [Proxy-CSCF][20783]: ERROR:  
[core/udp_server.c:596]: udp_send(): 
sendto(sock,0x7f36ef8ac740,416,0,10.100.72.230:5060,16): Invalid argument(22)
Sep 25 16:58:41 pcscf [Proxy-CSCF][20783]: CRITICAL:  
[core/udp_server.c:601]: udp_send(): invalid sendtoparameters#012one possible 
reason is the server is bound to localhost and#012attempts to send to the net
Sep 25 16:58:41 pcscf [Proxy-CSCF][20783]: ERROR: tm 
[../../core/forward.h:219]: msg_send_buffer(): udp_send failed
Sep 25 16:58:41 pcscf [Proxy-CSCF][20752]: ERROR:  
[core/udp_server.c:596]: udp_send(): 
sendto(sock,0x7f36ef8b5098,356,0,10.100.56.38:5060,16): Invalid argument(22)
Sep 25 16:58:41 pcscf [Proxy-CSCF][20805]: ERROR:  
[core/udp_server.c:596]: udp_send(): 
sendto(sock,0x7f36ef8e8f18,416,0,10.100.177.91:5060,16): Invalid argument(22)
Sep 25 16:58:41 pcscf [Proxy-CSCF][20805]: CRITICAL:  
[core/udp_server.c:601]: udp_send(): invalid sendtoparameters#012one possible 
reason is the server is bound to localhost and#012attempts to send to the net
Sep 25 16:58:41 pcscf [Proxy-CSCF][20805]: ERROR: tm 
[../../core/forward.h:219]: msg_send_buffer(): udp_send failed
Sep 25 16:58:41 pcscf [Proxy-CSCF][20752]: CRITICAL:  
[core/udp_server.c:601]: udp_send(): invalid sendtoparameters#012one possible 
reason is the server is bound to localhost and#012attempts to send to the net
Sep 25 16:58:41 pcscf [Proxy-CSCF][20752]: ERROR: sl 
[../../core/forward.h:219]: msg_send_buffer(): udp_send failed
Sep 25 16:58:41 pcscf [Proxy-CSCF][20777]: ERROR:

[SR-Users] SRVCC Support

2020-09-23 Thread Hamid Hashmi

Do Module RTPENGINE Supports 'Replaces' header (RFC 3891), if yes then how to 
use this feature if no then will module RTPEngine will have support for 
'Replaces' in the near future? I have been using Freeswitch for this 
functionality but facing many difficulties in it.


Regards

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

[SR-Users] Some Functions not defined in Documentation of Module ims_registrar_pcscf

2020-07-08 Thread Hamid Hashmi

I have been using a sample code of 
PCSCF,
 where a function "pcscf_assert_identity" is used but it's not defined in 
module ims_registrar_pcscf documentation. Can you please explain its 
functionality. The same way other functions are not defined in the 
documentation.

pcscf_assert_called_identity
reginfo_handle_notify
pcscf_unregister


Regards

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

[SR-Users] How S-CSCF route SIP INVITEs as per iFC ?

2020-05-08 Thread Hamid Hashmi

I have added an Application Server in iFC and try to route one user to that 
Application server for testing But INVITE to that subscriber following the 
default iFC. I am using ng-voice HSS Server.

I have been trying to differentiate between iFCs for two different subscribers 
and unable to find the store location of SAA xml on S-CSCF and I am Unable to 
find xml file of required subscribers in wireshark traces as well because it 
says in SAR that USER_DATA_ALREADY_EXISTS and SAA didn't contain any XML file 
for that specific users.

Furthermore if you can describe SIP INVITEs routing mechanism of S-CSCF, on 
which params or SIP Headers S-CSCF route INVITEs to Application Servers 
according to iFC ?



Regards

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

[SR-Users] opensource VoLTE/IMS Clients like IMSDroid

2020-01-06 Thread Hamid Hashmi

Dear Users

Can you please name some of VoLTE/IMS Clients (Like IMSDroid for Android) for 
Windows/Linux/MAC to test IMS Network. IMSdroid available clients on the 
internet are not working with android v8,9 and 10.  or if someone can guide me 
to create a working APK from IMSDroid available code on 
Github.

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

Re: [SR-Users] ims_ipsec_pcscf mandatory for ims_registrar_pcscf ?

2020-01-06 Thread Hamid Hashmi

Thanks, Henning

What if someone doesn't need ims_ipsec_pcscf. Isn't there any option to use 
ims_registrar_pcscf without ims_ipsec_pcacf?


Regards

Hamid R. Hashmi


From: Henning Westerholt 
Sent: Sunday, January 5, 2020 10:43 PM
To: Kamailio (SER) - Users Mailing List 
Cc: Hamid Hashmi 
Subject: RE: ims_ipsec_pcscf mandatory for ims_registrar_pcscf ?


Hello Hamid,



the documentation is probably outdated in this regards.



Please open an issue on our tracker about it, or even better – create a pull 
request that fixes the documentation.



Cheers,



Henning



--

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

Kamailio services – https://gilawa.com<https://gilawa.com/>



From: sr-users  On Behalf Of Hamid Hashmi
Sent: Friday, January 3, 2020 10:19 AM
To: sr-users@lists.kamailio.org
Subject: [SR-Users] ims_ipsec_pcscf mandatory for ims_registrar_pcscf ?



According to Module documentation ims_ipsec_pcscf is not mandatory



[cid:image001.png@01D5C3F7.F9355CA0]



but mod: ims_registrar_pcscf is giving error on ims_ipsec_pcscf.



Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: DEBUG: ims_registrar_pcscf 
[ims_registrar_pcscf_mod.c:253]: mod_init(): Successfully bound to TM module

Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: DEBUG:  
[core/sr_module.c:632]: find_mod_export_record(): found export of 
 in module ims_usrloc_pcscf 
[/opt/lib64/kamailio/modules/ims_usrloc_pcscf.so]

Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: DEBUG: ims_registrar_pcscf 
[ims_registrar_pcscf_mod.c:264]: mod_init(): Successfully bound to PCSCF Usrloc 
module

Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: DEBUG:  
[core/sr_module.c:638]: find_mod_export_record(): export of 
 not found (flags 0)

Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: ERROR: ims_registrar_pcscf 
[ims_registrar_pcscf_mod.c:268]: mod_init(): can't bind ims_ipsec_pcscf

Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: ERROR:  
[core/sr_module.c:849]: init_mod(): Error while initializing module 
ims_registrar_pcscf (/opt/lib64/kamailio/modules/ims_registrar_pcscf.so)

Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: DEBUG: cdp_avp 
[cdp_avp_mod.c:225]: cdp_avp_destroy(): Destroying module cdp_avp

Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: WARNING:  
[core/mem/q_malloc.c:487]: qm_free(): WARNING: free(0) called from cdp_avp: 
cdp_avp_mod.c: cdp_avp_destroy(226)

Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: INFO: cdp [cdp_mod.c:255]: 
cdp_exit(): CDiameterPeer child stopping ...

Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: INFO: cdp [cdp_mod.c:257]: 
cdp_exit(): ... CDiameterPeer child stopped

Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: DEBUG: tcpops [tcpops_mod.c:156]: 
mod_destroy(): TCP keepalive module unloaded.

Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: DEBUG: tm [t_funcs.c:84]: 
tm_shutdown(): start

Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: DEBUG: tm [t_funcs.c:87]: 
tm_shutdown(): emptying hash table

Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: DEBUG: tm [t_funcs.c:89]: 
tm_shutdown(): removing semaphores

Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: DEBUG: tm [t_funcs.c:91]: 
tm_shutdown(): destroying tmcb lists

Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: DEBUG: tm [t_funcs.c:94]: 
tm_shutdown(): done

Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: INFO:  
[core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized

Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: DEBUG:  
[core/mem/shm.c:288]: shm_destroy_manager(): destroying memory manager: q_malloc

Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: DEBUG:  
[core/mem/q_malloc.c:1185]: qm_shm_lock_destroy(): destroying the shared memory 
lock

Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: DEBUG:  [core/mem/pkg.c:97]: 
pkg_destroy_manager(): destroying memory manager: q_malloc



There is no option to use ims_registrar_pcscf without ims_ipsec_pcscf.

[cid:image002.png@01D5C3F7.F9355CA0]



Regards

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

[SR-Users] ims_ipsec_pcscf mandatory for ims_registrar_pcscf ?

2020-01-03 Thread Hamid Hashmi

According to Module documentation ims_ipsec_pcscf is not mandatory

[cid:9c92ff73-4978-4837-b541-a38e15525140]

but mod: ims_registrar_pcscf is giving error on ims_ipsec_pcscf.


Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: DEBUG: ims_registrar_pcscf 
[ims_registrar_pcscf_mod.c:253]: mod_init(): Successfully bound to TM module
Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: DEBUG:  
[core/sr_module.c:632]: find_mod_export_record(): found export of 
 in module ims_usrloc_pcscf 
[/opt/lib64/kamailio/modules/ims_usrloc_pcscf.so]
Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: DEBUG: ims_registrar_pcscf 
[ims_registrar_pcscf_mod.c:264]: mod_init(): Successfully bound to PCSCF Usrloc 
module
Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: DEBUG:  
[core/sr_module.c:638]: find_mod_export_record(): export of 
 not found (flags 0)
Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: ERROR: ims_registrar_pcscf 
[ims_registrar_pcscf_mod.c:268]: mod_init(): can't bind ims_ipsec_pcscf
Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: ERROR:  
[core/sr_module.c:849]: init_mod(): Error while initializing module 
ims_registrar_pcscf (/opt/lib64/kamailio/modules/ims_registrar_pcscf.so)
Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: DEBUG: cdp_avp 
[cdp_avp_mod.c:225]: cdp_avp_destroy(): Destroying module cdp_avp
Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: WARNING:  
[core/mem/q_malloc.c:487]: qm_free(): WARNING: free(0) called from cdp_avp: 
cdp_avp_mod.c: cdp_avp_destroy(226)
Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: INFO: cdp [cdp_mod.c:255]: 
cdp_exit(): CDiameterPeer child stopping ...
Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: INFO: cdp [cdp_mod.c:257]: 
cdp_exit(): ... CDiameterPeer child stopped
Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: DEBUG: tcpops [tcpops_mod.c:156]: 
mod_destroy(): TCP keepalive module unloaded.
Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: DEBUG: tm [t_funcs.c:84]: 
tm_shutdown(): start
Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: DEBUG: tm [t_funcs.c:87]: 
tm_shutdown(): emptying hash table
Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: DEBUG: tm [t_funcs.c:89]: 
tm_shutdown(): removing semaphores
Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: DEBUG: tm [t_funcs.c:91]: 
tm_shutdown(): destroying tmcb lists
Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: DEBUG: tm [t_funcs.c:94]: 
tm_shutdown(): done
Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: INFO:  
[core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized
Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: DEBUG:  
[core/mem/shm.c:288]: shm_destroy_manager(): destroying memory manager: q_malloc
Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: DEBUG:  
[core/mem/q_malloc.c:1185]: qm_shm_lock_destroy(): destroying the shared memory 
lock
Jan  3 02:19:09 CSCFNode2 [Proxy-CSCF][833]: DEBUG:  [core/mem/pkg.c:97]: 
pkg_destroy_manager(): destroying memory manager: q_malloc

There is no option to use ims_registrar_pcscf without ims_ipsec_pcscf.
[cid:ec21fdae-7d7e-437c-a7ea-6345f36a1428]


Regards

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

[SR-Users] Vendor Specific RBT Call Flow

2019-12-04 Thread Hamid Hashmi

Dear Users

Can the following call flow be implemented, if yes, can you give some 
suggestions with modules information?

 [cid:d15f60e7-73ec-4cd8-8954-92f472a94ef7]


Regards

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

Re: [SR-Users] Kamailio-5.1.6 Crash

2018-11-19 Thread Hamid Hashmi

 I am continuously receiving following error in the logs instead of disabling 
the sip trace module

captagent: [ERR] protocol_sip.c:132 Couldnot find this call

and when I restart the service there is a warning in the logs

Nov 18 20:33:47 kamailiostandby SIPSer[5495]: WARNING: tls [tls_init.c:781]: 
init_tls_h(): openssl bug #1491 (crash/mem leaks on low memory) workaround 
enabled (on low memory tls operations will fail preemptively) with free memory 
thresholds 17301504 and 8650752 bytes
Nov 18 20:33:47 kamailiostandby SIPSer[5495]: INFO:  
[core/cfg/cfg_ctx.c:598]: cfg_set_now(): tls.low_mem_threshold1 has been 
changed to 17301504
Nov 18 20:33:47 kamailiostandby SIPSer[5495]: INFO:  
[core/cfg/cfg_ctx.c:598]: cfg_set_now(): tls.low_mem_threshold2 has been 
changed to 8650752
Nov 18 20:33:47 kamailiostandby SIPSer[5495]: INFO:  
[core/udp_server.c:153]: probe_max_receive_buffer(): SO_RCVBUF is initially 
212992
Nov 18 20:33:47 kamailiostandby SIPSer[5495]: INFO:  
[core/udp_server.c:205]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984

and the following line in some calls

Nov 18 20:33:23 kamailiostandby SIPSer[5063]: BYE 
WnsCPQeXMiJ-7KJZVQTxshtvGpTkG.GD WARNING: tm [h_table.c:142]: 
free_cell_helper(): removed cell 0x7f4358d2dea0 is still linked in hash table 
(t_lookup.c:1497)



Regards

Hamid R. Hashmi


From: Hamid Hashmi 
Sent: Monday, November 19, 2018 3:40 PM
To: Kamailio (SER) - Users Mailing List
Subject: Re: Kamailio-5.1.6 Crash

I have just changed '#define MAX_EXTRA 4' to '#define MAX_EXTRA 6' in the 
following file.

kamailio-5.1.6/src/modules/auth_radius/extra.h


Regards

Hamid R. Hashmi


From: sr-users  on behalf of Hamid Hashmi 

Sent: Monday, November 19, 2018 3:32 PM
To: Kamailio (SER) - Users Mailing List
Subject: [SR-Users] Kamailio-5.1.6 Crash

I have been using the following version of kamailio

Version: kamailio 5.1.6 (x86_64/linux)
  Default config: /usr/local/etc/kamailio/kamailio.cfg
  Default paths to modules: /usr/local/lib64/kamailio/modules
  Compile 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, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, 
FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, 
USE_DST_BLACKLIST, HAVE_RESOLV_RES
  MAX_RECV_BUFFER_SIZE=262144
  MAX_URI_SIZE=1024
  BUF_SIZE=65535
  DEFAULT PKG_SIZE=8MB
  DEFAULT SHM_SIZE=64MB
  ADAPTIVE_WAIT_LOOPS=1024
  TCP poll methods: poll, epoll_lt, epoll_et, sigio_rt, select
  Source code revision ID: unknown
  Compiled with: gcc 4.8.5
  Compiled on: 11:48:33 Oct 11 2018

and I noticed today that the Kamailio service is crashing.

[root@kamailiostandby /]# gdb core.17805
GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-100.el7_4.1
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
[New LWP 17805]
Core was generated by `/usr/local/sbin/kamailio -P /run/kamailio/kamailio.pid 
-f /usr/local/SIP'.
Program terminated with signal 11, Segmentation fault.
#0  0x7f636559e54b in ?? ()
"/core.17805" is a core file.
Please specify an executable to debug.
(gdb) list
No symbol table is loaded.  Use the "file" command.
(gdb) bt
#0  0x7f636559e54b in ?? ()
#1  0x7f63a9571810 in ?? ()
#2  0x in ?? ()



Regards


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

Re: [SR-Users] Kamailio-5.1.6 Crash

2018-11-19 Thread Hamid Hashmi

I have just changed '#define MAX_EXTRA 4' to '#define MAX_EXTRA 6' in the 
following file.

kamailio-5.1.6/src/modules/auth_radius/extra.h


Regards

Hamid R. Hashmi


From: sr-users  on behalf of Hamid Hashmi 

Sent: Monday, November 19, 2018 3:32 PM
To: Kamailio (SER) - Users Mailing List
Subject: [SR-Users] Kamailio-5.1.6 Crash

I have been using the following version of kamailio

Version: kamailio 5.1.6 (x86_64/linux)
  Default config: /usr/local/etc/kamailio/kamailio.cfg
  Default paths to modules: /usr/local/lib64/kamailio/modules
  Compile 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, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, 
FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, 
USE_DST_BLACKLIST, HAVE_RESOLV_RES
  MAX_RECV_BUFFER_SIZE=262144
  MAX_URI_SIZE=1024
  BUF_SIZE=65535
  DEFAULT PKG_SIZE=8MB
  DEFAULT SHM_SIZE=64MB
  ADAPTIVE_WAIT_LOOPS=1024
  TCP poll methods: poll, epoll_lt, epoll_et, sigio_rt, select
  Source code revision ID: unknown
  Compiled with: gcc 4.8.5
  Compiled on: 11:48:33 Oct 11 2018

and I noticed today that the Kamailio service is crashing.

[root@kamailiostandby /]# gdb core.17805
GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-100.el7_4.1
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
[New LWP 17805]
Core was generated by `/usr/local/sbin/kamailio -P /run/kamailio/kamailio.pid 
-f /usr/local/SIP'.
Program terminated with signal 11, Segmentation fault.
#0  0x7f636559e54b in ?? ()
"/core.17805" is a core file.
Please specify an executable to debug.
(gdb) list
No symbol table is loaded.  Use the "file" command.
(gdb) bt
#0  0x7f636559e54b in ?? ()
#1  0x7f63a9571810 in ?? ()
#2  0x in ?? ()



Regards


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

[SR-Users] Kamailio-5.1.6 Crash

2018-11-19 Thread Hamid Hashmi

I have been using the following version of kamailio

Version: kamailio 5.1.6 (x86_64/linux)
  Default config: /usr/local/etc/kamailio/kamailio.cfg
  Default paths to modules: /usr/local/lib64/kamailio/modules
  Compile 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, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, 
FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, 
USE_DST_BLACKLIST, HAVE_RESOLV_RES
  MAX_RECV_BUFFER_SIZE=262144
  MAX_URI_SIZE=1024
  BUF_SIZE=65535
  DEFAULT PKG_SIZE=8MB
  DEFAULT SHM_SIZE=64MB
  ADAPTIVE_WAIT_LOOPS=1024
  TCP poll methods: poll, epoll_lt, epoll_et, sigio_rt, select
  Source code revision ID: unknown
  Compiled with: gcc 4.8.5
  Compiled on: 11:48:33 Oct 11 2018

and I noticed today that the Kamailio service is crashing.

[root@kamailiostandby /]# gdb core.17805
GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-100.el7_4.1
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
...
[New LWP 17805]
Core was generated by `/usr/local/sbin/kamailio -P /run/kamailio/kamailio.pid 
-f /usr/local/SIP'.
Program terminated with signal 11, Segmentation fault.
#0  0x7f636559e54b in ?? ()
"/core.17805" is a core file.
Please specify an executable to debug.
(gdb) list
No symbol table is loaded.  Use the "file" command.
(gdb) bt
#0  0x7f636559e54b in ?? ()
#1  0x7f63a9571810 in ?? ()
#2  0x in ?? ()



Regards


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

Re: [SR-Users] Freeradiusclient Interim-Update Support

2018-11-16 Thread Hamid Hashmi

How did you enable ALIVE packet?

Regards

Hamid


From: sr-users  on behalf of Hamid Hashmi 

Sent: Friday, November 16, 2018 4:27 PM
To: sr-users@lists.kamailio.org
Subject: [SR-Users] Freeradiusclient Interim-Update Support

Dear All

Is module acc_radius supports interim updates? If yes then how to configure it.


Regards

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

[SR-Users] Freeradiusclient Interim-Update Support

2018-11-16 Thread Hamid Hashmi

Dear All

Is module acc_radius supports interim updates? If yes then how to configure it.


Regards

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

Re: [SR-Users] Freeing already Freed pointer

2018-10-03 Thread Hamid Hashmi

No, I am not that expert 😊

I just find out that there are so many dump files in the working directory.  
Please find the backtrace below

#0  0x7f3e27818c9f in t_should_relay_response (Trans=0x7f3de60bdc60, 
new_code=200, branch=0, should_store=0x7fff44501d78, 
should_relay=0x7fff44501d7c, cancel_data=0x7fff44501fc0,
reply=0x7f3e2a042708) at t_reply.c:1281
#1  0x7f3e2781d1d6 in relay_reply (t=0x7f3de60bdc60, p_msg=0x7f3e2a042708, 
branch=0, msg_status=200, cancel_data=0x7fff44501fc0, do_put_on_wait=1) at 
t_reply.c:1785
#2  0x7f3e278223a2 in reply_received (p_msg=0x7f3e2a042708) at 
t_reply.c:2530
#3  0x004f0271 in do_forward_reply (msg=0x7f3e2a042708, mode=0) at 
core/forward.c:744
#4  0x004f1a31 in forward_reply (msg=0x7f3e2a042708) at 
core/forward.c:845
#5  0x00572d17 in receive_msg (
buf=0xa533c0  "SIP/2.0 200 OK\r\nVia: SIP/2.0/UDP 
X.X.X.X:xxx;branch=z9hG4bK408d.a486c78251b57e015f4f0942872a10bf.0;i=2;received=X.X.X.X\r\nVia:
 SIP/2.0/TCP 192.168.2.7:60336;received=58.65.176.42;rport=26439;b"..., 
len=969, rcv_info=0x7fff44502730) at core/receive.c:355
#6  0x00454f9c in udp_rcv_loop () at core/udp_server.c:554
#7  0x00424409 in main_loop () at main.c:1619
#8  0x0042b98e in main (argc=9, argv=0x7fff44502c78) at main.c:2638


Regards


Hamid R. Hashmi


From: Daniel-Constantin Mierla 
Sent: Thursday, October 4, 2018 11:30 AM
To: Kamailio (SER) - Users Mailing List; Hamid Hashmi
Subject: Re: [SR-Users] Freeing already Freed pointer


Hello,


do you have your own developed module or other private extensions made to 
kamailio?


The logs show there was a core dump file, locate it and get the back trace with 
gdb and send it here.


Cheers,
Daniel

On 03.10.18 10:39, Hamid Hashmi wrote:
Dear Kamailio User

Can you please guide me in identifying the issue.

Sep 27 14:40:19 kamailio_eu SIPSer[11289]: 923226363266 9231 27872 
INVITE haYKxpYM1QR8XTU37WdVbxf4VkEITe7A CRITICAL:  
[core/mem/q_malloc.c:504]: qm_free(): BUG: freeing already freed pointer 
(0x7f30c8a4df30), called from tm: t_reply.c: relay_reply(1920), first free tm: 
h_table.c: free_cell_helper(155) - aborting Sep 27 14:40:19 kamailio_eu 
SIPSer[11289]: 923226363266 9231 27872 INVITE 
haYKxpYM1QR8XTU37WdVbxf4VkEITe7A CRITICAL:  [core/mem/q_malloc.c:504]: 
qm_free(): BUG: freeing already freed pointer (0x7f30c8a4cc40), called from tm: 
h_table.c: free_cell_helper(153), first free tm: h_table.c: 
free_cell_helper(153) - aborting Sep 27 14:40:19 kamailio_eu SIPSer[11289]: 
923226363266 9231 27872 INVITE haYKxpYM1QR8XTU37WdVbxf4VkEITe7A 
CRITICAL:  [core/mem/q_malloc.c:504]: qm_free(): BUG: freeing already 
freed pointer (0x7f30c8a4afc8), called from tm: h_table.c: 
free_cell_helper(153), first free tm: h_table.c: free_cell_helper(153) - 
aborting Sep 27 14:40:19 kamailio_eu SIPSer[11289]: 923226363266 9231 
27872 INVITE haYKxpYM1QR8XTU37WdVbxf4VkEITe7A CRITICAL:  
[core/mem/q_malloc.c:504]: qm_free(): BUG: freeing already freed pointer 
(0x7f30c8a4af38), called from tm: h_table.c: free_cell_helper(174), first free 
tm: h_table.c: free_cell_helper(174) - aborting Sep 27 14:40:19 kamailio_eu 
SIPSer[11289]: 923226363266 9231 27872 INVITE 
haYKxpYM1QR8XTU37WdVbxf4VkEITe7A CRITICAL:  [core/mem/q_malloc.c:504]: 
qm_free(): BUG: freeing already freed pointer (0x7f30c8a4ae38), called from 
dialog: dlg_handlers.c: dlg_iuid_sfree(305), first free dialog: dlg_handlers.c: 
dlg_iuid_sfree(305) - aborting Sep 27 14:40:19 kamailio_eu SIPSer[11289]: 
923226363266 9231 27872 INVITE haYKxpYM1QR8XTU37WdVbxf4VkEITe7A 
CRITICAL:  [core/mem/q_malloc.c:504]: qm_free(): BUG: freeing already 
freed pointer (0x7f30c8a4aea8), called from tm: h_table.c: 
free_cell_helper(174), first free tm: h_table.c: free_cell_helper(174) - 
aborting Sep 27 14:40:19 kamailio_eu SIPSer[11289]: 923226363266 9231 
27872 INVITE haYKxpYM1QR8XTU37WdVbxf4VkEITe7A CRITICAL:  
[core/mem/q_malloc.c:504]: qm_free(): BUG: freeing already freed pointer 
(0x7f30c8a4ada8), called from tm: h_table.c: free_cell_helper(174), first free 
tm: h_table.c: free_cell_helper(174) - aborting Sep 27 14:40:19 kamailio_eu 
SIPSer[11289]: 923226363266 9231 27872 INVITE 
haYKxpYM1QR8XTU37WdVbxf4VkEITe7A CRITICAL:  [core/mem/q_malloc.c:504]: 
qm_free(): BUG: freeing already freed pointer (0x7f30c8a4ad18), called from tm: 
h_table.c: free_cell_helper(174), first free tm: h_table.c: 
free_cell_helper(174) - aborting Sep 27 14:40:19 kamailio_eu SIPSer[11289]: 
923226363266 9231 27872 INVITE haYKxpYM1QR8XTU37WdVbxf4VkEITe7A 
CRITICAL:  [core/mem/q_malloc.c:504]: qm_free(): BUG: freeing already 
freed pointer (0x7f30c8a4ac88), called from tm: h_table.c: 
free_cell_helper(174), first free tm: h_table.c: free_cell_helper(174) - 
aborting Sep 27 14:40:19 kamailio_eu SIPSer[11289]: 923226363266 9231 
27872 INVITE haYKxpYM1QR8XTU37WdVbx

Re: [SR-Users] Freeing already Freed pointer

2018-10-03 Thread Hamid Hashmi

Dear Kamailio User

Can you please guide me in identifying the issue.

Sep 27 14:40:19 kamailio_eu SIPSer[11289]: 923226363266 9231 27872 
INVITE haYKxpYM1QR8XTU37WdVbxf4VkEITe7A CRITICAL:  
[core/mem/q_malloc.c:504]: qm_free(): BUG: freeing already freed pointer 
(0x7f30c8a4df30), called from tm: t_reply.c: relay_reply(1920), first free tm: 
h_table.c: free_cell_helper(155) - aborting Sep 27 14:40:19 kamailio_eu 
SIPSer[11289]: 923226363266 9231 27872 INVITE 
haYKxpYM1QR8XTU37WdVbxf4VkEITe7A CRITICAL:  [core/mem/q_malloc.c:504]: 
qm_free(): BUG: freeing already freed pointer (0x7f30c8a4cc40), called from tm: 
h_table.c: free_cell_helper(153), first free tm: h_table.c: 
free_cell_helper(153) - aborting Sep 27 14:40:19 kamailio_eu SIPSer[11289]: 
923226363266 9231 27872 INVITE haYKxpYM1QR8XTU37WdVbxf4VkEITe7A 
CRITICAL:  [core/mem/q_malloc.c:504]: qm_free(): BUG: freeing already 
freed pointer (0x7f30c8a4afc8), called from tm: h_table.c: 
free_cell_helper(153), first free tm: h_table.c: free_cell_helper(153) - 
aborting Sep 27 14:40:19 kamailio_eu SIPSer[11289]: 923226363266 9231 
27872 INVITE haYKxpYM1QR8XTU37WdVbxf4VkEITe7A CRITICAL:  
[core/mem/q_malloc.c:504]: qm_free(): BUG: freeing already freed pointer 
(0x7f30c8a4af38), called from tm: h_table.c: free_cell_helper(174), first free 
tm: h_table.c: free_cell_helper(174) - aborting Sep 27 14:40:19 kamailio_eu 
SIPSer[11289]: 923226363266 9231 27872 INVITE 
haYKxpYM1QR8XTU37WdVbxf4VkEITe7A CRITICAL:  [core/mem/q_malloc.c:504]: 
qm_free(): BUG: freeing already freed pointer (0x7f30c8a4ae38), called from 
dialog: dlg_handlers.c: dlg_iuid_sfree(305), first free dialog: dlg_handlers.c: 
dlg_iuid_sfree(305) - aborting Sep 27 14:40:19 kamailio_eu SIPSer[11289]: 
923226363266 9231 27872 INVITE haYKxpYM1QR8XTU37WdVbxf4VkEITe7A 
CRITICAL:  [core/mem/q_malloc.c:504]: qm_free(): BUG: freeing already 
freed pointer (0x7f30c8a4aea8), called from tm: h_table.c: 
free_cell_helper(174), first free tm: h_table.c: free_cell_helper(174) - 
aborting Sep 27 14:40:19 kamailio_eu SIPSer[11289]: 923226363266 9231 
27872 INVITE haYKxpYM1QR8XTU37WdVbxf4VkEITe7A CRITICAL:  
[core/mem/q_malloc.c:504]: qm_free(): BUG: freeing already freed pointer 
(0x7f30c8a4ada8), called from tm: h_table.c: free_cell_helper(174), first free 
tm: h_table.c: free_cell_helper(174) - aborting Sep 27 14:40:19 kamailio_eu 
SIPSer[11289]: 923226363266 9231 27872 INVITE 
haYKxpYM1QR8XTU37WdVbxf4VkEITe7A CRITICAL:  [core/mem/q_malloc.c:504]: 
qm_free(): BUG: freeing already freed pointer (0x7f30c8a4ad18), called from tm: 
h_table.c: free_cell_helper(174), first free tm: h_table.c: 
free_cell_helper(174) - aborting Sep 27 14:40:19 kamailio_eu SIPSer[11289]: 
923226363266 9231 27872 INVITE haYKxpYM1QR8XTU37WdVbxf4VkEITe7A 
CRITICAL:  [core/mem/q_malloc.c:504]: qm_free(): BUG: freeing already 
freed pointer (0x7f30c8a4ac88), called from tm: h_table.c: 
free_cell_helper(174), first free tm: h_table.c: free_cell_helper(174) - 
aborting Sep 27 14:40:19 kamailio_eu SIPSer[11289]: 923226363266 9231 
27872 INVITE haYKxpYM1QR8XTU37WdVbxf4VkEITe7A CRITICAL:  
[core/mem/q_malloc.c:504]: qm_free(): BUG: freeing already freed pointer 
(0x7f30c8a4d290), called from tm: h_table.c: free_cell_helper(181), first free 
tm: h_table.c: free_cell_helper(181) - aborting Sep 27 14:40:19 kamailio_eu 
SIPSer[11289]: 923226363266 9231 27872 INVITE 
haYKxpYM1QR8XTU37WdVbxf4VkEITe7A CRITICAL:  [core/mem/q_malloc.c:504]: 
qm_free(): BUG: freeing already freed pointer (0x7f30c8a4ca20), called from tm: 
h_table.c: free_cell_helper(231), first free tm: h_table.c: 
free_cell_helper(231) - aborting Sep 27 14:40:19 kamailio_eu SIPSer[11289]: 
923226363266 9231 27872 INVITE haYKxpYM1QR8XTU37WdVbxf4VkEITe7A 
CRITICAL:  [core/mem/q_malloc.c:504]: qm_free(): BUG: freeing already 
freed pointer (0x7f30c8a4c998), called from tm: h_table.c: 
free_cell_helper(232), first free tm: h_table.c: free_cell_helper(232) - 
aborting Sep 27 14:40:19 kamailio_eu SIPSer[11289]: 923226363266 9231 
27872 INVITE haYKxpYM1QR8XTU37WdVbxf4VkEITe7A CRITICAL:  
[core/mem/q_malloc.c:504]: qm_free(): BUG: freeing already freed pointer 
(0x7f30c8a495d8), called from tm: h_table.c: free_cell_helper(251), first free 
tm: h_table.c: free_cell_helper(251) - aborting


Regards


Hamid R. Hashmi


From: sr-users  on behalf of Hamid Hashmi 

Sent: Thursday, September 27, 2018 5:14 PM
To: Kamailio (SER) - Users Mailing List
Subject: [SR-Users] Freeing already Freed pointer

I have been receiving CRITICAL core logs since I have updated my service to the 
following version.

Print out of kamailio internals
  Version: kamailio 5.1.5 (x86_64/linux) d06080
  Default config: /usr/local/SIPSer/etc/kamailio/kamailio.cfg
  Default paths to modules: /usr/local/SIPSer/lib64/kamailio/modules
  Compile flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS

Re: [SR-Users] Documentation of Kamailio.cfg

2018-09-27 Thread Hamid Hashmi

Yes. Please visit the documentation 
page.


Regards

Hamid R. Hashmi


From: sr-users  on behalf of Prabhat Kumar 

Sent: Thursday, September 27, 2018 5:24 PM
To: sr-users@lists.kamailio.org
Subject: [SR-Users] Documentation of Kamailio.cfg

[https://app.mailtag.io/email-event/379e8d90-c250-11e8-9be3-062582205cc4.png?ts=603484531]Hi
 everyone,
I there any suitable documentation for understating kamailio configuration file.

Regards,

Prabhat Kumar

Sr. Software Developer

[phone]

+91 92129 92129 Ext: 89


[moible]

+91 80831 10443


[https://keka.blob.core.windows.net/34edb1d1-7a7f-415f-8b62-6b9b74ee8aa6/200x200/profileimage/54e4875a37024f4aa23cb50b2ae6dfd2.jpg?1535006712022]

[Facebook][Twitter][Twitter][Linkedin][Google+]
[Logo] 



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

[SR-Users] Freeing already Freed pointer

2018-09-27 Thread Hamid Hashmi

I have been receiving CRITICAL core logs since I have updated my service to the 
following version.

Print out of kamailio internals
  Version: kamailio 5.1.5 (x86_64/linux) d06080
  Default config: /usr/local/SIPSer/etc/kamailio/kamailio.cfg
  Default paths to modules: /usr/local/SIPSer/lib64/kamailio/modules
  Compile 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, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, 
FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, 
USE_DST_BLACKLIST, HAVE_RESOLV_RES
  MAX_RECV_BUFFER_SIZE=262144
  MAX_URI_SIZE=1024
  BUF_SIZE=65535
  DEFAULT PKG_SIZE=8MB
  DEFAULT SHM_SIZE=64MB
  ADAPTIVE_WAIT_LOOPS=1024
  TCP poll methods: poll, epoll_lt, epoll_et, sigio_rt, select
  Source code revision ID: d06080
  Compiled with: gcc 4.8.5
  Compiled on: 14:17:56 Sep 13 2018
Thank you for flying kamailio!

I have been starting kamailio with the following command

$ /usr/local/sbin/kamailio -P /run/kamailio/kamailio.pid -f 
/usr/local/etc/kamailio/kamailio.cfg -m 1024 -M 512

Sample Critical Logs are below

Sep 27 14:40:19 kamailio_eu SIPSer[11289]: 923226363266 9231 27872 
INVITE haYKxpYM1QR8XTU37WdVbxf4VkEITe7A CRITICAL:  
[core/mem/q_malloc.c:504]: qm_free(): BUG: freeing already freed pointer 
(0x7f30c8a4df30), called from tm: t_reply.c: relay_reply(1920), first free tm: 
h_table.c: free_cell_helper(155) - aborting
Sep 27 14:40:19 kamailio_eu SIPSer[11289]: 923226363266 9231 27872 
INVITE haYKxpYM1QR8XTU37WdVbxf4VkEITe7A CRITICAL:  
[core/mem/q_malloc.c:504]: qm_free(): BUG: freeing already freed pointer 
(0x7f30c8a4cc40), called from tm: h_table.c: free_cell_helper(153), first free 
tm: h_table.c: free_cell_helper(153) - aborting

Its also causing service crash.  Complete logs are 
here.


Regards

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

Re: [SR-Users] Module RTPPROXY param Timeout_Socket not Working

2018-09-24 Thread Hamid Hashmi

Can any anybody please please into the following issue and guide me and sorry 
for multiple posts.


Regards


Hamid R. Hashmi


From: Hamid Hashmi 
Sent: Wednesday, September 12, 2018 11:57 AM
To: Yu Boot; Kamailio (SER) - Users Mailing List; Daniel-Constantin Mierla
Subject: Re: [SR-Users] Module RTPPROXY param Timeout_Socket not Working

Danial

Can you please answer to this comment ( 
https://github.com/kamailio/kamailio/issues/1597#issuecomment-416858027 )


Regards


Hamid R. Hashmi

__

www.hrhashmi.blogspot.com<http://www.trgworld.com/pakistan>

Mobile: +92 300 968 22 85 ; +92 322 636 32 66
Email: hamid.hashmi...@gmail.com<mailto:hamidraza.has...@trgworld.com>; 
hamid2kv...@hotmail.com

Sype:  hamidrhashmi


From: sr-users  on behalf of Yu Boot 

Sent: Monday, July 23, 2018 11:51 AM
To: sr-users@lists.kamailio.org
Subject: Re: [SR-Users] Module RTPPROXY param Timeout_Socket not Working


Hello.


AFAIK rtpproxy timeout socket requires very special version of rtpproxy itself 
and a patch. Personally, I've gived up to make this feature work.


Now I use dialog-based keepalives to detect and tear down dead sessions.



23.07.2018 9:42, Hamid Hashmi пишет:
waiting for suggestions.


Regards


Hamid R. Hashmi

__

www.hrhashmi.blogspot.com<http://www.trgworld.com/pakistan>

Mobile: +92 300 968 22 85 ; +92 322 636 32 66
Email: hamid.hashmi...@gmail.com<mailto:hamidraza.has...@trgworld.com>; 
hamid2kv...@hotmail.com<mailto:hamid2kv...@hotmail.com>

Sype:  hamidrhashmi

____
From: Hamid Hashmi <mailto:hamid2kv...@hotmail.com>
Sent: Thursday, July 19, 2018 1:05 PM
To: Hamid Hashmi; Kamailio (SER) - Users Mailing List
Subject: Re: Module RTPPROXY param Timeout_Socket not Working

I started the RTPproxy with the following command.


/usr/bin/rtpproxy -u root -A [PUBLIC IP] -F -f -T 45 -i -2 -l 192.168.3.22 -b 
-m 35000 -M 65000 -s udp:127.0.0.1:7722 -n tcp:127.0.0.1:8000 -d DBUG



Regards


Hamid R. Hashmi

__

www.hrhashmi.blogspot.com<http://www.trgworld.com/pakistan>

Mobile: +92 300 968 22 85 ; +92 322 636 32 66
Email: hamid.hashmi...@gmail.com<mailto:hamidraza.has...@trgworld.com>; 
hamid2kv...@hotmail.com<mailto:hamid2kv...@hotmail.com>

Sype:  hamidrhashmi


From: sr-users 
<mailto:sr-users-boun...@lists.kamailio.org>
 on behalf of Hamid Hashmi 
<mailto:hamid2kv...@hotmail.com>
Sent: Thursday, July 19, 2018 12:59 PM
To: sr-users@lists.kamailio.org<mailto:sr-users@lists.kamailio.org>
Subject: [SR-Users] Module RTPPROXY param Timeout_Socket not Working


Kamailio didn't start listening on IP mentioned in Module RTPPROXY parameter 
Timeout_Socket<https://kamailio.org/docs/modules/5.1.x/modules/rtpproxy.html#rtpproxy.p.timeout_socket>.

Below is my configuration file.

loadmodule "rtpproxy.so"
modparam("rtpproxy", "rtpproxy_sock", "udp:127.0.0.1:7722")
modparam("rtpproxy", "rtpproxy_tout", 1)
modparam("rtpproxy", "rtpproxy_retr", 2)
modparam("rtpproxy", "timeout_socket", "xmlrpc:http://127.0.0.1:8000/RPC2";)

loadmodule "xmlrpc.so"
modparam("xmlrpc", "route", "XMLRPC");
modparam("xmlrpc", "mode", 1)
modparam("xmlrpc", "url_match", "^/RPC2")

when I type a command

$ netstat -nlp

it only shows SIP listening ports. Kamailio should also start listening on 
127.0.0.1:8000.

 Below are the RTPproxy logs, RTPproxy is also unable to bridge the media


DBUG:get_command:GLOBAL: received command "19083_4 Uc120,101 
9a1060af660d4202976c419ab5300470 58.65.176.42 4000 
1ea06d1eb0a8443697a08e568045598c;1"
INFO:rtpp_command_ul_handle:GLOBAL: new session 
9a1060af660d4202976c419ab5300470, tag 1ea06d1eb0a8443697a08e568045598c;1 
requested, type strong
INFO:rtpp_command_ul_handle:9a1060af660d4202976c419ab5300470: new session on a 
port 35012 created, tag 1ea06d1eb0a8443697a08e568045598c;1
INFO:rtpp_command_ul_handle:9a1060af660d4202976c419ab5300470: pre-filling 
caller's address with 58.65.176.42:4000
DBUG:rtpc_doreply:GLOBAL: sending reply "35012 51.38.201.3
"
DBUG:get_command:GLOBAL: received command "19083_5 Uc120,101 
9a1060af660d4202976c419ab5300470 58.65.176.42 4022 
9RPsEBbcZSA23MmWAw0hfXzJ-bG1GYDq;1 1ea06d1eb0a8443697a08e568045598c;1 
xmlrpc:http://127.0.0.1:8000/RPC2";
INFO:rtpp_command_ul_handle:GLOBAL: new session 
9a1060af660d4202976c419ab5300470, tag 9RPsEBbcZSA23MmWAw0hfXzJ-bG1GYDq;1 
requested, type strong
INFO:rtpp_command_ul_handle:9a1060af660d4202976c419ab5300470: new session on a 
port 35014 created, tag 9RPsEBbcZSA23MmWAw0hfXzJ-bG1GYDq;1
ERR:rtpp_command_ul_han

Re: [SR-Users] Planing the release of Kamailio v5.1.6

2018-09-24 Thread Hamid Hashmi

Can you please look into the following issue. I have added more details, please 
look into this.

https://github.com/kamailio/kamailio/issues/1597



Regards


Hamid R. Hashmi


From: sr-users  on behalf of 
Daniel-Constantin Mierla 
Sent: Monday, September 24, 2018 11:59 AM
To: Kamailio (SER) - Users Mailing List; Kamailio (SER) - Devel Mailing List
Subject: [SR-Users] Planing the release of Kamailio v5.1.6

Hello,

a matter of the schedule to be agreed in the morning and the
availability during the Kamailio Developers Meeting, we may do a new
stable release from branch 5.1.6 on Thursday, Sep 27, 2018, in the
afternoon. Given that several of us will be in the same room, the
special goal would be to try to automate the process as much as possible.

If the time doesn't allow it, then the release will be done next week, a
specific day to be decided by the end of this week.

Anyhow, this is the informal notification to report as soon as possible
any issues you are aware of and not yet in bug tracker, so they get a
chance to be fixed.

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
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Roadmap to next major release - v5.2.0

2018-09-24 Thread Hamid Hashmi

Can you please look into this issue. You closed this issue but I have added 
more details can you have a look.

https://github.com/kamailio/kamailio/issues/1597



Regards


Hamid R. Hashmi



From: sr-users  on behalf of 
Daniel-Constantin Mierla 
Sent: Tuesday, September 11, 2018 12:35 PM
To: Kamailio (SER) - Users Mailing List; Kamailio (SER) - Devel Mailing List; 
busin...@lists.kamailio.org
Subject: [SR-Users] Roadmap to next major release - v5.2.0

Hello,

as it was discussed during our last IRC devel meeting before the summer,
the time to release a new major version should be this autumn.

With the Kamailio Developers Meeting planned for September 27-28, 2018,
I think it is better to freeze the code couple of days after that event.
So I propose the following milestones:

  * on Thursday, October 4, 2018 - last development day, code for 5.2.0
will be frozen at the end of the day

  * 4 to 6 weeks of testing

  * release sometime in November, to be decided more precisely after the
first weeks of testing, some rough candidates being within the weeks of
Nov 5 or Nov 19

If anyone has something to add or adjust, let's discuss on sr-users
mailing list.

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
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Module RTPPROXY param Timeout_Socket not Working

2018-09-11 Thread Hamid Hashmi

Danial

Can you please answer to this comment ( 
https://github.com/kamailio/kamailio/issues/1597#issuecomment-416858027 )


Regards


Hamid R. Hashmi

__

www.hrhashmi.blogspot.com<http://www.trgworld.com/pakistan>

Mobile: +92 300 968 22 85 ; +92 322 636 32 66
Email: hamid.hashmi...@gmail.com<mailto:hamidraza.has...@trgworld.com>; 
hamid2kv...@hotmail.com

Sype:  hamidrhashmi


From: sr-users  on behalf of Yu Boot 

Sent: Monday, July 23, 2018 11:51 AM
To: sr-users@lists.kamailio.org
Subject: Re: [SR-Users] Module RTPPROXY param Timeout_Socket not Working


Hello.


AFAIK rtpproxy timeout socket requires very special version of rtpproxy itself 
and a patch. Personally, I've gived up to make this feature work.


Now I use dialog-based keepalives to detect and tear down dead sessions.



23.07.2018 9:42, Hamid Hashmi пишет:
waiting for suggestions.


Regards


Hamid R. Hashmi

__

www.hrhashmi.blogspot.com<http://www.trgworld.com/pakistan>

Mobile: +92 300 968 22 85 ; +92 322 636 32 66
Email: hamid.hashmi...@gmail.com<mailto:hamidraza.has...@trgworld.com>; 
hamid2kv...@hotmail.com<mailto:hamid2kv...@hotmail.com>

Sype:  hamidrhashmi

____
From: Hamid Hashmi <mailto:hamid2kv...@hotmail.com>
Sent: Thursday, July 19, 2018 1:05 PM
To: Hamid Hashmi; Kamailio (SER) - Users Mailing List
Subject: Re: Module RTPPROXY param Timeout_Socket not Working

I started the RTPproxy with the following command.


/usr/bin/rtpproxy -u root -A [PUBLIC IP] -F -f -T 45 -i -2 -l 192.168.3.22 -b 
-m 35000 -M 65000 -s udp:127.0.0.1:7722 -n tcp:127.0.0.1:8000 -d DBUG



Regards


Hamid R. Hashmi

__

www.hrhashmi.blogspot.com<http://www.trgworld.com/pakistan>

Mobile: +92 300 968 22 85 ; +92 322 636 32 66
Email: hamid.hashmi...@gmail.com<mailto:hamidraza.has...@trgworld.com>; 
hamid2kv...@hotmail.com<mailto:hamid2kv...@hotmail.com>

Sype:  hamidrhashmi


From: sr-users 
<mailto:sr-users-boun...@lists.kamailio.org>
 on behalf of Hamid Hashmi 
<mailto:hamid2kv...@hotmail.com>
Sent: Thursday, July 19, 2018 12:59 PM
To: sr-users@lists.kamailio.org<mailto:sr-users@lists.kamailio.org>
Subject: [SR-Users] Module RTPPROXY param Timeout_Socket not Working


Kamailio didn't start listening on IP mentioned in Module RTPPROXY parameter 
Timeout_Socket<https://kamailio.org/docs/modules/5.1.x/modules/rtpproxy.html#rtpproxy.p.timeout_socket>.

Below is my configuration file.

loadmodule "rtpproxy.so"
modparam("rtpproxy", "rtpproxy_sock", "udp:127.0.0.1:7722")
modparam("rtpproxy", "rtpproxy_tout", 1)
modparam("rtpproxy", "rtpproxy_retr", 2)
modparam("rtpproxy", "timeout_socket", "xmlrpc:http://127.0.0.1:8000/RPC2";)

loadmodule "xmlrpc.so"
modparam("xmlrpc", "route", "XMLRPC");
modparam("xmlrpc", "mode", 1)
modparam("xmlrpc", "url_match", "^/RPC2")

when I type a command

$ netstat -nlp

it only shows SIP listening ports. Kamailio should also start listening on 
127.0.0.1:8000.

 Below are the RTPproxy logs, RTPproxy is also unable to bridge the media


DBUG:get_command:GLOBAL: received command "19083_4 Uc120,101 
9a1060af660d4202976c419ab5300470 58.65.176.42 4000 
1ea06d1eb0a8443697a08e568045598c;1"
INFO:rtpp_command_ul_handle:GLOBAL: new session 
9a1060af660d4202976c419ab5300470, tag 1ea06d1eb0a8443697a08e568045598c;1 
requested, type strong
INFO:rtpp_command_ul_handle:9a1060af660d4202976c419ab5300470: new session on a 
port 35012 created, tag 1ea06d1eb0a8443697a08e568045598c;1
INFO:rtpp_command_ul_handle:9a1060af660d4202976c419ab5300470: pre-filling 
caller's address with 58.65.176.42:4000
DBUG:rtpc_doreply:GLOBAL: sending reply "35012 51.38.201.3
"
DBUG:get_command:GLOBAL: received command "19083_5 Uc120,101 
9a1060af660d4202976c419ab5300470 58.65.176.42 4022 
9RPsEBbcZSA23MmWAw0hfXzJ-bG1GYDq;1 1ea06d1eb0a8443697a08e568045598c;1 
xmlrpc:http://127.0.0.1:8000/RPC2";
INFO:rtpp_command_ul_handle:GLOBAL: new session 
9a1060af660d4202976c419ab5300470, tag 9RPsEBbcZSA23MmWAw0hfXzJ-bG1GYDq;1 
requested, type strong
INFO:rtpp_command_ul_handle:9a1060af660d4202976c419ab5300470: new session on a 
port 35014 created, tag 9RPsEBbcZSA23MmWAw0hfXzJ-bG1GYDq;1
ERR:rtpp_command_ul_handle:9a1060af660d4202976c419ab5300470: invalid socket 
name 1ea06d1eb0a8443697a08e568045598c;1
INFO:rtpp_command_ul_handle:9a1060af660d4202976c419ab5300470: pre-filling 
caller's address with 58.65.176.42:4022
DBUG:rtpc_doreply:GLOBAL: sending reply "35014 51.38.201.3
"

DBUG:get_command:GLOBAL: received command "19086_4 D 
9a1060af660d4202976c419ab5300470 9RPsEBbcZSA23MmW

Re: [SR-Users] How to detect and Hangup a call on network lost at Caller or Callee?

2018-08-29 Thread Hamid Hashmi

Daniel

Default Session-Expires time is 1800 sec. Can't we set Max Session-Expires as 
Min-SE because I didn't find any softphone which provides an option to change 
Sessions-Expire time? Call disconnected after 1800 sec.

Alex
I already tried this but it didn't work. There are no OPTIONS packet to caller 
or callee.


Regards

Hamid R. Hashmi


From: sr-users  on behalf of Alex Balashov 

Sent: Wednesday, August 29, 2018 5:47 PM
To: Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] How to detect and Hangup a call on network lost at 
Caller or Callee?

Hamid,

I think the feature you're really looking for is:

https://kamailio.org/docs/modules/5.1.x/modules/dialog.html#dialog.p.ka_interval
https://kamailio.org/docs/modules/5.1.x/modules/dialog.html#dialog.p.ka_timer
https://kamailio.org/docs/modules/5.1.x/modules/dialog.html#dialog.p.send_bye

-- Alex

On Wed, Aug 29, 2018 at 11:35:18AM +0200, Daniel Grotti wrote:

> Hi,
> have you tired SIP Session Timers
> (https://kamailio.org/docs/modules/5.1.x/modules/sst.html)?
>
> Daniel
>
>
>
> On 08/29/2018 11:30 AM, Hamid Hashmi wrote:
> > Dear Users
> >
> > Please advise how to detect a network lost at caller or callee side. I
> > have tried timeout_socket 
> > <https://kamailio.org/docs/modules/5.1.x/modules/rtpproxy.html#rtpproxy.p.timeout_socket>
> > and keepalives 
> > <https://kamailio.org/docs/modules/5.1.x/modules/dialog.html#dialog.p.ka_interval>method
> > but nothing worked for me.
> >
> > RTPproxy did not send timeout notification to Kamailio (Issue #1597
> > <https://github.com/kamailio/kamailio/issues/1597>) while there is no
> > options packet within a dialog. Is there any other method to cater such
> > scenario.
> >
> > Regards
> >
> > *Hamid R. Hashmi*
> >
> >
> >
> > ___
> > 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


--
Alex Balashov | Principal | Evariste Systems LLC

Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.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

[SR-Users] How to detect and Hangup a call on network lost at Caller or Callee?

2018-08-29 Thread Hamid Hashmi

Dear Users

Please advise how to detect a network lost at caller or callee side. I have 
tried 
timeout_socket
 and keepalives 

 method but nothing worked for me.

RTPproxy did not send timeout notification to Kamailio (Issue 
#1597) while there is no 
options packet within a dialog. Is there any other method to cater such 
scenario.


Regards

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

Re: [SR-Users] Module RTPPROXY param Timeout_Socket not Working

2018-07-22 Thread Hamid Hashmi

waiting for suggestions.


Regards


Hamid R. Hashmi

__

www.hrhashmi.blogspot.com<http://www.trgworld.com/pakistan>

Mobile: +92 300 968 22 85 ; +92 322 636 32 66
Email: hamid.hashmi...@gmail.com<mailto:hamidraza.has...@trgworld.com>; 
hamid2kv...@hotmail.com

Sype:  hamidrhashmi

____
From: Hamid Hashmi 
Sent: Thursday, July 19, 2018 1:05 PM
To: Hamid Hashmi; Kamailio (SER) - Users Mailing List
Subject: Re: Module RTPPROXY param Timeout_Socket not Working

I started the RTPproxy with the following command.


/usr/bin/rtpproxy -u root -A [PUBLIC IP] -F -f -T 45 -i -2 -l 192.168.3.22 -b 
-m 35000 -M 65000 -s udp:127.0.0.1:7722 -n tcp:127.0.0.1:8000 -d DBUG



Regards


Hamid R. Hashmi

__

www.hrhashmi.blogspot.com<http://www.trgworld.com/pakistan>

Mobile: +92 300 968 22 85 ; +92 322 636 32 66
Email: hamid.hashmi...@gmail.com<mailto:hamidraza.has...@trgworld.com>; 
hamid2kv...@hotmail.com

Sype:  hamidrhashmi


From: sr-users  on behalf of Hamid Hashmi 

Sent: Thursday, July 19, 2018 12:59 PM
To: sr-users@lists.kamailio.org
Subject: [SR-Users] Module RTPPROXY param Timeout_Socket not Working


Kamailio didn't start listening on IP mentioned in Module RTPPROXY parameter 
Timeout_Socket<https://kamailio.org/docs/modules/5.1.x/modules/rtpproxy.html#rtpproxy.p.timeout_socket>.

Below is my configuration file.

loadmodule "rtpproxy.so"
modparam("rtpproxy", "rtpproxy_sock", "udp:127.0.0.1:7722")
modparam("rtpproxy", "rtpproxy_tout", 1)
modparam("rtpproxy", "rtpproxy_retr", 2)
modparam("rtpproxy", "timeout_socket", "xmlrpc:http://127.0.0.1:8000/RPC2";)

loadmodule "xmlrpc.so"
modparam("xmlrpc", "route", "XMLRPC");
modparam("xmlrpc", "mode", 1)
modparam("xmlrpc", "url_match", "^/RPC2")

when I type a command

$ netstat -nlp

it only shows SIP listening ports. Kamailio should also start listening on 
127.0.0.1:8000.

 Below are the RTPproxy logs, RTPproxy is also unable to bridge the media


DBUG:get_command:GLOBAL: received command "19083_4 Uc120,101 
9a1060af660d4202976c419ab5300470 58.65.176.42 4000 
1ea06d1eb0a8443697a08e568045598c;1"
INFO:rtpp_command_ul_handle:GLOBAL: new session 
9a1060af660d4202976c419ab5300470, tag 1ea06d1eb0a8443697a08e568045598c;1 
requested, type strong
INFO:rtpp_command_ul_handle:9a1060af660d4202976c419ab5300470: new session on a 
port 35012 created, tag 1ea06d1eb0a8443697a08e568045598c;1
INFO:rtpp_command_ul_handle:9a1060af660d4202976c419ab5300470: pre-filling 
caller's address with 58.65.176.42:4000
DBUG:rtpc_doreply:GLOBAL: sending reply "35012 51.38.201.3
"
DBUG:get_command:GLOBAL: received command "19083_5 Uc120,101 
9a1060af660d4202976c419ab5300470 58.65.176.42 4022 
9RPsEBbcZSA23MmWAw0hfXzJ-bG1GYDq;1 1ea06d1eb0a8443697a08e568045598c;1 
xmlrpc:http://127.0.0.1:8000/RPC2";
INFO:rtpp_command_ul_handle:GLOBAL: new session 
9a1060af660d4202976c419ab5300470, tag 9RPsEBbcZSA23MmWAw0hfXzJ-bG1GYDq;1 
requested, type strong
INFO:rtpp_command_ul_handle:9a1060af660d4202976c419ab5300470: new session on a 
port 35014 created, tag 9RPsEBbcZSA23MmWAw0hfXzJ-bG1GYDq;1
ERR:rtpp_command_ul_handle:9a1060af660d4202976c419ab5300470: invalid socket 
name 1ea06d1eb0a8443697a08e568045598c;1
INFO:rtpp_command_ul_handle:9a1060af660d4202976c419ab5300470: pre-filling 
caller's address with 58.65.176.42:4022
DBUG:rtpc_doreply:GLOBAL: sending reply "35014 51.38.201.3
"

DBUG:get_command:GLOBAL: received command "19086_4 D 
9a1060af660d4202976c419ab5300470 9RPsEBbcZSA23MmWAw0hfXzJ-bG1GYDq 
1ea06d1eb0a8443697a08e568045598c"
INFO:handle_delete:9a1060af660d4202976c419ab5300470: forcefully deleting 
session 1 on ports 35012/0
INFO:remove_session:9a1060af660d4202976c419ab5300470: RTP stats: 0 in from 
callee, 0 in from caller, 0 relayed, 0 dropped
INFO:remove_session:9a1060af660d4202976c419ab5300470: RTCP stats: 0 in from 
callee, 0 in from caller, 0 relayed, 0 dropped
INFO:remove_session:9a1060af660d4202976c419ab5300470: session on ports 35012/0 
is cleaned up
INFO:handle_delete:9a1060af660d4202976c419ab5300470: forcefully deleting 
session 1 on ports 35014/0
INFO:remove_session:9a1060af660d4202976c419ab5300470: RTP stats: 0 in from 
callee, 0 in from caller, 0 relayed, 0 dropped
INFO:remove_session:9a1060af660d4202976c419ab5300470: RTCP stats: 0 in from 
callee, 0 in from caller, 0 relayed, 0 dropped
INFO:remove_session:9a1060af660d4202976c419ab5300470: session on ports 35014/0 
is cleaned up
DBUG:rtpc_doreply:GLOBAL: sending reply "0
"
DBUG:get_command:GLOBAL: received command "19086_5 D 
9a1060af660d4202976c419ab5300470 9RPsEBbcZSA23MmWAw0hfXzJ-bG1GYDq 
1ea06d1eb0a8443697a08e568045598c&

Re: [SR-Users] Module RTPPROXY param Timeout_Socket not Working

2018-07-19 Thread Hamid Hashmi

I started the RTPproxy with the following command.


/usr/bin/rtpproxy -u root -A [PUBLIC IP] -F -f -T 45 -i -2 -l 192.168.3.22 -b 
-m 35000 -M 65000 -s udp:127.0.0.1:7722 -n tcp:127.0.0.1:8000 -d DBUG



Regards


Hamid R. Hashmi

__

www.hrhashmi.blogspot.com<http://www.trgworld.com/pakistan>

Mobile: +92 300 968 22 85 ; +92 322 636 32 66
Email: hamid.hashmi...@gmail.com<mailto:hamidraza.has...@trgworld.com>; 
hamid2kv...@hotmail.com

Sype:  hamidrhashmi


From: sr-users  on behalf of Hamid Hashmi 

Sent: Thursday, July 19, 2018 12:59 PM
To: sr-users@lists.kamailio.org
Subject: [SR-Users] Module RTPPROXY param Timeout_Socket not Working


Kamailio didn't start listening on IP mentioned in Module RTPPROXY parameter 
Timeout_Socket<https://kamailio.org/docs/modules/5.1.x/modules/rtpproxy.html#rtpproxy.p.timeout_socket>.

Below is my configuration file.

loadmodule "rtpproxy.so"
modparam("rtpproxy", "rtpproxy_sock", "udp:127.0.0.1:7722")
modparam("rtpproxy", "rtpproxy_tout", 1)
modparam("rtpproxy", "rtpproxy_retr", 2)
modparam("rtpproxy", "timeout_socket", "xmlrpc:http://127.0.0.1:8000/RPC2";)

loadmodule "xmlrpc.so"
modparam("xmlrpc", "route", "XMLRPC");
modparam("xmlrpc", "mode", 1)
modparam("xmlrpc", "url_match", "^/RPC2")

when I type a command

$ netstat -nlp

it only shows SIP listening ports. Kamailio should also start listening on 
127.0.0.1:8000.

 Below are the RTPproxy logs, RTPproxy is also unable to bridge the media


DBUG:get_command:GLOBAL: received command "19083_4 Uc120,101 
9a1060af660d4202976c419ab5300470 58.65.176.42 4000 
1ea06d1eb0a8443697a08e568045598c;1"
INFO:rtpp_command_ul_handle:GLOBAL: new session 
9a1060af660d4202976c419ab5300470, tag 1ea06d1eb0a8443697a08e568045598c;1 
requested, type strong
INFO:rtpp_command_ul_handle:9a1060af660d4202976c419ab5300470: new session on a 
port 35012 created, tag 1ea06d1eb0a8443697a08e568045598c;1
INFO:rtpp_command_ul_handle:9a1060af660d4202976c419ab5300470: pre-filling 
caller's address with 58.65.176.42:4000
DBUG:rtpc_doreply:GLOBAL: sending reply "35012 51.38.201.3
"
DBUG:get_command:GLOBAL: received command "19083_5 Uc120,101 
9a1060af660d4202976c419ab5300470 58.65.176.42 4022 
9RPsEBbcZSA23MmWAw0hfXzJ-bG1GYDq;1 1ea06d1eb0a8443697a08e568045598c;1 
xmlrpc:http://127.0.0.1:8000/RPC2";
INFO:rtpp_command_ul_handle:GLOBAL: new session 
9a1060af660d4202976c419ab5300470, tag 9RPsEBbcZSA23MmWAw0hfXzJ-bG1GYDq;1 
requested, type strong
INFO:rtpp_command_ul_handle:9a1060af660d4202976c419ab5300470: new session on a 
port 35014 created, tag 9RPsEBbcZSA23MmWAw0hfXzJ-bG1GYDq;1
ERR:rtpp_command_ul_handle:9a1060af660d4202976c419ab5300470: invalid socket 
name 1ea06d1eb0a8443697a08e568045598c;1
INFO:rtpp_command_ul_handle:9a1060af660d4202976c419ab5300470: pre-filling 
caller's address with 58.65.176.42:4022
DBUG:rtpc_doreply:GLOBAL: sending reply "35014 51.38.201.3
"

DBUG:get_command:GLOBAL: received command "19086_4 D 
9a1060af660d4202976c419ab5300470 9RPsEBbcZSA23MmWAw0hfXzJ-bG1GYDq 
1ea06d1eb0a8443697a08e568045598c"
INFO:handle_delete:9a1060af660d4202976c419ab5300470: forcefully deleting 
session 1 on ports 35012/0
INFO:remove_session:9a1060af660d4202976c419ab5300470: RTP stats: 0 in from 
callee, 0 in from caller, 0 relayed, 0 dropped
INFO:remove_session:9a1060af660d4202976c419ab5300470: RTCP stats: 0 in from 
callee, 0 in from caller, 0 relayed, 0 dropped
INFO:remove_session:9a1060af660d4202976c419ab5300470: session on ports 35012/0 
is cleaned up
INFO:handle_delete:9a1060af660d4202976c419ab5300470: forcefully deleting 
session 1 on ports 35014/0
INFO:remove_session:9a1060af660d4202976c419ab5300470: RTP stats: 0 in from 
callee, 0 in from caller, 0 relayed, 0 dropped
INFO:remove_session:9a1060af660d4202976c419ab5300470: RTCP stats: 0 in from 
callee, 0 in from caller, 0 relayed, 0 dropped
INFO:remove_session:9a1060af660d4202976c419ab5300470: session on ports 35014/0 
is cleaned up
DBUG:rtpc_doreply:GLOBAL: sending reply "0
"
DBUG:get_command:GLOBAL: received command "19086_5 D 
9a1060af660d4202976c419ab5300470 9RPsEBbcZSA23MmWAw0hfXzJ-bG1GYDq 
1ea06d1eb0a8443697a08e568045598c"
INFO:handle_command:GLOBAL: delete request failed: session 
9a1060af660d4202976c419ab5300470, tags 
9RPsEBbcZSA23MmWAw0hfXzJ-bG1GYDq/1ea06d1eb0a8443697a08e568045598c not found
DBUG:rtpc_doreply:GLOBAL: sending reply "E50

But if I comment out the param "Timeout_Socket" then there is no issue in 
bridging the media.


Regards

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

[SR-Users] Module RTPPROXY param Timeout_Socket not Working

2018-07-19 Thread Hamid Hashmi

Kamailio didn't start listening on IP mentioned in Module RTPPROXY parameter 
Timeout_Socket.

Below is my configuration file.

loadmodule "rtpproxy.so"
modparam("rtpproxy", "rtpproxy_sock", "udp:127.0.0.1:7722")
modparam("rtpproxy", "rtpproxy_tout", 1)
modparam("rtpproxy", "rtpproxy_retr", 2)
modparam("rtpproxy", "timeout_socket", "xmlrpc:http://127.0.0.1:8000/RPC2";)

loadmodule "xmlrpc.so"
modparam("xmlrpc", "route", "XMLRPC");
modparam("xmlrpc", "mode", 1)
modparam("xmlrpc", "url_match", "^/RPC2")

when I type a command

$ netstat -nlp

it only shows SIP listening ports. Kamailio should also start listening on 
127.0.0.1:8000.

 Below are the RTPproxy logs, RTPproxy is also unable to bridge the media


DBUG:get_command:GLOBAL: received command "19083_4 Uc120,101 
9a1060af660d4202976c419ab5300470 58.65.176.42 4000 
1ea06d1eb0a8443697a08e568045598c;1"
INFO:rtpp_command_ul_handle:GLOBAL: new session 
9a1060af660d4202976c419ab5300470, tag 1ea06d1eb0a8443697a08e568045598c;1 
requested, type strong
INFO:rtpp_command_ul_handle:9a1060af660d4202976c419ab5300470: new session on a 
port 35012 created, tag 1ea06d1eb0a8443697a08e568045598c;1
INFO:rtpp_command_ul_handle:9a1060af660d4202976c419ab5300470: pre-filling 
caller's address with 58.65.176.42:4000
DBUG:rtpc_doreply:GLOBAL: sending reply "35012 51.38.201.3
"
DBUG:get_command:GLOBAL: received command "19083_5 Uc120,101 
9a1060af660d4202976c419ab5300470 58.65.176.42 4022 
9RPsEBbcZSA23MmWAw0hfXzJ-bG1GYDq;1 1ea06d1eb0a8443697a08e568045598c;1 
xmlrpc:http://127.0.0.1:8000/RPC2";
INFO:rtpp_command_ul_handle:GLOBAL: new session 
9a1060af660d4202976c419ab5300470, tag 9RPsEBbcZSA23MmWAw0hfXzJ-bG1GYDq;1 
requested, type strong
INFO:rtpp_command_ul_handle:9a1060af660d4202976c419ab5300470: new session on a 
port 35014 created, tag 9RPsEBbcZSA23MmWAw0hfXzJ-bG1GYDq;1
ERR:rtpp_command_ul_handle:9a1060af660d4202976c419ab5300470: invalid socket 
name 1ea06d1eb0a8443697a08e568045598c;1
INFO:rtpp_command_ul_handle:9a1060af660d4202976c419ab5300470: pre-filling 
caller's address with 58.65.176.42:4022
DBUG:rtpc_doreply:GLOBAL: sending reply "35014 51.38.201.3
"

DBUG:get_command:GLOBAL: received command "19086_4 D 
9a1060af660d4202976c419ab5300470 9RPsEBbcZSA23MmWAw0hfXzJ-bG1GYDq 
1ea06d1eb0a8443697a08e568045598c"
INFO:handle_delete:9a1060af660d4202976c419ab5300470: forcefully deleting 
session 1 on ports 35012/0
INFO:remove_session:9a1060af660d4202976c419ab5300470: RTP stats: 0 in from 
callee, 0 in from caller, 0 relayed, 0 dropped
INFO:remove_session:9a1060af660d4202976c419ab5300470: RTCP stats: 0 in from 
callee, 0 in from caller, 0 relayed, 0 dropped
INFO:remove_session:9a1060af660d4202976c419ab5300470: session on ports 35012/0 
is cleaned up
INFO:handle_delete:9a1060af660d4202976c419ab5300470: forcefully deleting 
session 1 on ports 35014/0
INFO:remove_session:9a1060af660d4202976c419ab5300470: RTP stats: 0 in from 
callee, 0 in from caller, 0 relayed, 0 dropped
INFO:remove_session:9a1060af660d4202976c419ab5300470: RTCP stats: 0 in from 
callee, 0 in from caller, 0 relayed, 0 dropped
INFO:remove_session:9a1060af660d4202976c419ab5300470: session on ports 35014/0 
is cleaned up
DBUG:rtpc_doreply:GLOBAL: sending reply "0
"
DBUG:get_command:GLOBAL: received command "19086_5 D 
9a1060af660d4202976c419ab5300470 9RPsEBbcZSA23MmWAw0hfXzJ-bG1GYDq 
1ea06d1eb0a8443697a08e568045598c"
INFO:handle_command:GLOBAL: delete request failed: session 
9a1060af660d4202976c419ab5300470, tags 
9RPsEBbcZSA23MmWAw0hfXzJ-bG1GYDq/1ea06d1eb0a8443697a08e568045598c not found
DBUG:rtpc_doreply:GLOBAL: sending reply "E50

But if I comment out the param "Timeout_Socket" then there is no issue in 
bridging the media.


Regards

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

Re: [SR-Users] kamailio-5.2.0 Crash - udp_send failed

Re: [SR-Users] kamailio-5.2.0 Crash - udp_send failed

[SR-Users] [Mod: CDP] TCP Zero Window Error

[SR-Users] How to increase private & shared memory in kamailio Container?

[SR-Users] kamailio-5.2.0 Crash - udp_send failed

[SR-Users] SRVCC Support

[SR-Users] Some Functions not defined in Documentation of Module ims_registrar_pcscf

[SR-Users] How S-CSCF route SIP INVITEs as per iFC ?

[SR-Users] opensource VoLTE/IMS Clients like IMSDroid

Re: [SR-Users] ims_ipsec_pcscf mandatory for ims_registrar_pcscf ?

[SR-Users] ims_ipsec_pcscf mandatory for ims_registrar_pcscf ?

[SR-Users] Vendor Specific RBT Call Flow

Re: [SR-Users] Kamailio-5.1.6 Crash

Re: [SR-Users] Kamailio-5.1.6 Crash

[SR-Users] Kamailio-5.1.6 Crash

Re: [SR-Users] Freeradiusclient Interim-Update Support

[SR-Users] Freeradiusclient Interim-Update Support

Re: [SR-Users] Freeing already Freed pointer

Re: [SR-Users] Freeing already Freed pointer

Re: [SR-Users] Documentation of Kamailio.cfg

[SR-Users] Freeing already Freed pointer

Re: [SR-Users] Module RTPPROXY param Timeout_Socket not Working

Re: [SR-Users] Planing the release of Kamailio v5.1.6

Re: [SR-Users] Roadmap to next major release - v5.2.0

Re: [SR-Users] Module RTPPROXY param Timeout_Socket not Working

Re: [SR-Users] How to detect and Hangup a call on network lost at Caller or Callee?

[SR-Users] How to detect and Hangup a call on network lost at Caller or Callee?

Re: [SR-Users] Module RTPPROXY param Timeout_Socket not Working

Re: [SR-Users] Module RTPPROXY param Timeout_Socket not Working

[SR-Users] Module RTPPROXY param Timeout_Socket not Working

30 matches

Site Navigation

Mail list logo

Footer information