Hello,
as branch 4.4 was created to host the upcoming release series 4.4, new
features can be now pushed to master branch. They will be part of the
next future release, likely to be numbered 5.0.
Any fixes that affect existing code in branches 4.4 or older version
have to be backported - push first to master and then cherry pick --
some guidelines exemplified with branch 3.2 are available at:
- https://www.kamailio.org/wiki/devel/backporting-to-3.2.x
As usual, the next future release will be out as stable version in like
8-10 months, with the additional note that 5.0 is planned to include
some major refactoring and enhancements. See:
- https://www.kamailio.org/wiki/devel/kamailio-5.0-design
Many thanks to all contributors and enjoy Kamailio!
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio World Conference, May 18-20, 2016
Berlin, Germany - http://www.kamailioworld.com
Hello,
the GIT branch 4.4 was created, it will host the release series 4.4.x.
To get this branch from GIT, you can use:
git clone https://github.com/kamailio/kamailio.git kamailio
cd kamailio
git checkout -b 4.4 origin/4.4
Notes about installing Kamailio from this branch are available at:
- https://www.kamailio.org/wiki/install/4.4.x/git
Hopefully in about two weeks or so the full release of 4.4.0 will be out.
>From now on, any corresponding fix has to be pushed first to master
branch and then cherry-picked to branch 4.4. No new features can get in
branch 4.4. Enhancements to documentation or helping tools are still
allowed.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio World Conference, May 18-20, 2016
Berlin, Germany - http://www.kamailioworld.com
i send SIP reg request to kamailio and i got SIP request in wireshark and
also when i dump tcp then i got sip request
but in my kamailio.log i am not got SIP request please help me
my kamailio.log print this in my terminal
/usr/local/sbin/kamailio[25086]:INFO:<core>[main.c:798]:sig_usr():Signal 15
received
/usr/local/sbin/kamailio[15085]:INFO:<core>[main.c:798]:sig_usr():Signal 15
received
/usr/local/sbin/kamailio[15079]:INFO:<core>[sctp_core.c:53]:sctp_core_destroy():SCTP
API not initialized
/usr/local/sbin/kamailio[15079]:INFO:<core>[sctp_core.c:75]:sctp_core_check_support():SCTP
API not enabled-if you want to use it load sctp module
/usr/local/sbin/kamailio[23190]:INFO:rr[../outbound/api.h:54]:ob_load_api():failed
to import bind_ob
/usr/local/sbin/kamailio[23190]:INFO:rr[rr-mod.c:174]:mod_init():outbound
module not available
/usr/local/sbin/kamailio[23190]:INFO:usrloc[hslot.c:51]:ul_init_locks():locks
aaray size 1024
/usr/local/sbin/kamailio[23190]:INFO:<core>[udp_server.c:150]:probe_max_receive_buffer():SO_RCVBUF
is initially 163840
/usr/local/sbin/kamailio[23190]:INFO:<core>[udp_server.c:150]:probe_max_receive_buffer():SO_RCVBUF
is finally 327680
/usr/local/sbin/kamailio[23198]:INFO:ctl[io_listener.c:210]:io_listen_loop():io_listen_loop:using
epoll_lt as the io watch method (auto detected)
i want to print
INVITE
TO
FROM
Via
header file in my kamailio.log
Hello,
First excuse any mistakes in English. I'm working on a platform that makes
use of integrated Kamailio with asterisk (Elastix mt).
This platform allows the login of my SIP clients via the extension number
and the client's domain, where the kamailio after authentication change the
username to sip EXTENSION + _ + DOMAIN (expected by Asterisk) and sends to
the asterisk.
I need the client can also send the sip user in standard EXTENSION + _ +
DOMAIN, for it changed the view subscriber to also return a username record
in the format that the softphone is sending, but the platform still seems
not authenticate the REGISTER using new way functions in auth_check ("$
FD", "subscriber", "0") and auth_challenge ("$ FD", "0").
Thus works:
Login: 101
Domain/server: pabx999999.ligou.me
Password: PASSWORD_PLAIN
This way does not work:
Login: 101_pabx999999.ligou.me
Domain/server: pabx999999.ligou.me
Password: PASSWORD_PLAIN
Already got a good look at the documentation and could not find the
problem, could give me some help?
Kamailio.cfg: http://pasted.co/db8fb3a2
Execution debug log: http://pasted.co/49bfe5bf
Contents view subscriber:
+-----------------------------+---------------------+---------------+------+
| username | domain | ha1 | ha1b |
+-----------------------------+---------------------+---------------+------+
| admin | pabx999999.ligou.me | PASSWORD_PLAIN| NULL |
| adminIM | pabx999999.ligou.me | PASSWORD_PLAIN| NULL |
| 101 | pabx999999.ligou.me | PASSWORD_PLAIN| NULL |
| 103 | pabx999999.ligou.me | PASSWORD_PLAIN| NULL |
| 103IM | pabx999999.ligou.me | PASSWORD_PLAIN| NULL |
| admin_pabx999999.ligou.me | pabx999999.ligou.me | PASSWORD_PLAIN| NULL |
| adminIM_pabx999999.ligou.me | pabx999999.ligou.me | PASSWORD_PLAIN| NULL |
| 101_pabx999999.ligou.me | pabx999999.ligou.me | PASSWORD_PLAIN| NULL |
| 103_pabx999999.ligou.me | pabx999999.ligou.me | PASSWORD_PLAIN| NULL |
| 103IM_pabx999999.ligou.me | pabx999999.ligou.me | PASSWORD_PLAIN| NULL |
--------------------------------------------
Bruno H. G. Gouvêa
---
i am install kamailio in my linux pc and start kamailio successfully and
i want to print log messages in kamailio.log file please help me and give
me any idea what i need to add in my config file
please give me brief idea or reference for follow next step
my kamailio.log file print this but i want to print user registration
please help me what i need do
/usr/local/sbin/kamailio[25086]:INFO:<core>[main.c:798]:sig_usr():Signal 15
received
/usr/local/sbin/kamailio[15085]:INFO:<core>[main.c:798]:sig_usr():Signal 15
received
/usr/local/sbin/kamailio[15079]:INFO:<core>[sctp_core.c:53]:sctp_core_destroy():SCTP
API not initialized
/usr/local/sbin/kamailio[15079]:INFO:<core>[sctp_core.c:75]:sctp_core_check_support():SCTP
API not enabled-if you want to use it load sctp module
/usr/local/sbin/kamailio[23190]:INFO:rr[../outbound/api.h:54]:ob_load_api():failed
to import bind_ob
/usr/local/sbin/kamailio[23190]:INFO:rr[rr-mod.c:174]:mod_init():outbound
module not available
/usr/local/sbin/kamailio[23190]:INFO:usrloc[hslot.c:51]:ul_init_locks():locks
aaray size 1024
/usr/local/sbin/kamailio[23190]:INFO:<core>[udp_server.c:150]:probe_max_receive_buffer():SO_RCVBUF
is initially 163840
/usr/local/sbin/kamailio[23190]:INFO:<core>[udp_server.c:150]:probe_max_receive_buffer():SO_RCVBUF
is finally 327680
/usr/local/sbin/kamailio[23198]:INFO:ctl[io_listener.c:210]:io_listen_loop():io_listen_loop:using
epoll_lt as the io watch method (auto detected)
Hi folk!
Have a rare issue with tls connections.
Have a server with 100+ active tls connections, that are connected to
separate TCP proxy, that listen on port 443.
TCP proxy send sip traffic to Kamailio via localhost:5061. In this way all
connections in Kamailio are considered from Localhost.
Issue scheme:
- UA-A (sip-phone, UDP/TCP/TLS) -> call -> sip server (Kamailio+Asterisk
based) -> UA-B (sip phone, transport=TLS)
- The troubles happened in part of flow to UA-B:
--- kamailio script make lookup(location), find AOR for UA-B (here is OK)
--- after t_relay, kamailio make branch_route logic and try to send INVITE
to tcp socket
--- HERE IS the trouble: connection seems to be opened, but Kamailio cannot
send INVITE there (say: no open tcp connection found)
--- Kamailio try to open tcp connection from itself, TCP proxy refuse it
--- as a result - Kamailio answer 477 to Asterisk, and finish processing
debug level 3 logs (from the point where Kamailio try to send INVITE in
opened connection)
Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: <core> [tcp_main.c:1463]:
_tcpconn_find(): tcpconn_find: 0 port 60286
Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: <core> [ip_addr.c:243]:
print_ip(): tcpconn_find: ip 127.0.0.1
Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: <core> [tcp_main.c:1820]:
tcp_send(): tcp_send: no open tcp connection found, opening new one
Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: <core> [ip_addr.c:243]:
print_ip(): tcpconn_new: new tcp connection: 127.0.0.1
Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: <core> [tcp_main.c:1073]:
tcpconn_new(): tcpconn_new: on port 60286, type 3
Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: <core> [tcp_main.c:1626]:
_tcpconn_add_alias_unsafe(): _tcpconn_add_alias_unsafe: alias port 60286 for
hash 2646, id 404319
Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: <core> [tcp_main.c:1626]:
_tcpconn_add_alias_unsafe(): _tcpconn_add_alias_unsafe: alias port 60286 for
hash 2728, id 404319
Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: <core> [tcp_main.c:1624]:
_tcpconn_add_alias_unsafe(): _tcpconn_add_alias_unsafe: alias already
present
Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: <core> [tcp_main.c:1382]:
tcpconn_add(): tcpconn_add: hashes: 2646:2728:0, 863
Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: tls [tls_server.c:184]:
tls_complete_init(): Using TLS domain TLSc<default>
Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: tls [tls_domain.c:700]:
sr_ssl_ctx_info_callback(): SSL handshake started
Jan 25 14:32:43 /usr/sbin/kamailio[4722]: ERROR: <core> [tcp_main.c:2742]:
tcpconn_1st_send(): connect 127.0.0.1:60286 failed (RST) Connection refused
Jan 25 14:32:43 /usr/sbin/kamailio[4722]: ERROR: <core> [tcp_main.c:2752]:
tcpconn_1st_send(): 127.0.0.1:60286: connect & send for 0xb1d3b7e8 failed:
Connection refused (111)
Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: <core> [tcp_main.c:2947]:
tcpconn_chld_put(): tcpconn_chld_put: destroying connection 0xb1d3b7e8
(404319, -1) flags 0060
Jan 25 14:32:43 /usr/sbin/kamailio[4722]: ERROR: tm [../../forward.h:247]:
msg_send(): tcp_send failed
Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: tm [t_fwd.c:1591]:
t_send_branch(): t_send_branch: send to 127.0.0.1:60286 (3) failed
Jan 25 14:32:43 /usr/sbin/kamailio[4722]: WARNING: tm [t_fwd.c:1610]:
t_send_branch(): ERROR: t_send_branch: sending request on branch 0 failed
Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: tm [t_funcs.c:358]:
t_relay_to(): ERROR:tm:t_relay_to: t_forward_nonack returned error
Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: tm [t_funcs.c:375]:
t_relay_to(): -477 error reply generation delayed
Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: tm [t_lookup.c:1526]:
t_unref(): t_unref: delayed error reply generation(-477)
Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: <core>
[parser/msg_parser.c:339]: parse_headers(): parse_headers:
flags=ffffffffffffffff
Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: tm [t_reply.c:1670]:
cleanup_uac_timers(): DEBUG: cleanup_uac_timers: RETR/FR timers reset
Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: tm [t_reply.c:728]:
_reply_light(): DEBUG: reply sent out. buf=0xb67c000c: SIP/2.0 477
Unfortun..., shmem=0xb1b676cc: SIP/2.0 477 Unfortun
Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: tm [t_funcs.c:156]:
put_on_wait(): DEBUG: put on WAIT
Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: tm [t_reply.c:738]:
_reply_light(): DEBUG: _reply_light: finished
Additionally want to say, that suddenly we don't have clear reproduce, it
happened only on 2 production servers, what are common conditions for issue:
- transport=TLS
- when issued call is done, I checked with netstat, the connection is alive
- the issued device is re-REGISTERed as usual, in kamctl ul show I see
registration before/during/after issued call
- issue appear only when connection through our custom TCP proxy :443 (to
Kamailio it is from 127.0.0.1:5061)
- if connection switched to Kamailio 5061 directly - issue never (till now)
reproduced
- in one of the issued server - I noticed big number of tcp id. Doing kamcmd
core.tcp_list, I saw e.g. id: 567852 (usually id numbers are not more than
1000).
- if kamailio/device reboot - problem disappear
Because of not completely understanding how tcp core is working in kamailio,
ask any suggestion, why such could happen.
Any idea/hints would be greatly appreciated!
kamailio -v
version: kamailio 4.2.5 (i386/linux)
flags: STATS: Off, EXTRA_DEBUG, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS,
DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC,
F_MALLOC, DBG_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 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: unknown
compiled on 16:03:38 Jan 12 2016 with gcc 4.3.2
sorry for the long description
cheers!
--
View this message in context: http://sip-router.1086192.n5.nabble.com/rare-impossibility-to-send-requests…
Sent from the Users mailing list archive at Nabble.com.
Hello,
I am considering to branch v4.4 latest on March 10, after that the
master branch can be used again for adding new features and fixes will
be backported to branch 4.4. If it proves to worth branching earlier, it
can be done.
As an estimate date for the release of v4.4.0, a good candidate would be
one of the days between March 22, 23 or 24.
Any other suggestions or comments?
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, March 7-9, 2016 - http://www.asipto.com
As a suggestion for 5.0 having a scripted DB migration system would make upgrading much easier.
Something like what Asterisk now uses (Alembic https://pypi.python.org/pypi/alembic) would be ideal, as it works in a DB agnostic manner and you would just have to ensure that there is a driver for the DB you wish to use.
That way you would just update the definition script and select the target when you run the updater, and would allow kamailio a greater choice in backing DB's as once the script is written assuming a driver is available for you RDBMS the schema would be successfully ported.
This would do away with maintaining separate MySQL, Postgres, Oracle, MSSQL scripts as well.
The only issue I can think with a system like this is in the situation where hardcoded SQL strings are in the source and use a RDBMS specific function as that could cause some "fun" in debugging...
