Maybe I should ask this question another way that is more applicable to
my end-goal:
What exactly happens when max_inv_lifetime is reached without a final
response? Is a failure_route invoked? If so, is the appropriate means of
dealing with this to check t_is_expired() and handle it at that
Hello all.
Just want to tell you that the problem remains even after the patch Daniel
add to the latest 4.2.
I've sent another email yesterday (partially quoted bellow) to the mailing
list which was already answered by Juha Heinanen in cc regarding an odd
behavior (seems odd to me) i'm seeing.
Hi,
In this serial forking-based failover scenario
UAC -- Proxy -- UAS 1
UAS 2
...
UAS 3
I've got a requirement to terminate the call and return an error to the
UAC if there is no final response within 60 seconds.
The usual
Hi Juha.
Thanks for answering me back.
In my particular case my publisher is Kamailio itself.
You can see a code snippet for my presence configs (attached) in my
kamailio config file.
I'm using pua to generate SIP PUBLISH messages on 127.0.0.1 and probably
that isn't the best approach, but I don't
Hi ,
I've updated kamailio from 4.1.4 to 4.1.7 and some times dialog variables
are not writed on the db by the ACC module.
The variable that is not writed ,is setted in the on reply route ,when it
receive the 200ok and method is invite.
If i come back to the 4.1.4 all is ok.
If i patch kamailio
It is an ACK for a negative response, therefore it is hop-by-hop
(received and discared by kamailio, then a new one is generated to the
next hop). The information of direction which was detected with Route
header ftag cannot be done in this case. I will try to figure out how
can be solved...
Hello,
somehow your emails are a bit confusing, in first one you say that you
cannot get max_inv_lifetime as per transaction, being reset by a new
branch, is that still true?
The failure route should be called when the transaction is expired.
Cheers,
Daniel
On 21/01/15 18:16, Alex Balashov
Daniel,
Will failure_route will be called immediately when the transaction expires? I
tried a call where max_inv_lifetime was set at 5 ms and fr_inv_timer at
4 ms. Several new branches were attempted, each sending some 183s or 180s,
and Kamailio did not CANCEL the last pending branch
My Kamailio box works very well for a year, in front of a Freeswitch box.
Nowadays, some of my users live problems about receiving calls. But this
problem occurs on a couple of specific users. %1 of users complain about
it. When I capture the traffic, I see that, Kamailio receives an invite
Thank you Daniel,
The weird thing is, this problem is not persistent. Now it works as usual
and I can't reproduce the problem.
According to your reply, problem may be at Freeswitch box.
How can I calculate Content Length from capture? And if this is a message
size issue, how can I fix it?
Nuno Reis writes:
Here my publisher is Kamailio itself. Can someone elaborate a bit more on
this issue and maybe we can get to bottom of it?
when your application issues initial publish request, it does so without
SIP-If-Match header. 200 ok from presence server then contains an etag
in
On Wednesday 21 January 2015 08:45:59 Daniel-Constantin Mierla wrote:
To understand properly, this is after the re-INVITE from B to A? I will
look in the code as I get a chance, being out of the office for few days...
Yes. Full trace below. Only the ACK to SIP_A for the 488 has the wrong Call-
Hi,
Hello!
I'm having trouble with matching massages for some Patton equipment,
from the looks of it, Patton don't like / in headers.
The initial INVITE from Patton is sent without / in To and From-headers.
In the logs from Patton I can see that it matches the 100 trying that
Kamailio sends
Hello Folks:
Hope you can see this and share your ideas as to how to fix it?
Thanks and regards,
Zaka
From: Zaka Ul Isam
Sent: Wednesday, January 21, 2015 12:20 PM
To: Carsten Bock
Cc: mico...@gmail.com
Subject: RE: KAMAILIO IMS Questions
hello All:
Hi,
My Kamailio box works very well for a year, in front of a Freeswitch box.
Nowadays, some of my users live problems about receiving calls. But this
problem occurs on a couple of specific users. %1 of users complain about
it. When I capture the traffic, I see that, Kamailio receives an invite
On Wednesday 21 January 2015 13:42:07 Volkan Oransoy wrote:
Content-Length: 270.
v=0.
o=FreeSWITCH 1421813895 1421813896 IN IP4 1.2.3.6.
s=FreeSWITCH.
c=IN IP4 1.2.3.6.
t=0 0.
m=audio 28384 RTP/AVP 3 8 0 101 13.
a=rtpmap:3 GSM/8000.
a=rtpmap:8 PCMA/8000.
a=rtpmap:0 PCMU/8000.
On Wednesday 21 January 2015 15:10:07 Volkan Oransoy wrote:
The weird thing is, this problem is not persistent. Now it works as usual
and I can't reproduce the problem.
According to your reply, problem may be at Freeswitch box.
It is to early to conclude, the ngrep outpout isn't complete. If
17 matches
Mail list logo
