Im trying to do a t_suspend, but cant get htable to work
I save to $sht
$sht(vtp=>join::$rU) = "" + $T(id_index) + ":" + $T(id_label);
xlog( "L_ALERT", "Suspended transaction sht(vtp=>join::$rU) =
[$sht(vtp=>join::$rU)]\n" );
Mar 19 23:36:28 raspberrypi /usr/sbin/kamailio[2167]: ALERT:
I got a bit wiser on my problem.
It seems that the sequence of events matters.
I have a PBX which should send the call to the App. If the App does not
respond within three seconds, the call should be forwarded to a GSM number.
I have two scenarios, this one works:
1. PBX gets call
2. App
Am Montag, 19. März 2018, 13:49:52 CET schrieb Narayan P:
> Any update on this please.
>
Hello Naryan,
have you tried with time_mode = 1?
6.45. time_mode (int)
Store additional value related to the time of event.
Values can be:
* 0 - (default), save only unix timestamp for syslog
Am Montag, 19. März 2018, 19:51:17 CET schrieb Henning Westerholt:
> [..]
> You'll find all information about this issue consolidated on our web page
> at:
>
> https://www.kamailio.org/w/2018/03/kamailio-security-announcement-tmx-lcr/
There was a small error in the configuration (missing
Hello all,
It seems that the phonenum module in at least 5.1.2 (haven't tried previous
versions) is behaving somewhat erratically. More specifically, if there are
any references to any phn PVs with the key other than "number":
if ( phonenum_match("1-484-555-", "src") ) {
xlog("number norm:
Hello,
On 15.03.18 22:41, Stefan Sayer wrote:
> Hello,
>
> I have a bit of a strange situation where I want to add SIP MESSAGE
> reliability (store and forward) for a proxy that is in front of the
> (message-wise unreliable) registrar/message originator. So I m_store
> MESSAGEs in the
Hello,
no actions are executed in the same route block after the line with
async_task_route("NICE_TO_HAVE") -- see the readme of the async module
at the documentation for this function.
If you want to continue executing the actions after pushing a task for
another process, you can try to combine
On 16.03.18 19:00, Daniel Tryba wrote:
> On Wed, Mar 14, 2018 at 05:30:23PM +0100, Daniel-Constantin Mierla wrote:
>> I want to highlight that the last stable versions (for the latest 3
>> release series: 4.4, 5.0 and 5.1) include fixes for two issues that can
>> crash a running instance of
On Mon, Mar 19, 2018 at 04:23:01PM +0100, Kjeld Flarup wrote:
> Interesting
>
> Just to be sure that I understand You correctly.
> When a Register is done, then an Invite, must create a new TCP connection.
That is not what I tried to say. All I wanted to say was:
uac ipA:portX -> syn ->
Hello all,
I've been exploring the async module a little, and async_task_route() more
specifically. I have async_workers set, and the async module loaded.
However, whenever this async function is involved in SIP processing,
kamailio returns a 500 error to the UAC. I was hoping that someone could
Interesting
Just to be sure that I understand You correctly.
When a Register is done, then an Invite, must create a new TCP connection.
I agree, that a perfect implementetion would be to keep the TCP stream up
while the client is connected, and use that connection for all
communication between
Hello All,
Any update on this please.
Thanks,
Narayan
From: sr-users on behalf of Narayan P
Sent: Friday, March 16, 2018 11:02:19 AM
To: sr-users@lists.kamailio.org
Subject: [SR-Users] Issue
On Sun, Mar 18, 2018 at 12:59:28PM +0100, Kjeld Flarup wrote:
> Does this mean that Kamailio doesn't reuse this connection, and instead
> tries to establish a new one.
>
> And is it possible to have two concurrent connections, especially when it is
> trying to send an invite to a client behind
Hello,
we are glad to announces that, thanks to the sponsors, we can offer
again couple of free seats at Kamailio World Conference, May 14-16,
2018, in Berlin, for students as well as for underrepresented people.
In this way we are continuing the program from last years, based on the
roots and
On 03/19/2018 10:37 AM, Andrew Pogrebennyk wrote:
> On 03/16/2018 05:07 PM, John Petrini wrote:
>> The simple answer to that is it's a last ditch effort to look up an AOR
>> record on a reply but it's part of other logic we use to establish
>> direct media.
>
> try with $(hdr(Record-Route)[-1])..
On 03/16/2018 05:07 PM, John Petrini wrote:
> The simple answer to that is it's a last ditch effort to look up an AOR
> record on a reply but it's part of other logic we use to establish
> direct media.
try with $(hdr(Record-Route)[-1]).. it works for us (though, with
another header name).
Andrew
Hello,
as already announced from Daniel-Constantin Mierla on the lists last Wednesday
[1], we strongly advise you to update your Kamailio installation to the latest
stable release for security reasons.
All supported releases (4.4, 5.0. and 5.1) contains two important security
fixes related to
Hi,
Try $(hdr(Record-Route)[-1]), to extract URI only you can
use: $(hdr(Record-Route)[0]{nameaddr.uri})
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
18 matches
Mail list logo