September 2023 - sr-users

Unnecessary/Invalid AVPs in CCR message over Ro Interface
by s.ghahremannejad＠gmail.com 06 Sep '23

06 Sep '23

**Issue Description** I'm encountering an issue with my Kamailio configuration related to the inclusion of the "Accounting-Record-Type" (480) and "Accounting-Record-Number" (485) AVPs in Credit-Control Request (CCR) messages sent from the S-CSCF to the OCS. **Issue Details** - **Problem**: The "Accounting-Record-Type" and "Accounting-Record-Number" AVPs are being added to CCR messages generated by my Kamailio instance. - **Expected Behavior**: According to modern Diameter and 3GPP standards (e.g., RFC 4006 and TS 32.299), these AVPs should not be included in CCR messages. **Configuration Details** - **Kamailio Version**: 5.3.0 - **SigScale OCS Version**: 3.2.9 Note that I have redacted some specific information for confidentiality reasons. The actual values are placed in my Kamailio main configuration file (`kamailio.cfg`) and Diameter-specific configuration files (where applicable). Kamailio.cfg: modparam("ims_charging", "db_url", DB_URL) modparam("ims_charging", "db_mode", 1) modparam("ims_charging", "origin_host", HOSTNAME); modparam("ims_charging", "origin_realm", NETWORKNAME); modparam("ims_charging", "destination_host", DESTINATION_HOST); modparam("ims_charging", "destination_realm", DESTINATION_REALM); modparam("ims_charging","service_context_id_root", RO_ROOT); modparam("ims_charging","service_context_id_ext", RO_EXT); modparam("ims_charging","service_context_id_mnc", MNC); modparam("ims_charging","service_context_id_mcc", MCC); modparam("ims_charging","interim_update_credits",30); modparam("ims_charging","timer_buffer",5); SCSCF.xml: <?xml version="1.0" encoding="UTF-8"?> <DiameterPeer FQDN="scscf.mncXXX.mccXXX.3gppnetwork.org" Realm="ims.mncXXX.mccXXX.3gppnetwork.org" Vendor_Id="10415" Product_Name="CDiameterPeer" AcceptUnknownPeers="1" DropUnknownOnDisconnect="1" Tc="30" Workers="16" QueueLength="32" TransactionTimeout="5" SessionsHashSize="128" DefaultAuthSessionTimeout="3600" MaxAuthSessionTimeout="3600" > <Peer FQDN="diameter" Realm="ims.mncXXX.mccXXX.3gppnetwork.org" port="3868"/> <Peer FQDN="192.168.2.31" Realm="ocs.ims.mncXXX.mccXXX.3gppnetwork.org" port="3868"/> <Acceptor port="3868" bind="eth0"/> <Auth id="16777216" vendor="10415"/> <Auth id="16777216" vendor="4491"/> <Auth id="16777216" vendor="13019"/> <Auth id="16777216" vendor="0"/> <Auth id="4" vendor="10415"/>  <Acct id="4" vendor="10415" />  <SupportedVendor vendor="10415" /> <Realm name="ocs.ims.mncXXX.mccXXX.3gppnetwork.org"> <Route FQDN="192.168.2.31" metric="10"/> </Realm> <DefaultRoute FQDN="diameter" metric="10"/> </DiameterPeer> I am using SigScale OCS as my Online Charging System. Here is the error log I received from SigScale OCS: ERROR REPORT==== 5-Sep-2023::07:27:01.393554 === "DIAMETER AVP unsupported" service_name: {ocs_diameter_acct_service,{0,0,0,0},3868} capabilities: {diameter_caps, {<<"host1">>, <<"scscf-1.ims.mncXXX.mccXXX.3gppnetwork.org">>}, {<<"COMPANYNAME.local">>, <<"ims.mncXXX.mccXXX.3gppnetwork.org">>}, {[{0,0,0,0}],[{172,18,0,7}]}, {50386,10415}, {<<"SigScale OCS">>,<<"CDiameterPeer">>}, {[],[]}, {[10415],[10415]}, {[4,16777238],[16777216]}, {[],[]}, {[],[]}, {[{'diameter_base_Vendor-Specific-Application-Id',10415,[16777238],[]}], [{'diameter_base_Vendor-Specific-Application-Id',10415,[16777216],[]}, {'diameter_base_Vendor-Specific-Application-Id',4491,[16777216],[]}, {'diameter_base_Vendor-Specific-Application-Id',13019,[16777216],[]}, {'diameter_base_Vendor-Specific-Application-Id',10415,[4],[]}, {'diameter_base_Vendor-Specific-Application-Id',10415,[],[4]}]}, {[329],[]}, {[],[]}} errors: [{5001, {diameter_avp,480,undefined,true,false, <<0,0,0,2>>, 'Accounting-Record-Type',2,'Enumerated',5}}, {5001, {diameter_avp,485,undefined,true,false, <<0,0,0,0>>, 'Accounting-Record-Number',0,'Unsigned32',6}}, {5001, {diameter_avp,260,undefined,true,false, <<0,0,1,10,64,0,0,12,0,0,40,175,0,0,1,2,64,0,0,12,0,0,0,4>>, 'Vendor-Specific-Application-Id', {'3gpp_ro_Vendor-Specific-Application-Id',10415,[4],[]}, 'Grouped',10}}] I would greatly appreciate it if someone from the community could provide insights into the following: 1. Possible Configurations: Are there specific configurations or modules in Kamailio that might cause the inclusion of non-standard AVPs in CCR messages? 2. IMS Ro Interface Behavior: Does anyone have experience with IMS Ro interface behavior using Kamailio that could shed light on this? If you have any guidance, suggestions, or solutions to help me troubleshoot and resolve this problem, please share them. Thank you for your assistance.

2 1

kamcmd reload is slow or blocking additional reloads
by Martin Nyström 06 Sep '23

06 Sep '23

Hello, Running ”kamcmd permissions.trustedReload” it instantly returns “Reload OK” but I cannot repeat the reload for about 8 seconds. This is the same for dialplan.reload and dispatcher.reload. root@superman.local:/# kamcmd permissions.trustedReload Reload OK root@superman.local:/# kamcmd permissions.trustedReload error: 500 - ongoing reload root@superman.local:/# kamcmd permissions.trustedReload error: 500 - ongoing reload There are scenarios where I might need to reload the permission table multiple times within this 8 second window. Is this some kind of intended block or is something at fault? modparam("db_mysql", "ping_interval", 60) modparam("db_mysql", "timeout_interval", 4) modparam("db_mysql", "auto_reconnect", 1) modparam("db_mysql", "opt_ssl_mode", 0) modparam("permissions", "db_url", "mysql://kamailio:xxxxx@aws-rds-database /kamailio") version: kamailio 5.7.1 (x86_64/linux) flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, MEM_JOIN_FREE, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled with gcc 10.2.1 /M

4 6

关于acc_cdr的问题，请教一下
by bikq＠163.com 05 Sep '23

05 Sep '23

目前进行一通呼叫后，在acc表中可以看到Invite、ack及bye的记录详情并带有时间，acc_cdrs表中只有start_time及end_time,是对应invite和bye的。现在我想在acc_cdrs中增加ack的时间我该如何去做呢？有没有大佬能解答一下？万分感谢！！！

1 0

Configuring package memory
by Ivan Ribakov 05 Sep '23

05 Sep '23

Is there any specific reason why shared memory can be configured via the config files ("shm_mem_size") AND CLI flags ("-m") but package memory can only be set via CLI flags ("-M")? Did no one ever came across the need to configure the package memory limit so far, or is there another way to achieve it without using the CLI flag? -- Ivan Ribakov Software Engineer www.zaleos.net

3 2