On 02/06/2017 10:38 PM, Daniel-Constantin Mierla wrote:
On 06/02/2017 08:12, jungle boogie wrote:
On 02/05/2017 10:55 PM, Daniel-Constantin Mierla wrote:
It was impossible to me to assist to your presentation, however,
thanks for the slides, it's clearly an interesting approach.
During
Hello, thanks to this guide
http://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb
I successfully installed Asterisk 11.6 and Kamailio 4.4.4 on the same machine.
Everything works fine.
Right now I would like to extend this scenario adding MULTIDOMAIN support,
which is not en
Hello,
have you set the advertise address with public for listen socket (on
private ip)?
Cheers,
Daniel
On 06/02/2017 21:25, JBF wrote:
> Hello, yes, we kept TLS between kamailio and F5, and kamailio indeed have a
> private address, and doesnt see the firewall public address: the only way
> for
Hello, yes, we kept TLS between kamailio and F5, and kamailio indeed have a
private address, and doesnt see the firewall public address: the only way
for the proxy to reply to the F5 is through the client socket opened by
the F5 connection
--
View this message in context:
http://sip-router.10
Hi, Richard.
Seems with your latest patch rtpengine enable/disable commands work
correctly without any issues.
Tested on kamailio 4.4.5 on RHEL 7 x86_64
Thank you.
--
Best regards,
Sergey Basov e-mail: sergey.v.ba...@gmail.com
tel: (+38067) 403-62-54
2017-02-06 17:50 GMT+0
Hello,
with TCP there is no MTU. In the previous pcap you sent there was a
wrong Content-Length value. Was that fixed?
Cheers,
Daniel
On 06/02/2017 12:24, Hai Bui Duc Ha wrote:
> Hi Daniel,
>
> I send you the pcap files on both client and server side.
> Analyse this files, I see the packet can
On 06/02/2017 08:12, jungle boogie wrote:
> On 02/05/2017 10:55 PM, Daniel-Constantin Mierla wrote:
>>>
>>> It was impossible to me to assist to your presentation, however,
>>> thanks for the slides, it's clearly an interesting approach.
>>>
>>>
>>> During the past editions we organized a din
On 06/02/2017 20:00, Juha Heinanen wrote:
> Daniel-Constantin Mierla writes:
>
>>> I'm not aware of one, but xhttp requests inherently trigger an event_route:
>>>
>>> http://kamailio.org/docs/modules/4.4.x/modules/xhttp.html#idp49731828
>>>
>>> If you had a need to execute some other logic that c
On 06/02/2017 23:38, Jon Bonilla (Manwe) wrote:
> El Fri, 3 Feb 2017 10:06:21 +0100
> Daniel-Constantin Mierla escribió:
>
>
>> Would be good to see the difference, if it still crashes or not. But
>> this needs to be fixed, no crash should happen at runtime no matter of
>> what's the input fr
Any clue on this?
Or to work around this, can someone shed light on how to differentiate when
“Dialog:end” is called due to actual call drop - Bye vs some timeout.
I need to do some special logic only on call drop.
Relevant snippet from the logs are:
7719 Feb 3 21:41:20 labsip00 /usr/sbin/kama
El Fri, 3 Feb 2017 10:06:21 +0100
Daniel-Constantin Mierla escribió:
> Would be good to see the difference, if it still crashes or not. But
> this needs to be fixed, no crash should happen at runtime no matter of
> what's the input from network or db.
>
> As I looked quickly over the commits
Daniel-Constantin Mierla writes:
> > I'm not aware of one, but xhttp requests inherently trigger an event_route:
> >
> > http://kamailio.org/docs/modules/4.4.x/modules/xhttp.html#idp49731828
> >
> > If you had a need to execute some other logic that cannot be located
> > there, I suppose you could
On 02/06/2017 03:30 AM, Sergey Basov wrote:
Hi, All.
May be it helps.
After patch
https://github.com/kamailio/kamailio/commit/8ca410cba540e8c8b0f711fb26c85823375480a9
when running kamailio with debug level=3
when I do disable rtpengine I got in log:
Feb 6 10:24:27 csbc-uat /usr/sbin/kamailio
Hello,
DMQ will remove nodes from its internal list if they fail to respond to its
pings - with the exception of the original notification peer specified in
config. This way, if the network connection is lost, DMQ will continue to
try the original peer indefinitely until connectivity is restored,
Hi Daniel,
I send you the pcap files on both client and server side.
Analyse this files, I see the packet can not "reassemble" INVITE message
at server side:
- At client.pcapng, it can detect 6 and 7th packets are one.
- But on server.pcap, it can not "reassemble" 18 and 21st packets.
I just exp
Hello Daniel,
The parameters that i have configured on my kamailio server are:
#!ifdef ENABLE_REG_SYNC
modparam("registrar", "sock_flag", 18)
modparam("registrar", "sock_hdr_name", "Sock-Info")
### SIP registrar replication to other nodes ##
loadmodule "dmq.so"
### distributed messa
Hi, All.
May be it helps.
After patch
https://github.com/kamailio/kamailio/commit/8ca410cba540e8c8b0f711fb26c85823375480a9
when running kamailio with debug level=3
when I do disable rtpengine I got in log:
Feb 6 10:24:27 csbc-uat /usr/sbin/kamailio[10062]: DEBUG: mi_fifo
[mi_parser.c:245]: mi_
17 matches
Mail list logo
