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...
Cheers,
Daniel
On 20/01/15 13:13, Daniel Tryba wrote:
> Trying to call a T.38 enabled endpoint B from an endpoint A that doesn't.
> This
> results
Nuno Reis writes:
> I've been testing presence module for a while and I do notice that
> presentity table grows endlessly over time.
> Each time a call is made a new record is added in presentity with a
> different etag.
presence module does not do anything with calls. it handles publish and
sub
Hello all.
I've been testing presence module for a while and I do notice that
presentity table grows endlessly over time.
Each time a call is made a new record is added in presentity with a
different etag.
In documentation, namely developers guide we can read this:
int etag_not_new;
/*
Trying to call a T.38 enabled endpoint B from an endpoint A that doesn't. This
results in a "488 Not Acceptable" from A.
The kamailio (4.0.3) in between with topoh enabled (with mask_callid set to 1.
Kamailio ACKs the 488 to A, but the ACK has the wrong (masked) Call-ID,
resulting in the ACK to
You may setup your file extensions.conf is wrong.
Check it.
2015-01-20 8:45 GMT+01:00 Olle E. Johansson :
>
> On 19 Jan 2015, at 21:42, m...@sathees.co.uk
> wrote:
>
> kamailio passing DDI to asterisk, but its sending to wrong context.
>
>
> If any of the sip users is registered, the calls wer
Hi Alex,
I believe that statement goes back to me, but unfortunately, i was wrong.
While Kamailio implements a lot of functionality to be OMA/RCS
compliant, we are still missing some features. The best example is
probably, that 3GPP standards request, that MSRP sessions are
Store&Forward rather t
