Hi Răzvan Crainea:
I was sending an U command instead of an L command. This is what I interpreted
in the documentation. Is working great now. Thanks a lot! This was worrying me
a lot. I've being dealing with this RTP thing since long. Thought I had to
implement handling that protocol. Thanks a lot!
Sent with [ProtonMail](https://protonmail.com) Secure Email.
-------- Original Message --------
Subject: Re: [OpenSIPS-Users] rtpproxy not relaying data
Local Time: 22 de febrero de 2017 6:14 AM
UTC Time: 22 de febrero de 2017 10:14
From: [email protected]
To: [email protected]
Hi, Waldo!
I only see the command for Update (initial request), I don't see the command
for Lookup(200 OK).
Moreover, are you sure RTP traffic gets to the rtpproxy machine? Because
RTPProxy statistics doesn't see any packets getting to the server. Can you
double check if the firewall allows the traffic?
Best regards,
Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com
On 02/22/2017 11:44 AM, Waldoalvarez via Users wrote:
Hi:
I am trying to use rtpproxy with my SIP proxy. It starts a session and both SIP
clients send data to rtpproxy port as I see on wireshark after I modify the SDP
part. I see data comming to rtpproxy but no data comes out of it. What could be
going on wrong? Configuratoin issue? I send here a log of rtpproxy.
halplus@halplus-VirtualBox ~ $ rtpproxy -f -s unix:/var/run/rtp/rtpproxy.sock
-d DBUG:LOG_LOCAL3
INFO:main: rtpproxy started, pid 11266
ERR:main: can't open pidfile for writing: Permission denied
DBUG:handle_command: received command "U rWiXCizLxX 192.168.200.146 7076
SA6YGw3uI"
INFO:handle_command: new session rWiXCizLxX, tag SA6YGw3uI requested, type
strong
INFO:handle_command: new session on a port 37110 created, tag SA6YGw3uI
INFO:handle_command: pre-filling caller's address with 192.168.200.146:7076
DBUG:doreply: sending reply "37110
"
DBUG:handle_command: received command "U rWiXCizLxX 192.168.200.140 7078
SA6YGw3uI"
INFO:handle_command: adding strong flag to existing session, new=1/0/0
INFO:handle_command: lookup on ports 37110/0, session timer restarted
INFO:handle_command: pre-filling caller's address with 192.168.200.140:7078
DBUG:doreply: sending reply "37110
"
INFO:process_rtp: session timeout
INFO:remove_session: RTP stats: 0 in from callee, 0 in from caller, 0 relayed,
0 dropped
INFO:remove_session: RTCP stats: 0 in from callee, 0 in from caller, 0 relayed,
0 dropped
INFO:remove_session: session on ports 37110/0 is cleaned up
Any help is very much welcome.
Regards
Waldo
_______________________________________________ Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
