Portsip Webrtc Gateway User Guide
Portsip Webrtc Gateway User Guide
Trademarks
®
PortSIP , the PortSIP logo and the names and marks associated with PortSIP products are trademarks and/or service
marks of PortSIP Solutions, Inc. and are registered and/or common law marks in the United States and various other
countries. All other trademarks are property of their respective owners. No portion hereof may be reproduced or
transmitted in any form or by any means, for any purpose other than the recipient's personal use, without the express
written permission of PortSIP.
Patent Information
The accompanying product may be protected by one or more U.S. and foreign patents and/or pending patent
applications held by PortSIP Solutions, Inc.
Disclaimer
While PortSIP uses reasonable efforts to include accurate and up-to-date information in this document, PortSIP makes
no warranties or representations as to its accuracy. PortSIP assumes no liability or responsibility for any typographical or
other errors or omissions in the content of this document.
Limitation of Liability
PortSIP and/or its respective suppliers make no representations about the suitability of the information contained in this
document for any purpose. Information is provided “as is” without warranty of any kind and is subject to change without
notice. The entire risk arising out of its use remains with the recipient. In no event shall PortSIP and/or its respective
suppliers be liable for any direct, consequential, incidental, special, punitive or other damages whatsoever (including
without limitation, damages for loss of business profits, business interruption, or loss of business information), even if
PortSIP has been advised of the possibility of such damages.
Customer Feedback
We are striving to improve our documentation quality and we appreciate your feedback. Email your opinions
and comments to [email protected].
Visit the PortSIP® WebRTC Gateway for information on PortSIP software versions and administrative documentation, and
PortSIP release notes.
®
PortSIP WebRTC Gateway User Guide .............................................................................................1
1. The WebRTC Gateway Architecture ................................................................... 4
2. How it works? ....................................................................................................... 4
3. Install WebRTC Gateway ..................................................................................... 5
4. Manage WebRTC Gateway .................................................................................. 5
4.1 Configuring WebRTC Gateway by Wizard ................................................................................. 5
4.2 Settings ......................................................................................................................................... 6
5. Run WebRTC Web Client ..................................................................................... 8
6. Deployment Practices ........................................................................................ 10
6.1 Deploy WebRTC Gateway with official certificate ................................................................... 10
6.2 Deploy WebRTC Gateway with Self-signed certificate in LAN ............................................... 11
This document assumes that the Windows OS are already deployed and that Microsoft administrators
are available to administrators PortSIP WebRTC Gateway.
2. How it works?
PortSIP WebRTC Gateway sits at the network edge to bridge the traditional operator network
(PSTN/VoIP Provider/SIP Trunking/IP PBX) with the Web Browser, letting carriers build Web services
on top of it. The gateway essentially turns any Web page into a telephone that the network can dialogue
with as it would a phone.
Since the traditional operator network (PSTN/VoIP Provider/SIP Trunking) and SIP devices (IP Phone,
Softphone) don’t support the newest WebRTC standards such as TURN, DTLS-RTP, RTC-FB, ICE,
therefor we need the WebRTC Gateway to transform the signaling and RTP streams. That’s why the
Gateway is works like a bridge.
When the user make calls in Web Browser, the WebRTC Gateway will transform the Signaling to
standard SIP message and route calls to PSTN/VoIP Provider/SIP Trunking/IP PBX. After the call
established, the WebRTC Gateway receive RTP stream from browser and transcode it then send to
PSTN/VoIP Provider/SIP Trunking/IP PBX and vice versa.
You can set the WebRTC Gateway HTTP and HTTPS listen port during installation, the default HTTP
port is 9288, HTTPS ports is 9287 – Please ensure the port that doesn’t using by other
applications otherwise the HTTP/HTTPS service will fails.
After the WebRTC Gateway successfully installed, you can double click the Management Console on
your Windows desktop, which will open the Management Console.
You can also use this URL remotely to manage the Gateway: http://gatweayIP:port/manager/index.html
(the gawayIP is the IP of the server which you installed the Gateway, the port is the HTTP port which
you specify during your install the gateway).
Username: admin
Password: admin
Once the “Listen WSS” is selected, you should set below fields:
WSS port: set a port which is for the WSS, for example 10443.
Domain Name: Your WebRTC Gateway domain name, it’s must resolvable, if you don’t have
domain name of Gateway server, enter the Gateway IP.
PortSIP Solutions, Inc 5
Certificate File: for WSS, you must upload the certificate file. You can generate the SSL
certificate file by yourself or purchase a certificate from provider such as Thawte or Digicert.
The certificate must matched the WebRTC Gateway domain.
Password of Private key: the password of private key file which is you entered when you
generate the certificate file. If no password for private key then leave it blank.
Note: If you haven’t a valid certificate, and don’t know how to create a Self-
signed certificate, you can upload the sample certificate(server.crt and
server.key) which is in Gateway installed folder, e.g.: “C:\Program
Files\PortSIP\WebRTC”.
1. SIP Domain: specify your SIP Domain here here, it’s can be an IP address or domain.
2. Use DNS SRV records: If your SIP Domain support DNS SRV, you can select this option.
If the DNS SRV is enabled, next steps will be skipped.
3. The server address is same as SIP domain: this option default is selected. Please un-selected
it if your SIP server address is not same as SIP Domain.
4. SIP Server Address: if your SIP Server address is not same as SIP Domain, you MUST specify
your SIP server address here.
5. SIP Transport: your SIP server transport, usually is UDP.
6. Server Port: your SIP server port.
Note: after you clicked the Save button, the WebRTC Gateway will restart, you have to sign in the
management console again.
4.2 Settings
4.2.1 Log
You can enable/disable WebRTC log by select/un-select “Enable SipMessage Logging” option, and
choose the log level. The log file will be generated in WebRTC Gateway installed folder, the name is
“webrtcgw.log”. You must restart WebRTC Gateway to take effect.
Click the “Settings” in the WebRTC Gateway Management Console and set the stun server IP as the
Run stunerver PC IP, the port default is 3478.
You can change to any other port as you want. Https is request 4.1.1 step to upload a valid certificate.
Once the web client registered, you can make & receive calls with other SIP client.
Once the web client registered, you can make & receive calls with other SIP client.
You can purchase an official certificate from the certificate provider such Thawte or Digicert in order to
avoid the security alert and don’t need add the security exception manually.
During you purchase the certificate, you should generate the private key and CSR by yourself – please
read the provider’s instructions or ask the provider support. We recommend you don’t set the password
for private key file. You must keep the private key file by yourself.
Assume we purchased a certificate from Thawte (in case we use the Thawte SSL123 certificate as
example) for domain examplertc.com. After you downloaded the certificate .zip file, just extract it, there
has IntermediateCA.crt and ssl_certificate.crt, you will need to use a plain text editor (for example
Windows Notepad, don’t use MS Word) to combine your two certs with them into one file:
copy all text from IntermediateCA.crt and append to ssl_certificate.crt, the ssl_certificate.crt at the top
and IntermediateCA.crt at the bottom.
1. Ensure the domain examplertc.com has been resolve correct to the server which you installed
the PortSIP WebRTC Gateway.
2. Assume the SIP server address is 69.164.210.98, the SIP Domain is: sip.testsip.com, the
transport is UDP on port 5060, it has SIP user 100, 101, 102, 103, 104.
For Firefox:
Below settings are for last version Firefox.
1. Assume we have a SIP Server/PBX which IP 192.168.0.98 and SIP domain is 192.168.0.98,
this server/PBX use the UDP transport on port 5060, it has SIP user 100, 101, 102, 103, 104.
2. Assume we installed the WebRTC Gateway on a server which IP is 192.168.0.28.
3. Use browser open http://192.168.0.28:9288/manager/index.html, sign in the Management
Console with admin/admin.
4. Click the “Wizard” on left and click the “Next” button.
5. Enter 192.168.0.28 for the “Gateway IP Address” filed.
6. Click the “Next” button.
7. Enter the SIP Domain, in case it is 192.168.0.98.
8. Select the SIP Transport as UDP.
9. The Server port is: 5060.
10. Click the “Save” button, the WebRTC Gateway will be restart automatically, you will need to
sign in management console again.
11. If in LAN the WebRTC Gateway can’t access the internet, Download the STUN Server then
extract stunserver.zip and run stunserver.exe.
12. Click the “Settings” in the WebRTC Gateway Management Console and set the stun server as
192.168.0.28:3478.
13. Open http://192.168.0.28:9288/portgo/index.html by last version Firefox.
14. SIP Username filed: enter a name as 100.
15. SIP password filed: enter the password of SIP user 100.
16. SIP Domain in case is: sip.testsip.com.
17. WS URI: in case is ws://192.168.0.28:10080 (the IP is WebRTC Gateway IP and WS port).
18. Press “enter” button
19. Once the web client registered, you can make & receive calls with other SIP client.