Hi,
i'd like to propose a few, simple changes to the init.d file for Debian:
- for NAME use "basename $0", so a simple copy would result in a new $NAME
- use $NAME in the following variables:
HOMEDIR=/var/run/$NAME
PIDFILE=$HOMEDIR/$NAME.pid
DEFAULTS=/etc/default/$NAME
CFGFILE=/etc/$NAME/kamailio.cfg
I think those changes would help very much, in case you have multiple
instances of Kamailio running on a single server (e.g. a Proxy-CSCF,
Interrogating-CSCF and a Serving-CSCF).
What do you think? If nobody objects, i will change the init.d files
for Debian accordingly.
Thanks,
Carsten
--
Carsten Bock
CEO (Geschäftsführer)
ng-voice GmbH
Schomburgstr. 80
D-22767 Hamburg / Germany
http://www.ng-voice.com
mailto:carsten@ng-voice.com
Office +49 40 5247593-0
Fax +49 40 5247593-99
Sitz der Gesellschaft: Hamburg
Registergericht: Amtsgericht Hamburg, HRB 120189
Geschäftsführer: Carsten Bock
Ust-ID: DE279344284
Hier finden Sie unsere handelsrechtlichen Pflichtangaben:
http://www.ng-voice.com/imprint/
as i reported on sr-users list, i noticed that sometimes rtpengine
requests from kamailio set ip header don't fragment flag that causes
icmp error message from a router on the path to rtpengine. as result,
rtpengine modules things that the rtpengine is dead.
enclosed is an example of such an ip packet.
after i made this kind of patch to rtpengine.c, the flag is not set
anymore:
*** /usr/src/orig/kamailio/modules/rtpengine/rtpengine.c 2015-06-16 12:33:56.497242900 +0300
--- rtpengine.c 2015-06-29 09:03:26.959479313 +0300
***************
*** 1059,1064 ****
--- 1059,1065 ----
struct addrinfo hints, *res;
struct rtpp_set *rtpp_list;
struct rtpp_node *pnode;
+ int ip_mtu_discover = IP_PMTUDISC_DONT;
if(rtpp_set_list==NULL )
return 0;
***************
*** 1121,1126 ****
--- 1122,1131 ----
return -1;
}
+ setsockopt(rtpp_socks[pnode->idx], IPPROTO_IP,
+ IP_MTU_DISCOVER, &ip_mtu_discover,
+ sizeof(ip_mtu_discover));
+
if (bind_force_send_ip(pnode->idx) == -1) {
LM_ERR("can't bind socket\n");
close(rtpp_socks[pnode->idx]);
any comments on this?
-- juha
Hello
We use the permission module on kamailio 4.2.5. with the "allow_trusted()"
function, to check if a customer has to be whitelisted or not.
With the "tag_col" we define the user that is linked to the specific
matching IP.
Now we have the problem that a specific IP could be liked to multiple
accounts, so the tech prefix is what we thought to use in order to fix this
without involving others files or modules.
Permission module, only allows to apply the regex against the from header,
and we'd like to do this against the request URI instead.
We have patched the permission module locally in order to have the
possibility to chose witch field kamailio has to consider (From, or request
URI).
Before sending a pull request, we'd like to know from you if this change is
something you may want to take in consideration.
Thanks
Nexmo Team