[OpenSIPS-Users] Users Digest, Vol 48, Issue 23 - Raspberry Pi / OpenSIPS (Duncan Bell)
Duncan Bell
duncanfbell at yahoo.co.uk
Fri Jul 6 17:24:00 CEST 2012
Hi Razvan
Thanks for the tip, it has got OpenSIPS up and running again and without the 1000's of error messages! Good enough for me at the moment, I know OpenSIPS isn't really meant for hardware like this... haven't had these problems installing on anything else, including some pretty low power thin clients.
If you are interested I used the Webinar guide with a few other guides and put together a Raspberry Pi guide for setting up OpenSIPS www.raspberryvoip.com
I will add these modifications to the opensips.cfg file to avoid the error messages to my guide later.
Thanks again for your help
Duncan
Current log results on restart....
Jul 6 16:16:33 raspberryvoip opensips: WARNING:core:warn: warning in config file /usr/local/opensips_proxy/etc/opensips/opensips_residential_2012-7-4_22:50:0.cfg, line 50, column 13-16: tls support not compiled in
Jul 6 16:16:33 raspberryvoip opensips: INFO:core:init_tcp: using epoll_lt as the TCP io watch method (auto detected)
Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: NOTICE:core:main: version: opensips 1.8.0-notls (armv6l/linux)
Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: INFO:core:main: using 64 Mb shared memory
Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: INFO:core:main: using 4 Mb private memory per process
Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: NOTICE:signaling:mod_init: initializing module ...
Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: INFO:sl:mod_init: Initializing StateLess engine
Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: INFO:tm:mod_init: TM - initializing...
Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: CRITICAL:tm:lock_set_init: semget (..., 251, 0700) failed: Invalid argument
Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: INFO:tm:lock_initialize: semaphore arrays of size 250 allocated
Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: INFO:rr:mod_init: rr - initializing
Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: INFO:maxfwd:mod_init: initializing...
Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: INFO:sipmsgops:mod_init: initializing...
Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: INFO:usrloc:ul_init_locks: locks array size 128
Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: INFO:registrar:mod_init: initializing...
Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: INFO:acc:mod_init: initializing...
Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: INFO:auth:mod_init: initializing...
Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: INFO:auth_db:mod_init: initializing...
Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: INFO:dialog:mod_init: Dialog module - initializing
Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: INFO:core:probe_max_sock_buff: using rcv buffer of 216 kb
Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: INFO:core:probe_max_sock_buff: using snd buffer of 216 kb
Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: INFO:core:init_sock_keepalive: -- TCP keepalive enabled on socket
Jul 6 16:16:33 raspberryvoip opensips: INFO:core:daemonize: pre-daemon process exiting with 0
>________________________________
> From: "users-request at lists.opensips.org" <users-request at lists.opensips.org>
>To: users at lists.opensips.org
>Sent: Friday, 6 July 2012, 14:49
>Subject: Users Digest, Vol 48, Issue 23
>
>Send Users mailing list submissions to
> users at lists.opensips.org
>
>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
> users-request at lists.opensips.org
>
>You can reach the person managing the list at
> users-owner at lists.opensips.org
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of Users digest..."
>
>
>Today's Topics:
>
> 1. Re: Users Digest, Vol 48, Issue 21 - Raspberry Pi / OpenSIPS
> (R?zvan Crainea)
> 2. Re: Late media offer/answer.. (sindrek)
> 3. Re: About L4 Swtich + 2 * opensips (Ali Pey)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Fri, 06 Jul 2012 15:42:57 +0300
>From: R?zvan Crainea <razvan at opensips.org>
>Subject: Re: [OpenSIPS-Users] Users Digest, Vol 48, Issue 21 -
> Raspberry Pi / OpenSIPS
>To: users at lists.opensips.org
>Message-ID: <4FF6DD51.8020302 at opensips.org>
>Content-Type: text/plain; charset=UTF-8; format=flowed
>
>Hi, Duncan!
>
>It seems you have discovered two issues: an inconsistency (usrloc vs
>dialog) of the hash_size parameter and a small bug in dialog module. For
>the first one, the dialog module desires the exact number of the hash
>size, but the usrloc module requires a power of two. Therefore, the
>proper parameters should be something like that:
>
>modparam("usrloc", "hash_size", 7)
>modparam("dialog", "hash_size", 128)
>
>For the second issue, the dialog could not fix the parameter properly. I
>have just committed a fix for trunk and 1.8.
>
>Regards,
>
>Razvan Crainea
>OpenSIPS Core Developer
>http://www.opensips-solutions.com
>
>
>
>
>------------------------------
>
>Message: 2
>Date: Fri, 6 Jul 2012 06:25:16 -0700 (PDT)
>From: sindrek <rauskjegg at gmail.com>
>Subject: Re: [OpenSIPS-Users] Late media offer/answer..
>To: users at lists.opensips.org
>Message-ID: <1341581116851-7580711.post at n2.nabble.com>
>Content-Type: text/plain; charset=us-ascii
>
>I fixed it!
>
>/BR
>Sindre
>
>--
>View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Late-media-offer-answer-tp7580695p7580711.html
>Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
>
>
>
>------------------------------
>
>Message: 3
>Date: Fri, 6 Jul 2012 09:48:58 -0400
>From: Ali Pey <alipey at gmail.com>
>Subject: Re: [OpenSIPS-Users] About L4 Swtich + 2 * opensips
>To: OpenSIPS users mailling list <users at lists.opensips.org>
>Message-ID:
> <CA+q4kRLMPYmZSv-QwdsOg60Cf=PXwYZ0bw15ms5B-q7qMXjLAw at mail.gmail.com>
>Content-Type: text/plain; charset="utf-8"
>
>Nick,
>
>If lookup is returning -1 or -3, that means it didn't find the user in the
>location table and it should send 404 instead of routing the call.
>
>You need to find out why lookup can not find the user. You need to look at
>opensips logs not the sip logs.
>
>Enable debugging in your opensips.cfg file and look at the logs and see why
>it can't find the user in the location table. If you don't see any error
>messages, then post the opensips logs here.
>
>Regards,
>Ali Pey
>
>
>On Fri, Jul 6, 2012 at 2:23 AM, Nick Chang <nick.chang at kland.com.tw> wrote:
>
>> Hello****
>>
>> ** **
>>
>> I found this error.****
>>
>> ** **
>>
>> In my old opensips.cfg****
>>
>> ** **
>>
>> route[generic_relay] {****
>>
>> # for INVITEs enable some additional helper routes****
>>
>> #---- Helper route, if nat=yes in the R-URI set flag 6 ----#****
>>
>> #---- This is used to Process REINVITES ----#****
>>
>> if (subst_uri('/((sip:.*)||(sip:.*:.*));nat=yes/\1/')){****
>>
>> setbflag(6);****
>>
>> };****
>>
>> ** **
>>
>> #---- If caller(flag 5) or callee(flag 6) are behind NAT ---#****
>>
>> #---- Call the route(6) to force the use of the RTP Proxy ---#****
>>
>> if (isflagset(5)||isbflagset(6)) {****
>>
>> route(nat_fixups);****
>>
>> };****
>>
>> ** **
>>
>> if (!t_relay()) {****
>>
>> sl_reply_error();****
>>
>> };****
>>
>> exit;****
>>
>> }****
>>
>> ** **
>>
>> route[user_location]{****
>>
>> if (!lookup("location", "m")) {****
>>
>> switch ($retcode) {****
>>
>> case -1:****
>>
>> case -3:****
>>
>> t_newtran();****
>>
>> send_reply("404", "Not Found");****
>>
>> exit;****
>>
>> case -2:****
>>
>> send_reply("405", "Method Not Allowed");**
>> **
>>
>> exit;****
>>
>> }****
>>
>> }****
>>
>> # when routing via usrloc, log the missed calls also****
>>
>> setflag(2); # Account missed calls****
>>
>> ** **
>>
>> t_on_failure("user_failure");****
>>
>> ** **
>>
>> route(generic_relay);****
>>
>> }****
>>
>> ** **
>>
>> Then, I modify it.****
>>
>> ** **
>>
>> route[generic_relay] {****
>>
>> # for INVITEs enable some additional helper routes****
>>
>> #---- Helper route, if nat=yes in the R-URI set flag 6 ----#****
>>
>> #---- This is used to Process REINVITES ----#****
>>
>> if (subst_uri('/((sip:.*)||(sip:.*:.*));nat=yes/\1/')){****
>>
>> setbflag(6);****
>>
>> };****
>>
>> ** **
>>
>> #---- If caller(flag 5) or callee(flag 6) are behind NAT ---#****
>>
>> #---- Call the route(6) to force the use of the RTP Proxy ---#****
>>
>> if (isflagset(5)||isbflagset(6)) {****
>>
>> route(nat_fixups);****
>>
>> };****
>>
>> ** **
>>
>> if (!t_relay()) {****
>>
>> sl_reply_error();****
>>
>> };****
>>
>> exit;****
>>
>> }****
>>
>> ** **
>>
>> route[user_location]{****
>>
>> if (!lookup("location", "m")) {****
>>
>> switch ($retcode) {****
>>
>> case -1:****
>>
>> case -3:****
>>
>> route(generic_relay);****
>>
>> # t_newtran();****
>>
>> # send_reply("404", "Not Found");****
>>
>> # exit;****
>>
>> case -2:****
>>
>> send_reply("405", "Method Not Allowed");**
>> **
>>
>> exit;****
>>
>> }****
>>
>> }****
>>
>> # when routing via usrloc, log the missed calls also****
>>
>> setflag(2); # Account missed calls****
>>
>> ** **
>>
>> t_on_failure("user_failure");****
>>
>> ** **
>>
>> route(generic_relay);****
>>
>> }****
>>
>> ** **
>>
>> ** **
>>
>> ** **
>>
>> Now, SIP1 can call to SIP2. It?s OK.****
>>
>> But, If User isn?t online.****
>>
>> It can not display ?user not found?, only display ?request timeout(408)?**
>> **
>>
>> ** **
>>
>> Do everyone have any good suggest??****
>>
>> Can modify it to fine??****
>>
>> ** **
>>
>> Thanks for your support.****
>>
>> Nick****
>>
>> ** **
>>
>> *From:* users-bounces at lists.opensips.org [mailto:
>> users-bounces at lists.opensips.org] *On Behalf Of *Ali Pey
>> *Sent:* Thursday, July 05, 2012 11:34 PM
>> *To:* OpenSIPS users mailling list
>> *Subject:* Re: [OpenSIPS-Users] About L4 Swtich + 2 * opensips****
>>
>> ** **
>>
>> What do you see in the logs? Is it that it can not find the other user or
>> is it that it can not reach it? ****
>>
>> If you can't find the reason in the logs, then post them here.****
>>
>> ** **
>>
>> Regards,****
>>
>> Ali Pey ****
>>
>> On Thu, Jul 5, 2012 at 11:05 AM, Nick <nick.chang at kland.com.tw> wrote:****
>>
>> Dear****
>>
>> ** **
>>
>> My two opensips connected to the same location table in the same database
>>
>> Thanks****
>>
>> Nick****
>>
>>
>> Ali Pey <alipey at gmail.com> ? 2012/7/5 22:24 ???****
>>
>> Both opensips server should be connected to the same location table in the
>> same Database.****
>>
>> ** **
>>
>> Regards,****
>>
>> Ali Pey****
>>
>> ** **
>>
>> On Thu, Jul 5, 2012 at 6:18 AM, Nick Chang <nick.chang at kland.com.tw>
>> wrote:****
>>
>> Dear ****
>>
>> ****
>>
>> I have a ServerIronADX 1000. ****
>>
>> I have two OpenSIPS Server****
>>
>> ****
>>
>> Then I setup this L4 Switch for SIP?s load balance****
>>
>> ****
>>
>> When client1 login to SIP1 and client2 login to SIP2****
>>
>> Then client1 call to client2.****
>>
>> ****
>>
>> Client1 can?t call to client2. It?s failed.****
>>
>> ****
>>
>> How to setup OpenSIPS, Lets it found client1 and client2??****
>>
>> Thanks for your help.****
>>
>> ****
>>
>> It?s my config.****
>>
>> server real SIP1 10.1.3.131****
>>
>> port default disable****
>>
>> port sip****
>>
>> port sip udp-only****
>>
>> !****
>>
>> server real SIP2 10.1.3.132****
>>
>> port default disable****
>>
>> port sip****
>>
>> port sip udp-only****
>>
>> !****
>>
>> server virtual SIP-VIP 10.1.3.130****
>>
>> port sip****
>>
>> port sip udp-only****
>>
>> port sip reset-on-port-fail****
>>
>> bind sip SIP1 sip SIP2 sip****
>>
>> ****
>>
>> Thanks****
>>
>> Nick****
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users****
>>
>> ** **
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users****
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users****
>>
>> ** **
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>-------------- next part --------------
>An HTML attachment was scrubbed...
>URL: <http://lists.opensips.org/pipermail/users/attachments/20120706/6e937ce4/attachment.htm>
>
>------------------------------
>
>_______________________________________________
>Users mailing list
>Users at lists.opensips.org
>http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>End of Users Digest, Vol 48, Issue 23
>*************************************
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20120706/629af85b/attachment-0001.htm>
More information about the Users
mailing list