THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#234 - kamailio crah [pass_fd.c:293]: ERROR: receive_fd: EOF on 46
User who did this - David Kovarik (kovik)
----------
kamailio -V
version: kamailio 3.3.0-pre2 (x86_64/linux) 62baa1
flags: STATS: Off, USE_IPV6, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 4MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: 62baa1
compiled on 09:39:56 May 17 2012 with gcc 4.4.5
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=234#comment650
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - David Kovarik (kovik)
Attached to Project - sip-router
Summary - kamailio crah [pass_fd.c:293]: ERROR: receive_fd: EOF on 46
Task Type - Bug Report
Category - Core
Status - Unconfirmed
Assigned To -
Operating System - All
Severity - Critical
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - kamailio crash with [pass_fd.c:293]: ERROR: receive_fd: EOF on 46
after auth INVITE from different port from 3g network
First INVITE come from port 2833 and auth INVITE from port 56393
One or more files have been attached.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=234
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
Hello,
looking at the volume of reported issues on mailing lists and tracker,
upcoming v3.3.0 seems to go well. I have few items on my to-do reported
on the mailing list.
Otherwise, in my side, I have 3.3.0 running in a production-like
environment for about 4 weeks without problems and another one in a
pre-production phase.
Having in consideration all these, I propose to branch 3.3 on June 11.
If everything looks very good at that time (or actually few days
before), I think we can do the release also by that date. If not, we can
do it a week later.
Branching will allow new features development on git master, there are
already several contributed patches with new features flowing around on
mailing lists and tracker.
Therefore, if you are aware of any issue, please report asap on mailing
list (sr-dev) or tracker (preferable - http://sip-router.org/tracker/).
Other suggestions about planning the release 3.3.0 are welcome, as well.
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - http://asipto.com/u/katu
Hi
Is there any reason why shm_free does not set the pointer it is freeing to
zero once it is free-ed?
Code like:
*if (pointer) {
shm_free(pointer);*
Is not really useful seen as how shm_free does not set the pointer to zero
- any double free will still cause a crash.
I suppose it forces the developer to be careful with memory management - is
this the only reason?
Regards
Richard.
This email is subject to the disclaimer of Smile Communications (PTY) Ltd. at http://www.smilecoms.com/disclaimer
"
1.4.6. delete_timer (integer)
Time after which a to-be-deleted transaction currently ref-ed by a process will be tried to be deleted again (in milliseconds).
Note: this parameter is obsolete for ser 2.1 (in 2.1 the transaction is deleted the moment it's not referenced anymore).
Default value is 200 milliseconds."
What's the status of the delete_timer in 3.2 and devel (3.3) ? We should propably update docs here.
/O
Hi
Please excuse the newbie posting, but I really need some help !
I want to expand Kamailio to act as an OMA PoC Server. To do this, I
need to build some floor-control using TBCP and add logic to select
speakers, etc, which I can do.
But.... Before I even do that, I need to support the PUBLISH event
"poc-settings" This is where the client declares that it is a PoC
device and what it's status is (RFC 4354). I've read, re-read and
re-re-read the documentation, but the architecture and how it impacts
the various modules is still unclear to me.
Here are my questions:
1) I can see that presence_xml is where the "presence" and
"winfo...." events are handled. Do I need to expand this to include
poc-settings ?
2) The poc-settings per client are sent in the XML body.
Where/how does that get parsed, and is that then stored in the MySQL
database ? Does that mean that I need to expand the parser to handle
the new poc-settings message ? Does that also mean that I need to add
new elements to my openser database ?
Thanks in advance
David
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#230 - $sndto(ip) gives ip:port instead of just IP
User who did this - Daniel-Constantin Mierla (miconda)
Reason for closing: Fixed
Additional comments about closing: Fixed some time ago, see comment.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=230
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.