> On 5 Jan 2023, at 07:06, Waqar 40 wrote:
>
> Dear All,
>
> For a normal call, Kamailio receives 200:OK sip response for the method
> invite only once but for some calls, it receives 200:OK too many times around
> 6 to 7. And I also do not receive BYE or any other packets for this kind of
Dear All,
For a normal call, Kamailio receives 200:OK sip response for the method
invite only once but for some calls, it receives 200:OK too many times
around 6 to 7. And I also do not receive BYE or any other packets for this
kind of call. How can I detect such calls in Kamailio and cancel
In latest stable K release, we noticed pkg memory leak (pgk memory usage
increases by each processed call). It turned out that the leak goes
away if acc module cdr_enable is not enabled.
Could be a bug in dialog or acc module. Any debug instructions if the
bug is not obvious?
-- Juha
Hello Alex,
I completely agree to your point regarding the product management topic.
Some of our customers are also doing upgrades from chan_sip to chan_pjsip right
now. Let's see if they are affected, then I could have a closer look to that
code. In case there is a fix, I will let you (and
> On Jan 4, 2023, at 12:17 PM, Henning Westerholt wrote:
>
> so far, we did not have any customer that need this functionality.
I've had numerous customers who have needed the functionality, and ended up
having to use something like the "imaginative" Contact workaround instead.
I suppose
Hi Alex,
so far, we did not have any customer that need this functionality.
We did some work in asterisk chan_pjsip recently related to a special inter-op
bug [1]. But it's certainly a bit more work as for Kamailio, especially if you
are not doing it that often and are not familiar with the
> On Jan 4, 2023, at 8:25 AM, Henning Westerholt wrote:
>
> it seems that this bug apparently does not harm to many people, or the
> workaround with the outbound proxy works for most of them.
I've been complaining about it constantly, but lack the PJSIP depth to provide
a robust fix.
I
Hello,
as mentioned, analyse the sip traces, the re-INVITE in particular regarding
Route header etc..
Cheers,
Henning
--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://gilawa.com
-Original Message-
From: nathan.casti...@snapcom.fr
Sent: Wednesday,
> On 4 Jan 2023, at 14:28, nathan.casti...@snapcom.fr wrote:
>
> Hello all,
>
> I'm trying to figure out one problem on my Kamailio server.
>
> When kamailio receive a reinvite from the infra, I get the error message "477
> - Unforunately error on sending to next hop" and the call drop.
>
Hello all,
I'm trying to figure out one problem on my Kamailio server.
When kamailio receive a reinvite from the infra, I get the error message "477 -
Unforunately error on sending to next hop" and the call drop.
I don't understand why this message appears as the first invite is well
answered
Hello,
it seems that this bug apparently does not harm to many people, or the
workaround with the outbound proxy works for most of them.
Nobody from the open source community or other companies did it picked up as
well in the last years.
Cheers,
Henning
--
Henning Westerholt –
Hello,
you can use different methods, a common way is to use the htable module fort
that.
If you are fine with a dialog-stateful proxy, you can also just use the dialog
module for that – for a counter per dialog.
Cheers,
Henning
--
Henning Westerholt – https://skalatan.de/blog/
Kamailio
Thanks for the workaround Alex
I do find it pathetic on digiums part that they still havent done anything
about it.
Cheers
Sent with [Proton Mail](https://proton.me/) secure email.
--- Original Message ---
On Tuesday, January 3rd, 2023 at 5:26 PM, nutxase wrote:
> Hi All
>
> I have
Hello Henning
Thanks for Response, When Remote Server goes down in Ringing Call state we
will not get any Negative Response from remote server and we should not
wait for transaction timeout because its to 1-2 min
so in this case there is anything that we found Remote server is down and
we can
Hello,
you can tune the transaction timeouts with tm configuration values and also tm
functions to your needs. But I agree that at a server failure in ringing state
it takes usually longer to go to the failure_route.
For that reasons you use dispatcher probing, it will detect the failure and
15 matches
Mail list logo