Sip server Brekeke

We used Brekeke SIP server to run our SIP applications . Although there are newer versions of Brekeke SIP server out now . More awesome than before , we prefer using the old one for the sake of not messing with legacy SIP applications . The official site for brekeke is – http://www.brekeke.com/sip/ .

A general architecture of Brekeke SIP server is .

Here are the steps of installing and configuring a Brekeke SIP server .

Step 1: Download the Server form http://www.brekeke.com/sip/ and run the setup file .

brekeke0

brekeke01

brekeke1

brekeke8

Step 2: It is always good to give a look to README file .

Step 3: Run the local implementation of SIP server at localhost or 127.0.0.1 at port 8080

Step 4: Important is to get the license which will help us activate the SIP server . One can obtain a free license from http://www.brekeke.com/downloads/sip-server-trial-license.php

Step 5 : Once the license is activates , we can goto the console screen after loggin with default username and password sa .

Step 6 : Once we are at console , we could add/ delete / modify parameters like port , start/shutdown status etc . Step 7 : Once the server is all setup , just add the IP and port of SIP server to SIP clients server filed . Now all the SIP request and response will be catered by this SIP Server

TeleMedicine and WebRTC November 24, 2020
The solution enables doctors / nurses / medical practitioners and patients to do High definition Audio/video calls End to end encrypted p2p chats Integration with HMS ( hospital management system ) to fetch history of the patients Screens sharing to show reports without transferring them as files Include more concerned people of doctors using Mesh based pee […]
Performance of WebRTC sites and electron apps October 3, 2020
As security is a broad topic touching on many sections of WebRTC this section is not meant to address all topics but instead to focus on specific “hot spots”, areas that require special attention due to the unique properties of the WebRTC service. There are several security related topics that are of particular interest with respect to WebRTC. They can be g […]
5G September 26, 2020
striking features of 5G - entirely IP based ability to connect 100x more devices ( IOT favourable ) speed upto 10 Gbit/s high peak bit rate high data volume per unit area virtually 0 latency hence high response time
General Data Protection Regulation (GDPR) in VoIP June 27, 2020
GDPR , Europe’s digital privacy legislation passed in 2018, replaces the 1995 EU Data Protection Directive. It is rules designed to give EU citizens more control over their personal data & strengthen privacy rights. It aims to simplify the regulatory environment for business and citizens. To read about other Certificates , compliances and Security in VoI […]
Media Architecture June 22, 2020
With the sudden onset of Covid-19 and building trend of working-from-home , the demand for building scalable conferncing solution and virtual meeting room has skyrocketed . Here is my advice if you are building a auto- scalable conferencing solution
WebRTC Audio/Video Codecs May 5, 2020
Codecs signifies the media stream’s compession and decompression. For peers to have suceesfull excchange of media, they need a common set of codecs to agree upon for the session . The list codecs are sent between each other as part of offeer and answer or SDP in SIP. As WebRTC provides containerless bare mediastreamgtrackobjects. Codecs … Continue reading W […]
Attacks on SIP Networks April 12, 2020
Major standards bodies including 3GPP, ITU-T, and ETSI have all adopted SIP as the core signalling protocol for services such as LTE , VoIP, conferencing, Video on Demand (VoD), IPTV (Internet Television), presence, and Instant Messaging (IM) etc. With the continous evolution of SIP as the defacto VoIP protocol , we need to underatdn the … Continue reading A […]
HTTP/2 – offer/answer signaling for WebRTC call March 23, 2020
HTTP ( Hyper Text Transfer Protocol ) is the top application layer protocol atop the Tarnsport layer ( TCP ) and the Network layer ( IP ) HTTP/1.1 release in 1997. Since HTTP/1 allowed only 1 req at a time , HTTP/1.1 Allows one one outstanding connection on a TCP session but allowed request pieplinig … Continue reading HTTP/2 – offer/answer signaling for Web […]