An update regarding this item:
I have tested release 5.1.x and 5.2.x and neither release resolves the
issue.
However I did notice in the master branch that there is new code that is
related to this issue.
https://github.com/kamailio/kamailio/issues/1681
In issue 1681 there is code that allows
Hi all,
We are using kamailio 5.1.6, configured as P-CSCF, facing following problem.
Please indicate, if you need further information - e.g. I could provide a
tshark trace.
If during call setup (by simulated UAs) at the terminating P-CSCF the simulated
PCRF rejects the Diameter AAR message,
Hello!
Sorry for my confusion. Now I get it. There are two different IDs. One for
pua.publish and second that I was missing for jsonrpcs.
Thanks everyone for help!
ср, 23 січ. 2019 о 10:05 Daniel-Constantin Mierla пише:
> Hello,
>
> the rpc interface is not matching parameters by name, but by
Greetings,
Thank you for your answer.
I have my destinations set as a sip uri with ip "sip:xxx.xxx.xxx.xxx:".
Is there a way to increase that limit?
Best regards,
Duarte Rocha
Na(o) quarta, 23/01/2019, 08:09, Daniel-Constantin Mierla
escreveu:
> Hello,
>
> for keepalive, there should
Hello,
for keepalive, there should be no limitation, as far as I can remember.
Upon a quick search, I see that 16 is used as a limit to resolve
domains. Are you having the destination addresses with IP or with hostname?
Cheers,
Daniel
On 21.01.19 12:35, Duarte Rocha wrote:
> Greetings,
>
> Is
Hello,
the rpc interface is not matching parameters by name, but by possition.
You can add them with name, but must be at the right/expected possition.
In your last example, body field is out of parameters structure. And as
it was pointed out before, you need an id in the root jsonrpc structure.
