SMS Server Tools 3
 Menu
Basic information:
Additional information:
Support:
Get SMS Server Tools 3:
Additional Options

 Sponsored links

 Search
Custom Search

 Visitor locations
 
 SMS Server Tools 3 Community
Welcome, Guest. The forum is currently read-only, but will open soon. Fri Mar 14, 2025 12:30
SMSTools3 Community » Search Bottom

Page:  1

Keywords:
Mode: All keywords (AND)
itsarno: Hi, just to let you know and add that model to the list of known working devices. A Samsung F480 works fine with smsd version 3.0.10 (no unnecessary upgrades on a production system...) OS is linux kernel 2.6.22 (SUSE out-of-the-box) x86_64. Configuration: The phone is connected with the USB cable that came with it. Setting in the phone is to use the Samsung PC suite mode. lsusb reports the phone like this: Bus 003 Device 065: ID 04e8:6601 Samsung Electronics Co., Ltd Z100 Mobile Phone The phone gets assigned a ttyACMx device name automatically. For better mamageability, I created a udev rule to create a symlink with a known name for it: KERNEL=="ttyACM*", ATTRS{product}=="SAMSUNG Mobile Modem", SYMLINK="tty2-for-SMS", OWNER="sms",GROUP="sms", MODE="0640", OPTIONS="last-rule" (this needs to be on ONE LINE ONLY) The configuration of this device is [F480] device = /dev/tty2-for-SMS incoming = yes pin = <hidden> init1 = AT+CPMS="SM","ME","SM" memory_start = 0 cs_convert = yes The only quirks I experienced were that I had to set the storage area where incoming SMSes are stored to "SM" explicitly, and the phone uses storage slots numbered from 0. I guess many modern phones with USB connectors would work similarly, i.e. they are acm devices and need minimal setup in smsd.conf. Apart from that - thanks for a useful product! Arno

Page:  1

SMSTools3 Community » Search Top

 
Time in this board is UTC.  

Privacy Policy   SMS Server Tools 3 Copyright © Keijo Kasvi.