You can start with websockets module documentation. It gives details
explaination of how it works and what needs to be done in config.
http://kamailio.org/docs/modules/4.4.x/modules/websocket.html#idp1214176
I have worked with JSSIP, SIPML5 and a few others using Kamailio and
FreeSWITCH, all work
Great.
Thank you so much for your help.
On Mon, Oct 26, 2015 at 8:58 AM, Daniel-Constantin Mierla wrote:
>
>
> On 23/10/15 17:34, M S wrote:
>
> Since I don't have systemd compatible start script for RHEL, so i was
> starting kamailio through commandline, e.g. /usr/lo
sufficient private
> memory. What is your -M parameter? If you haven't provided it, then try
> with -M 12
>
> Cheers,
> Daniel
>
> On 22/10/15 16:28, M S wrote:
> > I am sorry for inconvenience, I was a bit confused whether it is a
> > related to dev or user mail
Hi,
I have been trying to setup Kamailio v4.3.3 rev. e275bc on RHEL 7.1 64bit.
It has been very difficult to resolve all dependencies initially due to
RHEL's extremely limited repositories and libraries support, but
nevertheless I am finally able to successfully compile kamailio with all
essentia
Hi,
I was asked some interesting questions yesterday by a rather techy client
related to Kamailio and RTPEngine performance.
Q1:
For Kamailio we have say 8 child processes, which means there are 8 threads
per listen address to process sip messages, i.e. for example 8 INVITE
messages at any instan
Hi,
After doing all the test cases, it seems the problem has been resolved in
v4.3.2-3763f6.
Thank you so much for your help in this timely fix.
On Mon, Sep 14, 2015 at 12:52 PM, M S wrote:
> OK, let me test it and get back to you.
>
> Thank you.
>
>
>
> On Mon, Sep
you
> reply with a negative response code from kamailio and then quickly a new
> invite with same callid and from tag arrives.
>
> Can you upgrade to latest version in branch 4.3, try and see if works fine
> now?
>
> Cheers,
> Daniel
>
>
> On 14/09/15 11:55, M S wr
at main.c:1644
#14 0x080e4c99 in main (argc=13, argv=0xbff3ad44) at main.c:2533
--
Does this makes any sense to you? Let me know if you need anything else.
Thank you.
On Mon, Sep 14, 2015 at 11:36 AM, M S wrote:
> Sure, here is the list of module in given order,
>
> --
> l
loadmodule "xhttp_pi.so"
loadmodule "xcap_server.so"
loadmodule "pua.so"
loadmodule "pua_mi.so"
loadmodule "rls.so"
loadmodule "cfgutils.so"
loadmodule "htable.so"
loadmodule "msrp.so"
loadmodule "websocket.so"
loa
Hi,
Over last weekend i upgraded one of my test servers from Kamailio
v4.3.1-4d1b65 to latest stable release v4.3.2-07690f and now kamailio goes
crazy even with single call (I am using same db and configuration of
course).
As soon as call establishes system load average (as seen in top command)
s
26, 2015 at 9:28 AM, Daniel-Constantin Mierla wrote:
> Hello,
>
> On 25/08/15 20:21, M S wrote:
>
> Hi,
>
> We have a bit of confusion regarding tcp_connecton_timeout core parameter.
>
>
> are you talking about tcp_connect_timeout or tcp_connection_lifetime?
>
>
Hi,
We have a bit of confusion regarding tcp_connecton_timeout core parameter.
The documentation says,
--
Lifetime in seconds for TCP sessions. TCP sessions which are inactive for
longer than *tcp_connection_lifetime* will be closed by Kamailio.
--
However we observe a strange behaviour.
1. The
what the dial to pass out through this
> externally registered account.
>
> Keith
>
> On Wed, Aug 5, 2015 at 12:42 PM, M S wrote:
>
>> Perhaps the uuid you are giving to mi command is incorrect. You can look
>> at the db table where the uac registrations are stored to fi
yes, using set_contact_alias() fixed the problem.
Many thanks and kind regards.
On Wed, Aug 5, 2015 at 4:18 PM, Daniel-Constantin Mierla
wrote:
> Use set_contact_alias()/handle_uri_alias() instead of fix_nated_contact().
>
> Cheers,
> Daniel
>
>
> On 03/08/15 13:49, M
back, but
> when I run:
> kamcmd uac.reg_info l_uuid (UUID here)
>
> I don't see anything, just a blank line is returned?
>
> Thanks
> Keith
>
>
> On Tue, Aug 4, 2015 at 12:19 PM, M S wrote:
>
>> Make sure to enable and set reg_timer_interval and r
Well, your provider is right, the top most VIA header define the sender
address where the replies are expected. Each hop in the path adds its own
VIA at top till the request reaches the final destination. At final
destination, the list of VIA headers reflects the reply path from top to
bottom (i.e.
db method
> but can't see the registration requests going out. Is there something you
> have to do to force the registration attempts?
> Thanks
> Keith
>
> On Tue, Aug 4, 2015 at 11:48 AM, M S wrote:
>
>> If you have just one or two carriers requiring registration, then y
If you have just one or two carriers requiring registration, then you can
using this,
http://kamailio.org/docs/modules/4.3.x/modules/uac.html#uac.f.uac_auth%28%29
If you have many carriers or want db based backend for periodic
registration then look at reg_* module parameters in UAC module,
http
possible?
Thank you.
On Mon, Aug 3, 2015 at 12:56 PM, Daniel-Constantin Mierla wrote:
> Look at the trace when the SUBSCRIBE is handled, because the R-URI in
> NOTIFY is the Contact from SUBSCRIBE.
>
> Cheers,
> Daniel
>
>
> On 03/08/15 12:51, M S wrote:
>
> Yes
t;)
modparam("rls", "hash_size", 12)
modparam("rls", "to_presence_code", 10)
modparam("rls", "integrated_xcap_server", 1)
modparam("rls", "disable_remote_presence", 1)
modparam("rls", "rls_event", &qu
Any ideas anyone?
I have updated the Kamailio to v4.3.1 Rev.4717b5, still the same issue.
Thank you.
On Fri, Jul 31, 2015 at 7:36 PM, M S wrote:
> Hi,
>
> I have a Kamailio v4.3.0 with SVN Rev. c6aa95 running an RLS based
> presence setup. Everything works fine when end-
Hi,
I have a Kamailio v4.3.0 with SVN Rev. c6aa95 running an RLS based presence
setup. Everything works fine when end-user has UDP transport, however, if
user has TCP or TLS transport then i aggregated NOTIFY sent by RLS gives
send error,
--
WARNING: [forward.c:231]: get_send_socket2(): protocol
22 matches
Mail list logo
