Hello, I am working on IMS core network. In this network we have these
node with private IP:
P-CSCF: 192.168.100.101(pcscf.kamailio-ims.test)
I-CSCF: 192.168.100.102(icscf.kamailio-ims.test)
S-CSCF: 192.168.100.103(scscf.kamailio-ims.test)
HSS: 192.168.100.200(hss.kamailio-ims.test)
I have two default users (bob and alice) and all things right great.
Now i want use this network with one public IP behind nat. Let me know
What should i do?
In one way i could use SEMS-SBC and set public IP on it, How should i
config sems-sbc to work correctly?
Thanks.With Regads.
M.ES.S
Hello,
there is some ongoing work on Siremis (web management interface for
kamailio) to make it fully compatible with Kamailio 5.0.x as well as
update some of its legacy components:
- https://github.com/asipto/siremis
So I thought to start a discussion here and see if some of those changes
are going to impact too much existing installations or what are the best
options to use for the future.
Done so far:
1) implemented the JSONRPC client using UDP and unix domain sockets, to
work in pair with jsonrpcs module as a replacement for removed MI
interface. The old JSONRPC over HTTP is still an option.
2) charts system has been migrated from open flash chart (ofc) to
echarts (pure html5/javascript) -- therefore no more requiring to enable
flash in browser. Configuration is the same and the charts should look
pretty similar. If you upgrade, apart of different html view for the
charts, the config files should not be changed. If you notice something
broken, open an issue on github project linked above.
Planned to be done:
3) Relocate siremis/modules/ser to siremis/modules/sipadmin -- this
purely for more suggestive name for the admin module related to the SIP
services offered by Kamailio, and be in pair with the module sipuser.
This is mainly search and replace over php and xml files, however, it is
going to impact if you developed your own internal extensions for
siremis and placed them in the 'ser' module. It will require that you do
the same search+replace
4) Review existing database tables views and add fields for missing columns.
5) Add views for other database tables. First in my mind being the table
for rtpengine module. If you use some modules with tables not yet
managed by siremis, reply and list them to set a list of priorities.
Should have other things to report about siremis and are not yet listed
on project's issue tracker, let's discuss here.
Testing and feedback for 1) and 2) are very appreciated!
Cheers,
Daniel
--
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - www.asipto.com
Kamailio World Conference - www.kamailioworld.com
hello,
when m_dump() function is called as user gets online, the function
i.e=m_dump() sends multiple copies of same message,can anyone please
provide way to stop m_dump() sending multiple copies of same message.
I am providing the code of m_dump function
if (m_dump("$fu"))
{
xlog("L_INFO","MSILO: offline messages
dumped - if they were\n");
}else{
xlog("L_INFO","MSILO: no offline messages
dumped\n");
};
Hi,
I was comparing the documentation of the "uid_domain" and "domain" modules and I was wondering what is the main difference between the two modules.
While the "uid_domain" module has more documentation, it seems to me that both modules are offering very similar functionality, or am I missing something ?
Also I found it curious that the documentation of the "uid_domain" module uses "domain" as the module name in all its examples for the module configuration. E.g.
modparam("domain", "domain_table", "new_name")
But when I try to use the "uid_domain" module, I actually have to specify the parameters as :
modparam("uid_domain", "domain_table", "new_name")
The same question also applies to the "uid_auth_db" module that resembles closely the "auth_db" module in the documentation, but not in the implementation.
Kind Regards,
Andreas
Hi,
we have written some logic for a project in lua. There is a small
function that gets called from Kamailio, but the main logic is done in
a self-written module. That module does initialize some values from
database on the first request that comes in.
Now when reloading app_lua from kamcmd or via jsonrpc, I don't see the
log output generated when initializing.
In the debug log, I can see that the reload is taking place, but the
variables and state seem to not get reset.
What does the reload command actually reload?
Best Regards,
Sebastian
Hello,
We are facing scenario when msilo dump function is called the user's device
gets hanged/crash as messages are sent together to the user who gets
online,please provide solution how to delay the messages which are send to
the user when 'm_dump' function is called.
I am providing the code of m_dump function
if (m_dump("$fu"))
{
xlog("L_INFO","MSILO: offline messages
dumped - if they were\n");
}else{
xlog("L_INFO","MSILO: no offline messages
dumped\n");
};
Hi All,
I have a basic proxy up and running for over 6 months without issue,
had a random crash, not sure why. Restarted kamailio process and it's
working as expected. Any clue is the log to indicate what might have
happened?
----snip----
Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13416]: :
<core> [mem/q_malloc.c:468]: qm_free(): BUG: qm_free: freeing already
freed pointer (0x7fa1e1ebd658), called from <core>: mem/shm_mem.c:
sh_realloc(88), first free <core>: mem/shm_mem.c: sh_realloc(88) -
aborting
Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13415]:
ALERT: <core> [main.c:775]: handle_sigs(): child process 13416 exited
by a signal 6
Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13415]:
ALERT: <core> [main.c:778]: handle_sigs(): core was not generated
Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13415]:
INFO: <core> [main.c:790]: handle_sigs(): INFO: terminating due to
SIGCHLD
Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13423]:
INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received
Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13420]:
INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received
Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13424]:
INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received
Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13419]:
INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received
Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13421]:
INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received
Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13422]:
INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received
Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13418]:
INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received
Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13417]:
INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received
Jul 5 16:31:46 sip-router3-ve206 /usr/local/sbin/kamailio[13415]:
ERROR: ctl [ctl.c:379]: mod_destroy(): ERROR: ctl: could not delete
unix socket /tmp/kamailio_ctl: Operation not permitted (1)
----snip----
RTPProxy also running on the server was not affected.
root@sip-router3-ve206:/var/log# kamailio -V
version: kamailio 4.1.0 (x86_64/linux) 350d2e
flags: STATS: Off, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS,
DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC,
DBG_QM_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE,
USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 4MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: 350d2e
compiled on 16:41:38 Dec 17 2013 with gcc 4.4.5
Yes, I know it's an older version but I prefer not to upgrade unless
absolutely necessary. I'm sure this was a random event, not too
concerned but since it is a production server, I'm obligated to
investigate.
Thanks.
JR
--
JR Richardson
Engineering for the Masses
Chasing the Azeotrope
Hi,
I'm trying to remove all custom headers starting with X-, except a certain header, but Kamailio won't start due to an error.
ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-1) at cfg:/etc/kamailio/kamailio.cfg:455
remove_hf_re("^(?!X-ThisHeaderShouldNotBeRemoved)X-.*")
or
remove_hf_re("^(?!X- ThisHeaderShouldNotBeRemoved)X-")
This is valid regex according to https://regex101.com/
Any idea's why this won't compile?
Regards,
Grant
