Any idea?
From: Mickael Marrache [mailto:mickaelmarrache@gmail.com]
Sent: Thursday, April 09, 2015 2:08 PM
To: sr-users(a)lists.sip-router.org
Subject: RE: Avoiding "script writer didn't release transaction" warnings
I think understand in which case it happens.
When I receive a REGISTER, I create a transaction since I need to use the
t_continue feature to wake up a suspended transaction. However, the save()
command of the REGISTRAR module doesn't seem to call t_reply for replying
the 200 (it looks like the SL module is used instead). Therefore, I get the
warning every time it happens since the transaction is not released
explicitly.
Should I call t_release just before exiting the block handling the REGISTER?
From: Mickael Marrache [mailto:mickaelmarrache@gmail.com]
Sent: Thursday, April 09, 2015 1:43 PM
To: sr-users(a)lists.sip-router.org
Subject: Avoiding "script writer didn't release transaction" warnings
Hi,
In my logs, I get a lot of the following warnings:
WARNING: tm [t_lookup.c:1476]: t_unref(): WARNING: script writer didn't
release transaction
I force transaction creation from my script to absorb retransmissions as
soon as possible. I understand that I need to explicitly call t_release in
order to avoid this warning.
What is the most appropriate place in the script to call t_release?
Thanks,
Mickael
I have a small-ish project that could benefit from using an htable for storage of very basic data that doesn't change much, and I'd like to get an idea of what the group's experience is with storing larger amounts of data? Something in the 15-20GB range.
Yes I could use Redis, but the idea here is to minimize the amount of dependencies and processing required.
Thoughts?
Brooks Bridges | Sr. Voice Services Engineer
O1 Communications
5190 Golden Foothill Pkwy
El Dorado Hills, CA 95762
office: 916.235.2097 | main: 888.444.1111, Option 2
email: bbridges(a)o1.com<mailto:bbridges@o1.com> | web: www.o1.com<http://www.o1.com/>
Hi,
Why are all the CDR fields inserted as strings?
For extra fields, I can understand it is easier to implement. However, for
the built in fields (e.g. duration), we need to perform queries based on
duration and time and it is not really possible using strings.
I see that the time field for failed transactions is inserted as a date.
Thanks,
Mickael
Hi,
Very short question.
Why the time at which the dialog ended is also included in the CDRs?
There already are the start time and duration.
Is it there to avoid end time computation?
Mickael
Hi,
I'm using the ACC module to generate dialog based CDRs and I see that CDRs
are generated even for failed calls.
For example, a CDR is generated for cancelled calls.
At first, I thought that dialog based CDRs are generated only for
successfully established dialogs but it doesn't seem to be the case.
Thanks,
Mickael
Hello,
We have setup Kamailio SIP Server v4.1.7 at latest our Rackspace server
(ubuntu 14.10)
Chat works fine on all cases and calls are working for Local network only(
I think its when it doesn't uses rtpproxy). Over Internet( on real ips
rather than local one), we are able to make calls(audio/video) and we can
see that Our packets are being transmitted properly to the server, but we
are unable to get those packets to client side back from the server.
So, Client-to-Server : works
but, Server-to-Client : it doesn't works
FYI, We have confirmed that firewalll is inactive on our server and
required ports are open. We have tried with and without tls (self signed
certificates only). The SIP client we used to test the environment is JITSI.
We are getting following error :
Apr 10 10:46:39 telezang-app /usr/local/sbin/kamailio[25670]: ERROR:
rtpproxy [rtpproxy.c:1756]: select_rtpp_node(): script error -no valid set
selected
Apr 10 10:46:39 telezang-app /usr/local/sbin/kamailio[25670]: ERROR:
rtpproxy [rtpproxy.c:2636]: force_rtp_proxy(): no available proxies
Apr 10 10:46:44 telezang-app /usr/local/sbin/kamailio[25641]: ERROR:
rtpproxy [rtpproxy.c:1756]: select_rtpp_node(): script error -no valid set
selected
Apr 10 10:46:44 telezang-app /usr/local/sbin/kamailio[25641]: ERROR:
rtpproxy [rtpproxy.c:2636]: force_rtp_proxy(): no available proxies
Apr 10 10:46:44 telezang-app /usr/local/sbin/kamailio[25641]: NOTICE: acc
[acc.c:315]: acc_log_request(): ACC: transaction answered:
timestamp=1428662804;method=INVITE;from_tag=978a791a;to_tag=3458055147;call_id=6c08683633dd586d0e634f5e2bbfa99c@0
:0:0:0:0:0:0:0;code=200;reason=OK;src_user=user1;src_domain=
mobileappplatform.com
;src_ip=202.157.76.21;dst_ouser=user4;dst_user=user4;dst_domain=192.168.5.115
Apr 10 10:46:44 telezang-app /usr/local/sbin/kamailio[25643]: ERROR:
rtpproxy [rtpproxy.c:1756]: select_rtpp_node(): script error -no valid set
selected
Apr 10 10:46:44 telezang-app /usr/local/sbin/kamailio[25643]: ERROR:
rtpproxy [rtpproxy.c:2636]: force_rtp_proxy(): no available proxies
Apr 10 10:46:48 telezang-app /usr/local/sbin/kamailio[25670]: ERROR:
rtpproxy [rtpproxy.c:1756]: select_rtpp_node(): script error -no valid set
selected
Apr 10 10:46:48 telezang-app /usr/local/sbin/kamailio[25670]: ERROR:
rtpproxy [rtpproxy.c:1960]: unforce_rtp_proxy(): no available proxies
Apr 10 10:46:49 telezang-app /usr/local/sbin/kamailio[25644]: NOTICE: acc
[acc.c:315]: acc_log_request(): ACC: transaction answered:
timestamp=1428662809;method=BYE;from_tag=978a791a;to_tag=3458055147;call_id=6c08683633dd586d0e634f5e2bbfa99c@0
:0:0:0:0:0:0:0;code=200;reason=OK;src_user=user1;src_domain=
mobileappplatform.com
;src_ip=202.157.76.21;dst_ouser=user4;dst_user=user4;dst_domain=202.157.76.21
Thanks
On Fri, Apr 10, 2015 at 4:38 PM, <users-request(a)lists.opensips.org> wrote:
> Welcome to the Users(a)lists.opensips.org mailing list!
>
> To post to this list, send your email to:
>
> users(a)lists.opensips.org
>
> General information about the mailing list is at:
>
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
> If you ever want to unsubscribe or change your options (eg, switch to
> or from digest mode, change your password, etc.), visit your
> subscription page at:
>
>
> http://lists.opensips.org/cgi-bin/mailman/options/users/followtest111%40gma…
>
>
> You can also make such adjustments via email by sending a message to:
>
> Users-request(a)lists.opensips.org
>
> with the word `help' in the subject or body (don't include the
> quotes), and you will get back a message with instructions.
>
> You must know your password to change your options (including changing
> the password, itself) or to unsubscribe. It is:
>
> 123456
>
> Normally, Mailman will remind you of your lists.opensips.org mailing
> list passwords once every month, although you can disable this if you
> prefer. This reminder will also include instructions on how to
> unsubscribe or change your account options. There is also a button on
> your options page that will email your current password to you.
>
Hi,
is there any way to configure the tls curve like secp384r1 in the config?
I use actually version 4.2.4
On the other side i can't see any connection Information in the logs.
I would like to see something like: "Connected with TLSv1.1 using cipher
ECDHE-RSA-AES256-GCM-SHA384 and curve secp384r1"
With this logs the variety of the offered ciphers can be shortened to
the most secure and only needed by the clients.
Regard T.Tributh
Hello,
I'd like to authenticate Kamailio users in LDAP. But it looks like
Kamailio need to download password from LDAP and authenticate
user on it's own. Is there any possibility to send password to LDAP
and let LDAP to say, if the user can be sign in?
Thanks
Marek Moravčík