Error, if i save my sms phone group and sending a sms only an one number of the group

Hello everybody,
does somebody has any idea?
Thanks in advance.

I will send a sms to some people with my gps informations.
I have configurated:
-sms group. Phone Groups: with 3 numbers:


If i Save:
grafik
if i save the page before

i create a error.
I don’t know, if that a problem.

-Reboot Scheduler:


He make his job.

-Event reporting:


Problem:
Only the first number i the group receives a sms
grafik

Log infos:

Firmware:

Hello

Welcome to the Teltonika Community :smiley:

Regarding your query,
We have tried the same setup as yours, and we have noticed the strange behavior as well, which produces

Fri Dec 29 09:29:51 2023 daemon.err events_reporting[24768]: SMS send error (lgsm) 4
Fri Dec 29 09:29:51 2023 daemon.err events_reporting[24768]: SMS send error (lgsm) 4
Fri Dec 29 09:29:51 2023 daemon.err events_reporting[24768]: SMS send error (lgsm) 4

error (lgsm) 4 in this case,
What we have found to mitigate this issue is to manually turn ON or OFF, depending on what your provider allows. In my case i had to turn OFF


Please try this solution and let us know if it solves the issue , if not kindly play around with the Volte Option and restart the router

Please revert to us in case the issue persists

Thanks

Hello Rashid,

I wish you all the best for the new year.

I tried your suggestion with 2 different mobile providers and the different options with VoLTE.
It did not work.
I don’t get any error in the System Log. :frowning:

What I noticed is.
I have 3 different phone numbers for the test.
I’m the first to have my first mobile phone.
I get 2 text messages on the my first number.
As if the group wasn’t going through.
But it already worked properly with an older release.
Bye ralph

Hello Ralph

Happy new Year

Since that option does not work, could you kindly upload the trouble shoot file, so that we can see the logs

Thanks

Hello Rashid,
i that the right way?

Hello,

Thank you for reaching out.

We would like to ask your help in testing the following steps:

  1. The first step is to gain SSH access or CLI (System>Maintenance>CLI)
  2. Second, we wanted you to give the screenshots of the LOGS ,run ‘logread’ after you replicate the issue, and Screenshot the logs at least 10-50 lines .

We will be awaiting your feedback for this.

Regards,

Hello Rashid,

i Have chanded the configuration.

Then, if configurated the reboot scheduler for 13:48

Infos logred and “Call failed”:
RUTX14 login: root
Password:

BusyBox v1.34.1 (2023-12-19 09:26:03 UTC) built-in shell (ash)


| _ \ _ | | / _ / |
| |
) | | | | | | | _ \
| _ <| |
| | |
| || |) |
|
| _\
,|_|__/|____/

Teltonika RUTX series 2023                                                                                                                            

Device: RUTX14
Kernel: 5.10.199
Firmware: RUTX_R_00.07.06
Build: e93742651d
Build date: 2023-12-19 10:18:23

root@RUTX14:~# logread
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.000000] Booting Linux on physical CPU 0x0
Wed Jan 3 13:48:45 2024 kern.notice kernel: [ 0.000000] Linux version 5.10.199 (app@runner-wcht1mz7-project-352-concurrent-1) (arm-openwrt-linux-muslg
nueabi-gcc (OpenWrt GCC 8.4.0 r16279-5cc0535800) 8.4.0, GNU ld (GNU Binutils) 2.34) #0 SMP Tue Dec 19 09:26:03 2023
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.000000] CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c5387d
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.000000] CPU: div instructions available: patching division code
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.000000] OF: fdt: Machine model: RUTX14 STM32
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.000000] Memory policy: Data cache writealloc
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.000000] Zone ranges:
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.000000] Normal [mem 0x0000000080000000-0x000000008fffffff]
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.000000] HighMem empty
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.000000] Movable zone start for each node
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.000000] Early memory node ranges
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.000000] node 0: [mem 0x0000000080000000-0x0000000087dfffff]
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.000000] node 0: [mem 0x0000000087e00000-0x0000000087ffffff]
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.000000] node 0: [mem 0x0000000088000000-0x000000008fffffff]
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.000000] Initmem setup node 0 [mem 0x0000000080000000-0x000000008fffffff]
Wed Jan 3 13:48:45 2024 kern.debug kernel: [ 0.000000] On node 0 totalpages: 65536
Wed Jan 3 13:48:45 2024 kern.debug kernel: [ 0.000000] Normal zone: 576 pages used for memmap
Wed Jan 3 13:48:45 2024 kern.debug kernel: [ 0.000000] Normal zone: 0 pages reserved
Wed Jan 3 13:48:45 2024 kern.debug kernel: [ 0.000000] Normal zone: 65536 pages, LIFO batch:15
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.000000] percpu: Embedded 15 pages/cpu s30924 r8192 d22324 u61440
Wed Jan 3 13:48:45 2024 kern.debug kernel: [ 0.000000] pcpu-alloc: s30924 r8192 d22324 u61440 alloc=15*4096
Wed Jan 3 13:48:45 2024 kern.debug kernel: [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 64960
Wed Jan 3 13:48:45 2024 kern.notice kernel: [ 0.000000] Kernel command line: ubi.mtd=rootfs ubi.block=0,1 root=/dev/ubiblock0_1 rootfstype=squashfs co
nsole=ttyMSM0,115200n8 rootwait
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes, linear)
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes, linear)
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.000000] Memory: 247156K/262144K available (6364K kernel code, 613K rwdata, 1616K rodata, 1024K init, 239
K bss, 14988K reserved, 0K cma-reserved, 0K highmem)
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.000000] rcu: Hierarchical RCU implementation.
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.000000] Tracing variant of Tasks RCU enabled.
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.000000] arch_timer: cp15 timer(s) running at 48.00MHz (virt).
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0xb11fd3bfb, max_idle_ns: 4407
95203732 ns
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.000008] sched_clock: 56 bits at 48MHz, resolution 20ns, wraps every 4398046511096ns
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.000026] Switching to timer-based delay loop, resolution 20ns
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.000403] Calibrating delay loop (skipped), value calculated using timer frequency… 96.00 BogoMIPS (lpj=4
80000)
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.000428] CPU: Testing write buffer coherency: ok
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.000485] pid_max: default: 32768 minimum: 301
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.000662] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.000683] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.002036] qcom_scm: convention: smc legacy
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.003066] Setting up static identity map for 0x80300000 - 0x8030003c
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.003256] rcu: Hierarchical SRCU implementation.
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.003538] dyndbg: Ignore empty _ddebug table in a CONFIG_DYNAMIC_DEBUG_CORE build
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.003916] smp: Bringing up secondary CPUs …
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.007628] smp: Brought up 1 node, 4 CPUs
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.007655] SMP: Total of 4 processors activated (384.00 BogoMIPS).
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.007666] CPU: All CPU(s) started in SVC mode.
Wed Jan 3 13:48:45 2024 kern.warn kernel: [ 0.011903] Duplicate name in mnfinfo, renamed to “name#1”
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.013701] VFP support v0.3: implementor 41 architecture 2 part 30 variant 7 rev 5
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.013887] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.013915] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.014158] pinctrl core: initialized pinctrl subsystem
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.016066] NET: Registered protocol family 16
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.016482] DMA: preallocated 256 KiB pool for atomic coherent allocations
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.017642] thermal_sys: Registered thermal governor ‘step_wise’
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.018146] cpuidle: using governor ladder
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.018207] cpuidle: using governor menu
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.046570] cryptd: max_cpu_qlen set to 1000
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.051316] usbcore: registered new interface driver usbfs
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.051398] usbcore: registered new interface driver hub
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.051460] usbcore: registered new device driver usb
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.051512] pps_core: LinuxPPS API ver. 1 registered
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.051525] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti giometti@linux.it
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.051553] PTP clock support registered
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.053394] clocksource: Switched to clocksource arch_sys_counter
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.054430] NET: Registered protocol family 2
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.054682] IP idents hash table entries: 4096 (order: 3, 32768 bytes, linear)
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.055744] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear)
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.055803] TCP established hash table entries: 2048 (order: 1, 8192 bytes, linear)
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.055844] TCP bind hash table entries: 2048 (order: 2, 16384 bytes, linear)
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.055897] TCP: Hash tables configured (established 2048 bind 2048)
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.056023] UDP hash table entries: 256 (order: 1, 8192 bytes, linear)
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.056069] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear)
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.056384] NET: Registered protocol family 1
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.056441] PCI: CLS 0 bytes, default 64
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.059773] workingset: timestamp_bits=14 max_order=16 bucket_order=2
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.064481] squashfs: version 4.0 (2009/01/31) Phillip Lougher
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.064507] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
Wed Jan 3 13:48:45 2024 kern.err kernel: [ 0.206305] bam-dma-engine 8e04000.dma: num-channels unspecified in dt
Wed Jan 3 13:48:45 2024 kern.err kernel: [ 0.206335] bam-dma-engine 8e04000.dma: num-ees unspecified in dt
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.207076] tcsr 194b000.tcsr: setting usb hs phy mode select = e700e7
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.207195] tcsr 1953000.ess_tcsr: setting ess interface select = 0
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.207290] tcsr 1949000.tcsr: setting wifi_glb_cfg = 41000000
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.207380] tcsr 1957000.tcsr: setting wifi_noc_memtype_m0_m2 = 2222222
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.207720] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.208330] msm_serial 78af000.serial: msm_serial: detected port #0
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.208379] msm_serial 78af000.serial: uartclk = 1843200
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.208439] 78af000.serial: ttyMSM0 at MMIO 0x78af000 (irq = 34, base_baud = 115200) is a MSM
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.208473] msm_serial: console setup on port #0
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.758243] printk: console [ttyMSM0] enabled
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.763453] msm_serial: driver initialized
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.772414] loop: module loaded
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.773608] spi_qup 78b5000.spi: IN:block:16, fifo:64, OUT:block:16, fifo:64
Wed Jan 3 13:48:45 2024 kern.warn kernel: [ 0.775515] spi-nor spi0.0: found w25q128, expected n25q128a11
Wed Jan 3 13:48:45 2024 kern.info kernel: [ 0.781689] spi-nor spi0.0: w25q128 (16384 Kbytes)
Wed Jan 3 13:48:45 2024 kern.notice kernel: [ 0.787489] 16 fixed-partitions partitions found on MTD device spi0.0
Wed Jan 3 13:48:45 2024 kern.notice kernel: [ 0.792080] Creating 16 MTD partitions on “spi0.0”:

bye ralph

Hello

I can see some IPV6 config running, could you go to Network>WAN>General Setting
select IPV4 only in PDP type


and re run the test on a fresh router, reflash the firmware or restore to factory default

and let us know if the issue persist

Thanks

Hi,
i have do following stepps:
change configuration from SIM 2 (is the activated sim)

restore default setting

first reboot by client

scound reboot with sheduler

→ Only I have received a sms.

Then I have send a sms to the scound number in the list
about this way: Services → Mobile Utilities → Send Messages
I have chat over whatsapp and he said does he doesn’t received a sms.

If i Send to my number. I received directly the sms.

Can i reset the system complete?
More then I insert a new firmware without existing configuration?

Thanks for your help.

bye ralph

Hey Ralph

We would suggest to do a firmware upgrade without keep settings, would it to be possible to reach out to you’re sales manager so that a proper troubleshoot session can be arranged.

Thanks

Hello Rashid,

I completed the last update without applying the settings.
It hadn’t helped.
But I would like to do it again.

We can also carry out the analysis remotely via Teams or Teamsviewer.

I don’t know who my sales manager is. I bought the device online.
I’m from germany.

What should I do?

Hello

We appreciate your information. We want to look into this issue more closely. The best way to do that is to contact your reseller or sales manager. They can give you a direct way to communicate with us and help us solve the problem. If you don’t have a reseller or a sales manager, please use this form to contact us: Teltonika Networks - LTE Routers, Gateways & Modems for IoT 2

Thank you for your cooperation!

Best regards,

Hello,
i have create a message.

Otherwise I’ll wait for the next update and do this without applying my settings and test it again.
Thanks.
Bye Ralph

This topic was automatically closed after 15 days. New replies are no longer allowed.