Hello,
first I want to thank to all participants at 10 Years SER event in
Berlin last Friday. We spent great time, at least I did!
We accepted 50 visiting participants to match the maximum capacity of
the conference room, being full booked about 2 weeks before. Just few
people didn't show up and didn't inform us at all in advance, which was
a pity over all since several persons that registered later were not
accepted, thus some of them could have attended. Folks at Fokus working
with SER/Kamailio joined us and we had probably one of the very few
occasions so far to get so dense knowledge of SIP/VoIP in the same
place, making a day of interesting presentations and open discussions.
Accompanied by nice weather in Berlin, the evening at Playa Paradiso on
river Spree offered a great place for continuing the technical and
mufti-cultural debates (I could count attendees from about 15 countries
(including Brazil!)). Many thanks again to our sponsors for free drinks
and food at this event: Sipgate (http://www.sipgate.de), Amooma
(http://www.amooma.de), NG-Voice (http://www.ng-voice.com), Asipto
(http://www.asipto.com), Frafos (http://www.frafos.com) and Fokus
Institute (http://www.fokus.fraunhofer.de).
I will upload the presentations soon and send an update here -- there
were 15 talks, covering from technical concepts to business matters and
open source philosophy. Therefore if you were a speaker and see this
message, please send the pdf slides to me.
Do not forget, you can join the next party for this celebration this
week in Vienna, details at:
* http://sip-router.org/10-years-ser-vienna/
Meanwhile, be sure you start/continue testing the upcoming release
v3.2.0, we have to be sure it is stable to release it and start a new
development cycle in the near future, to be able to present new features
at the 11th celebration :-) . Here is a step by step guide to pull the
code from GIT and install:
*
http://www.kamailio.org/dokuwiki/doku.php/install:kamailio-devel-from-git
Cheers,
Daniel
--
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Oct 10-13, Berlin: http://asipto.com/u/kathttp://linkedin.com/in/miconda -- http://twitter.com/miconda
Hi,
I am experiencing two problem:
First:
I am experiencing that tls read buffer overflow, if i use default value
of tcp_rd_buf_size
If i doubled the size of read buffer and i use
tcp_rd_buf_size=8192
then the problem seems to be solved.
Second:
I am experiencing that TLS connection is dropped by sip proxy very
frequently!
And i think the tcp connection shouldn't dropped! So my guess is that
TLS communication is not restarting the timeout counters!
So in every 2 minutes the sip-router is restarting the TCP connection
with tcp RST.
like this:
Sep 5 11:28:48 hal /usr/sbin/kamailio[8129]: DEBUG: <core>
[tcp_main.c:4304]: tcp_main: entering timer for 0xac537c74
(ticks=446299809, ti
meout=446299809 (0 s), wr_timeout=0 (240541717 s)), write queue: 0 bytes
Sep 5 11:28:48 hal /usr/sbin/kamailio[8129]: DEBUG: <core>
[tcp_main.c:4346]: tcp_main: timeout for 0xac537c74
Sep 5 11:28:48 hal /usr/sbin/kamailio[8129]: DEBUG: <core>
[io_wait.h:617]: DBG: io_watch_del (0x824cf80, 48, -1, 0x10) fd_no=41 called
Sep 5 11:28:48 hal /usr/sbin/kamailio[8129]: DEBUG: tls
[tls_server.c:597]: Closing SSL connection 0xac4a0374
Sep 5 11:28:48 hal /usr/sbin/kamailio[8129]: DEBUG: <core>
[ip_addr.c:247]: tcpconn_new: new tcp connection: 10.10.10.10
Sep 5 11:28:48 hal /usr/sbin/kamailio[8129]: DEBUG: <core>
[tcp_main.c:1081]: tcpconn_new: on port 36142, type 3
Sep 5 11:28:48 hal /usr/sbin/kamailio[8129]: DEBUG: <core>
[tcp_main.c:1382]: tcpconn_add: hashes: 2473:3781:3367, 5
This second problem is not solved and very urgent for me.
Any help suggestion is highly appreciated!
Thanks,
Misi
Hi all,
I'm happy to announce a new developer for the sip-router project:
Sven Knoblich.
Sven is an experienced C/C++ developer in our offices in Karlsruhe and since
about a year part of the team that develops our VoIP backend services.
Past contributions of him were the CDR based accounting extensions in the acc
module and several other bugfixes and extensions for the dialog module. He'll
maintain in the future this new acc and dialog functionality and also other
code contributed from us.
Best regards,
Henning
--
Henning Westerholt - Head of IT Operations Internet Access & Communications
1&1 Internet AG, Brauerstraße 48, 76135 Karlsruhe, Germany
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#122 - Kamailio 3.1.3 crash
User who did this - Jasmin Schnatterbeck (jasmin)
----------
Hey Timo,
thanks for the integration of the patches. I'm going to try out dlg_manage() instead of dlg_get() (which does not detect spirals properly) within the next week...
Regarding the working "quick and dirty" fix:
modules_k/mi_datagram/mi_datagram.c
line 280:
pid=fork_process(PROC_NOCHLDINIT, "MI DATAGRAM", 1);
to:
pid=fork_process(PROC_RPC, "MI DATAGRAM", 1);
I have not recognized any disadvantages reasoned by that... at least in 3.1 it's not included yet.
Jasmin
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=122#comment255
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.
The following task has a new comment added:
FS#149 - Via parser does not accept any token as transport
User who did this - Iñaki Baz Castillo (ibc)
----------
RFC 3261 is very clear:
Via = ( "Via" / "v" ) HCOLON via-parm *(COMMA via-parm)
via-parm = sent-protocol LWS sent-by *( SEMI via-params )
via-params = via-ttl / via-maddr
/ via-received / via-branch
/ via-extension
via-ttl = "ttl" EQUAL ttl
via-maddr = "maddr" EQUAL host
via-received = "received" EQUAL (IPv4address / IPv6address)
via-branch = "branch" EQUAL token
via-extension = generic-param
sent-protocol = protocol-name SLASH protocol-version
SLASH transport
protocol-name = "SIP" / token
protocol-version = token
transport = "UDP" / "TCP" / "TLS" / "SCTP"
/ other-transport
other-transport = token
So Via transport can be _token_, which means any ASCII string.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=149#comment254
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 - Iñaki Baz Castillo (ibc)
Attached to Project - sip-router
Summary - Via parser does not accept any token as transport
Task Type - Bug Report
Category - Core
Status - Assigned
Assigned To - Andrei Pelinescu-Onciul
Operating System - All
Severity - Low
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - Hi, sip-router Via parser is not RFC compliant as it does not accept any token in the transport (even if this does NOT occur in the top Via). A real example: kamailio receives a REGISTER like this (removing other headers):
REGISTER sip:domain,org SIP/2.0
Via: SIP/2.0/UDP 1.2.3.4:9090;branch=z9hG4bK3afb3d8e9ea4c4259f9d;rport
Via: SIP/2.0/WS 1.2.3.4:36638;branch=z9hG4bK5089;received=9.9.9.9;rport=36638
And it fails parsing so also processing the request:
ERROR: <core> [parser/parse_via.c:1677]: ERROR: parse_via: bad char <W> on state 122
ERROR: <core> [parser/parse_via.c:2366]: ERROR: parse_via on: <SIP/2.0/UDP 1.2.3.4:9090;branch=z9hG4bK3afb3d8e9ea4c4259f9d;rport [...]>
ERROR: <core> [parser/parse_via.c:2370]: ERROR: parse_via parse error, parsed so far:<SIP/2.0/>
ERROR: <core> [parser/msg_parser.c:139]: ERROR: get_hdr_field: bad via
INFO: <core> [parser/msg_parser.c:353]: ERROR: bad header field [Via: SIP/2.0/WS 1.2.]
Please, make it possible for the Via transport to contain an unknown token, at least when it does NOT occur in the top Via header. Why should Kamailio care about the second Via transport field?
Thanks a lot.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=149
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 user has added themself to the list of users assigned to this task.
FS#149 - Via parser does not accept any token as transport
User who did this - Iñaki Baz Castillo (ibc)
http://sip-router.org/tracker/index.php?do=details&task_id=149
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.
Jon Bonilla has taken ownership of the following task:
FS#148 - typo in debian packaging files (kamailio-xmlrcp-modules)
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=148
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.