added param sip_uri_match
0 - case sensitive (default)
1 - case insensitive
can be extended to a more compliant version, (sensitive user, insensitive domain).
the parameter sets the function to call to match uris.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/94
-- Commit Summary --
* presence - match sip uris using alternative function
-- File Changes --
M modules/presence/hash.c (4)
M modules/presence/notify.c (10)
M modules/presence/presence.c (45)
M modules/presence/presence.h (3)
M modules/presence/presentity.c (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/94.patchhttps://github.com/kamailio/kamailio/pull/94.diff
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/94
Hi Team,
Recently we upgraded our kamailo server to 4.2.1 and it was running successfuly with out any issue. We are seeing some issue with the TCP calls which are relayed from the kamilio.
We have set of physical servers and the calls are distributed by checking the dispacther module. Sometimes we are seeing the TCP packets are malformed from kamilio to one server. We can see the UDP calls are working fine with the same server at the same time TCP packets are malformed. That means there is no issue with the network connectivity between the kamailio server and our media server. Once we restart the kamilio we are not seeing this issue and the TCP calls will start working with kamilio and media server.
Can you help us to answer these questions.
1. Any idea about this TCP packet malformed error ?. We were not able to reproduce this TCP packet issue and we are seeing this error in our production environment.
2. Sometimes we have some errors for TCP max conn (ERROR) : 2048 (the default). We are plannig to increase the TCP connection to 4096 (tcp_max_connections=4096). Whether it will create any issue if we are increasing to 4096 or it will affect kamailio performance ?.
Thanks for looking in to this.
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/51
adds 3rd parameter to registered to optionally restrict the contacts
adds module parameter to optionally
add contact xavp on successful match when calling registered
add contact xavp to the $ulc structure
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/101
-- Commit Summary --
* registrar - add registered extra parameter
-- File Changes --
M modules/registrar/api.c (2)
M modules/registrar/lookup.c (66)
M modules/registrar/lookup.h (2)
M modules/registrar/reg_mod.c (88)
M modules/registrar/reg_mod.h (8)
M modules/registrar/regpv.c (313)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/101.patchhttps://github.com/kamailio/kamailio/pull/101.diff
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/101
Hi,
I want to propose a patch to usrloc:
https://github.com/kamailio/kamailio/commit/14852a98ed46b7a88c92bff31c319d2…
this patch adds a new parameter, close_expired_tcp, that makes usrloc
request the main TCP process to end the connections of expired
registrations (assuming 1 connection = 1 contact).
It enables to release resources on the system ASAP, in the event of a
lost connection (e.g. when clients are on mobile networks).
Any thoughts?
Cheers,
--
Camille
There are two files in tmrec module that has no copyright, no boilerplate, anything.
period.c and period.h
Do you know their history? Should we add a GPL or BSD boilerplate or something?
If so, please take action.
/O
Yesterday I used the UAC module to register 10.000 accounts while testing a platform. I guess this is something it wasn't built for. I just wanted to add some notes to the archives about this:
- The module seems to read all 10.000 entries from the database in one go and then add them to shared memory.
It may be good for the future to limit the amounts of records for each read and take it in multiple batches (other modules
have this functionality).
- The module registers all at once, it's very fast. I think we could add a throttle and register in batches in the future.
- The error handling seems very simple. If something goes bad, we disable the account. I am not sure if the
TM module will handle failover and retries if we get a 503 with retry-after. There's no code in uac_reg.c for it.
- There's no different handling of local timeouts and remote 408s. Again, maybe the TM module handles some
of that.
- Maybe we need an event route for disabling/enabling registrations.
I created a branch and added counter support for all database entries, disabled entries and active entries (working registrations). Pull request will come :-)
All in all, while this is not a normal use of it, I think it is a very good tool for testing of new platforms. As usual - Kamailio rocks!
/O
kamailio -v
version: kamailio 4.3.0-dev4 (x86_64/linux) caf1db
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,
F_MALLOC, DBG_F_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 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: caf1db
compiled on 16:09:10 Feb 26 2015 with gcc 4.8.2
We use this server for webrtc endpoints and it does not work. I see at
location table that webrtc endpoint register packet arrives and added
correctly endpoint itself give me unregistered result.