[OpenSIPS-Users] ERROR:core:tls_accept: New TLS connection from 123.123.123.12:41556 failed to accept: rejected by client

Gary Nyquist Tue, 22 Jul 2014 17:26:26 -0700

Tried with CERT signed by Certificate Authority recognised by the SIP client.

Still same issue.

No change...

I have the Opensips and SEMS deployed on AWS.

Because of the private IP on the ethrenet of the AWS servers, I have configured the listen adddress like this:

listen=tls:10.0.0.100:5061 as 100.101.102.103:5061

I also use the script_helper module of OpenSIPS 1.11.2

The TLS errors are showing up, when the script_helper module is trying to route ACK/PRACK automatically.

I guess, the pvt & public IP of AWS is confusing the OpenSIPS.

Can anyone please advice how this can be fixed in the opensips.cfg?

Thanks

-Gary

Sent: Friday, July 18, 2014 at 5:21 PM
From: [email protected]
To: "OpenSIPS users mailling list" <[email protected]>
Subject: Re: [OpenSIPS-Users] WARNING:core:get_send_socket: protocol/port mismatch

Most likely the TLS certificate used by OpenSIPS is not signed by a Certificate Authority recognised by the SIP client.

Adrian

On 18 Jul 2014, at 18:08, Gary Nyquist <[email protected]> wrote:

Hi Bogdan,

Thanks for the response.

I have a bunch of SIP softphones pointing to the OpenSIPS.
The OpenSIPS is lestening on:
1. UDP/5060
2. TCP/5060
3. TLS/5061

The OpenSIPS is routing the calls(coming from the SIP softphones) to an SEMS media server,
The SEMS is listening only on UDP transport.

Everything works fine (no warnings/errors in the log file) when the softphones use UDP or TCP transport.
But when I put the softphones on TLS, following warning/errors messages showing up in the log file.

WARNING:core:get_send_socket: protocol/port mismatch
ERROR:core:tls_accept: New TLS connection from 123.123.123.12:41556 failed to accept: rejected by client

Not sure why "New TLS connection" error is showing up.

I am not using force_send_socket() in this scenario.
Would you suggest to use it?

Thanks again...

-Gary
Sent: Friday, July 18, 2014 at 6:31 AM
From: "Bogdan-Andrei Iancu" <[email protected]>
To: "OpenSIPS users mailling list" <[email protected]>, "Gary Nyquist" <[email protected]>
Subject: Re: [OpenSIPS-Users] WARNING:core:get_send_socket: protocol/port mismatch
Hi, That error means OpenSIPS detected a conflict when comes to what protocol to be used for sending out a requests - the protocol may be given by the RURI and in the same time by the forced socket. And RURI may say "TCP" and the used socket "UDP" -> conflict. Are you using the "force_send_socket()" function in this scenario ? Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 17.07.2014 23:41, Gary Nyquist wrote:
I am getting the following WARNING:

 

DBG:tm:t_relay_to: forwarding ACK

DBG:core:mk_proxy: doing DNS lookup...

DBG:core:get_send_socket: force_send_socket of different proto (3)!

WARNING:core:get_send_socket: protocol/port mismatch

 

 

I am using opensips 1.11.2 script_helper module.

I believe, the ACK is suppososed to be route automatically.

Any idea, why this WARNING ?

 

Thanks

-Gary

 

 

 

Hi,

 

I am getting this error in the log.

 

WARNING:core:get_send_socket: protocol/port mismatch
 

Any advice how to fix it?

 


Thanks

-Gary






 

 
 

_______________________________________________
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

_______________________________________________ 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

[OpenSIPS-Users] ERROR:core:tls_accept: New TLS connection from 123.123.123.12:41556 failed to accept: rejected by client

Reply via email to