<html><body><div style="color:#000; background-color:#fff; font-family:verdana, helvetica, sans-serif;font-size:10pt"><div>Hi Razvan</div><div><br></div><div>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.</div><div><br></div><div>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 <br></div><div><br></div><div>I will add these modifications to the opensips.cfg file to avoid the error messages to my guide later.</div><div><br></div><div>Thanks again for your help</div><div>Duncan</div><div><br></div><div>Current log results on
restart....<br><span></span></div><div><br><span></span></div><div><span>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<br>Jul 6 16:16:33 raspberryvoip opensips: INFO:core:init_tcp: using epoll_lt as the TCP io watch method (auto detected)<br>Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: NOTICE:core:main: version: opensips 1.8.0-notls (armv6l/linux)<br>Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: INFO:core:main: using 64 Mb shared memory<br>Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: INFO:core:main: using 4 Mb private memory per process<br>Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: NOTICE:signaling:mod_init: initializing module
...<br>Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: INFO:sl:mod_init: Initializing StateLess engine<br>Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: INFO:tm:mod_init: TM - initializing...<br>Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: CRITICAL:tm:lock_set_init: semget (..., 251, 0700) failed: Invalid argument<br>Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: INFO:tm:lock_initialize: semaphore arrays of size 250 allocated<br>Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: INFO:rr:mod_init: rr - initializing<br>Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: INFO:maxfwd:mod_init: initializing...<br>Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: INFO:sipmsgops:mod_init: initializing...<br>Jul 6 16:16:33
raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: INFO:usrloc:ul_init_locks: locks array size 128<br>Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: INFO:registrar:mod_init: initializing...<br>Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: INFO:acc:mod_init: initializing...<br>Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: INFO:auth:mod_init: initializing...<br>Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: INFO:auth_db:mod_init: initializing...<br>Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: INFO:dialog:mod_init: Dialog module - initializing<br>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<br>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<br>Jul 6 16:16:33 raspberryvoip /usr/local/opensips_proxy/sbin/opensips[1296]: INFO:core:init_sock_keepalive: -- TCP keepalive enabled on socket<br>Jul 6 16:16:33 raspberryvoip opensips: INFO:core:daemonize: pre-daemon process exiting with 0<br></span></div><div><br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; margin-top: 5px; padding-left: 5px;"> <div style="font-family: verdana, helvetica, sans-serif; font-size: 10pt;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div dir="ltr"> <font face="Arial" size="2"> <hr size="1"> <b><span style="font-weight:bold;">From:</span></b> "users-request@lists.opensips.org" <users-request@lists.opensips.org><br> <b><span style="font-weight: bold;">To:</span></b> users@lists.opensips.org <br> <b><span style="font-weight: bold;">Sent:</span></b> Friday, 6 July 2012,
14:49<br> <b><span style="font-weight: bold;">Subject:</span></b> Users Digest, Vol 48, Issue 23<br> </font> </div> <br>Send Users mailing list submissions to<br> <a ymailto="mailto:users@lists.opensips.org" href="mailto:users@lists.opensips.org">users@lists.opensips.org</a><br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>or, via email, send a message with subject or body 'help' to<br> <a ymailto="mailto:users-request@lists.opensips.org" href="mailto:users-request@lists.opensips.org">users-request@lists.opensips.org</a><br><br>You can reach the person managing the list at<br> <a ymailto="mailto:users-owner@lists.opensips.org" href="mailto:users-owner@lists.opensips.org">users-owner@lists.opensips.org</a><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: Users Digest, Vol 48, Issue 21 - Raspberry Pi / OpenSIPS<br> (R?zvan Crainea)<br> 2. Re: Late media offer/answer.. (sindrek)<br> 3. Re: About L4 Swtich + 2 * opensips (Ali Pey)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Fri, 06 Jul 2012 15:42:57 +0300<br>From: R?zvan Crainea <<a ymailto="mailto:razvan@opensips.org" href="mailto:razvan@opensips.org">razvan@opensips.org</a>><br>Subject: Re: [OpenSIPS-Users] Users Digest, Vol 48, Issue 21 -<br> Raspberry Pi / OpenSIPS<br>To: <a ymailto="mailto:users@lists.opensips.org" href="mailto:users@lists.opensips.org">users@lists.opensips.org</a><br>Message-ID: <<a ymailto="mailto:4FF6DD51.8020302@opensips.org"
href="mailto:4FF6DD51.8020302@opensips.org">4FF6DD51.8020302@opensips.org</a>><br>Content-Type: text/plain; charset=UTF-8; format=flowed<br><br>Hi, Duncan!<br><br>It seems you have discovered two issues: an inconsistency (usrloc vs <br>dialog) of the hash_size parameter and a small bug in dialog module. For <br>the first one, the dialog module desires the exact number of the hash <br>size, but the usrloc module requires a power of two. Therefore, the <br>proper parameters should be something like that:<br><br>modparam("usrloc", "hash_size", 7)<br>modparam("dialog", "hash_size", 128)<br><br>For the second issue, the dialog could not fix the parameter properly. I <br>have just committed a fix for trunk and 1.8.<br><br>Regards,<br><br>Razvan Crainea<br>OpenSIPS Core Developer<br><a href="http://www.opensips-solutions.com/" target="_blank">http://www.opensips-solutions.com</a><br><br><br><br><br>------------------------------<br><br>Message: 2<br>Date:
Fri, 6 Jul 2012 06:25:16 -0700 (PDT)<br>From: sindrek <<a ymailto="mailto:rauskjegg@gmail.com" href="mailto:rauskjegg@gmail.com">rauskjegg@gmail.com</a>><br>Subject: Re: [OpenSIPS-Users] Late media offer/answer..<br>To: <a ymailto="mailto:users@lists.opensips.org" href="mailto:users@lists.opensips.org">users@lists.opensips.org</a><br>Message-ID: <<a ymailto="mailto:1341581116851-7580711.post@n2.nabble.com" href="mailto:1341581116851-7580711.post@n2.nabble.com">1341581116851-7580711.post@n2.nabble.com</a>><br>Content-Type: text/plain; charset=us-ascii<br><br>I fixed it!<br><br>/BR<br>Sindre<br><br>--<br>View this message in context: <a href="http://opensips-open-sip-server.1449251.n2.nabble.com/Late-media-offer-answer-tp7580695p7580711.html" target="_blank">http://opensips-open-sip-server.1449251.n2.nabble.com/Late-media-offer-answer-tp7580695p7580711.html</a><br>Sent from the OpenSIPS - Users mailing list archive at
Nabble.com.<br><br><br><br>------------------------------<br><br>Message: 3<br>Date: Fri, 6 Jul 2012 09:48:58 -0400<br>From: Ali Pey <<a ymailto="mailto:alipey@gmail.com" href="mailto:alipey@gmail.com">alipey@gmail.com</a>><br>Subject: Re: [OpenSIPS-Users] About L4 Swtich + 2 * opensips<br>To: OpenSIPS users mailling list <<a ymailto="mailto:users@lists.opensips.org" href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>><br>Message-ID:<br> <CA+q4kRLMPYmZSv-QwdsOg60Cf=<a ymailto="mailto:PXwYZ0bw15ms5B-q7qMXjLAw@mail.gmail.com" href="mailto:PXwYZ0bw15ms5B-q7qMXjLAw@mail.gmail.com">PXwYZ0bw15ms5B-q7qMXjLAw@mail.gmail.com</a>><br>Content-Type: text/plain; charset="utf-8"<br><br>Nick,<br><br>If lookup is returning -1 or -3, that means it didn't find the user in the<br>location table and it should send 404 instead of routing the call.<br><br>You need to find out why lookup can not find the user. You need to
look at<br>opensips logs not the sip logs.<br><br>Enable debugging in your opensips.cfg file and look at the logs and see why<br>it can't find the user in the location table. If you don't see any error<br>messages, then post the opensips logs here.<br><br>Regards,<br>Ali Pey<br><br><br>On Fri, Jul 6, 2012 at 2:23 AM, Nick Chang <<a ymailto="mailto:nick.chang@kland.com.tw" href="mailto:nick.chang@kland.com.tw">nick.chang@kland.com.tw</a>> wrote:<br><br>> Hello****<br>><br>> ** **<br>><br>> I found this error.****<br>><br>> ** **<br>><br>> In my old opensips.cfg****<br>><br>> ** **<br>><br>> route[generic_relay] {****<br>><br>> # for INVITEs enable some additional helper routes****<br>><br>> #---- Helper route, if nat=yes in the R-URI set flag 6 ----#****<br>><br>> #---- This is
used to Process REINVITES ----#****<br>><br>> if (subst_uri('/((sip:.*)||(sip:.*:.*));nat=yes/\1/')){****<br>><br>> setbflag(6);****<br>><br>> };****<br>><br>> ** **<br>><br>> #---- If caller(flag 5) or callee(flag 6) are behind NAT ---#****<br>><br>> #---- Call the route(6) to force the use of the RTP Proxy ---#****<br>><br>> if (isflagset(5)||isbflagset(6)) {****<br>><br>> route(nat_fixups);****<br>><br>> };****<br>><br>> ** **<br>><br>> if (!t_relay()) {****<br>><br>>
sl_reply_error();****<br>><br>> };****<br>><br>> exit;****<br>><br>> }****<br>><br>> ** **<br>><br>> route[user_location]{****<br>><br>> if (!lookup("location", "m")) {****<br>><br>> switch ($retcode) {****<br>><br>> case -1:****<br>><br>> case -3:****<br>><br>> t_newtran();****<br>><br>> send_reply("404", "Not Found");****<br>><br>>
exit;****<br>><br>> case -2:****<br>><br>> send_reply("405", "Method Not Allowed");**<br>> **<br>><br>> exit;****<br>><br>> }****<br>><br>> }****<br>><br>> # when routing via usrloc, log the missed calls also****<br>><br>> setflag(2); # Account missed calls****<br>><br>> ** **<br>><br>> t_on_failure("user_failure");****<br>><br>> **
**<br>><br>> route(generic_relay);****<br>><br>> }****<br>><br>> ** **<br>><br>> Then, I modify it.****<br>><br>> ** **<br>><br>> route[generic_relay] {****<br>><br>> # for INVITEs enable some additional helper routes****<br>><br>> #---- Helper route, if nat=yes in the R-URI set flag 6 ----#****<br>><br>> #---- This is used to Process REINVITES ----#****<br>><br>> if (subst_uri('/((sip:.*)||(sip:.*:.*));nat=yes/\1/')){****<br>><br>> setbflag(6);****<br>><br>> };****<br>><br>> ** **<br>><br>> #---- If caller(flag 5) or callee(flag 6) are behind NAT
---#****<br>><br>> #---- Call the route(6) to force the use of the RTP Proxy ---#****<br>><br>> if (isflagset(5)||isbflagset(6)) {****<br>><br>> route(nat_fixups);****<br>><br>> };****<br>><br>> ** **<br>><br>> if (!t_relay()) {****<br>><br>> sl_reply_error();****<br>><br>> };****<br>><br>> exit;****<br>><br>> }****<br>><br>> ** **<br>><br>> route[user_location]{****<br>><br>> if (!lookup("location", "m")) {****<br>><br>> switch ($retcode) {****<br>><br>>
case -1:****<br>><br>> case -3:****<br>><br>> route(generic_relay);****<br>><br>> # t_newtran();****<br>><br>> # send_reply("404", "Not Found");****<br>><br>> # exit;****<br>><br>> case -2:****<br>><br>> send_reply("405", "Method Not Allowed");**<br>>
**<br>><br>> exit;****<br>><br>> }****<br>><br>> }****<br>><br>> # when routing via usrloc, log the missed calls also****<br>><br>> setflag(2); # Account missed calls****<br>><br>> ** **<br>><br>> t_on_failure("user_failure");****<br>><br>> ** **<br>><br>> route(generic_relay);****<br>><br>> }****<br>><br>> ** **<br>><br>> ** **<br>><br>> ** **<br>><br>> Now, SIP1 can call to SIP2. It?s OK.****<br>><br>> But, If User isn?t online.****<br>><br>> It can not display ?user not found?, only display ?request timeout(408)?**<br>> **<br>><br>> **
**<br>><br>> Do everyone have any good suggest??****<br>><br>> Can modify it to fine??****<br>><br>> ** **<br>><br>> Thanks for your support.****<br>><br>> Nick****<br>><br>> ** **<br>><br>> *From:* <a ymailto="mailto:users-bounces@lists.opensips.org" href="mailto:users-bounces@lists.opensips.org">users-bounces@lists.opensips.org</a> [mailto:<br>> <a ymailto="mailto:users-bounces@lists.opensips.org" href="mailto:users-bounces@lists.opensips.org">users-bounces@lists.opensips.org</a>] *On Behalf Of *Ali Pey<br>> *Sent:* Thursday, July 05, 2012 11:34 PM<br>> *To:* OpenSIPS users mailling list<br>> *Subject:* Re: [OpenSIPS-Users] About L4 Swtich + 2 * opensips****<br>><br>> ** **<br>><br>> What do you see in the logs? Is it that it can not find the other user or<br>> is it that it can not reach it? ****<br>><br>> If you can't find the reason in the logs, then post them
here.****<br>><br>> ** **<br>><br>> Regards,****<br>><br>> Ali Pey ****<br>><br>> On Thu, Jul 5, 2012 at 11:05 AM, Nick <<a ymailto="mailto:nick.chang@kland.com.tw" href="mailto:nick.chang@kland.com.tw">nick.chang@kland.com.tw</a>> wrote:****<br>><br>> Dear****<br>><br>> ** **<br>><br>> My two opensips connected to the same location table in the same database<br>><br>> Thanks****<br>><br>> Nick****<br>><br>><br>> Ali Pey <<a ymailto="mailto:alipey@gmail.com" href="mailto:alipey@gmail.com">alipey@gmail.com</a>> ? 2012/7/5 22:24 ???****<br>><br>> Both opensips server should be connected to the same location table in the<br>> same Database.****<br>><br>> ** **<br>><br>> Regards,****<br>><br>> Ali Pey****<br>><br>> ** **<br>><br>> On Thu, Jul 5, 2012 at 6:18 AM, Nick Chang <<a ymailto="mailto:nick.chang@kland.com.tw"
href="mailto:nick.chang@kland.com.tw">nick.chang@kland.com.tw</a>><br>> wrote:****<br>><br>> Dear ****<br>><br>> ****<br>><br>> I have a ServerIronADX 1000. ****<br>><br>> I have two OpenSIPS Server****<br>><br>> ****<br>><br>> Then I setup this L4 Switch for SIP?s load balance****<br>><br>> ****<br>><br>> When client1 login to SIP1 and client2 login to SIP2****<br>><br>> Then client1 call to client2.****<br>><br>> ****<br>><br>> Client1 can?t call to client2. It?s failed.****<br>><br>> ****<br>><br>> How to setup OpenSIPS, Lets it found client1 and client2??****<br>><br>> Thanks for your help.****<br>><br>> ****<br>><br>> It?s my config.****<br>><br>> server real SIP1 10.1.3.131****<br>><br>> port default disable****<br>><br>> port sip****<br>><br>> port sip udp-only****<br>><br>>
!****<br>><br>> server real SIP2 10.1.3.132****<br>><br>> port default disable****<br>><br>> port sip****<br>><br>> port sip udp-only****<br>><br>> !****<br>><br>> server virtual SIP-VIP 10.1.3.130****<br>><br>> port sip****<br>><br>> port sip udp-only****<br>><br>> port sip reset-on-port-fail****<br>><br>> bind sip SIP1 sip SIP2 sip****<br>><br>> ****<br>><br>> Thanks****<br>><br>> Nick****<br>><br>><br>> _______________________________________________<br>> Users mailing list<br>> <a ymailto="mailto:Users@lists.opensips.org" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users****" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users****</a><br>><br>> ** **<br>><br>> _______________________________________________<br>> Users mailing
list<br>> <a ymailto="mailto:Users@lists.opensips.org" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users****" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users****</a><br>><br>><br>> _______________________________________________<br>> Users mailing list<br>> <a ymailto="mailto:Users@lists.opensips.org" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users****" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users****</a><br>><br>> ** **<br>><br>> _______________________________________________<br>> Users mailing list<br>> <a ymailto="mailto:Users@lists.opensips.org" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>> <a
href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>><br>><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <<a href="http://lists.opensips.org/pipermail/users/attachments/20120706/6e937ce4/attachment.htm" target="_blank">http://lists.opensips.org/pipermail/users/attachments/20120706/6e937ce4/attachment.htm</a>><br><br>------------------------------<br><br>_______________________________________________<br>Users mailing list<br><a ymailto="mailto:Users@lists.opensips.org" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br><a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br><br><br>End of Users Digest, Vol 48, Issue 23<br>*************************************<br><br><br> </div> </div>
</blockquote></div> </div></body></html>