Hello,
have you captured the traffic on loopback network interface? Try also to
run with debug=3 in kamailio.cfg.
Cheers,
Daniel
On 10/09/15 22:44, huseyin kalyoncu wrote:
> Hi
>
> I am trying to implement BLF functionality as described
> in http://kb.asipto.com/kamailio:presence:k43-blf.
>
> I
Hi Federico,
didn't get the time to write a more detailed report, but my quick look
at the tsilo code revealed two potential issues:
- the ts transaction structure is cloned in shared memory to be passed
as parameter to a tm callback. The clone is stil linked to the list with
prev and next. In th
Hi
After some struggling i solved the problem. It turns out that Kamailio was
sending 407 for PUBLISH messages
which sent to itself by itself :) and because of that it was not relaying
PUBLISH messages. It is a very strange behaviour and hard to recognize
without a proper debug output.
I fixed th
Hello,
I will adjust the tutorial to make the note about PUBLISH looping back
and need to authorize it by IP check.
Regarding "db_mode", are you referring to "subs_db_mode" parameter?
Cheers,
Daniel
On 11/09/15 09:17, huseyin kalyoncu wrote:
> Hi
>
> After some struggling i solved the problem.
Hi Daniel,
thank you for having a look. Regard your remarks:
1) when the cloned transaction structure is passed to ts_onreply, we take
the pointer to its urecord and from this last one we take the transaction
list. So, the transaction list should still be coherent. We could have a
problem if the u
Hi,
Can we make Kamailio to re-route calls from an address that does not respond to
a different address?
Thanks,Al ___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-rout
hello;
you can do with carrierroute or other routing modules. when address doesn't
respond in session time , it gives 408 request timeout. so with
failure_route methods, you can re-route calls to different addresss.
--
View this message in context:
http://sip-router.1086192.n5.nabble.com/no-re
Hello,
I got two more crashes but they seem to be different.
The logs mentioned:
kernel: kamailio[27096] general protection ip:7f0b3e0bae55 sp:7fffdbce5fd0
error:0 in dialog.so[7f0b3e077000+8f000]
/usr/local/sbin/kamailio[27056]: ALERT: [main.c:784]: handle_sigs():
child process 27096 ex
Is Kamailio getting too complicated? Trying to do everything?
Kind regards,
<>___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hello,
this one is also from the cleanup process at shut down -- if you look at
the backtrace, if frames are executing shutdown_children(), cleanup(),
destory_modules()... then it is the shutdown. There should be another
core that is the reason for the runtime problem -- if there was
something wro
Well, not many relevant changes were done for quite some time to core
components, so those should be very stable, but it happened that we
discovered bugs even after more than 5 years, because they can be
triggered by corner cases that don't show up.
Then, we get always new modules, those take time
Hello,
default kamailio.cfg does re-routing to voicemail server (if you set the
address for such server). The mechanism is based on failure_route --
before sending to first destination, arm a failure_route using
t_on_failure("name") and then define faolure_route[name] where you
handle the case whe
Thank you for the response. Which function in carrierroute module can check for
session time?
Is something like this works?
route {
if(!cr_route(“SONUS", "0", "$rU", "$rU", "call_id")){
sl_send_reply("408", “Request Timeout");
} else {
# Relay the request to the gateway
t
Hello,
I have two UACs registered to kamailio v4.0.4 with the same URI.
(b...@example.com)
Then a third registered UAC (al...@example.com) sends an invite to
b...@example.com.
Both bob UACs accept the call and respond with a 200 Ok.
The statefull proxy now takes the first one and cancels the s
Hi Federico,
I will try last code in 4.3.x branch.
The scenario is very easy: I am calling a SIP client (running on a mobile)
First the client is stopped. Then launch the app. As expected, the calll is
presented after it has registered.
Then kill the application (before answering), then launching
15 matches
Mail list logo
