Hi,
After many many months of faultless operation, today we experienced a SEG
FAULT on one of our proxies running OpenSER 1.1.0-notls:
Below is a back trace (with some values masked with xxx's), however our
initial analysis can not make any sense of what the problem is. Any ideas
would be greatly appreciated.
res.c:194 is =====> r = (db_res_t*)pkg_malloc(sizeof(db_res_t));
Here is the back trace:
(gdb) bt
#0 0x00000000 in ?? ()
#1 0x4016ad2c in new_result () at res.c:194
#2 0x4016a495 in store_result (_h=0x81301b8, _r=0xbffff198) at dbase.c:322
#3 0x404bfc0a in db_load_avp (uuid=0x81301b8, username=0x81301b8,
domain=0x81301b8, attr=0x81301b8 "@X\022\bø\034\023\b",
table=0x0, scheme=0x404ce9e0) at avpops_db.c:270
#4 0x404c05d6 in ops_dbload_avps (msg=0x8134cd8, sp=0x8128210,
dbp=0x8128b18, use_domain=0) at avpops_impl.c:393
#5 0x404bef47 in w_dbload_avps (msg=0x81301b8, source=0x81301b8
"@X\022\bø\034\023\b",
param=0x81301b8 "@X\022\bø\034\023\b") at avpops.c:1183
#6 0x0805071b in do_action (a=0x8128de8, msg=0x8134cd8) at action.c:701
#7 0x08050631 in do_action (a=0x8129478, msg=0x8134cd8) at action.c:89
#8 0x08050631 in do_action (a=0x81294a8, msg=0x8134cd8) at action.c:89
#9 0x080522c2 in run_actions (a=0x8126548, msg=0x8134cd8) at action.c:89
#10 0x08051f2e in run_top_route (a=0x81301b8, msg=0x81301b8) at action.c:151
#11 0x08071ec1 in receive_msg (
buf=0x80ea340 "REGISTER sip:xx.xxxxxxx.xxx SIP/2.0\r\nVia: SIP/2.0/UDP
192.168.1.2:5060;branch=z9hG4bK-f1cef63e\r\nFrom: xxxxx <
sip:xxxxxx@xx.xxxxxxx.xxx>;tag=fe10f354c23eb963o0\r\nTo: xxxxx <
sip:xxxxxx@xx.xxxxxxx.xxx>\r\nC"..., len=475,
rcv_info=0xbffff9a0) at receive.c:155
#12 0x08089654 in udp_rcv_loop () at udp_server.c:465
#13 0x08063b64 in main_loop () at main.c:925
#14 0x08064fae in main (argc=9, argv=0xbffffb24) at main.c:1477
(gdb) quit
Thanks in advance
Martin
Hello,
Version 1.2.1 of OpenSER has been released. It is an update of version
1.2.0 and includes the fixes for the issues discovered in version 1.2.0,
therefore all people using 1.2.0 should upgrade to this new version.
The compatibility of the configuration file and database has been
preserved (you do not need to do database reinstallation/migration).
Detailed changelog:
http://www.openser.org/pub/openser/1.2.1/ChangeLog
For people using SVN, a new TAG was created ( 1.2.1 ). The development
of the 1.2 branch will continue on the SVN 1.2 branch. So, if you want
to synchronize with the latest changes/release in 1.2, keep using the
1.2 branch. If you want to take the 1.2.1 snapshot, use the 1.2.1 SVN tag.
Source tarball can be downloaded from:
http://www.openser.org/pub/openser/latest/src/
Or SourceForge:
http://sourceforge.net/project/showfiles.php?group_id=139143&package_id=224…
If someone wants to contribute with packages for different distros,
please send the link from where can be downloaded to team(a)openser.org.
Regards,
Bogdan
---------- Forwarded message ----------
From: flavio <flavio.patria(a)gmail.com>
Date: 23-mag-2007 17.35
Subject: acl
To: serusers(a)list.iptel.org
Cc: serweb-users(a)lists.iptel.org
Hi to all,
I have successfully installed serweb and I can manage acl users grants as admin.
Should I configure my ser.cfg anyway?how to?
Any references will be well accepted.
Thanks,
Flavio
--
********************************
* (o< ing. Patria Flavio
* //\ phone 0823451358
* V_/_ mobile 3407873357
*
********************************
Hi all,
a customer of ours are having some trouble with the Content-Lenght
header when a NOTIFY-message goes through our OpenSER 1.2.0.
Here is what seem to happend.
SIP NOTIFY from our PSTN-gateway to our OpenSER:
--- CUT ---
Content-Length: 21.
.
SIP/2.0 100 Trying.
.
--- CUT ---
SIP NOTIFY from our OpenSER to Customer:
--- CUT ---
Content-Length: 21.
.
SIP/2.0 100 Trying.
--- CUT ---
Now, the customer has to manually do this in his OpenSER to make the UA
on his side happy:
if (method=="NOTIFY") {
if (search_body("SIP/2\.0 100 Trying"))
{
xlog("L_WARN", "R: Setting Content-Length to 20\n");
remove_hf("Content-Length");
append_hf("Content-Length: 20\r\n");
}
}
Please advice on what we are doing wrong here?
Br,
/Tobias
Hello everyone,
I'm currently running into the following problem, I currently run
openser SVN 1.3. With the following modparam("acc", "detect_direction", 1)
ON INCOMING CALL FROM PSTN AND HANGUP ON UAC
from/to username is flipped. (ERROR)
ON INCOMING CALL FROM PSTN AND HANGUP ON PSTN
from/to username remains 'detected'
ON OUTGOING CALL FROM UAC AND HANGUP ON PSTN.
from/to username is flipped. (ERROR)
ON OUTGOING CALL FROM UAC AND HANGUP ON UAC
from/tousername remains 'detected'
Has anyone ran into this issue, or know what I can do to remain direction
state? Thanks, all help is appreciated.
--
Brandon Armstead
Hi all, this is my first email to this list. hoping to mingle with you all
from now on.
I have been working on asterisk for about a year. Now my company is planning
to use openser with asterisk having asterisk at backend for features and
voicemail. So is there any book for starters for openser as there is for
asterisk (Asterisk the future of telephony). i need a book or any helpfull
link which should reveil the basic concepts of openser, how to install it,
how to program it, and how to manage it.
Thanx in advance
--
Rizwan Hisham
Software Engineer
AXVOICE Inc.
Hi!
Let's assume I have a load balancer which distributes (using hash over
R-URI) calls to 4 proxies. Further, ds_mark_dst() is used to marked
broken proxys.
Marking a destination as inactive - does this change the routing
completely (as if there were only 3 proxies in the config file) or will
it still hash over the 4 proxies, but choose automatically the second
entry in the resulting list if the result is the inactive proxy?
regards
klaus
Change log
xcap-lite (1.0.1) unstable; urgency=low
* Added support for multiple applications and detect them based on
xcap-root
* Added xcap-root setting in config.php
* Added pidf-manipulation application (to allow persistent
publication of
data using xcap server)
* Detect auth_domain from XCAP URI if SIP user is formatted as
user@domain
* Added DELETE method
The software can be downloaded from:
http://download.dns-hosting.info/XCAP/xcap-lite-1.0.1.tar.gz
Regards,
Adrian
