Configuring oversip as proxy

141 views
Skip to first unread message

Zhainar Zhanekenoff

unread,
Jan 30, 2016, 5:50:58 AM1/30/16
to OverSIP
Hi, how can I configure oversip as proxy between Browser and SIP server?
I tried to connect with jsSIP on browser side, but connection to websocket failed. 

"WebSocket connection to 'ws://91.185.25.22:1900/' failed: Connection closed before receiving a handshake response"

I checked websocket here: http://www.websocket.org/echo.html
and got ERROR: undefined.

oversip.conf is next:
  core:
    nameservers                     :  null
    syslog_facility                 :  daemon
    syslog_level                    :  debug

  sip:
    sip_udp                         :  yes
    sip_tcp                         :  yes
    sip_tls                         :  yes
    enable_ipv4                     :  yes
    listen_ipv4                     :  91.185.25.22
    advertised_ipv4                 :  null
    enable_ipv6                     :  no
    listen_ipv6                     :  null
    advertised_ipv6                 :  null
    listen_port                     :  5065
    listen_port_tls                 :  5066
    use_tls_tunnel                  :  yes
    listen_port_tls_tunnel          :  5067
    callback_on_client_tls_handshake:  yes
    local_domains                   :  null
    tcp_keepalive_interval          :  300
    record_route_hostname_tls_ipv4  :  null
    record_route_hostname_tls_ipv6  :  null

  websocket:
    sip_ws                          :  yes
    sip_wss                         :  no
    enable_ipv4                     :  yes
    listen_ipv4                     :  91.185.25.22
    advertised_ipv4                 :  null
    enable_ipv6                     :  no
    listen_ipv6                     :  null
    advertised_ipv6                 :  null
    listen_port                     :  1900
    listen_port_tls                 :  null
    use_tls_tunnel                  :  yes
    listen_port_tls_tunnel          :  10444
    callback_on_client_tls_handshake:  yes
    max_ws_message_size             :  65536
    max_ws_frame_size               :  65536
    ws_keepalive_interval           :  300

  tls:
    public_cert                     :  /etc/oversip/tls/demo-tls.oversip.net.crt
    private_cert                    :  /etc/oversip/tls/demo-tls.oversip.net.key
    ca_dir                          :  /etc/oversip/tls/ca/
    full_cert                       :  /tmp/oversip_full_cert_20160130-34708-p1kfxl


proxies.conf is default

and in server.rb 

I only replaced
proxy.route request
on
proxy.route request, "192.168.21.7", 5065, :udp.

Iñaki Baz Castillo

unread,
Jan 30, 2016, 5:53:35 AM1/30/16
to oversip
The logs should tell you what is happening. I'm sorry but I cannot
figure it out with the above information.
> --
> You received this message because you are subscribed to the Google Groups
> "OverSIP" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to oversip+u...@googlegroups.com.
> To post to this group, send email to ove...@googlegroups.com.
> Visit this group at https://groups.google.com/group/oversip.
> For more options, visit https://groups.google.com/d/optout.



--
Iñaki Baz Castillo
<i...@aliax.net>

Zhainar Zhanekenoff

unread,
Feb 1, 2016, 1:27:20 AM2/1/16
to OverSIP
logs told me next:

ERROR: <SIP WS IPv4 server> error obtaining remote IP/port (SocketError: getnameinfo: Non-recoverable failure in name resolution), closing connection
ERROR: <SIP WS IPv4 server> error obtaining remote IP/port (SocketError: getnameinfo: Non-recoverable failure in name resolution), closing connection
ERROR: <SIP TCP IPv4 server> error obtaining remote IP/port (SocketError: getnameinfo: Non-recoverable failure in name resolution), closing connection

суббота, 30 января 2016 г., 16:53:35 UTC+6 пользователь Iñaki Baz Castillo написал:

Iñaki Baz Castillo

unread,
Feb 1, 2016, 2:39:36 AM2/1/16
to oversip
Reply all
Reply to author
Forward
0 new messages