Documentation

Documentation.Tutorials-WebSocket History

Hide minor edits - Show changes to markup

July 02, 2013, at 10:48 AM by 109.99.235.212 -
Changed line 36 from:

OverSIP has two basic configuration files that will need to be changed in order :

to:

OverSIP has two basic configuration files that will need to changed in order to achieve our desired functionality :

July 02, 2013, at 10:47 AM by 109.99.235.212 -
Changed line 52 from:
  • If you are using a pre 1.3.8 version, you need to edit the file and add request.fix_nat right after the def (OverSIP::SipEvents).on_request request line - basically we're forcing OverSIP to consider all requests as NAT-ed ( since we'll be using it only for Websocket clients, and they are considered NATed by default due to browser considerations )
to:
  • If you are using a pre 1.3.8 OverSIP version, you need to edit the file and add request.fix_nat right after the def (OverSIP::SipEvents).on_request request line - basically we're forcing OverSIP to consider all requests as NAT-ed ( since we'll be using it only for Websocket clients, and they are considered NATed by default due to browser considerations )
July 02, 2013, at 10:47 AM by 109.99.235.212 -
Changed lines 50-51 from:

server.rb ( by default located in /etc/oversip/server.rb ) contains the actual routing logic for the OverSIP server - written in Ruby. The default server.rb script is suitable for the purpose of WS to SIP gateway, so you shouldn't do any changes to it, with one single exception : \\

to:

server.rb ( by default located in /etc/oversip/server.rb ) contains the actual routing logic for the OverSIP server - written in Ruby. The default server.rb script is suitable for the purpose of WS to SIP gateway, so you shouldn't do any changes to it, with one single exception :