It should be fixed now in the latest 4.4 and master branches.
Cheers,
Daniel
On 07/09/16 08:58, Daniel-Constantin Mierla wrote:
>
> I forgot about it, I will investigate.
>
> Cheers,
> Daniel
>
>
> On 06/09/16 15:19, DanB wrote:
>>
>> Have noticed this thread remaining without a follow up.
>>
>>
I forgot about it, I will investigate.
Cheers,
Daniel
On 06/09/16 15:19, DanB wrote:
>
> Have noticed this thread remaining without a follow up.
>
> I can also confirm that in newer Kamailio the events are not longer
> sent out.
>
> Can I help in any way?
>
>
> Ta,
>
> DanB
>
>
> Hi Daniel,
>
>
Have noticed this thread remaining without a follow up.
I can also confirm that in newer Kamailio the events are not longer sent
out.
Can I help in any way?
Ta,
DanB
Hi Daniel,
sorry for not being clear.
I have all three evapi event routes in my config. When I telnet to port
8448, xlog
Hi Daniel,
sorry for not being clear.
I have all three evapi event routes in my config. When I telnet to port
8448, xlog shows that evapi:connection-new is exectued. When I send
6:efelin, to telnet, the evapi:message-received is executed. When I close
the telnet session, the evapi:connection-clos
On 22/08/16 09:31, Efelin Novak wrote:
> [...]
>
> When I connect to evapi using telnet, I receive NO answer:
>
> root@PC:~$ telnet 192.168.30.29 8448
> Trying 192.168.30.29...
> Connected to 192.168.30.29.
> Escape character is '^]'.
>
>
> However it reacts on my netstring messages and executes
Hi Daniel,
kamctl ps:
root@cgrates:/usr/share/cgrates/tutorials/kamevapi/cgrates/etc/init.d#
kamctl ps
Process:: ID=0 PID=14529 Type=main process - attendant
Process:: ID=1 PID=14530 Type=udp receiver child=0 sock=192.168.30.29:5060
Process:: ID=2 PID=14531 Type=udp receiver child=1 sock=192.1
Hello,
did you get the event_route[evapi:connection-new] executed when you
opened the connection towards evapi?
Cheers,
Daniel
On 22/08/16 09:26, Efelin Novak wrote:
> Hi,
>
> thanks for a reply. Command "ngrep -d any -t -W byline port 8448" prints
>
> #
>
> when CGRateS and telnet connect
Hello,
did you get the evapi message on your application or telnet connection?
Can you give the output of:
kamctl ps
to see if the evapi processes are running?
Cheers,
Daniel
On 19/08/16 18:45, Efelin Novak wrote:
> Hi folks,
>
> I came into a problem with evapi module, while I was trying to
Hi,
thanks for a reply. Command "ngrep -d any -t -W byline port 8448" prints
#
when CGRateS and telnet connect (TCP handshakes) and stays quiet during the
rest of the test. When I type something into telnet, I can see incoming
packets:
T 2016/08/22 09:18:21.115922 192.168.30.1:46378 -> 192.
Hi,
Use "ngrep -t -W byline port 8448" to sniff the port and see if it helps.
regards
Ganesh Kumar
On 8/19/16, Efelin Novak wrote:
> Hi folks,
>
> I came into a problem with evapi module, while I was trying to make the
> CGRateS tutorial work. It does not send any messages at all.
>
> Taken s
Hi folks,
I came into a problem with evapi module, while I was trying to make the
CGRateS tutorial work. It does not send any messages at all.
Taken steps:
I start kamailio with debug=3.
I start:
CGRates (on the kamailio machine)
telnet 192.168.30.29 8448 (from my PC)
tcpdump port 8448 -A
11 matches
Mail list logo
