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
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 Rega
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, Ra(zvan Crainea wrote:
Hi,
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 rtpprox
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
Razva,
Yes, Great! I am currently running version 1.8.1 of Opensips.
Thanks
Nathaniel
On 9/27/12 3:02 AM, Răzvan Crainea wrote:
Hi, Nathaniel!
You are right, according to OpenSIPS error code, one of the send
function parameters is invalid, and most likely the file descriptor.
Unfortunatel
Hello,
Can anyone help me understand what might be causing the following error
messages to be reported by OpenSIPS?
2018-01-16 16:42:47 ERROR:rtpproxy:engage_rtp_proxy4_f: error forcing rtp
proxy
2018-01-16 16:42:48 ERROR:rtpproxy:force_rtp_proxy_body: unhandled rtpproxy
error: 71
2018-01-16 16:
Hi, John!
Those errors are reported by the RTPProxy server, and depending on the
error, they can be handled by opensips.
In your case, the errors 71 and 72 are reported by RTPProxy when it can
not create UDP listeners for media. Usually these errors are triggered
when rtpproxy runs out of avai
Hello Razvan,
I have just seen your response to my question.
Thank you for explaining the rtpproxy error messages.
I will try the -L parameter as you suggest. I think this will be the answer.
John Quick
Smartvox Limited
Web: www.smartvox.co.uk
> Hi, John!
>
> Those errors are reported by the RT
