i compiled today sr from master and got warning:
CC (cc) [M kex.so] core_stats.o
core_stats.c: In function ‘mi_reset_and_add_stat’:
core_stats.c:342: warning: implicit declaration of function ‘get_stat_val_long’
-- juha
Hello,
in about five weeks the kamailio project will (again) be present on the
LinuxTag fair, "the most important place for Linux and open source software in
Europe" - http://www.linuxtag.org/2011/en.html .
If you are in Berlin during this time, plan to visit the LinuxTag or just like
to help your favourite SIP server project - please consider supporting us in
running our fair booth! Even showing up for one or two hours helps a lot.
We need also support to properly present our project, like flyers, a banner,
maybe some live demonstrations.. So even if you can't participate in person,
there are other ways to help us!
Please contact me per mail if you could help at the booth or have some ideas
about our project presentation. The actual state of preparations can be found
in our wiki: http://sip-router.org/wiki/meetings/berlin_2011
Cheers,
Henning
(moving to sr-dev)
This looks like a bug to me. All such AVPs should be preserved for
reply and failure route blocks. Let me see if I can reproduce it, I'll
get back to you later this week.
-Jan
On Fri, Apr 22, 2011 at 3:00 PM, Juha Heinanen <jh(a)tutpro.com> wrote:
> domain module sets $td.did at lookup_domain call. $td.did seems to be a
> normal avp, because i can print its value with xlog by referring to it
> as $avp(td.did). however, its value is gone at failure route, which
> makes me suspect that $td.did is not really a normal avp.
>
> in route block i have
>
> $avp(did) = $td.did;
> xlog("L_INFO", "at t_relay: <td/td.did> = <$avp(did)/$avp(td.did)>\n");
> if (t_relay()) exit;
>
> branch route, onreply route, and failure route are set when the above
> t_relay() takes place.
>
> at the end of branch route block, i have
>
> xlog("L_INFO", "at end of contact branches: <did/td.did> = <$avp(did)/$avp(td.did)>\n");
>
> and at the beginning of onreply route block:
>
> xlog("L_INFO", "at beginning of onreply: <did/td.did> = <$avp(did)/$avp(td.did)>\n");
>
> and at the beginning of failure route block:
>
> xlog("L_INFO", "at beginning of contact failure: <did/td.did = <$avp(did)/$avp(td.did)>\n");
>
> when i make a call, i get to syslog:
>
> Apr 22 15:53:27 sip /usr/sbin/sip-proxy[13706]: INFO: at t_relay: <td/td.did> = <test.fi/test.fi>
> Apr 22 15:53:27 sip /usr/sbin/sip-proxy[13706]: INFO: at end of contact branches: <did/td.did> = <test.fi/test.fi>
> Apr 22 15:53:27 sip /usr/sbin/sip-proxy[13708]: INFO: at beginning of onreply: <did/td.did> = <test.fi/<null>>
> Apr 22 15:53:27 sip /usr/sbin/sip-proxy[13705]: INFO: at beginning of contact failure: <did/td.did = <test.fi/<null>>
>
> why is it that $avp(did) value has been preserved from route/branch
> route block to onreply/failure blocks, but value of $avp(td.did) is not?
>
> i'll cc to jan in case he is not on this list.
>
> -- juha
>
>
Hi all,
I'm trying to use the TLS module in order to allow the secure communication
between Kamailio server v. 3.1.3 as registrar and presence server and my PC
Client.
I'm using SIP Communicator (Jitsi).
When the PC client open the SSL connection to Kamailio server for
Register/Subscriber/Publish messages, all seems OK. We see the PC client
send "Client Hello" and the Kamailio answer "Server Hello" then they
exchange the SIP messages (Register/Subscriber/Publish and thier answer).
We observed a strange behavior, when Kamailio try to send the Notify to PC
client, it open a new SSL connection as a client from kamailio to PC client
and send the "Client Hello" to PC client, but PC client send back the
Handshake Failure (40) Fatal error back to Kamailio.
Here are the doubts:
- why kamailio open a new ssl connection to PC in order to send the Notify
even the ssl connection is already opened by PC?
- is it the problem of the PC client which can not treat as a SSL server?
Is it a PC client's problem or Kamailio's problem?
The error in the kamailio site is:
/usr/sbin/kamailio[4483]: ERROR: tls [tls_server.c:1174]: TLS
connect:error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert
handshake failure
/usr/sbin/kamailio[4483]: ERROR: <core> [tcp_read.c:882]: ERROR:
tcp_read_req: error reading
Could you please suggest another SIP client supporting the TLS protocol?
thanks anf kind regards.
laura