Somwhere losted since openser 1.0 :)
Please fix in:
start() {
echo -n $"Starting $prog: "
.....
[ $RETVAL = 0 ] && touch something
to
[ $RETVAL = 0 ] && touch someting && success
I mean call function
success
in the end of the expression.
Thanks in advance
Hello,
I am experiencing some disconnections with my VOIP phones.
Let me explain:
My server is an Asterisk + Kamailio in a datacenter with a fixed IP, and a bridge firewall in front of it, so no NAT here.
My client (several offices) have usually no problem when they have a fixed IP, but encounter fatal disconnection when they have a dynamic IP. I had the case with Siemens, SNOM and Aastra phones, without any difference. They are of course natted behind an ADSL router. I also have clients doing load-balance between two ADSL lines, which is also problematic.
The only way for me to recover is to change the private IP of the VOIP phones. Seems more like a TCP problem or a routing problem, but I am no network guru.
I have two ADSL lines to test it, and when I switch from one line to another, every phone becomes "Not registered". Even falling back tot he first line does not help recovering. I did not try to wait for longer than 24 hours to recover.
So my question is, more generally: is it possible to allow the clients (VOIP phones) to re-connect with a new IP address without having closed correctly the first connection (SIP session, I presume)? It seems not by default, but I played with the timeouts server-side and phone-side, without luck.
I saw many posts with PBX having problems when behind a dynamic IP, but nothing about the clients having dynamic addresses or load-balancing. Normally, having a dynamic IP does not mean that your IP will change << on-the-fly >>, but each time you shut down and reboot later your ADSL router, but we came to the conclusion that every client NOT having a fixed IP was experiencing fatal disconnects. So I managed to test and validate this behavior with our two ADSL lines.
Hope someone can help me.
Greetings
Simon
Spam detection software, running on the system "mail.iptel.org", has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email. If you have any questions, see
the administrator of that system for details.
Content preview: As a company we deal with advising other business and end
users on reusable materials, green advancements and nontypical forms of energy
and also produce and promote projects that are web media focused. [...]
Content analysis details: (9.6 points, 5.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
0.7 SPF_SOFTFAIL SPF: sender does not match SPF record (softfail)
3.3 RCVD_IN_PBL RBL: Received via a relay in Spamhaus PBL
[139.195.43.246 listed in zen.spamhaus.org]
1.7 URIBL_BLACK Contains an URL listed in the URIBL blacklist
[URIs: euroinjobs.com]
0.6 URIBL_PH_SURBL Contains an URL listed in the PH SURBL blocklist
[URIs: euroinjobs.com]
0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60%
[score: 0.5000]
1.7 URIBL_DBL_SPAM Contains an URL listed in the DBL blocklist
[URIs: euroinjobs.com]
0.8 RDNS_NONE Delivered to internal network by a host with no rDNS
Spam detection software, running on the system "mail.iptel.org", has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email. If you have any questions, see
the administrator of that system for details.
Content preview: As a company we deal with advising other business and end
users on reusable materials, green advancements and nontypical forms of energy
and also produce and promote projects that are web media focused. [...]
Content analysis details: (15.1 points, 5.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
3.6 HELO_DYNAMIC_IPADDR2 Relay HELO'd using suspicious hostname (IP addr
2)
0.0 TVD_RCVD_IP TVD_RCVD_IP
0.7 SPF_SOFTFAIL SPF: sender does not match SPF record (softfail)
3.3 RCVD_IN_PBL RBL: Received via a relay in Spamhaus PBL
[186.63.33.68 listed in zen.spamhaus.org]
0.4 RCVD_IN_XBL RBL: Received via a relay in Spamhaus XBL
1.4 RCVD_IN_BRBL_LASTEXT RBL: RCVD_IN_BRBL_LASTEXT
[186.63.33.68 listed in bb.barracudacentral.org]
1.7 URIBL_DBL_SPAM Contains an URL listed in the DBL blocklist
[URIs: euroinjobs.com]
1.7 URIBL_BLACK Contains an URL listed in the URIBL blacklist
[URIs: euroinjobs.com]
0.6 URIBL_PH_SURBL Contains an URL listed in the PH SURBL blocklist
[URIs: euroinjobs.com]
0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60%
[score: 0.4970]
0.8 RDNS_NONE Delivered to internal network by a host with no rDNS
Spam detection software, running on the system "mail.iptel.org", has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email. If you have any questions, see
the administrator of that system for details.
Content preview: As a company we deal with advising other business and end
users on reusable materials, green advancements and nontypical forms of energy
and also produce and promote projects that are web media focused. [...]
Content analysis details: (10.3 points, 5.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
3.6 HELO_DYNAMIC_IPADDR2 Relay HELO'd using suspicious hostname (IP addr
2)
0.0 TVD_RCVD_IP TVD_RCVD_IP
-0.0 SPF_PASS SPF: sender matches SPF record
1.4 RCVD_IN_BRBL_LASTEXT RBL: RCVD_IN_BRBL_LASTEXT
[184.77.159.149 listed in bb.barracudacentral.org]
1.7 URIBL_DBL_SPAM Contains an URL listed in the DBL blocklist
[URIs: euroinjobs.com]
1.7 URIBL_BLACK Contains an URL listed in the URIBL blacklist
[URIs: euroinjobs.com]
0.6 URIBL_PH_SURBL Contains an URL listed in the PH SURBL blocklist
[URIs: euroinjobs.com]
-0.0 BAYES_40 BODY: Bayes spam probability is 20 to 40%
[score: 0.2745]
0.4 RCVD_IN_XBL RBL: Received via a relay in Spamhaus XBL
[184.77.159.149 listed in zen.spamhaus.org]
0.8 RDNS_NONE Delivered to internal network by a host with no rDNS
Hello,
I would like to use the module and create our own version of the Application Server using the SEAS protocol but there are some pieces of information missing from the web site (links to images that contains information about headers etc ). The basic information on how it works is there, the AS registers to the OpenSER, receives information, sends information but the details of how to register, the format of the messages etc are not there.
I checked for information in previous versions only to find the same situation.(3.1 thru 3.3)
Is the information about the SEAS module specific to the WeSIP Application Server?
Thank you
fborot
Hi guys,
In the pua table, there is a unique key on the "expires" column, which
seems wrong to me, because you'll sooner or later end up with different
pua entries having the same expiry time, no?
At least we ended up with messages like this in the logs, I think it's
caused by pua_reginfo tests:
ERROR: db_mysql [km_dbase.c:122]: driver error on query: Duplicate entry
'1345474412' for key 'expires_idx'
ERROR: <core> [db_query.c:210]: error while submitting query
ERROR: pua [pua.c:1171]: while inserting in db table pua
Any comments on that?
Andreas
Hi,
I am trying to get the db_cassandra working in kamailio 3.1.1 with thrift 0.6.1 API and however I get the following
compile error.
ol.h:33,
from dbcassa_base.h:38,
from dbcassa_base.cpp:47:
../../lib/srdb1/db.h:388:20: error: expected unqualified-id before âdeleteâ
dbcassa_base.cpp: In function âColumnVecPtr cassa_translate_query(const db1_con_t*, str* const*, const db_val_t*, str* const*, int, int, int*)â:
dbcassa_base.cpp:538:8: warning: format â%dâ expects argument of type âintâ, but argument 7 has type âstd::vector<org::apache::cassandra::KeySlice>::size_type {aka long unsigned int}â [-Wformat]
dbcassa_base.cpp:538:8: warning: format â%dâ expects argument of type âintâ, but argument 5 has type âstd::vector<org::apache::cassandra::KeySlice>::size_type {aka long unsigned int}â [-Wformat]
dbcassa_base.cpp:538:8: warning: format â%dâ expects argument of type âintâ, but argument 6 has type âstd::vector<org::apache::cassandra::KeySlice>::size_type {aka long unsigned int}â [-Wformat]
dbcassa_base.cpp:538:8: warning: format â%dâ expects argument of type âintâ, but argument 4 has type âstd::vector<org::apache::cassandra::KeySlice>::size_type {aka long unsigned int}â [-Wformat]
dbcassa_base.cpp:538:8: warning: format â%dâ expects argument of type âintâ, but argument 4 has type âstd::vector<org::apache::cassandra::KeySlice>::size_type {aka long unsigned int}â [-Wformat]
../../lib/srdb1/db_res.h: At global scope:
../../lib/srdb1/db_res.h:105:19: warning: inline function âdb1_res_t* db_new_result()â used but never defined [enabled by default]
../../lib/srdb1/db_res.h:121:12: warning: inline function âint db_allocate_columns(db1_res_t*, unsigned int)â used but never defined [enabled by default]
../../lib/srdb1/db_res.h:98:12: warning: inline function âint db_free_columns(db1_res_t*)â used but never defined [enabled by default]
../../lib/srdb1/db_res.h:129:12: warning: inline function âint db_allocate_rows(db1_res_t*)â used but never defined [enabled by default]
../../lib/srdb1/db_row.h:74:12: warning: inline function âint db_allocate_row(const db1_res_t*, db_row_t*)â used but never defined [enabled by default]
../../lib/srdb1/db_res.h:111:12: warning: inline function âint db_free_result(db1_res_t*)â used but never defined [enabled by default]
make[1]: *** [dbcassa_base.o] Error 1
make: *** [install-modules] Error 1
Anybody has got any ideas?
Thanks in advance,
Bou
Spam detection software, running on the system "mail.iptel.org", has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email. If you have any questions, see
the administrator of that system for details.
Content preview: ðÒÏÄÁÅÔÓÑ ÚÄÅÓØ www.ËÕÐÉ-ÄÏÍ-ÚÄÅÓØ.ÒÆ [...]
Content analysis details: (10.2 points, 5.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
3.5 BAYES_99 BODY: Bayes spam probability is 99 to 100%
[score: 1.0000]
0.8 RCVD_IN_SORBS_WEB RBL: SORBS: sender is an abusable web server
[116.203.165.242 listed in dnsbl.sorbs.net]
1.4 RCVD_IN_BRBL_LASTEXT RBL: RCVD_IN_BRBL_LASTEXT
[116.203.165.242 listed in bb.barracudacentral.org]
0.4 RCVD_IN_XBL RBL: Received via a relay in Spamhaus XBL
[116.203.165.242 listed in zen.spamhaus.org]
3.3 RCVD_IN_PBL RBL: Received via a relay in Spamhaus PBL
0.8 RDNS_NONE Delivered to internal network by a host with no rDNS
0.0 UNPARSEABLE_RELAY Informational: message has unparseable relay lines
Hi All Kamailio Experts,
I have configured Kamailio (kamailio 3.1.5) as media server. All things
are working fine. Now i want to use Asterisk (Asterisk 1.6) for Outbound
Calls. For this purpose i have followed the web page :
http://kb.asipto.com/asterisk:realtime:kamailio-3.1.x-asterisk-1.6.2-astdb.
In this page, some points are not clear for me , as given below:
(1) In case you use *sipregs* you have to create a record for each
extension where to set the 'name' to value of 'name' from *sipusers*.
The rest is populated by Asterisk from registrations.
(2) Be sure you configure Asterisk *to not authenticate* SIP requests
coming from Kamailio.
I am not sure that my local users chat is working through kamailio or
asterisk, who is used for authorization.
Any specific Web page to correct the issue will highly appreciated
according to my scenario.
Kindly guide me. Thanks in advance.
--
Best Regards,
Vijay Thakur
(Assistant Manager - Networks)
Mobile : +91 8744018065
Mail : vijay.thakur(a)loopmethods.com
Loop IT Methods Private Limited
1st Floor, B-10, Sector-7, Noida, (U.P) India
Ph: +91 120 305 3481,82 (INDIA), +1 347 468 8631 (USA), +61 390 011 178 (AUS)
Fax: +91 971 728 330
Web: www.loopmethods.com
LOOP Disclaimer -------------------------------------------------------------------------------------------------
This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
-----------------------------------------------------------------------------------------------------------------