THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Tomek Kotecki (koteckit)
Attached to Project - sip-router
Summary - Error in generating Publush with state confirmed at recived 200OK package.
Task Type - Bug Report
Category - Module
Status - Unconfirmed
Assigned To -
Operating System - Linux
Severity - Low
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - Hi,
We have found a bug in version 3.2.0 kamailio (also occurs in 3.2.1).
Pua_dialoginfo module generates an incorrect status for the package xml 200OK (method INVITE).
In version 3.1.5 for package 200OK status in the body XML was correct and was: <state>confirmed </ state>.
In version 3.2.x for package 200OK status in the body XML is: <state>terminated</ state>.
In log from kamailio 3.2.0 we found ERROR:
/usr/sbin/kamailio[1997]: ERROR: pua_dialoginfo [pua_dialoginfo.c:284]: unhandled dialog callback type 8 received, from=sip:username12@sip.mydomain.com
/usr/sbin/kamailio[1997]: DEBUG: pua_dialoginfo [dialog_publish.c:242]: new_body: <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="0" state="full" entity="sip:username12@sip.mydomain.com"> <dialog id="baeb1755-42d613e2(a)192.168.2.59" call-id="baeb1755-42d613e2(a)192.168.2.59" direction="initiator"> <state>terminated</state> <remote> <identity>sip:11@sip.mydomain.com</identity> <target uri="sip:11@sip.mydomain.com"/> </remote> <local> <identity>sip:username12@sip.mydomain.com</identity> <target uri="sip:username12@XX.XX.6.1:29727"/> </local> </dialog> </dialog-info>
Correct in kamailio 3.1.5, without ERROR:
/usr/sbin/kamailio[29551]: DEBUG: pua_dialoginfo [pua_dialoginfo.c:223]: dialog confirmed, from=sip:username12@sip.mydomain.com
/usr/sbin/kamailio[29551]: DEBUG: pua_dialoginfo [dialog_publish.c:242]: new_body: <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="0" state="full" entity="sip:username12@sip.mydomain.com"> <dialog id="16ee2c89-2e618509(a)192.168.2.59" call-id="16ee2c89-2e618509(a)192.168.2.59" direction="initiator"> <state>confirmed</state> <remote> <identity>sip:11@sip.mydomain.com</identity> <target uri="sip:11@sip.mydomain.com"/> </remote> <local> <identity>sip:username12@sip.mydomain.com</identity> <target uri="sip:username12@XX.XX.6.1:58340"/> </local> </dialog> </dialog-info>
Best Regards,
TK
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=187
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.
Question: how does the 'autoexpire' parameter to the 'htable' modparam
interact with the 'expires' value now present in the database table
definition for a DB-backed 'htable'? Which one has priority?
--
Alex Balashov - Principal
Evariste Systems LLC
260 Peachtree Street NW
Suite 2200
Atlanta, GA 30303
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/
Sorry for the stupid question, but is there a generic toplevel make
target that will compile Kamailio/SR in ways maximally suitable for
GDB analysis, e.g.
- Without optimisations that strip out some symbols and values.
- With -g, -ggdb, etc.
Thanks!
--
Alex Balashov - Principal
Evariste Systems LLC
260 Peachtree Street NW
Suite 2200
Atlanta, GA 30303
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/
Just a note for the archives or somebodys todo-list:
When compiling mi_xmlrpc with the latest xmlrpc-c package in Centos 6 or FreeBSD 8 compilation fails. Seems like we're very depending on a particular library version. Which the build system warns me about...
/O
Hi all,
when there many records in DB tables like location(usrloc use write
back mode), pua etc, kamailio fail to start by complaining "no pkg
memory left" when try to load (restore) all records from DB to
hashtable of location/pua. The share momory are allocated enough for
the hashtable, but the default compilation of the PKG_MEMORY_SIZE is
4MB, which allow only restore several thousands records. I know I can
increase the PKG_MEMORY_SIZE, but anyway there is a limitation which
may fail to restore all records from DB during the startup of kamailio
if it reach the limit of the number of records in DB.
Is there anyway to reload the hashtable from table by doing query n
rows a time and loop until non more result from DB? this will avoid
the kamailio startup problem when there are many records in hashtable
which are save also in DB.
Thank you very much in advanced!
Laura
Are these variables valid?
Are the explanations still up to date?
Thanks,
/O
---------------
# -DUSE_TLS
# compiles in tls support, requires -DUSE_TCP. Note: this is only
# generic support (parsing a.s.o.), it does not include the actual
# "tls engine". If you really want tls you need also either
# -DCORE_TLS and a tls/ subdir with the tls code or -DTLS_HOOKS and
# the tls module loaded.
# -DCORE_TLS
# compiles tls in-core support. Requires -DUSE_TLS, conflicts
# -DTLS_HOOKS. Please use make CORE_TLS=1 instead (it will set all the
# needed defines automatically and extra libraries needed for linking).
# -DTLS_HOOKS
# compile tls module support (support for having the "tls engine" in a
# module). Requires -DUSE_TLS, conflicts -DCORE_TLS.
# Please use make TLS_HOOKS=1 (or TLS_HOOKS=0 to for disabling) instead
# of setting -DTLS_HOOKS (it will set all the needed defines
# automatically)
Greetings,
This is a call for presenters (with presentations!) for the telephony
and communications devroom at FOSDEM 2012 - http://www.fosdem.org/.
We will be holding a day full of presentations on development topics in
the area of open source telephony and communications on Sunday, February
5th. The schedule allows for presentations from 9:00 to 17:00. The room
we will be using will have a projector, wifi, and 100 seats.
Please submit all proposals no later than 2011-12-09. Notification of
accepted speakers will be provided by 2011-12-16. We will then work to
have a schedule finalized by 2012-01-06. Talks should be submitted by
subscribing to and then posting to the telephony-devroom mailing list
hosted on http://lists.fosdem.org/. If you would like to contact the
devroom organizer directly, please contact Kevin P. Fleming <kpfleming
at digium.com>.
Feel free to forward this along to any people or mailing lists that you
think would be interested in this event.
Thank you!
Bryan M. Johns
Digium, Inc. | Community Director
Direct: 256.428.6007
http://twitter.com/bryanmjohns
Check us out at : www.asterisk.org or www.digium.com