On 10/11/16 10:41, Ján Füri wrote:
> I have set only sip_trace() without FLAG
Can you try setting also the sip trace flag? That should reveal if there
is an issue in the code, if you don't see any OUT record. Be sure you
use tm module for relaying, so the sending callbacks are available to
siptr
On 11/11/16 13:38, Daniel Tryba wrote:
> On Thu, Nov 10, 2016 at 04:41:36PM +0100, andrzej.ciupek-asterisk.edu.pl
> wrote:
>> I have some UAC like Panasonic PBX, that send traffic to port 6060 that I am
>> listening on,
>> but that port isn't included to R-URI.
>> I can see that only at tcpdump,
Hello,
you provide only one parameter to the rpc command.
You can try with:
{"jsonrpc": "2.0", "method": "dlg.profile_get_size","params":{"profile":
"accountno", "value": "1234567"}, "id": "0deadb33f"}
The name of parameters doesn't matter, the order is important, so you
can also try with:
{"j
On Thu, Nov 10, 2016 at 04:41:36PM +0100, andrzej.ciupek-asterisk.edu.pl wrote:
> I have some UAC like Panasonic PBX, that send traffic to port 6060 that I am
> listening on,
> but that port isn't included to R-URI.
> I can see that only at tcpdump, or sip_trace from sip_capture module.
> Kamailio
Hello,
the configuration file obviously is lacking proper routing of requests
within dialog. It is not an easy task to adjust it because you have
custom logic there that one doesn't know what is supposed to do.
Again, from my point of view, the easiest way is to go start from the
example config i
