Yes, as YASIN said, you could look register module. In the following i
paste a simple example of definition:
int route_no;
if(hi1_eventrb){
route_no = route_get(_rt, hi1_eventrb);
if (route_no == -1){
LM_ERR("Failed to hi1 route block number of \"%s\",
Hi Paolo,
Have a look at this article (shameless plug - I am the author):
http://www.evaristesys.com/blog/sip-udp-fragmentation-and-kamailio-the-sip-header-diet/
-- Alex
On Fri, Jan 18, 2019 at 11:20:59PM +0100, * Paolo Visintin - evosip.cloud wrote:
> Hi Alex,
> thanks for your suggestion,
>
Hi Alex,
thanks for your suggestion,
maybe RR with DNS alias could be a way to go!
Will try asap !
And another question, how do you suggest do make a diet to an INVITE with
Auth , RR and SDP that exceed the 1500 mtu size ? (without using topos )
Many thanks!
Paolo
Il giorno ven 18 gen 2019
By way of further answer:
While it can perhaps be argued that OpenSIPS have done a better job of
"packaging" certain very specific functionalities from a marketing and
ease-of-use standpoint, I've learned time and time again that the raw
functionality for equivalent uses - and the flexibility
Hi Mark,
On Fri, Jan 18, 2019 at 04:37:05PM -0500, Mark Thomas wrote:
> I’m currently and OpenSIPS user and I really want to be able to use
> their software on OpenWRT, but I have found it really hard to
> cross-compile. Is there a possibility to run Kamailio as a
> mid-registrar? For my
I’m currently and OpenSIPS user and I really want to be able to use their
software on OpenWRT, but I have found it really hard to cross-compile. Is there
a possibility to run Kamailio as a mid-registrar? For my application this is
required, and I haven’t been able to find any information on
It seems to me this problem would be more easily solved by using
Record-Route as intended, and finding a way to float the IP address of
the proxy, or injecting a (reliably resolvable!) DNS alias into RR.
On Fri, Jan 18, 2019 at 10:14:28PM +0100, * Paolo Visintin - evosip.cloud wrote:
> Hi Alex,
Hi Alex,
I relay packets with another kamailio on top, that is not using
record-route; the "inner" kamailio sends packets setting the $du relaying
always to proxy.
It works well except for packets generated directly in "inner" kamailio
(double bye generated by dialog-timeout).
Paolo
Il giorno
Hi,
Perhaps it is worthwhile to ask the question: why do you want to
manipulate $du for these internally generated BYEs? What is the root
problem you are trying to solve?
-- Alex
On Fri, Jan 18, 2019 at 03:27:19PM +0100, * Paolo Visintin - evosip.cloud wrote:
> Hello!
>
> I'm wondering if
Hello
You can look registrar module that has usrloc:contact-expire
Good luck
Yasin Caner
Mojtaba mailto:mes...@gmail.com>> şunları yazdı (18 Oca 2019
22:34):
I'm gone away right now. I'll send for you as soon as
On Fri, 18 Jan 2019, 22:34 Ivan Ribakov,
mailto:i.riba...@zaleos.net>> wrote:
I'm gone away right now. I'll send for you as soon as
On Fri, 18 Jan 2019, 22:34 Ivan Ribakov, wrote:
> Thanks for the suggestion. I thought about that, but TM module is not one
> of the smallest. If there is a smaller, simpler model that uses events that
> someone could recommend I could look
I have just tested on Kamailio 5.2 and result is the same.
Maybe issue is with config?
[root@test]# kamailio -v
version: kamailio 5.2.1 (x86_64/linux) 947769
flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS,
DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP,
Thanks for the suggestion. I thought about that, but TM module is not one of
the smallest. If there is a smaller, simpler model that uses events that
someone could recommend I could look into it. But in any case, I was looking
for something more documented to learn about all capabilities of the
Hello,
I am testing how kamailio reacts to various database conditions. One such
condition is if the database engine is simply shut down (that is, database
server process no longer running, tcp listening socket closed, etc...)
I am utilizing the db_unixodbc module to connect to an Informix
Hello Ivan,
Actually i haven't seen documentation but there is a good reference for it,
the impelemention of modules. You could look around them to find out. It is
very strightforwards.
On Fri, 18 Jan 2019, 18:57 Ivan Ribakov, wrote:
> Is there any documentation for module developers that lays
Hi Daniel
After update my test kamailio to latest 5.2 branch, it's seems to work
properly.
Best regards, Javier Valencia.
El 18/1/19 a las 13:33, Daniel-Constantin Mierla escribió:
Hello,
can you try with latest 5.1.x or 5.2.x to see if it is about something
already fixed? Then
Is there any documentation for module developers that lays out API for
registering and triggering events from a custom Kamailio module (similar to
https://kamailio.org/docs/modules/5.0.x/modules/tm.html#tm.event_routes)?
I have been referring to
Hello!
I'm wondering if someone have experience in changing $du on local kamailio
generated packets (like BYE generated at the dialog-timeout) I'm trying to
manipulate in `event_route[tm:local-request]` with no success.
In the end I have it working using the `forward()` function and then using
Hello,
I already tested on 5.2.x and it is working.
Yasin CANER
From: Daniel-Constantin Mierla
Sent: Friday, January 18, 2019 3:33 PM
To: Javier Valencia; Kamailio (SER) - Users Mailing List; YASIN CANER
Subject: Re: [SR-Users]
Hello,
can you try with latest 5.1.x or 5.2.x to see if it is about something
already fixed? Then could be tracked back via commit logs. Or if still
an issue, it is easier to troubleshoot from dev team point of view.
Cheers,
Daniel
On 18.01.19 11:47, Javier Valencia wrote:
>
> Hi Yasin and
kamailio is debian based. If you know debian then for you may be more easy
extend this image.
This primary dist that is supported by kamailio team.
kamailio-ci is Alpine dist based. Alpine dist allow create more thin and
secure docker images.
Please check kamailio images sizes
1)
Hi Yasin and Daniel
I upgrade my testing kamailio to 4.4.7, the last branch on 4.4.x
version, but it's still running like 4.4.3, don't run event_route.
Saludos, Javier Valencia.
El 18/1/19 a las 10:01, Daniel-Constantin Mierla escribió:
Hello,
4.4.3 is very old to remember if there
On Fri, 18 Jan 2019 at 00:09, Victor Seva <
linuxman...@torreviejawireless.org> wrote:
> On Thu, Jan 17, 2019, 23:28 Grant Bagdasarian wrote:
>
>> Hello,
>>
>> I was wondering when the Kamailio Docker image will be updated to use
>> 5.2.1 and be available
>>
>
> I'll try to find some spare
Thanks for the explanation, but I meant the different docker images like
kamailio, kamailio-ci and pkg-kamailio-docker.
Ive been building upon the kamailio/kamailio docker image, as that one made
the most sense to me.
___
Kamailio (SER) - Users Mailing
Hi Daniel,
I have checked and I have a SIP trace of the call. Can I send it to you to
your email?
Best regards,
Cyrille
De : Daniel-Constantin Mierla
Envoyé : vendredi 18 janvier 2019 10:06
À : Kamailio (SER) - Users Mailing List ;
Cyrille Demaret
Objet : Re: [SR-Users] Problem
This from image description
Tags master, latest, 5.2 and 5.1 based on alpine image with removed all
libs except libc, busybox, tcpdump, dumpcap, gawk, kamailio and dependent
libs.
Tags that contains -alpine keyword based on alpine image. All OS tools is
untouched and possible to use apk utility.
Hello,
as pointed before, the use a more recent version is strongly recommended.
Then 3.7 was never a kamailio release, maybe you just have 3.3.7.
For the records, if you want to go ahead and troubleshoot yourself that
version, here are some hints to start with:
-
Hello,
rtpengine_manage() as well as rtpproxy_manage() do a delete command if
it is a failure processing context, like failure_route or resuming a
suspended transaction (which is like canceling the suspended branch).
The reason for doing delete is to allow disengaging rtpengine after a
Hello,
is the database server using a lot of cpu? You can also try to set a
larger value for tcp_children global parameter -- note that for all
tcp/tls sockets, there is a single pool of processes, not per socket
like for udp.
Cheers,
Daniel
On 15.01.19 11:32, Laurent Schweizer wrote:
> Hello,
Hello,
they should not stay that long, there are some parameters related to it,
see:
-
https://kamailio.org/docs/modules/5.1.x/modules/dialog.html#dialog.p.early_timeout
Does it happen that you have the sip trace for this call?
Cheers,
Daniel
On 17.01.19 20:25, Cyrille Demaret wrote:
>
>
Thanks!
What’s the difference and purpose of the three different images?
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Hello,
4.4.3 is very old to remember if there was any related issue and
moreover it is not the latest in its series, so try first to upgrade to
latest 4.4.x version, to ensure that you have all fixes for what was
found wrong during maintenance of 4.4.x.
Cheers,
Daniel
On 18.01.19 09:20,
Hello,
this option is added after 4.4.x . Sorry that I looked wrong branch. I tested
it on new versions and it is working.
Good luck.
From: Javier Valencia
Sent: Friday, January 18, 2019 11:07 AM
To: YASIN CANER; Kamailio (SER) - Users Mailing List
Subject:
No,
It's a hidden feature? I can't see in docs.
I made the changes, but Kamailio (as expected) don't start
ERROR: [modparam.c:141]: set_mod_param_regex(): parameter
of type <1> not found in module
Best regards, Javier Valencia.
El 18/1/19 a las 6:46, YASIN CANER escribió:
Hello
34 matches
Mail list logo