Hello,
what kind of operations are you looking to perform?
The typical way is to manage (add/delete/update) the records in the
database and then issue a RPC command to kamailio to reload them. But
not all records are cached, for example, subscriber table, so any change
there is immediately visibl
Hello,
I was not really able to understand the issue you write about ...
Anyhow, any sip reply triggers the repply_route or onreply_route[x] that
was set for transaction. After those routes are executed, the
failure_route[z] can be also executed if the reply code is >=300 and the
failure route wa
Hello,
On 30/06/15 13:27, Anil Kumar wrote:
> Hi,
>
> I am using Kamailio(4.2.5) as my SIP proxy also enabled authentication.
>
> Added two users xyz_0 and xyz_1 to the kamailio database.
>
> While Registration I am getting 401 Unauthorized as shown below
>
> SIP/2.0 401 Unauthorized
> Via: SIP/2.
Thanks for answer. Main problem is that 1[08][03] and 200 replies resend
correctly but 480/486 can not do it at same way...
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.o
As I read at README to Nathelper it may not work with usrloc table, Is it
write?
now I use NAT traversal module and Websocket module to keepalive
mechanisms, that uses UDP or WS.
with UDP it is wery simple method - OPTIONS replies.
With WebSocket module keepalive mechanism uses thomething else.
Hello,
are kamailio and asterisk installed on same server? To they use
different ports?
Cheers,
Daniel
On 30/06/15 09:50, zhangkai.gis wrote:
> Hello.
> When I installed kamailio I add users then I can make a call.But When
> I install asterisk I found the asterisk take over the kamailio and I
>
Hello,
On 29/06/15 20:26, Sharath Kumar wrote:
>
> Hello,
>
>
>
> Is there an API that can notify Kamailio of media inactivity in the
> RTPProxy?
>
>
>
> The documentation has something called “timeout_socket” . I don’t
> understand how to use it though. Any help will be greatly appreciated.
>
Hello,
On 25/06/15 15:06, Austin Einter wrote:
> Hi All
> I am having a sip client, I am using GNU tls for transport layer security.
>
> I am using Kamailio (TLS enabled) to test all the functionalities.
>
> I did registration over TLS. It was fine.
>
> I tried to make call.
> I was able to send I
Hello,
On 19/06/15 12:14, Muhammad Shahzad wrote:
> Hi,
>
> Lasting night i was doing some tests and identified a strange behavior
> from dialog module. I am using Kamailio v4.3.0 rev. c6aa95.
>
> I basically wanted to identify if an incoming sequential ACK (from
> caller for an answered call) or
Hello,
what do you mean by "resend correctly"? -- I don't understand and can
help otherwise. Maybe you should look at the sip traffic on the network
and send it over here, describing what you expect to happen for each
1/2xx and 4xx.
Cheers,
Daniel
On 01/07/15 10:29, Yuriy Gorlichenko wrote:
> Th
Hello,
On 26/06/15 13:05, Nelson Migliaro wrote:
> Hello everybody,
>
> My SIP vendor request me to replace FROM before sending the traffic.
> In order to achieve this I use uac_replace_from.
>
> UAC module is setup in restore_mode = auto.
>
> In my insfrastructure I have an Asterisk and then a Ka
Hello,
I'm doing a subst on the From header for some particular cases, like this
one: subst('/^(From|f):(.*):5060>;tag=3fdce0-a658bfa-13c4-50029-55941ccd-5eab9369-55941ccd\r\n
I can't reproduce.
The only potential explanation is that this impact the User-Agent that have
the From at the
Hi All,
I am playing with the new dmq_replicate module and am banging my head
against an issue I have come accross. I can see the kamailio registrars
sending the replication messages to the other node(s) in the dmq bus,
and the payload looks to be of type json. However, on the recieving
nodes
Hello,
Should be no need to load any additional deserializer. The docs simply mean
if you wish to send/receive your own messages from within a module or
script, it's up to you to choose the best payload type and method of
(de)serialization.
Can you post an example KDMQ message here to look at?
C
Hi,
Thanks for the clarification.
If I'm not mistaken, the message below, grabbed with sipgrep, is the
corresponding message that the debug output relates to. Some details
modifed to protect the kittens :)
U 2015/07/01 20:42:33.766671 10.6.0.173:5060 -> 10.6.0.174:5060
KDMQ sip:usrloc@10.6.
Hi,
Sorry, the previous sample, was the incorrect timestamp, this one is the
corresponding message sent:
U 2015/07/01 20:40:52.446646 10.6.0.173:5060 -> 10.6.0.174:5060
KDMQ sip:usrloc@10.6.0.174:5060 SIP/2.0.
Via: SIP/2.0/UDP
10.6.0.173;branch=z9hG4bK9b3c.fe993716.0.
Hi All,
Another thing I noticed while playing with kamailio and dmq/dmq_usrloc
is that 7 out of 10 times the kamailio process crashes when I initially
start it up.
Any tips/requests for further debugging would be greatly appreciated.
Kamailio version:
version: kamailio 4.3.0 (x86_64/linux)
Hello,
at the quick look it seems that dmq_usrloc was not updated with the
latest format of the serialized structure returned by usrloc when
fetching the contacts. It seems to use the same function as nathelper
(which use it for sending keepalives) and that is returning both contact
and received a
Hello,
according to the log, you got a coredump:
Jul 1 14:44:52 sipa /usr/local/sbin/kamailio[2837]: ALERT:
[main.c:754]: core was generated
Send the output of 'bt full' taken with gdb from the core file -- the
core file is either in / or in the working dir of kamailio.
Also, mention the ve
Hello,
if you just want to update the dispay name in From header, you can use:
$fn = "Anonymous";
To avoid conflicts in replacements, use mag_apply_changes() after first
changes -- in your case, after subst(...) -- read carefully the docs for
msg_apply_changes() to understand its impact and limi
Hello,
As with your other thread, I suspect dmq_usrloc is at fault here. I've not
looked at this module before, but can take a look over the next day or so
if no one else gets to it first.
Cheers,
On 1 Jul 2015 22:13, "Asgaroth" <00asgarot...@gmail.com> wrote:
> Hi,
>
> Sorry, the previous samp
21 matches
Mail list logo