sr-users June 2018

sr-users@lists.kamailio.org

88 participants
118 discussions

SIP Notify use UDP instead TCP
by denislav.tsonev＠musala.com 19 Jun '18

19 Jun '18

Hello, I'm trying to configure Kamailio 5.1 like "presence" server. Pretty much with default settings of kamailio: # ----- presence params ----- modparam("presence", "db_url", DBURL) ;modparam("presence", "server_address", "sip:10.0.6.226:5060" ) modparam("presence", "send_fast_notify", 0) modparam("presence", "db_update_period", 20) modparam("presence", "clean_period", 40) modparam("presence", "subs_db_mode", 2) modparam("presence", "fetch_rows", 1000) # ----- presence_xml params ----- modparam("presence_xml", "db_url", DBURL) modparam("presence_xml", "force_active", 1) # ----- presence_dialoginfo params ----- modparam("presence_dialoginfo", "force_single_dialog", 0) # ----- pua params ----- modparam("pua", "db_url", DBURL) modparam("pua", "db_mode", 2) modparam("pua", "update_period", 60) modparam("pua", "dlginfo_increase_version", 0) modparam("pua", "reginfo_increase_version", 0) modparam("pua", "check_remote_contact", 1) modparam("pua", "fetch_rows", 1000) # ----- pua_dialoginfo params ----- modparam("pua_dialoginfo", "include_callid", 1) modparam("pua_dialoginfo", "send_publish_flag", FLT_DLGINFO) modparam("pua_dialoginfo", "caller_confirmed", 0) modparam("pua_dialoginfo", "include_tags", 1) modparam("pua_dialoginfo", "override_lifetime", 124) # ----- dialog params ----- modparam("dialog", "db_url", DBURL) modparam("dialog", "enable_stats", 1) modparam("dialog", "db_mode", 1) modparam("dialog", "dlg_flag", FLT_DLG) And when UDP transport is using, everything works perfect. But when TCP is using (only "listen: tcp:IP:5060" is set) NOTIFY is not send. When "listen: tcp:IP:5060" and "listen: udp:IP:5060" I receive NOTIFY but through UDP. SIP trace is bellow: No. Time Source Destination Protocol Length Info 715 2018-06-18 17:05:13,164685 10.0.8.249 10.0.6.226 SIP 585 Request: SUBSCRIBE sip:71010@10.0.6.226:5060;transport=tcp | Frame 715: 585 bytes on wire (4680 bits), 585 bytes captured (4680 bits) on interface 0 Ethernet II, Src: LcfcHefe_86:92:0a (28:d2:44:86:92:0a), Dst: 8e:5c:a8:56:db:cb (8e:5c:a8:56:db:cb) Internet Protocol Version 4, Src: 10.0.8.249, Dst: 10.0.6.226 Transmission Control Protocol, Src Port: 50636, Dst Port: 5060, Seq: 1, Ack: 1, Len: 531 Session Initiation Protocol (SUBSCRIBE) Request-Line: SUBSCRIBE sip:71010@10.0.6.226:5060;transport=tcp SIP/2.0 Message Header Via: SIP/2.0/TCP 10.0.8.249:5060;transport=tcp;branch=z9hG4bK-10772-1-0 From: <sip:61010@10.0.8.249>;transport=tcp;tag=1 To: <sip:71010@10.0.6.226:5060> Call-ID: 1-10772(a)10.0.8.249 CSeq: 1 SUBSCRIBE Contact: sip:61010@10.0.8.249:5060;transport=tcp Max-Forwards: 10 Event: dialog Expires: 7200 [Expert Info (Warning/Malformed): Header has no colon after the name] User-Agent: SIPp/Win32 Accept: application/dialog-info+xml, multipart/related, application/rlmi+xml Content-Length: 0 No. Time Source Destination Protocol Length Info 870 2018-06-18 17:05:13,259323 10.0.6.226 10.0.8.249 SIP 439 Status: 202 OK | Frame 870: 439 bytes on wire (3512 bits), 439 bytes captured (3512 bits) on interface 0 Ethernet II, Src: 8e:5c:a8:56:db:cb (8e:5c:a8:56:db:cb), Dst: LcfcHefe_86:92:0a (28:d2:44:86:92:0a) Internet Protocol Version 4, Src: 10.0.6.226, Dst: 10.0.8.249 Transmission Control Protocol, Src Port: 5060, Dst Port: 50636, Seq: 1, Ack: 532, Len: 385 Session Initiation Protocol (202) Status-Line: SIP/2.0 202 OK Message Header Via: SIP/2.0/TCP 10.0.8.249:5060;transport=tcp;branch=z9hG4bK-10772-1-0 From: <sip:61010@10.0.8.249>;transport=tcp;tag=1 To: <sip:71010@10.0.6.226:5060>;tag=b3c72a85f6f978c1e325d5994421001b-970f Call-ID: 1-10772(a)10.0.8.249 CSeq: 1 SUBSCRIBE Expires: 3600 Contact: <sip:10.0.6.226:5060;transport=tcp> Server: kamailio (5.1.3 (x86_64/linux)) Content-Length: 0 No. Time Source Destination Protocol Length Info 871 2018-06-18 17:05:13,259815 10.0.8.249 10.0.6.226 SIP 337 Status: 200 OK | Frame 871: 337 bytes on wire (2696 bits), 337 bytes captured (2696 bits) on interface 0 Ethernet II, Src: LcfcHefe_86:92:0a (28:d2:44:86:92:0a), Dst: 8e:5c:a8:56:db:cb (8e:5c:a8:56:db:cb) Internet Protocol Version 4, Src: 10.0.8.249, Dst: 10.0.6.226 Transmission Control Protocol, Src Port: 50636, Dst Port: 5060, Seq: 532, Ack: 386, Len: 283 Session Initiation Protocol (200) Status-Line: SIP/2.0 200 OK Message Header Via: SIP/2.0/TCP 10.0.8.249:5060;transport=tcp;branch=z9hG4bK-10772-1-0 From: <sip:61010@10.0.8.249>;transport=tcp;tag=1 To: <sip:71010@10.0.6.226:5060>;tag=b3c72a85f6f978c1e325d5994421001b-970f Call-ID: 1-10772(a)10.0.8.249 CSeq: 1 SUBSCRIBE Content-Length: 0 No. Time Source Destination Protocol Length Info 1924 2018-06-18 17:05:19,259639 10.0.6.226 10.0.8.249 SIP 1193 Request: NOTIFY sip:61010@10.0.8.249:5060 | Frame 1924: 1193 bytes on wire (9544 bits), 1193 bytes captured (9544 bits) on interface 0 Ethernet II, Src: 8e:5c:a8:56:db:cb (8e:5c:a8:56:db:cb), Dst: LcfcHefe_86:92:0a (28:d2:44:86:92:0a) Internet Protocol Version 4, Src: 10.0.6.226, Dst: 10.0.8.249 User Datagram Protocol, Src Port: 5060, Dst Port: 5060 Session Initiation Protocol (NOTIFY) Request-Line: NOTIFY sip:61010@10.0.8.249:5060 SIP/2.0 Message Header Via: SIP/2.0/UDP 10.0.6.226;branch=z9hG4bKe05d.273c9ca6000000000000000000000000.0 To: <sip:61010@10.0.8.249>;tag=1 From: <sip:71010@10.0.6.226>;tag=b3c72a85f6f978c1e325d5994421001b-970f CSeq: 2 NOTIFY Call-ID: 1-10772(a)10.0.8.249 Content-Length: 644 User-Agent: kamailio (5.1.3 (x86_64/linux)) Max-Forwards: 70 Event: dialog Contact: <sip:10.0.6.226:5060;transport=tcp> Subscription-State: active;expires=3594 Content-Type: application/dialog-info+xml Message Body No. Time Source Destination Protocol Length Info 1989 2018-06-18 17:05:19,705774 10.0.6.226 10.0.8.249 SIP 1193 Request: NOTIFY sip:61010@10.0.8.249:5060 | Frame 1989: 1193 bytes on wire (9544 bits), 1193 bytes captured (9544 bits) on interface 0 Ethernet II, Src: 8e:5c:a8:56:db:cb (8e:5c:a8:56:db:cb), Dst: LcfcHefe_86:92:0a (28:d2:44:86:92:0a) Internet Protocol Version 4, Src: 10.0.6.226, Dst: 10.0.8.249 User Datagram Protocol, Src Port: 5060, Dst Port: 5060 Session Initiation Protocol (NOTIFY) Request-Line: NOTIFY sip:61010@10.0.8.249:5060 SIP/2.0 Message Header Via: SIP/2.0/UDP 10.0.6.226;branch=z9hG4bKe05d.273c9ca6000000000000000000000000.0 To: <sip:61010@10.0.8.249>;tag=1 From: <sip:71010@10.0.6.226>;tag=b3c72a85f6f978c1e325d5994421001b-970f CSeq: 2 NOTIFY Call-ID: 1-10772(a)10.0.8.249 Content-Length: 644 User-Agent: kamailio (5.1.3 (x86_64/linux)) Max-Forwards: 70 Event: dialog Contact: <sip:10.0.6.226:5060;transport=tcp> Subscription-State: active;expires=3594 Content-Type: application/dialog-info+xml Message Body Could someone help? Thanks in advance. Best regards, Denislav Raychev Tsonev | Integration and Infrastructure Engineer | Musala Soft JSC www.musala.com | t: +359 2 969 58 21 | m: +359 878 270 965 | f: +359 2 969 58 22 World Trade Center, 36 Dragan Tsankov blvd., Sofia 1057, Bulgaria

2 1

Timer child process loosing MySQL connections
by Tobias Lindgren 19 Jun '18

19 Jun '18

Hi all! Having an issue with MySQL db connections being dropped in a system running 4.4.7. We're using db_mysql and db_cluster modules setup a cluster connecting two different DB servers. We have two cluster connections, one for acc and one for "other queries". One DB (A) is on the same network, another DB (B) is on another network. The default DB connection is for the remote server B. Auto reconnect is enabled. The specific issue seen is that the "timer" child process looses/drops both connections to DB A and B. Looking at the output from lsof when this happens, the connections usually does not both drop connections for A and B at the same time. Sometimes the connections keep up for ~24h, sometimes for 10 minutes, but normally the problem re-occurs every 6 hours or so. We're seeing this problem on two Kamailio servers, both handling fairly high amount of calls. None of the other Kamailio child processes seems to get their connections dropped, only the "timer" process. To solve this we need to restart Kamailio. Lately I've added the timer.so module to make a simple query on each cluster connection each 10 seconds. This is an example output from when the problem appears and connections are dropped: Jun 15 09:39:12 /usr/sbin/kamailio[10439]: ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Can't connect to MySQL server on 'xxx' (4) (2003) Jun 15 09:39:12 /usr/sbin/kamailio[10439]: ERROR: <core> [db_query.c:181]: db_do_raw_query(): error while submitting query Jun 15 09:39:12 /usr/sbin/kamailio[10439]: ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) Jun 15 09:39:12 /usr/sbin/kamailio[10439]: ERROR: <core> [db_query.c:181]: db_do_raw_query(): error while submitting query Jun 15 09:39:13 /usr/sbin/kamailio[10439]: ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Can't connect to MySQL server on 'xxx' (4) (2003) Jun 15 09:39:13 /usr/sbin/kamailio[10439]: ERROR: <core> [db_query.c:235]: db_do_insert_cmd(): error while submitting query Jun 15 09:39:13 /usr/sbin/kamailio[10439]: ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Can't connect to MySQL server on 'xxx' (4) (2003) Jun 15 09:39:13 /usr/sbin/kamailio[10439]: ERROR: <core> [db_query.c:235]: db_do_insert_cmd(): error while submitting query Jun 15 09:39:13 /usr/sbin/kamailio[10439]: ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Can't connect to MySQL server on 'xxx' (4) (2003) Jun 15 09:39:13 /usr/sbin/kamailio[10439]: ERROR: <core> [db_query.c:235]: db_do_insert_cmd(): error while submitting query Jun 15 09:39:14 /usr/sbin/kamailio[10439]: ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) Jun 15 09:39:14 /usr/sbin/kamailio[10439]: ERROR: <core> [db_query.c:235]: db_do_insert_cmd(): error while submitting query Jun 15 09:39:14 /usr/sbin/kamailio[10439]: ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server at 'waiting for initial communication packet', system error: 4 (2013) Jun 15 09:39:14 /usr/sbin/kamailio[10439]: ERROR: <core> [db_query.c:181]: db_do_raw_query(): error while submitting query Jun 15 09:39:15 /usr/sbin/kamailio[10439]: ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server at 'waiting for initial communication packet', system error: 4 (2013) Jun 15 09:39:15 /usr/sbin/kamailio[10439]: ERROR: <core> [db_query.c:235]: db_do_insert_cmd(): error while submitting query Jun 15 09:39:16 /usr/sbin/kamailio[10439]: ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server at 'waiting for initial communication packet', system error: 4 (2013) Jun 15 09:39:16 /usr/sbin/kamailio[10439]: ERROR: <core> [db_query.c:181]: db_do_raw_query(): error while submitting query Jun 15 09:39:17 /usr/sbin/kamailio[10439]: ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server at 'waiting for initial communication packet', system error: 4 (2013) Jun 15 09:39:17 /usr/sbin/kamailio[10439]: ERROR: <core> [db_query.c:181]: db_do_raw_query(): error while submitting query Jun 15 09:39:18 /usr/sbin/kamailio[10439]: ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server at 'waiting for initial communication packet', system error: 4 (2013) Jun 15 09:39:18 /usr/sbin/kamailio[10439]: ERROR: <core> [db_query.c:181]: db_do_raw_query(): error while submitting query Jun 15 09:39:27 /usr/sbin/kamailio[10439]: ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server at 'waiting for initial communication packet', system error: 4 (2013) Jun 15 09:39:27 /usr/sbin/kamailio[10439]: ERROR: <core> [db_query.c:181]: db_do_raw_query(): error while submitting query Jun 15 09:39:28 /usr/sbin/kamailio[10439]: ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server at 'waiting for initial communication packet', system error: 4 (2013) Jun 15 09:39:28 /usr/sbin/kamailio[10439]: ERROR: <core> [db_query.c:181]: db_do_raw_query(): error while submitting query Jun 15 09:39:32 /usr/sbin/kamailio[10439]: ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server at 'waiting for initial communication packet', system error: 4 (2013) Jun 15 09:39:32 /usr/sbin/kamailio[10439]: ERROR: <core> [db_query.c:235]: db_do_insert_cmd(): error while submitting query Jun 15 09:39:32 /usr/sbin/kamailio[10439]: ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server at 'waiting for initial communication packet', system error: 4 (2013) Jun 15 09:39:32 /usr/sbin/kamailio[10439]: ERROR: <core> [db_query.c:181]: db_do_raw_query(): error while submitting query Jun 15 09:39:34 /usr/sbin/kamailio[10439]: ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server at 'waiting for initial communication packet', system error: 4 (2013) Jun 15 09:39:34 /usr/sbin/kamailio[10439]: ERROR: <core> [db_query.c:235]: db_do_insert_cmd(): error while submitting query Jun 15 09:39:34 /usr/sbin/kamailio[10439]: ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server at 'waiting for initial communication packet', system error: 4 (2013) Jun 15 09:39:34 /usr/sbin/kamailio[10439]: ERROR: <core> [db_query.c:181]: db_do_raw_query(): error while submitting query Jun 15 09:39:35 /usr/sbin/kamailio[10439]: ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server at 'waiting for initial communication packet', system error: 4 (2013) Jun 15 09:39:35 /usr/sbin/kamailio[10439]: ERROR: <core> [db_query.c:235]: db_do_insert_cmd(): error while submitting query Jun 15 09:39:35 /usr/sbin/kamailio[10439]: ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server at 'waiting for initial communication packet', system error: 4 (2013) Jun 15 09:39:35 /usr/sbin/kamailio[10439]: ERROR: <core> [db_query.c:181]: db_do_raw_query(): error while submitting query Jun 15 09:39:37 /usr/sbin/kamailio[10439]: ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server at 'waiting for initial communication packet', system error: 4 (2013) Jun 15 09:39:37 /usr/sbin/kamailio[10439]: ERROR: <core> [db_query.c:181]: db_do_raw_query(): error while submitting query Jun 15 09:39:38 /usr/sbin/kamailio[10439]: ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server at 'waiting for initial communication packet', system error: 4 (2013) Jun 15 09:39:38 /usr/sbin/kamailio[10439]: ERROR: <core> [db_query.c:181]: db_do_raw_query(): error while submitting query Jun 15 09:39:47 /usr/sbin/kamailio[10439]: ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server at 'waiting for initial communication packet', system error: 4 (2013) Jun 15 09:39:47 /usr/sbin/kamailio[10439]: ERROR: <core> [db_query.c:181]: db_do_raw_query(): error while submitting query Jun 15 09:39:48 /usr/sbin/kamailio[10439]: ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server at 'waiting for initial communication packet', system error: 4 (2013) Jun 15 09:39:48 /usr/sbin/kamailio[10439]: ERROR: <core> [db_query.c:181]: db_do_raw_query(): error while submitting query Jun 15 09:39:50 /usr/sbin/kamailio[10439]: ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server at 'waiting for initial communication packet', system error: 4 (2013) Jun 15 09:39:50 /usr/sbin/kamailio[10439]: ERROR: <core> [db_query.c:235]: db_do_insert_cmd(): error while submitting query Jun 15 09:39:50 /usr/sbin/kamailio[10439]: ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server at 'waiting for initial communication packet', system error: 4 (2013) Jun 15 09:39:50 /usr/sbin/kamailio[10439]: ERROR: <core> [db_query.c:181]: db_do_raw_query(): error while submitting query Jun 15 09:39:57 /usr/sbin/kamailio[10439]: ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server at 'waiting for initial communication packet', system error: 4 (2013) Jun 15 09:39:57 /usr/sbin/kamailio[10439]: ERROR: <core> [db_query.c:181]: db_do_raw_query(): error while submitting query Again, it's always and only the timer child process where these error messages are seen. Have been trying to debug this for some time now but I'm running out of ideas. Do you have any ideas on what I could look for? Any idea on why it's just the timer-process? Kind regards, /Tobias

2 5

rtpproxy_stream2uac
by Narasimhaiah, Vinod Maralenahalli 18 Jun '18

18 Jun '18

Hi, I am trying to configure kamailio to play early media and i am using rtpproxy_stream2uac(), but the audio file plays only after the call is connected. How to use rtpproxy_stream2uac() to play only the early media. Thank you vinod.M.N -- To download the app, click: iOS <http://goo.gl/ZJx3y1> | Android <http://goo.gl/G1ehjZ> -- ***This transmission contains information that is confidential and proprietary of Kirusa Inc.,its affiliates and/or its partners and customers. This information is intended to be shared only with the recipient of this e-mail who is bound by confidentiality. If you received this e-mail in error, please delete the e-mail and notify the sender by return e-mail.***

1 0

Textops Regex
by Duarte Rocha 18 Jun '18

18 Jun '18

Greetings, What kind of regex does textops module uses? I'm trying to find the string "application\sdp" but i can't the escape character for the "\". Thanks in advance

2 1

Please Deregister me
by siva chirravuri 18 Jun '18

18 Jun '18

2 1

Registration Failed
by Ashok kumar Marra 18 Jun '18

18 Jun '18

Hi all, Few days back only, I started working on Kamailio IMS. I set up PSCSF, ICSCF, SCSCF and HSS(from open hss). When I try to send Register request from Zoiper, ICSCF is giving request timeout. At SCSCF, MAR failed error is logged. Kindly, let me know where I am doing wrong? >From my observation, At HSS, I can't see MAR request processing, It is only processing UAR from ICSCF. Find the attached log file. -- With Best Regards, Ashok Kumar.

1 0

18 Jun '18

Hi all, Few days back only, I started working on Kamailio IMS. I set up PSCSF, ICSCF, SCSCF and HSS(from open hss). When I try to send Register request from Zoiper, ICSCF is giving request timeout. At SCSCF, MAR failed error is logged. I am attaching the screenshot of log. Kindly, let me know where I am doing wrong? >From my observation, At HSS, I can't see MAR request processing, It is only processing UAR from ICSCF. -- With Best Regards, Ashok Kumar

1 0

TLS module and IPv6 (using tls.cfg).
by Joel Serrano 17 Jun '18

17 Jun '18

Hi all, I was playing around with the "config" modparam to specify and use a TLS configuration file instead of inline modparams inside kamailio.cfg. I did some testing and when I went to try with IPv6 I run into a little doubt?? tls.cfg config example: [server:1.2.3.4:5061] <----- How do you put an IPv6 in there? method = TLSv1 verify_certificate = yes require_certificate = no private_key = /usr/local/etc/kamailio/tls/local_key.pem certificate = /usr/local/etc/kamailio/tls/local_cert.pem verify_depth = 3 ca_list = local_ca.pem crl = local_crl.pem Applying the logic of the "listen" param, it should be: [server:[AAAA:BBBB:CCCC:DDDD:EEEE:FFFF:GGGG:HHHH]:5061] But it just seems totally wrong and I haven't found anything in the docs. Any suggestions? Thanks, Joel.

2 2

SDPC on SDP
by Duarte Rocha 17 Jun '18

17 Jun '18

Greetings, Please help me understand the reason and source of this behaviour on Kamailio. I receive a 200OK to a RE-INVITE that has : Session Name (s) : MySession Connection Information (c) : IN IP4 xxx.xxx.xxx.xxx Then, Kamailio routes the 200OK to it's destination, and it leaves Kamailio like this : Session Name (s) : MySession sdpc=IN xxx.xxx.xxx.xxx The line Connection Information got deleted and it's info is now on Session Name. How can i disable this ? Thanks

2 1

Alias listen
by kai.ohnacker＠cbc.de 17 Jun '18

17 Jun '18

Hello everybody, I have a question about the function "aliases". With my server no alias entry is registered and there is no DNS server (reverse DNS is not possible) in the network. Nevertheless, the SIP server listens to a defined alias. Is there next to the config file and the kamctlrc file another place where an alias can be entered? Cheers, Kai

2 1

← Newer
1
2
3
4
5
6
7
8
9
...
12
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users June 2018