[OpenSIPS-Users] TLS handshake failing

[Diego Carvalho Domingos]

Hi all, I'm trying to set up opensips with TLS enabled. I followed the webnair 
to install opensips and the advanced tutorial about TLS. Everything seems to be 
configured correctly but when I try to register using TLS it fails. I tried 
both latest LTS version and the master version of opensips, Bria and Linphone 
softphones and the default and customized TLS certificates. For all tests I got 
this log:

Jan 20 15:41:27 devmachine /usr/local/opensips/sbin/opensips[3318]: 
DBG:core:probe_max_sock_buff: getsockopt: snd is initially 262142
Jan 20 15:41:27 devmachine /usr/local/opensips/sbin/opensips[3318]: 
INFO:core:probe_max_sock_buff: using snd buffer of 255 kb
Jan 20 15:41:27 devmachine /usr/local/opensips/sbin/opensips[3318]: 
INFO:core:init_sock_keepalive: -- TCP keepalive enabled on socket
Jan 20 15:41:27 devmachine /usr/local/opensips/sbin/opensips[3318]: 
DBG:core:print_ip: tcpconn_new: new tcp connection to: 192.168.14.26
Jan 20 15:41:27 devmachine /usr/local/opensips/sbin/opensips[3318]: 
DBG:core:tcpconn_new: on port 50853, type 3
Jan 20 15:41:27 devmachine /usr/local/opensips/sbin/opensips[3318]: 
DBG:core:tls_tcpconn_init: entered: Creating a whole new ssl connection
Jan 20 15:41:27 devmachine /usr/local/opensips/sbin/opensips[3318]: 
DBG:core:tls_tcpconn_init: looking up socket based TLS server domain 
[192.168.14.23:5061]
Jan 20 15:41:27 devmachine /usr/local/opensips/sbin/opensips[3318]: 
DBG:core:tls_find_server_domain: virtual TLS server domain not found, Using 
default TLS server domain settings
Jan 20 15:41:27 devmachine /usr/local/opensips/sbin/opensips[3318]: 
DBG:core:tls_tcpconn_init: found socket based TLS server domain [0.0.0.0:0]
Jan 20 15:41:27 devmachine /usr/local/opensips/sbin/opensips[3318]: 
DBG:core:tls_tcpconn_init: Setting in ACCEPT mode (server)
Jan 20 15:41:27 devmachine /usr/local/opensips/sbin/opensips[3318]: 
DBG:core:tcpconn_add: hashes: 613, 3
Jan 20 15:41:27 devmachine /usr/local/opensips/sbin/opensips[3318]: 
DBG:core:handle_new_connect: new connection: 0x7f3aeafa9eb8 25 flags: 0002
Jan 20 15:41:27 devmachine /usr/local/opensips/sbin/opensips[3318]: 
DBG:core:send2child: to tcp child 0 0(3314), 0x7f3aeafa9eb8 rw 1
Jan 20 15:41:27 devmachine /usr/local/opensips/sbin/opensips[3314]: 
DBG:core:handle_io: We have received conn 0x7f3aeafa9eb8 with rw 1
Jan 20 15:41:27 devmachine /usr/local/opensips/sbin/opensips[3314]: 
DBG:core:io_watch_add: io_watch_add op on 20 (0x84d120, 20, 2, 
0x7f3aeafa9eb8,1), fd_no=1
Jan 20 15:41:27 devmachine /usr/local/opensips/sbin/opensips[3314]: 
DBG:core:tcp_read_req: Using the global ( per process ) buff
Jan 20 15:41:27 devmachine /usr/local/opensips/sbin/opensips[3314]: 
DBG:core:tls_update_fd: New fd is 20
Jan 20 15:41:27 devmachine /usr/local/opensips/sbin/opensips[3314]: 
DBG:core:tcp_read_req: Using the global ( per process ) buff
Jan 20 15:41:27 devmachine /usr/local/opensips/sbin/opensips[3314]: 
DBG:core:tls_update_fd: New fd is 20
Jan 20 15:41:27 devmachine /usr/local/opensips/sbin/opensips[3314]: 
INFO:core:tls_accept: New TLS connection from 192.168.14.26:50853 accepted
Jan 20 15:41:27 devmachine /usr/local/opensips/sbin/opensips[3314]: 
DBG:core:tls_accept: new TLS connection from 192.168.14.26:50853 using 
TLSv1/SSLv3 AES256-SHA 256
Jan 20 15:41:27 devmachine /usr/local/opensips/sbin/opensips[3314]: 
DBG:core:tls_accept: local socket: 192.168.14.23:5061
Jan 20 15:41:27 devmachine /usr/local/opensips/sbin/opensips[3314]: 
INFO:core:tls_accept: Client did not present a TLS certificate
Jan 20 15:41:27 devmachine /usr/local/opensips/sbin/opensips[3314]: 
INFO:core:tls_dump_cert_info: tls_accept: local TLS server certificate subject: 
/C=XY/ST=Some State/O=My Large Organization Name/OU=My Subunit of Large 
Organization/CN=somename.somewhere.com/emailAddress=r...@somename.somewhere.com,
 issuer: 
/CN=Your_NAME/ST=Your_STATE/C=CO/emailAddress=YOUR_EMAIL/O=YOUR_ORG_NAME
Jan 20 15:41:27 devmachine /usr/local/opensips/sbin/opensips[3314]: 
DBG:core:tls_update_fd: New fd is 20
Jan 20 15:41:27 devmachine /usr/local/opensips/sbin/opensips[3314]: 
DBG:core:tcp_read_req: read= 0 bytes, parsed=0, state=0, error=1
Jan 20 15:41:27 devmachine /usr/local/opensips/sbin/opensips[3314]: 
DBG:core:tcp_read_req: last char=0x00, parsed msg=#012
Jan 20 15:41:27 devmachine /usr/local/opensips/sbin/opensips[3314]: 
DBG:core:tcp_read_req: We didn't manage to read a full request. Back to child 
poll
Jan 20 15:41:27 devmachine /usr/local/opensips/sbin/opensips[3314]: 
DBG:core:tcp_read_req: tcp_read_req end
Jan 20 15:41:27 devmachine /usr/local/opensips/sbin/opensips[3314]: 
DBG:core:tcp_read_req: Using the per connection buff
Jan 20 15:41:27 devmachine /usr/local/opensips/sbin/opensips[3314]: 
DBG:core:tls_update_fd: New fd is 20
Jan 20 15:41:27 devmachine /usr/local/opensips/sbin/opensips[3314]: 
INFO:core:_tls_read: TLS connection to 192.168.14.26:50853 closed cleanly
Jan 20 15:41:27 devmachine /usr/local/opensips/sbin/opensips[3314]: 

Re: [OpenSIPS-Users] rtpproxy sends rtp from caller to callee before 200OK

[symack]

Can you please post where you are using rtpproxy_offer/_answer?​

Nick from Toronto.
​
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Rtpproxy issue with serial forking

[John Nash]

I have used opensips+rtpproxy for years for simple scenarios but now I am
trying to use it with serial forking. My flow is

UA---Invite ---Opensips
   1 Branch
---Media Server
Session
Progress-
   2 Branch (0n failure
message)-Some Gateway
  --Second session
progress--

My issue is SIP UA receives two session progress messages with different
ports from rtpproxy. UA should receive same port in both session progress
?? isnt it?.Where should I call rtpproxy_offer and rtpproxy_answer and
delete for this to achieve?

John
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] rtpproxy sends rtp from caller to callee before 200OK

[Marco Hierl]

Dear all,

first of all I need to apologize that I was not able to find information about 
this issue although I’m sure that I’m not the first one complaining!

The caller is sending an INVITE via OpenSIPS and rtpproxy_offer() is executed, 
callee answers with REPLY 180 or REPLY 183 (with SDP) and rtpproxy_answer() is 
made. In this status it should be ok that the rtp stream from callee to caller 
is transferred via the rtpproxy (e.g. for announcements), but I can see that 
rtp stream from caller to callee is transferred too!!! This means that there 
can be a conversation without receiving the 200OK and what is the real problem: 
that means (at least for me) they can talk to each other without any charging 
!! A timer will stop the conversion after the a while, but this can take time.

How can I overcome this problem? How can prevent RTP to be send to the callee 
before REPLY 200 is received?

I can’t find any help in the RTPproxy protocol 
http://www.b2bua.org/wiki/RTPproxy/Protocol, nor in the rtpproxy module 
description in OpenSIPS.

Thanks for your ideas, and best regards
  Marco

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users