otakudang.org (v2.0)

“CODEC anu itu butuh bw-nya brapa sih?”

Sering banget dapet pertanyaan ini. Dan kebetulan sekali ada thread di forum ASTERISK.ID yang menanyakan hal sama.

(Terima kasih mas Asoka!)

Jadi, jika ada codec yang di tabel disebutkan bw nya 64kbps, itu kalo jalan di jalur “bersih” seperti E1, DS0, dan teman-temannya. Ketika masuk ke ranah Internet Protocol (IP), akan ada penambahan header IP dan UDP yang mengakitbatkan konsumsi bw jadi bengkak sedikit, menjadi kurang lebih 85 – 87 kbps an.

Itu baru satu arah. Kalo ngobrol di telpon pastinya dua arah, jadi harus dikalikan dua, kira-kira menjadi 170 – 174kbps an per call. Untuk lebih lengkapnya bisa dibaca di:

https://www.voip-info.org/wiki/view/Bandwidth+consumption

Dan berikut tabel untuk mudah jadi pengingat (terutama untuk saya sendiri):

*NEB: Normal Ethernet Bandwidth

Pas lagi create database untuk OpenSIPS, saya mendapati error berikut:

# opensipsdbctl create
 MySQL password for root:
 INFO: test server charset
 INFO: creating database opensips ...
 INFO: Using table engine InnoDB.
 INFO: Core OpenSIPS tables successfully created.
 Install presence related tables? (y/n): y
 INFO: creating presence tables into opensips ...
 ERROR 1101 (42000) at line 2: BLOB, TEXT, GEOMETRY or JSON column 'extra_hdrs' can't have a default value
 ERROR: Failed to create presence tables!

Setelah baca sana sini ternyata ini berhubungan dengan setting MySQL yang terlalu strict. Untuk mengakali sementara, edit file my.cnf dan tambahkan baris berikut:

[mysqld]
 sql-mode = ""

kemudian restart layanan MySQL. Ulangi lagi proses penambahan database OpenSIPS, jika lancar akan seperti ini:

# opensipsdbctl create
 MySQL password for root:
 INFO: test server charset
 INFO: creating database opensips ...
 INFO: Using table engine InnoDB.
 INFO: Core OpenSIPS tables successfully created.
 Install presence related tables? (y/n): y
 INFO: creating presence tables into opensips ...
 INFO: Presence tables successfully created.
 Install tables for imc cpl siptrace domainpolicy carrierroute userblacklist b2b cachedb_sql registrant call_center fraud_detection emergency? (y/n): y
 INFO: creating extra tables into opensips ...
 INFO: Extra tables successfully created.

Wah, belum sampe lama memanfaatkan AsteriskNow agak lama, baru-baru ini muncul komunitas yang sudah melakukan forking dari project Elastix. Ini kabar yang cukup menggembirakan. Artikel mengenai pengembang Issabel ini bisa dibaca di web berikut:

http://www.issabel.org/

Dan ada juga artikel berbahasa spanyol :

https://www.sinologic.net/blog/2016-12/la-comunidad-elastix-crea-el-proyecto-issabel.html

Berikut adalah terjemahannya:

===========================================================================================================

The Elastix community creates the ISSABEL project

This December is quite frantic, perhaps because of the importance of the theme and is that, as we announced last week, 3CX has bought the brand Elastix and the entire ecosystem (forums, lists, emails, etc.) so that The community has taken action in the matter and has created an Elastix fork which they have christened ISSABEL.

Unlike Elastix, the new ISSABEL project is not based on the system of ” benevolent dictator ” consisting of a single company that controls and manages the project from start to finish with the condition of being “benevolent”, but it ISSABEL born Directly from the own members of the Elastix community and keeps the door open to the rest of the community to enter the project and actively participate.

Within the community there are developers, system administrators, Linux and Asterisk experts, and companies that want a communications system with which to work, modify, distribute … so the ISSABEL project is not only maintained by users related to The philosophy of free software and free unified communications, if not also by companies that will provide business support and quality services to all those who require it. The difference with Elastix is that decisions on the “core” will not be taken unilaterally by a single entity but it will be by consensus of the general community using the usual social channels ( forums, twitter, lists, etc. ) for Agree on the decisions and direction of the project.

ISSABEL: the new Elastix

ISSABEL is based on the GPL version of the Elastix 4 project, a distribution that, as many remember, the members of the community came together to make an economic crownfunding and to give a boost to the project, among other things, to update the system Operative to CentOS 7, to update the versions of diverse free projects, reason why it is 100% legal, ethical and does not have any type of legal problem as some people and webs suggest. Any user of Elastix 4 does not have to do anything to continue receiving updates, only to change the repositories to use those of ISSABEL instead of the old Elastix systems and the system will be updated as normal.

As you can see, the only thing that changes in the interface is the name, and therefore, all the functionalities will continue working as before.

For all purposes, Elastix 4 passes called ISSABEL and any user who was already working with Elastix 4, you can continue working as normal with ISSABEL.

More information: http://www.issabel.org