<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><pre>Eric, Thanks for your reply,<br>My question is not about Kamailio. I just want to configure SIPS as SBC and I looking for wiki or some info if available to configure it as SBC.<br>Thanks<br>Abdul<br></pre><br><br><div>> From: users-request@lists.opensips.org<br>> Subject: Users Digest, Vol 80, Issue 52<br>> To: users@lists.opensips.org<br>> Date: Mon, 16 Mar 2015 19:00:06 +0100<br>> <br>> Send Users mailing list submissions to<br>> users@lists.opensips.org<br>> <br>> To subscribe or unsubscribe via the World Wide Web, visit<br>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users<br>> or, via email, send a message with subject or body 'help' to<br>> users-request@lists.opensips.org<br>> <br>> You can reach the person managing the list at<br>> users-owner@lists.opensips.org<br>> <br>> When replying, please edit your Subject line so it is more specific<br>> than "Re: Contents of Users digest..."<br>> <br>> <br>> Today's Topics:<br>> <br>> 1. Re: SBC for Kamailio or Metaswitch (malik sherif)<br>> 2. Re: SBC for Kamailio or Metaswitch (Eric Tamme)<br>> 3. Re: orchestration. (Tito Cumpen)<br>> 4. Re: SBC for Kamailio or Metaswitch (Terrance Devor)<br>> 5. Re: orchestration. (Eric Tamme)<br>> 6. 1.11.3 Crash on Fifo query (Kneeoh)<br>> 7. Re: [NEW] Emergency call handling module (R?zvan Crainea)<br>> <br>> <br>> ----------------------------------------------------------------------<br>> <br>> Message: 1<br>> Date: Mon, 16 Mar 2015 16:47:38 +0000<br>> From: malik sherif <asherif74@hotmail.com><br>> Subject: Re: [OpenSIPS-Users] SBC for Kamailio or Metaswitch<br>> To: "users@lists.opensips.org" <users@lists.opensips.org><br>> Message-ID: <BLU174-W44B9B10E107749E7E4F140AE020@phx.gbl><br>> Content-Type: text/plain; charset="iso-8859-1"<br>> <br>> <br>> <br>> <br>> <br>> Hello,<br>> I have configured Kamailio server and sisp on the same <br>> machine. Is their a link as to how to configure sips as SBC for <br>> Kamailio serer or Metaswitch?<br>> Thanks for you help<br>> <br>> <br>> <br>> <br>> <br>> <br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL: <http://lists.opensips.org/pipermail/users/attachments/20150316/4c1c0f7e/attachment-0001.htm><br>> <br>> ------------------------------<br>> <br>> Message: 2<br>> Date: Mon, 16 Mar 2015 10:49:01 -0600<br>> From: Eric Tamme <eric@uphreak.com><br>> Subject: Re: [OpenSIPS-Users] SBC for Kamailio or Metaswitch<br>> To: OpenSIPS users mailling list <users@lists.opensips.org><br>> Message-ID: <5507097D.1020203@uphreak.com><br>> Content-Type: text/plain; charset="windows-1252"; Format="flowed"<br>> <br>> This is not a mailing list for Kamailio.<br>> <br>> <br>> On 03/16/2015 10:47 AM, malik sherif wrote:<br>> ><br>> > Hello,<br>> > I have configured Kamailio server and sisp on the same machine. Is <br>> > their a link as to how to configure sips as SBC for Kamailio serer or <br>> > Metaswitch?<br>> > Thanks for you help<br>> ><br>> > ------------------------------------------------------------------------<br>> ><br>> ><br>> ><br>> ><br>> > _______________________________________________<br>> > Users mailing list<br>> > Users@lists.opensips.org<br>> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users<br>> <br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL: <http://lists.opensips.org/pipermail/users/attachments/20150316/3de92ef0/attachment-0001.htm><br>> <br>> ------------------------------<br>> <br>> Message: 3<br>> Date: Mon, 16 Mar 2015 12:53:32 -0400<br>> From: Tito Cumpen <tito@xsvoce.com><br>> Subject: Re: [OpenSIPS-Users] orchestration.<br>> To: OpenSIPS users mailling list <users@lists.opensips.org><br>> Message-ID:<br>> <CANZPVB7RXeohAwvOSwaxO_cjfo5v_ngkMUepgT-H4Pqaw_qLsA@mail.gmail.com><br>> Content-Type: text/plain; charset="utf-8"<br>> <br>> Terrance,<br>> <br>> <br>> Thanks for your two cents . The reason I ask is because I am hearing of<br>> aware of standards being drafted in this emerging need. I also need to<br>> weight the capabilities of opensips over sippservlets which by the way has<br>> some pretty effective ways of auto scaling :<br>> <br>> https://www.youtube.com/watch?v=Tsa0QgffZ28<br>> <br>> On Thu, Mar 12, 2015 at 6:00 PM, Terrance Devor <ter.devor@gmail.com> wrote:<br>> <br>> > 1) What is the best way?<br>> > - Finite number of ways to cook a potato<br>> > 2) Is there a way?<br>> > If there is a will... :)<br>> ><br>> > Terrance.<br>> > ?<br>> ><br>> > _______________________________________________<br>> > Users mailing list<br>> > Users@lists.opensips.org<br>> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users<br>> ><br>> ><br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL: <http://lists.opensips.org/pipermail/users/attachments/20150316/18b0d3cf/attachment-0001.htm><br>> <br>> ------------------------------<br>> <br>> Message: 4<br>> Date: Mon, 16 Mar 2015 13:02:43 -0400<br>> From: Terrance Devor <ter.devor@gmail.com><br>> Subject: Re: [OpenSIPS-Users] SBC for Kamailio or Metaswitch<br>> To: OpenSIPS users mailling list <users@lists.opensips.org><br>> Message-ID:<br>> <CA+w+2f-82ZaMBv0By1TeoQvxK3FXb59iqe7Xe8v8m69S3VANbg@mail.gmail.com><br>> Content-Type: text/plain; charset="utf-8"<br>> <br>> Or Metaswich for that matter...<br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL: <http://lists.opensips.org/pipermail/users/attachments/20150316/5a507578/attachment-0001.htm><br>> <br>> ------------------------------<br>> <br>> Message: 5<br>> Date: Mon, 16 Mar 2015 11:03:04 -0600<br>> From: Eric Tamme <eric@uphreak.com><br>> Subject: Re: [OpenSIPS-Users] orchestration.<br>> To: OpenSIPS users mailling list <users@lists.opensips.org><br>> Message-ID: <55070CC8.2010809@uphreak.com><br>> Content-Type: text/plain; charset="utf-8"; Format="flowed"<br>> <br>> There are many ways of building scalable signaling networks with <br>> OpenSIPS, how you do it depends on your needs, and your capability.<br>> <br>> -Eric<br>> <br>> On 03/16/2015 10:53 AM, Tito Cumpen wrote:<br>> > Terrance,<br>> ><br>> ><br>> > Thanks for your two cents . The reason I ask is because I am hearing <br>> > of aware of standards being drafted in this emerging need. I also need <br>> > to weight the capabilities of opensips over sippservlets which by the <br>> > way has some pretty effective ways of auto scaling :<br>> ><br>> > https://www.youtube.com/watch?v=Tsa0QgffZ28<br>> ><br>> > On Thu, Mar 12, 2015 at 6:00 PM, Terrance Devor <ter.devor@gmail.com <br>> > <mailto:ter.devor@gmail.com>> wrote:<br>> ><br>> > 1) What is the best way?<br>> > - Finite number of ways to cook a potato<br>> > 2) Is there a way?<br>> > If there is a will... :)<br>> ><br>> > Terrance.<br>> > ?<br>> ><br>> > _______________________________________________<br>> > Users mailing list<br>> > Users@lists.opensips.org <mailto:Users@lists.opensips.org><br>> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users<br>> ><br>> ><br>> ><br>> ><br>> > _______________________________________________<br>> > Users mailing list<br>> > Users@lists.opensips.org<br>> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users<br>> <br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL: <http://lists.opensips.org/pipermail/users/attachments/20150316/1ca4a74b/attachment-0001.htm><br>> <br>> ------------------------------<br>> <br>> Message: 6<br>> Date: Mon, 16 Mar 2015 17:37:14 +0000 (UTC)<br>> From: Kneeoh <kneeoh@yahoo.com><br>> Subject: [OpenSIPS-Users] 1.11.3 Crash on Fifo query<br>> To: Opensips Users <users@lists.opensips.org><br>> Message-ID:<br>> <948650354.613863.1426527434100.JavaMail.yahoo@mail.yahoo.com><br>> Content-Type: text/plain; charset=UTF-8<br>> <br>> I just spun up a light system for testing some new things. I've been getting system crashes while running get_statistics. I've included all of the data I have. I was hoping someone could point me towards a solution to fix. Thank you.<br>> <br>> <br>> Environment:<br>> <br>> Cores: 2 x <br>> Intel(R) Xeon(R) CPU E5-2680 0 @ 2.70GHz<br>> <br>> Memory: 8 Gb<br>> <br>> Opensips 1.11.3<br>> <br>> Children = 4<br>> <br>> <br>> S_MEMORY=1024<br>> P_MEMORY=64<br>> <br>> <br>> Command:<br>> <br>> opensipsctl fifo get_statistics all | grep udp<br>> <br>> <br>> Debug 6 Output during crash:<br>> <br>> Mar 16 16:47:23 opensips /usr/local/sbin/opensips[17059]: DBG:tm:timer_routine: timer routine:0,tl=0x7f4fda24cf58 next=0x7f4fda575850, timeout=88<br>> Mar 16 16:47:23 opensips /usr/local/sbin/opensips[17059]: DBG:tm:timer_routine: timer routine:0,tl=0x7f4fda575850 next=0x7f4fda5719f8, timeout=88<br>> Mar 16 16:47:23 opensips /usr/local/sbin/opensips[17059]: DBG:tm:timer_routine: timer routine:0,tl=0x7f4fda5719f8 next=0x7f4fda56d798, timeout=88<br>> Mar 16 16:47:23 opensips /usr/local/sbin/opensips[17049]: DBG:mi_fifo:mi_parse_tree: adding node <> ; val <all><br>> Mar 16 16:47:23 opensips /usr/local/sbin/opensips[17049]: DBG:mi_fifo:mi_parse_node: end of input tree<br>> Mar 16 16:47:23 opensips /usr/local/sbin/opensips[17049]: DBG:mi_fifo:mi_fifo_server: done parsing the mi tree<br>> Mar 16 16:47:24 opensips /usr/local/sbin/opensips[17049]: DBG:mi_fifo:mi_parse_tree: adding node <> ; val <all><br>> Mar 16 16:47:24 opensips /usr/local/sbin/opensips[17049]: DBG:mi_fifo:mi_parse_node: end of input tree<br>> Mar 16 16:47:24 opensips /usr/local/sbin/opensips[17049]: DBG:mi_fifo:mi_fifo_server: done parsing the mi tree<br>> Mar 16 16:47:25 opensips /usr/local/sbin/opensips[17049]: DBG:mi_fifo:mi_parse_tree: adding node <> ; val <all><br>> Mar 16 16:47:25 opensips /usr/local/sbin/opensips[17049]: DBG:mi_fifo:mi_parse_node: end of input tree<br>> Mar 16 16:47:25 opensips /usr/local/sbin/opensips[17049]: DBG:mi_fifo:mi_fifo_server: done parsing the mi tree<br>> Mar 16 16:47:25 opensips /usr/local/sbin/opensips[17048]: DBG:core:handle_sigs: status = 139<br>> Mar 16 16:47:25 opensips /usr/local/sbin/opensips[17048]: INFO:core:handle_sigs: child process 17057 exited by a signal 11<br>> Mar 16 16:47:25 opensips /usr/local/sbin/opensips[17048]: INFO:core:handle_sigs: core was generated<br>> Mar 16 16:47:25 opensips /usr/local/sbin/opensips[17048]: INFO:core:handle_sigs: terminating due to SIGCHLD<br>> Mar 16 16:47:25 opensips /usr/local/sbin/opensips[17051]: INFO:core:sig_usr: signal 15 received<br>> Mar 16 16:47:25 opensips /usr/local/sbin/opensips[17050]: INFO:core:sig_usr: signal 15 received<br>> Mar 16 16:47:25 opensips /usr/local/sbin/opensips[17053]: INFO:core:sig_usr: signal 15 received<br>> Mar 16 16:47:25 opensips /usr/local/sbin/opensips[17052]: INFO:core:sig_usr: signal 15 received<br>> Mar 16 16:47:25 opensips /usr/local/sbin/opensips[17049]: INFO:core:sig_usr: signal 15 received<br>> Mar 16 16:47:25 opensips /usr/local/sbin/opensips[17058]: INFO:core:sig_usr: signal 15 received<br>> Mar 16 16:47:25 opensips /usr/local/sbin/opensips[17048]: INFO:core:cleanup: cleanup<br>> Mar 16 16:47:25 opensips /usr/local/sbin/opensips[17048]: NOTICE:cachedb_couchbase:destroy: destroy module cachedb_couchbase ...<br>> Mar 16 16:47:25 opensips /usr/local/sbin/opensips[17048]: DBG:tm:tm_shutdown: tm_shutdown : start<br>> Mar 16 16:47:25 opensips /usr/local/sbin/opensips[17048]: DBG:tm:unlink_timer_lists: emptying DELETE list for set 0<br>> Mar 16 16:47:25 opensips /usr/local/sbin/opensips[17048]: DBG:tm:tm_shutdown: emptying hash table<br>> Mar 16 16:47:25 opensips /usr/local/sbin/opensips[17048]: DBG:tm:tm_shutdown: releasing timers<br>> Mar 16 16:47:25 opensips /usr/local/sbin/opensips[17048]: DBG:tm:tm_shutdown: removing semaphores<br>> Mar 16 16:47:25 opensips /usr/local/sbin/opensips[17048]: DBG:tm:tm_shutdown: destroying callback lists<br>> Mar 16 16:47:25 opensips /usr/local/sbin/opensips[17048]: DBG:tm:tm_shutdown: tm_shutdown : done<br>> Mar 16 16:47:25 opensips /usr/local/sbin/opensips[17048]: DBG:core:shm_mem_destroy: destroying the shared memory lock<br>> Mar 16 16:47:25 opensips /usr/local/sbin/opensips[17048]: DBG:core:handle_sigs: terminating due to SIGCHLD<br>> <br>> <br>> <br>> ------------------------------<br>> <br>> Message: 7<br>> Date: Mon, 16 Mar 2015 19:59:58 +0200<br>> From: R?zvan Crainea <razvan@opensips.org><br>> Subject: Re: [OpenSIPS-Users] [NEW] Emergency call handling module<br>> To: OpenSIPS users mailling list <users@lists.opensips.org>,<br>> devel@lists.opensips.org, business@lists.opensips.org,<br>> news@lists.opensips.org<br>> Message-ID: <55071A1E.6080603@opensips.org><br>> Content-Type: text/plain; charset="utf-8"; Format="flowed"<br>> <br>> Hello all!<br>> <br>> Thank you Evandro and Robison for the new emergency module. I bet the <br>> community will find it useful.<br>> <br>> I've added the extra documentation you provided on the wiki[1]. <br>> Therefore, anybody who is looking to deploy this feature on their <br>> platform can read and get some ideas about what the module does and how.<br>> The wiki page contains the following information:<br>> * The specifications and design of the NENA i2 architecture<br>> * Use case scenarios<br>> * Configuration examples<br>> <br>> [1] http://www.opensips.org/Documentation/Tutorials-Emergency-2-1<br>> <br>> Best regards,<br>> <br>> R?zvan Crainea<br>> OpenSIPS Solutions<br>> www.opensips-solutions.com<br>> <br>> On 03/14/2015 03:07 AM, Evandro Villaron Franceschinelli wrote:<br>> > /*We are proud to present the opensips emergency module.*/<br>> ><br>> > *Opensips: Emergency Module - Abstract*<br>> > To make as emergency call using a single code (e.g.: 911 in US or 112 <br>> > in Europe) has been a challenge for VOIP technology. This is a problem <br>> > because a crucial information is missing: the user's location and the <br>> > location is essential to route the call to the closest PSAP(call <br>> > center responsible for answering emergency calls).<br>> ><br>> > This has been studied by many entities, such as the IETF, who created <br>> > several RFC on the topic, and the American NENA (National Emergency <br>> > Number Association), who devised a solution based on the concepts of <br>> > the IETF. The main elements of this solution are, LIS (Location <br>> > information server ,which is the node that determines the location of <br>> > the VoIP terminal), ERDB (servers that determines the area's emergency <br>> > closest PSAP due this location ), VPC (servers that manage the <br>> > location and routing information associated with a call) and, most <br>> > importantly, the SIP PROXY that can make routing the call according to <br>> > the data sent by these servers.<br>> ><br>> > The OpenSIPS can be an element in this architecture acting as a SIP <br>> > proxy, but need to meet the requirements of this solution. To provide <br>> > this we have developed the Emergency Module, which basically makes the <br>> > interface with the servers mentioned and adds the new SIP extensions <br>> > that the IETF has created for this purpose. Including only two <br>> > commands and some parameters in your configuration file, we enable <br>> > OpenSIPS to be an important component in the solution of this problem, <br>> > with great potential to meet American market or other countries that <br>> > could adopt a similar architecture.<br>> ><br>> ><br>> > For details on usage scenarios, configuration params, etc, see the <br>> > online documentation at:<br>> > http://www.opensips.org/html/docs/modules/2.1.x/emergency.html<br>> ><br>> ><br>> > Best regards,<br>> ><br>> ><br>> > Evandro/Robison<br>> ><br>> ><br>> ><br>> > _______________________________________________<br>> > Users mailing list<br>> > Users@lists.opensips.org<br>> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users<br>> <br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL: <http://lists.opensips.org/pipermail/users/attachments/20150316/c9541d56/attachment.htm><br>> <br>> ------------------------------<br>> <br>> _______________________________________________<br>> Users mailing list<br>> Users@lists.opensips.org<br>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users<br>> <br>> <br>> End of Users Digest, Vol 80, Issue 52<br>> *************************************<br></div> </div></body>
</html>