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