Hi, Nathaniel!
You are right, according to OpenSIPS error code, one of the send
function parameters is invalid, and most likely the file descriptor.
Unfortunately I can't confirm this with the logs we have so far. In
order to study the problem further we should add some extra debugging in
the code, and follow the RTPProxy connections.
In order to see all the rtpproxy servers used, you could use the
nh_show_rtpp MI command, but it doesn't give you enough information. You
can only see which servers are you using and what is their current status.
Let me know if you are willing to add some extra debugging, and I will
try to prepare a patch for you. If so, also let me know the OpenSIPS
version you use.
Best regards,
Razvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com
On 09/27/2012 11:55 AM, Nathaniel L Keeling III wrote:
Razvan,
This seems to occur when one client is Nat'ed and the other client has
a public IP address. The client with the private IP, is established
first and ok with rtpproxy. The second client, with public IP, is
where the failure occurs. I can confirm that no packets are being sent
to rtpproxy for the second client when I was checking with ngrep. I
can also concur that I am getting audio one way, which is from the
first client (one with private IP). I also see where the failing
process originally establishes connectivity with rtpproxy successfully
(the failing process here is 15868):
Sep 27 00:36:20 -f ./opensips[15868]: [ID 309935 local1.debug]
DBG:core:init_mod_child: type=CHILD, rank=1, module=rtpproxy
Sep 27 00:36:20 -f ./opensips[15868]: [ID 389318 local1.debug]
DBG:rtpproxy:connect_rtpproxies: [RTPProxy] set list ffffffff5a6b59e0
Sep 27 00:36:20 -f ./opensips[15868]: [ID 423527 local1.debug]
DBG:rtpproxy:connect_rtpproxies: [Re]connecting sockets (1 > 0)
Sep 27 00:36:20 -f ./opensips[15868]: [ID 454524 local1.debug]
DBG:rtpproxy:connect_rtpproxies: connected xxxxxxxxxxxxxxx:22222
Sep 27 00:36:20 -f ./opensips[15867]: [ID 615994 local1.info]
INFO:rtpproxy:rtpp_test: rtp proxy <udp:xxxxxxxxxxxxxxx:22222> found,
support for it enabled
Sep 27 00:36:20 -f ./opensips[15868]: [ID 615994 local1.info]
INFO:rtpproxy:rtpp_test: rtp proxy <udp:xxxxxxxxxxxxxxx:22222> found,
support for it enabled
Sep 27 00:36:20 -f ./opensips[15870]: [ID 309935 local1.debug]
DBG:core:init_mod_child: type=CHILD, rank=3, module=tm
Is there a list of the rtpproxies and their connections? If there is
maybe, this is where the corruption is occurring?
Thanks
Nathaniel
On 9/18/12 12:57 PM, Nathaniel L Keeling III wrote:
Razvan,
I have copied the log file in the home directory of the server that
you have access to. I was pretty large, so I thought that would be
better. I also copied the opensip config file that we are using to
that directory.
Thanks
Nathaniel
On 9/18/12 11:57 AM, Răzvan Crainea wrote:
Hi, Nathaniel!
The lack of media is not the problem. It seems like one of the
OpenSIPS processes (pid 28602) doesn't initiate a proper
communication channel with RTPproxy, or some data was corrupted. Can
you please send me (privately if preferred) OpenSIPS logs so I can
check this?
Best Regards,
Razvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com
On 09/18/2012 06:45 PM, Nathaniel L Keeling III wrote:
Hello,
I am testing our new Opensips setup with SEMS and RTPProxy and I am
seeing these errors in the log file. Client A and B are both
natted. Client A calls client B. Client B is unavailable so call
gets routed to SEMS for voicemail. I see this error on sending the
200 reply back to SEMS. I am not receiving any audio and I am
thinking this may be the reason. Any help would be appreciated. I
am using the residential script generated from the menuconfig
option and the latest version of rtpproxy, 1.2.1.
Sep 18 00:59:17 -f ./opensips[28602]:
ERROR:rtpproxy:send_rtpp_command: can't send command to a RTP proxy
Invalid argument
Sep 18 00:59:17 -f ./opensips[28602]: [ID 848861 local1.error]
ERROR:rtpproxy:send_rtpp_command: proxy <udp:xxxxxx.xxxx.com:22222>
does not respond, disable it
Sep 18 00:59:17 -f ./opensips[28602]: [ID 863797 local1.debug]
DBG:rtpproxy:raise_rtpproxy_event: no event sent
Sep 18 00:59:17 -f ./opensips[28602]: [ID 338976 local1.error]
ERROR:rtpproxy:force_rtp_proxy_body: cannot lookup a session on a
different RTPProxy
Thanks
Nathaniel
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
