I have kamailio behind a TLS termination proxy so the sockets are correctly
deduced to be TCP. However the clients only talk TLS to the proxy and are
confused when the top Via header added by Kamailio is TCP. Is there a way
for Kamailio to forcibly pretend its protocol is TLS? Like
advertised_address but "advertised_protocol" instead.
(With pjsip testing: it has a flag use_tls which ignores TCP from Kamailio
and continues to use the persistent TLS transport to proxy. Linphone fails
because it tries to honor TCP in Via and is unable to establish TCP
transport).
BTW I am using t_relay_to_tcp so Kamailio will return traffic to the proxy
as TCP even though the contact addresses specify transport=TLS.
Hi everybody,
I'm just testing Kamailio 5.4.1 with dialog replication over DMQ. This
seems to work very good. Dialogs are replicated without problems.
When I'm restarting one node I would have expected, that all dialogs are
synced again, just like in dmq_usrloc.
But this does not happen. After a restart the nodes dialog-list is empty.
Did I miss somethin? Is there a special parameter that I have to set?
BR, Björn
--
Björn Klasen, Specialist
TNG Stadtnetz GmbH, Network Management (VoIP)
Projensdorfer Straße 324
24106 Kiel
Germany
T +49 431/ 530530
F +49 431/ 7097-555
mailto: bklasen(a)tng.de
http://www.tng.de
Register: Amtsgericht Kiel HRB 6002 KI
Executive board (Geschäftsführung): Dr.-Ing. Volkmar Hausberg,
Sven Schade, Carsten Tolkmit, Dr. Sven Willert
Tax-Id (Steuernr.): 2029047020, VAT-Id (USt-Id): DE225201428
Hi there,
I have taken over a project that uses Kamailio.
I am aware of what we use it for - I am just not sure on the how... apart
from what I have read in the docs.
We're currently running 5.4.2 and I'd like to upgrade to (at least) the
latest 5.4 offering - as that seems as if it would be the easiest and
safest option.
So I am hoping I might get some direction, please - on the way forward for
an upgrade.
The documentation seems OK if you're upgrading minor versions... but I
couldn;t find anything about upgrading patch versions.
Thanks!
Hello,
we should consider an online devel meeting sometime soon to summarize
what was done at (and still needs to be done after) devel meeting in
Dusseldorf and plan a bit the targets for next major release (5.8 or 6.0)?
If considered useful, I propose Dec 5 at 15:00UTC (16:00
Berlin/Paris/Madrid/Rome), but we can also look for other dates as well.
Topics to be discussed can be added at:
-
https://github.com/kamailio/kamailio-wiki/blob/main/docs/devel/irc-meetings…
Pull requests can be made by users without git access.
Cheers,
Daniel
PS: Previous announcement indicated the start time 14:30 UTC, this
message changes it to 15:00 UTC - 30min later due to a constraint in
availability of one of the Kamailio developers.
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Hi,
I am needing some help setting up kamailio as a sip proxy between a
provider(trunk) and a test pbx
The trunk requires username&password and i would like to add that
information to the request within the Kamailio proxy, so that the PBX can
authenticate directly by IP (without username&password) through the
Kamailio proxy.
As a programmer with a limited background in SIP (currently learning), I am
keen on understanding the intricacies of this setup at the SIP level.
Could you please direct me to resources or documentation that covers
scenarios similar to mine?
Any help or guidance you could provide would be greatly appreciated.
Thanks
Hi,
I wanted to revisit the topic of tsilo dependence on the location service. All three ts_append*() functions have the following quality:
- ts_append(): "performing a contact lookup on the table specified by the domain parameter."
- ts_append_by_contact(): "the contact lookup is performed"
- ts_append_to(): "performing a contacts lookup on the table specified by the domain parameter"
Why is this extensive coupling to usrloc necessary? This makes it impossible to use `tsilo` in case of providing a push-notification add-on that front-ends an upstream registrar, requiring a kind of local shadow registrar or mid-registrar. What would make more sense is a generic mechanism that allows one to "drip" new contacts into an existing transaction, whether suspended or active.
Kamailio has a mechanism to add more branches to an existing transaction, but the scope of that mechanism is only from *inside* the vantage point of the transaction in question. The key parlour trick of `tsilo` is that it permits dripping new branches into a *different* transaction.
ts_append_to() almost does the trick, providing a target index and label, but it just insists on doing a registrar lookup to source the contacts.
What is really wanted and needed for the downstream PN gateway use-case is a means of extracting contacts from incoming registrations (or other sources, potentially) without storing them in any fashion locally, without using or even loading usrloc, and just throwing them over the fence into a different transaction.
Is this somehow possible by means other than tsilo? Am I overlooking something?
Cheers,
-- Alex
--
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: https://evaristesys.com
Tel: +1-706-510-6800
Hi List
I want to find a way to check how many users are regsitered.
https://www.kamailio.org/docs/modules/devel/modules/usrloc.html#usrloc.r.db…
But no matter how I try, I get a 500 error...
# kamcmd ul.db_users location
And yes, the table is called 'location'.
I did try to find out how kamctl ul show --brief pulls that
information, but did not succeed. Also that command takes way too long
how that we have several thousand registered users.
Or would I need to query this directly from the database?
Mit freundlichen Grüssen
-Benoît Panizzon-
--
I m p r o W a r e A G - Leiter Commerce Kunden
______________________________________________________
Zurlindenstrasse 29 Tel +41 61 826 93 00
CH-4133 Pratteln Fax +41 61 826 93 01
Schweiz Web http://www.imp.ch
______________________________________________________
Hi,
I have a timer which is called each 5 seconds:
modparam("timer", "declare_timer", "REFRESH_CALLSTATE_TIMER=REFRESH_CALLSTATE_TIMER,5000,slow");
I'm enabling setting the variable "testvar" and enabling the timer when an INVITE is received:
if (is_method("INVITE|ACK|UPDATE|CANCEL|BYE")) {
$var(testvar) = "blablabla";
timer_enable("REFRESH_CALLSTATE_TIMER", "1");
...
route[REFRESH_CALLSTATE_TIMER] {
xlog("L_INFO", "Testvariable: $var(test)\n");
}
However, the variable is always 0:
INFO: <script>: Testvariable: 0
I've also tried printing pseudovariables like $ci, $du but nothinh seems accessible. Is there a workaround for this?
Best regards,
Dries
Hi,
I would like to catch TCP timeouts when I use a socket that was not closed.
In this example I am sending SIP MESSAGE
...
t_on_reply("ON_REPLY_MESSAGE");
t_on_failure("FAILURE_MESSAGE");
if (!t_relay())
sl_reply_error();
Hello,
I'm trying to use the evapi_async_relay function from the evapi
module, however,I don't want the transaction to be suspended for more
than 1 second.
For instance, if there's no response from the external application
within this time frame, I want the script to continue and remove that
transaction from memory.
One potential approach I am considering is to add suspended
transactions to a hash table with a timestamp value. Then, using
rtimer module, I could periodically parse this table every second and
process the results, but I'm not sure how efficient is that.
Maybe you know other alternative, more efficient solutions (from a
performance point of view) that could achieve the same goal?
Any insights or recommendations would be greatly appreciated.
Thank you.