Hi all
Just looking at the latest GeoIP2 MaxMind databases (now requires registration, but still free) and noticed that they also include the AS (ISP) lookup one in the free offering.
Wondering if this is another way to facilitate better security for users on dynamic IP. Typically working from home these days.
So, rather than just limiting an end device to a country we could limit it to a particular ISP within that country.
Has anyone tried this? Have I missed a reason why this wouldn’t help? Admin overhead not worth it?
Thoughts?
Best regards
Mark
--
Mark Boyce
Dark Origins Ltd
Hi Guys,
Sorry if this is too generic or silly a question but I am testing
kamailio 5.3.5 within Azure and its behind NAT.
I am having an issue with passing an ACK from our internal side back out to
the carrier side and it appears having run loose_route a none local route-header is
consistently being removed by kamailio at this point.
ie Route: <sip:CARRIER_IP;lr>
Is this normal or configuration related?
As I am unsure within what scenario I would remove a route header which doesnt contain the local
Proxy IP.
Please can someone advise?
Many thanks
Jon
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
Hi all,
Can anyone give me some info on what this warning means:
Jul 7 17:02:29 csbc02 csbc[16006]: WARNING: <core> [core/daemonize.c:596]:
mem_lock_pages(): failed to lock the memory pages (disable swap): Cannot
allocate memory [12]
Yes, if I set mlock_pages=no I don't see the warning, but I'm trying to
understand why can't it allocate with mlock_pages=yes.
Joel.
Hello All ,
I am trying to setup Kamailio on Debian . May i know which document should
be followed for installing the latest version of Kamailio on Debian 10
Buster. ?
Thanks and Regards
Abdul Rasheed
Hello,
I'm trying to use the dialplan with $avp("key") on match_exp and
subst_exp but i'm getting an error message when there is a regex
capturing group on subst_exp to be used on repl_exp
This is the config used:
modparam("dialplan", "match_dynamic", 1)
$avp(s:PSTNAC) = "0";
Dialplan entry:
dpid = 1
match_op = 1
match_exp = ^$avp(s:PSTNAC)
match_len = 0
subst_exp = ^$avp(s:PSTNAC)(.*)
repl_exp = 9\1
After executing dp_translate while the dialplan is properly matched
the following error message occurs and the repl_exp didn't work as
expected:
ERROR: dialplan [dp_repl.c:422]: rule_translate(): illegal access to
1-th subexpr of subst expr (max 0)
I've tried some other dialplan entries like:
dpid = 1
match_op = 1
match_exp = ^$(avp(s:PSTNAC)[*])
match_len = 0
subst_exp = ^$(avp(s:PSTNAC)[*])(.*)
repl_exp = 9\1
But that resulted in the same error message and no replacement either.
Any suggestion on what I'm doing wrong here?
Thanks,
Joao Arruda
Hi all,
im fairly new to Kamailio and currently setting up our new sip-server
systems so, hello everyone!
right now i have a Kamailio SBC which routes all calls using the
dispatcher module to our internally setup application servers (freeswitch).
i just got the idea that we might want specific routing based on
destination phone number in addition to simple loadbalancing.
can anyone point me in the right direction where i should look for
something i can place before the dispatcher routing to route calls based
on some entries in a database like destination number XYZ goes to server
A, number ABC goes to server Z and so on.
Or is there a way to select the dispatcher group id from the database
based on destination number?
best regards
Christoph
Hello all,
I am using the siptrace module on Kamailio 5.3.5 and I am trying to monitor
the SIP over websockets traffic with Homer 7.8.1 (heplify-server).
I notice a strange behavior, some packets are not presented on Homer.
I checked heplify-server and i notice the next warning:
heplify-server: 2020/07/22 18:41:09.425513 decoder.go:103: WARN HEP packet
length is 8192 but should be 11663
So I think the packets are truncated by 8192 (packet size), so they are
ignored by heplify-server.
I have done a tcpdump on the Homer machine and have the next output, where
I can see some packets with size greater than 8192.
19:58:29.788927 IP X.X.X.X.6666 > Y.Y.Y.Y.9060: UDP, bad length 11658 > 1472
19:58:29.793539 IP X.X.X.X.6666 > Y.Y.Y.Y.9060: UDP, length 626
19:58:29.810733 IP X.X.X.X.6666 > Y.Y.Y.Y.9060: UDP, length 579
19:58:29.811121 IP X.X.X.X.6666 > Y.Y.Y.Y.9060: UDP, length 579
19:58:29.838824 IP X.X.X.X.6666 > Y.Y.Y.Y.9060: UDP, bad length 11953 > 1472
19:58:29.852286 IP X.X.X.X.6666 > Y.Y.Y.Y.9060: UDP, length 473
19:58:29.865388 IP X.X.X.X.6666 > Y.Y.Y.Y.9060: UDP, bad length 3521 > 1472
19:58:29.875311 IP X.X.X.X.6666 > Y.Y.Y.Y.9060: UDP, length 562
Can you guide me to identify where the packets are truncated?
Os melhores cumprimentos / Best regards,
*José Lopes*
Research and Development Technician
Phone: +351 256 370 980
Email: jose.lopes(a)itcenter.com
Hello,
I've updated the "New in version 5.4.0" document in our wiki. It is again an impressive list!
* In this development period (started October 2019) almost 1500 commits have been added to the repository
* 5 new modules have been added (pv_headers, kafka, secsipid, systemdops, dlgs)
* Over 70 modules have been extended, many of them substantially (dispatcher, pv, tls, presence etc..)
* Countless bugfixes and documentation extensions/fixes have been added as well
* Many refactorings, extensions and architectural improvements were done in Kamailio core, tooling and modules
You'll find the full details at the usual place: https://www.kamailio.org/wiki/features/new-in-5.4.x
Many thanks to everybody that contributed to the Kamailio project.
Cheers,
Henning
--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://gilawa.com<https://gilawa.com/>
Hi
We recently setup Kamailio as the IMS core in our test lab, and we
would like to test scenarios with TAS, is there any recommendation?
Does Kamailio able to setup as a SIP AS? if yes, any online
instruction on how we can make it works?
Thanks
RBK