Module RTPPROXY param Timeout_Socket not Working

List overview All Threads
Download

newer

older

Issuse with http_client and...

uac usage

Hamid Hashmi

19 Jul 2018 19 Jul '18

7:59 a.m.

Kamailio didn't start listening on IP mentioned in Module RTPPROXY parameter Timeout_Sockethttps://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

Attachments:

attachment.html (text/html — 9.4 KB)

Show replies by date

Hamid Hashmi

19 Jul 19 Jul

8:05 a.m.

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.comhttp://www.trgworld.com/pakistan

Mobile: +92 300 968 22 85 ; +92 322 636 32 66 Email: hamid.hashmi006@gmail.commailto:hamidraza.hashmi@trgworld.com; hamid2kviii@hotmail.com

Sype: hamidrhashmi

________________________________ From: sr-users sr-users-bounces@lists.kamailio.org on behalf of Hamid Hashmi hamid2kviii@hotmail.com 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_Sockethttps://kamailio.org/docs/modules/5.1.x/modules/rtpproxy.html#rtpproxy.p.timeout_socket.

Below is my configuration file.

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

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

Regards

Hamid R. Hashmi

Hamid Hashmi

23 Jul 23 Jul

6:42 a.m.

waiting for suggestions.

Regards

Hamid R. Hashmi

______________________________

www.hrhashmi.blogspot.comhttp://www.trgworld.com/pakistan

Mobile: +92 300 968 22 85 ; +92 322 636 32 66 Email: hamid.hashmi006@gmail.commailto:hamidraza.hashmi@trgworld.com; hamid2kviii@hotmail.com

Sype: hamidrhashmi

________________________________ From: Hamid Hashmi hamid2kviii@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.comhttp://www.trgworld.com/pakistan

Mobile: +92 300 968 22 85 ; +92 322 636 32 66 Email: hamid.hashmi006@gmail.commailto:hamidraza.hashmi@trgworld.com; hamid2kviii@hotmail.com

Sype: hamidrhashmi

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

Below is my configuration file.

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

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

Regards

Hamid R. Hashmi

Yu Boot

6:51 a.m.

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.hashmi006@gmail.com mailto:hamidraza.hashmi@trgworld.com; _hamid2kviii@hotmail.com_

Sype: _hamidrhashmi_

*From:* Hamid Hashmi hamid2kviii@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.hashmi006@gmail.com mailto:hamidraza.hashmi@trgworld.com; _hamid2kviii@hotmail.com_

Sype: _hamidrhashmi_

*From:* sr-users sr-users-bounces@lists.kamailio.org on behalf of Hamid Hashmi hamid2kviii@hotmail.com *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 parameterTimeout_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

Hamid Hashmi

12 Sep 12 Sep

6:57 a.m.

Danial

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

Regards

Hamid R. Hashmi

______________________________

www.hrhashmi.blogspot.comhttp://www.trgworld.com/pakistan

Mobile: +92 300 968 22 85 ; +92 322 636 32 66 Email: hamid.hashmi006@gmail.commailto:hamidraza.hashmi@trgworld.com; hamid2kviii@hotmail.com

Sype: hamidrhashmi

________________________________ From: sr-users sr-users-bounces@lists.kamailio.org on behalf of Yu Boot yu@yu-boot.ru 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.comhttp://www.trgworld.com/pakistan

Mobile: +92 300 968 22 85 ; +92 322 636 32 66 Email: hamid.hashmi006@gmail.commailto:hamidraza.hashmi@trgworld.com; hamid2kviii@hotmail.commailto:hamid2kviii@hotmail.com

Sype: hamidrhashmi

________________________________ From: Hamid Hashmi hamid2kviii@hotmail.com mailto:hamid2kviii@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.comhttp://www.trgworld.com/pakistan

Mobile: +92 300 968 22 85 ; +92 322 636 32 66 Email: hamid.hashmi006@gmail.commailto:hamidraza.hashmi@trgworld.com; hamid2kviii@hotmail.commailto:hamid2kviii@hotmail.com

Sype: hamidrhashmi

________________________________ From: sr-users sr-users-bounces@lists.kamailio.org mailto:sr-users-bounces@lists.kamailio.org on behalf of Hamid Hashmi hamid2kviii@hotmail.com mailto:hamid2kviii@hotmail.com Sent: Thursday, July 19, 2018 12:59 PM To: sr-users@lists.kamailio.orgmailto: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_Sockethttps://kamailio.org/docs/modules/5.1.x/modules/rtpproxy.html#rtpproxy.p.timeout_socket.

Below is my configuration file.

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

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.orgmailto:sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Hamid Hashmi

24 Sep 24 Sep

7:29 a.m.

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

Regards

Hamid R. Hashmi

________________________________ From: Hamid Hashmi hamid2kviii@hotmail.com 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.comhttp://www.trgworld.com/pakistan

Mobile: +92 300 968 22 85 ; +92 322 636 32 66 Email: hamid.hashmi006@gmail.commailto:hamidraza.hashmi@trgworld.com; hamid2kviii@hotmail.com

Sype: hamidrhashmi

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.comhttp://www.trgworld.com/pakistan

Mobile: +92 300 968 22 85 ; +92 322 636 32 66 Email: hamid.hashmi006@gmail.commailto:hamidraza.hashmi@trgworld.com; hamid2kviii@hotmail.commailto:hamid2kviii@hotmail.com

Sype: hamidrhashmi

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.comhttp://www.trgworld.com/pakistan

Mobile: +92 300 968 22 85 ; +92 322 636 32 66 Email: hamid.hashmi006@gmail.commailto:hamidraza.hashmi@trgworld.com; hamid2kviii@hotmail.commailto:hamid2kviii@hotmail.com

Sype: hamidrhashmi

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

Below is my configuration file.

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

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

Regards

Hamid R. Hashmi

Daniel-Constantin Mierla

8:43 a.m.

Hello,

until someone what rtpproxy does and cannot open the connection, maybe you can use rtpengine. They just added native support for closing dialog on rtp timeout via kamailio's rpc command -- see:

* https://github.com/sipwise/rtpengine

Look for -x, --xmlrpc-format parameter.

There was a discussion on sr-users mailing list as well, with some examples there.

Cheers, Daniel

On 24.09.18 09:29, Hamid Hashmi wrote:

...

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

Regards

*Hamid R. Hashmi*

*From:* Hamid Hashmi hamid2kviii@hotmail.com *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.hashmi006@gmail.com mailto:hamidraza.hashmi@trgworld.com; _hamid2kviii@hotmail.com_

Sype: _hamidrhashmi_

*From:* sr-users sr-users-bounces@lists.kamailio.org on behalf of Yu Boot yu@yu-boot.ru *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.hashmi006@gmail.com mailto:hamidraza.hashmi@trgworld.com; _hamid2kviii@hotmail.com mailto:hamid2kviii@hotmail.com_

Sype: _hamidrhashmi_

*From:* Hamid Hashmi hamid2kviii@hotmail.com mailto:hamid2kviii@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.hashmi006@gmail.com mailto:hamidraza.hashmi@trgworld.com; _hamid2kviii@hotmail.com mailto:hamid2kviii@hotmail.com_

Sype: _hamidrhashmi_

*From:* sr-users sr-users-bounces@lists.kamailio.org mailto:sr-users-bounces@lists.kamailio.org on behalf of Hamid Hashmi hamid2kviii@hotmail.com mailto:hamid2kviii@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 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 mailto: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

2391

Age (days ago)

2458

Last active (days ago)

sr-users@lists.kamailio.org

6 comments

3 participants

tags (0)

participants (3)

Daniel-Constantin Mierla
Hamid Hashmi
Yu Boot