We often hear the questions:
We decided to answer these questions and created a detailed performance test for OpenSER and SIP Express Router. To simulate a production environment, the SIP proxy under test queries an external OSP server for routing information on each and call and then reports call detail records to an external OSP server. Five destinations are returned to the SIP proxy for each call in random order. Four of the five destinations simulate call failure scenarios so the SIP proxy must retry the call an average of two times before the call is completed. These tests were performed on a single core of an Intel Xeon 5140 2.33 GHz CPU.
Here is a brief summary of what we learned. For all the test details, click here.
-
The performance of OpenSER V1.2 and SER 2.0 are not materially different, however, there are two minor differences.
-
SER V2.0 requires less memory.
-
OpenSER V1.2 has less post dial delay.
-
By all measures, OpenSER V1.2 is significantly better than OpenSER V1.1.
-
For production operation (with call retries and CDR reporting), we suggest the following simple guideline for sizing server hardware to operate at 60% CPU utilization for OpenSER V1.2 and SER V2.0:
One GHz of CPU processing capacity can manage 60 calls per second.
For example, a server with two, dual core, 3.0 GHz CPUs would effectively have (2 CPUs * 2 cores * 3 GHz per CPU) twelve GHz of CPU processing capacity. This server, hosting either OpenSER V1.2 or SER 2.0, would be able to manage 720 calls per second at approximately 60% CPU utilization.
The following chart plots CPU utilization as a function of calls per second. The results for OpenSER V1.2 and SER 2.0 are identical. The performance of OpenSER V1.2 is 13% better than OpenSER V1.1.
Memory is not a major resource requirement, even at high loads. SER 2.0 has the lowest memory requirement.
The data on the following chart is an indirect indication of Post Dial Delay (PDD). The data presented is the percentage of calls in each test that experienced a PDD greater than six seconds.
The following chart presents the percentage of calls which were not completed successfully for each test. When CPU utilization was less 90%, both OpenSER V1.2 and SER 2.0 completed all calls successfully.
分享到:
相关推荐
KAMAILIO(OpenSER)-健壮,安全和可扩展的开源(GPL)SIP(RFC3261)服务器实施,具有大型功能集(超过90个扩展模块)。 截至2009年5月,源代码由GIT存储库托管,网址为http://sip-router.org。
基于开源Openser的内网SIP客户端的管理研究和实现,李义君,吴军,SIP协议是NGN中的一个重要协议,由于它是基于文本的一个协议,使用起来更加地灵活,掌握也更加容易,因此目前出现了很多基于该协议
openSER 完整介绍 We are starting a new era in the collaboration area. Voice and Video over IP are starting to dominate the world of telecommunications in a disruptive movement capable of changing ...
OpenSIPS(以前的OpenSER)是多功能SIP服务器的GPL实现,旨在提供用于专业SIP服务器平台的高级技术解决方案(性能,安全性和质量)。 重要提示:这不再是项目的主要托管。 这已在GITHUB上移动-...
免费的VOIP网络电话,Android平台SIP客户端 支持服务端: Cisco CallManager, OpenSER, Kamailio, OpenSIPS, Asterisk, ...支持DTMF: 发送DTMF tone(RFC2833 and SIP INFO), 检测DTMF tone(RFC2833 and SIP INFO).
Openser软交换系统的早期版本OpenSer-1.2.3-tls_src
Building Telephony Systems With OpenSER 原文翻译为中文版本
当时的项目名称是SIP Express Router(又名SER)。 2005年,创建了一个名为OpenSER的叉子,由于商标问题,该叉子在2008年7月更名为Kamailio。 从2008年秋天开始,Kamailio和SER启动了合并这两个项目的过程。 合并...
openser的配置说明,包括注册,认证,NAT穿越,计费(freeradius和cdrtool的安装与配置).
手把手教你安装VOIP、SIP服务器,最新版本电子书,经典。免费提供,此为PART2,一共2部分。
会话初始化协议是互联网工程任务组(IETF)制定的协议标准,在多个RFC(Request for Comments)文档中被进行了描述说明。RFC3261是最近的一个RFC,一般称它为SIP版本2。SIP是一个应用层的协议,用来建立,修改,终止...
基于openSER的register 包
利用开源的Sofia- SIP库来开发SIP用户代理,采用OpenSER作为SIP服务器。另外可以使用PHP脚本开发一个支持SIP消息发送的网络平台,发送作为控制消息的SIP即时消息,适用于手机上的web浏览器。实验结果表明,设计的系统...
用于管理 OpenSER SIP 服务器的 Web 界面。
linux系统下sip开源服务器kamailio的源码,kamailio前身是openSER,本人编译通过可使用,安装配置稍麻烦,官方指导http://www.kamailio.org/dokuwiki/doku.php/install:kamailio-3.0.x-from-git 这类资源官方都有...
使用OpenSER构建电话通信系统.docx
手把手教你安装VOIP、SIP服务器,最新版本电子书,经典。免费提供,此为PART1,一共2部分。
Kamailio是一个开源的SIP服务器,原名OpenSER Kamailio is an Open Source, GPL2, SIP Server Routing ... It is written in C for Linux/Unix plaforms and focuses on performance, flexibility and security.