I want to use gammu for sending sms.
I have problem when want to identify the phone from gammu utility
Environment used:
- openSUSE 12.3 32-bit
- Gammu version 1.32.0 built 09:27 on Aug 10 2012 using GCC 4.7
> gammu -f /var/log/gammulog identify
No response in specified timeout. Probably phone not connected.
I make sure my modem is connected to my laptop
> lsusb
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 019: ID 12d1:1001 Huawei Technologies Co., Ltd. E169/E620/E800 HSDPA Modem
Bus 003 Device 002: ID 04f2:b3bb Chicony Electronics Co., Ltd
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 001 Device 005: ID 0cf3:3004 Atheros Communications, Inc.
Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Then I check using this command to make sure the modem is detected
> ls /dev/serial/by-id -l
lrwxrwxrwx 1 root root 13 Oct 31 11:16 usb-HSDPA_USB_Modem_HSDPA_USB_Modem-if00-port0 -> ../../ttyUSB0
lrwxrwxrwx 1 root root 13 Oct 31 11:16 usb-HSDPA_USB_Modem_HSDPA_USB_Modem-if01-port0 -> ../../ttyUSB1
lrwxrwxrwx 1 root root 13 Oct 31 11:16 usb-HSDPA_USB_Modem_HSDPA_USB_Modem-if02-port0 -> ../../ttyUSB2
lrwxrwxrwx 1 root root 13 Oct 31 11:16 usb-HSDPA_USB_Modem_HSDPA_USB_Modem-if03-port0 -> ../../ttyUSB3
When call the gammu-detect
[gammu]
device = /dev/ttyUSB0
name = Phone on USB serial port HSDPA_USB_Modem HSDPA_USB_Modem
connection = at
[gammu1]
device = /dev/ttyUSB1
name = Phone on USB serial port HSDPA_USB_Modem HSDPA_USB_Modem
connection = at
[gammu2]
device = /dev/ttyUSB2
name = Phone on USB serial port HSDPA_USB_Modem HSDPA_USB_Modem
connection = at
[gammu3]
device = /dev/ttyUSB3
name = Phone on USB serial port HSDPA_USB_Modem HSDPA_USB_Modem
connection = at
[gammu4]
device = /dev/ttyS0
name = Phone on serial port 0
connection = at
[gammu5]
device = /dev/ttyS1
name = Phone on serial port 1
connection = at
[gammu6]
device = /dev/ttyS2
name = Phone on serial port 2
connection = at
[gammu7]
device = /dev/ttyS3
name = Phone on serial port 3
connection = at
[gammu8]
device = /dev/ttyS4
name = Phone on serial port 4
connection = at
[gammu9]
device = /dev/ttyS5
name = Phone on serial port 5
connection = at
[gammu10]
device = /dev/ttyS6
name = Phone on serial port 6
connection = at
[gammu11]
device = /dev/ttyS7
name = Phone on serial port 7
connection = at
opening socket: No such device
Here is the gammu-config, placed in /etc/gammurc
[gammu]
port = /dev/ttyUSB0
connection = at115200
logformat = textall
I really stuck, don't know what's wrong
Even when using wammu (GUI version), to detect phones
Wammu is now searching for phone:
Checking /dev/ttyUSB0 - ['at19200', 'at115200', 'fbusdlr3', 'fbus', 'mbus', 'fbuspl2303']
Checking /dev/ttyUSB1 - ['at19200', 'at115200', 'fbusdlr3', 'fbus', 'mbus', 'fbuspl2303']
Checking /dev/ttyUSB2 - ['at19200', 'at115200', 'fbusdlr3', 'fbus', 'mbus', 'fbuspl2303']
Checking /dev/ttyUSB3 - ['at19200', 'at115200', 'fbusdlr3', 'fbus', 'mbus', 'fbuspl2303']
Finished /dev/ttyUSB2 - ['at19200', 'at115200', 'fbusdlr3', 'fbus', 'mbus', 'fbuspl2303']
Finished /dev/ttyUSB0 - ['at19200', 'at115200', 'fbusdlr3', 'fbus', 'mbus', 'fbuspl2303']
Finished /dev/ttyUSB3 - ['at19200', 'at115200', 'fbusdlr3', 'fbus', 'mbus', 'fbuspl2303']
Finished /dev/ttyUSB1 - ['at19200', 'at115200', 'fbusdlr3', 'fbus', 'mbus', 'fbuspl2303']
All finished, found 0 phones
No phone has been found!
Thanks
Updated
Here is add some log that happen when I specify the log file
> tail -f gammu.log
Thu 2013/10/31 11:55:14: [Gammu - 1.32.0 built 09:27 Aug 10 2012 using GCC 4.7]
Thu 2013/10/31 11:55:14: [Connection - "at"]
Thu 2013/10/31 11:55:14: [Connection index - 0]
Thu 2013/10/31 11:55:14: [Model type - ""]
Thu 2013/10/31 11:55:14: [Device - "/dev/ttyUSB0"]
Thu 2013/10/31 11:55:14: [Running on - Linux, kernel 3.7.10-1.16-desktop (#1 SMP PREEMPT Fri May 31 20:21:23 UTC 2013 (97c14ba))]
Thu 2013/10/31 11:55:14: Serial device: DTR is up, RTS is up, CAR is up, CTS is up
Thu 2013/10/31 11:55:14: Setting speed to 19200
Thu 2013/10/31 11:55:14: [Module - "auto"]
Thu 2013/10/31 11:55:14: Escaping SMS mode
Thu 2013/10/31 11:55:14: Sending simple AT command to wake up some devices
Thu 2013/10/31 11:55:14: 1 "OK"
Thu 2013/10/31 11:55:14: Checking line: OK
Thu 2013/10/31 11:55:14: AT reply state: 1
Thu 2013/10/31 11:55:14: Enabling echo
Thu 2013/10/31 11:55:15: 1 "OK"
Thu 2013/10/31 11:55:15: Checking line: OK
Thu 2013/10/31 11:55:15: AT reply state: 1
Thu 2013/10/31 11:55:15: Trying Motorola mode switch
Thu 2013/10/31 11:55:15: 1 "ERROR"
Thu 2013/10/31 11:55:15: Checking line: ERROR
Thu 2013/10/31 11:55:15: AT reply state: 3
Thu 2013/10/31 11:55:15:
Thu 2013/10/31 11:55:15: Frame not request now. If you can, please report it (see <http://wammu.eu/support/bugs/>). Thank you
Thu 2013/10/31 11:55:15: LAST SENT frame type 0x00/length 10
Thu 2013/10/31 11:55:15: 41A|54T|2B+|4DM|4FO|44D|45E|3D=|322|0D AT+MODE=2.
Thu 2013/10/31 11:55:15: RECEIVED frame type 0x00/length 0x7/7
Thu 2013/10/31 11:55:15: 45E|52R|52R|4FO|52R|0D |0A ERROR..
Thu 2013/10/31 11:55:15:
Thu 2013/10/31 11:55:17: Seems not to be supported
Thu 2013/10/31 11:55:17: Enabling CME errors
Thu 2013/10/31 11:55:17: 1 "OK"
Thu 2013/10/31 11:55:17: Checking line: OK
Thu 2013/10/31 11:55:17: AT reply state: 1
Thu 2013/10/31 11:55:17:
Thu 2013/10/31 11:55:17: Frame not request now. If you can, please report it (see <http://wammu.eu/support/bugs/>). Thank you
Thu 2013/10/31 11:55:17: LAST SENT frame type 0x00/length 10
Thu 2013/10/31 11:55:17: 41A|54T|2B+|43C|4DM|45E|45E|3D=|311|0D AT+CMEE=1.
Thu 2013/10/31 11:55:17: RECEIVED frame type 0x00/length 0x4/4
Thu 2013/10/31 11:55:17: 4FO|4BK|0D |0A OK..
Thu 2013/10/31 11:55:17:
Thu 2013/10/31 11:55:19: 1 "OK"
Thu 2013/10/31 11:55:19: Checking line: OK
Thu 2013/10/31 11:55:19: AT reply state: 1
Thu 2013/10/31 11:55:19:
Thu 2013/10/31 11:55:19: Frame not request now. If you can, please report it (see <http://wammu.eu/support/bugs/>). Thank you
Thu 2013/10/31 11:55:19: LAST SENT frame type 0x00/length 10
Thu 2013/10/31 11:55:19: 41A|54T|2B+|43C|4DM|45E|45E|3D=|322|0D AT+CMEE=2.
Thu 2013/10/31 11:55:19: RECEIVED frame type 0x00/length 0x4/4
Thu 2013/10/31 11:55:19: 4FO|4BK|0D |0A OK..
Thu 2013/10/31 11:55:19:
Thu 2013/10/31 11:55:21: CME errors could not be enabled, some error types won't be detected.
Thu 2013/10/31 11:55:21: 1 "+CSCS: "IRA""
Thu 2013/10/31 11:55:21: 2 "OK"
Thu 2013/10/31 11:55:21: Checking line: OK
Thu 2013/10/31 11:55:21: AT reply state: 1
Thu 2013/10/31 11:55:21:
Thu 2013/10/31 11:55:21: UNKNOWN frame. If you can, please report it (see <http://wammu.eu/support/bugs/>). Thank you
Thu 2013/10/31 11:55:21: LAST SENT frame type 0x00/length 9
Thu 2013/10/31 11:55:21: 41A|54T|2B+|43C|53S|43C|53S|3F?|0D AT+CSCS?.
Thu 2013/10/31 11:55:21: RECEIVED frame type 0x00/length 0x14/20
Thu 2013/10/31 11:55:21: 2B+|43C|53S|43C|53S|3A:|20 |22"|49I|52R|41A|22"|0D |0A |0D |0A +CSCS: "IRA"....
Thu 2013/10/31 11:55:21: 4FO|4BK|0D |0A OK..
Thu 2013/10/31 11:55:21:
Thu 2013/10/31 11:55:23: Init:GSM_TryGetModel failed with error TIMEOUT[14]: No response in specified timeout. Probably phone not connected.
Thu 2013/10/31 11:55:23: [Terminating]
Thu 2013/10/31 11:55:23: [Closing]
In the beginning part everything is OK
We i look more details in this part everything is success
Thu 2013/10/31 11:55:14: Sending simple AT command to wake up some devices
Thu 2013/10/31 11:55:14: 1 "OK"
Thu 2013/10/31 11:55:14: Checking line: OK
Thu 2013/10/31 11:55:14: AT reply state: 1
Thu 2013/10/31 11:55:14: Enabling echo
Thu 2013/10/31 11:55:15: 1 "OK"
Thu 2013/10/31 11:55:15: Checking line: OK
Thu 2013/10/31 11:55:15: AT reply state: 1
Error occured in this part. It's like detecting this is Motorola, but I'm using Huawei E169
Thu 2013/10/31 14:13:16: Trying Motorola mode switch
Thu 2013/10/31 14:13:16: SENDING frametype 0x00/length 0x0A/10
Thu 2013/10/31 14:13:16: 41A|54T|2B+|4DM|4FO|44D|45E|3D=|322|0D AT+MODE=2.
Thu 2013/10/31 14:13:16: 1 "ERROR"
Thu 2013/10/31 14:13:16: Checking line: ERROR
Update
I try to use other modem ZTE MF288, and it works just fine.
Still don't know how to configure Huawei E169
I'm using the Huawei E169 too, but I have only 3 Ports (ttyUSB0, ttyUSB1, ttyUSB2).
Bought it in Germany, using Ubuntu 13.10 with gammu 1.33.0.
Works fine for me when I use the highest port (ttyUSB2).
-> gammu identify
Gerät : /dev/ttyUSB2
Hersteller : Huawei
Modell : E169 (E169)
Firmware : 11.314.13.00.264
It could also be possible the device is in Storage-Mode and you need to switch it to "phone-mode".
There is a lot of information in the output but the key output appears to be.
"Seems to not be supported"
Even though gammu connects to your phone it may not be able to connect to the SMS commands.
Check here for a list of supported phones. http://wammu.eu/phones it appears that your phone is listed.
You may need to set the model in your .gammurc file. Like this model = E169
Related
I have a PYNQ-Z2 board and it contains FT2232HQ chip, which convert data from USB to JTAG and UART
The problem is the board is working and is detected by Vivado (I can program it), but the device doesn't show up as /dev/ttyUSB* device, it shows up as /dev/ftdi-x (where x is a random number) and I can't open a serial port with this device file.
I used lsusb command and I found the chip is correctly detected:
Bus 003 Device 017: ID 0403:6010 Future Technology Devices International, Ltd FT2232C Dual USB-UART/FIFO IC
After that I tried to check the syslog file, and I noticed two weird behaviors, the first is when I connect the board two ttyUSB devices are recognized, not one! /dev/ttyUSB0 & /dev/ttyUSB1.
the second behavior is these two devices are immediately disconnected after they are connected.
Here is the full syslog:
Oct 27 11:45:20 ao20xa kernel: [73109.798748] usb 3-4: new high-speed USB device number 17 using xhci_hcd
Oct 27 11:45:21 ao20xa kernel: [73109.949757] usb 3-4: New USB device found, idVendor=0403, idProduct=6010
Oct 27 11:45:21 ao20xa kernel: [73109.949761] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 27 11:45:21 ao20xa kernel: [73109.949763] usb 3-4: Product: TUL
Oct 27 11:45:21 ao20xa kernel: [73109.949765] usb 3-4: Manufacturer: Xilinx
Oct 27 11:45:21 ao20xa kernel: [73109.949767] usb 3-4: SerialNumber: 1234-tul
Oct 27 11:45:21 ao20xa kernel: [73109.950844] ftdi_sio 3-4:1.0: FTDI USB Serial Device converter detected
Oct 27 11:45:21 ao20xa kernel: [73109.950899] usb 3-4: Detected FT2232H
Oct 27 11:45:21 ao20xa kernel: [73109.951100] usb 3-4: FTDI USB Serial Device converter now attached to ttyUSB0
Oct 27 11:45:21 ao20xa kernel: [73109.951815] ftdi_sio 3-4:1.1: FTDI USB Serial Device converter detected
Oct 27 11:45:21 ao20xa kernel: [73109.951861] usb 3-4: Detected FT2232H
Oct 27 11:45:21 ao20xa kernel: [73109.952058] usb 3-4: FTDI USB Serial Device converter now attached to ttyUSB1
Oct 27 11:45:21 ao20xa mtp-probe: checking bus 3, device 17: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4"
Oct 27 11:45:21 ao20xa mtp-probe: bus: 3, device: 17 was not an MTP device
Oct 27 11:45:21 ao20xa systemd-udevd[18701]: Process '/bin/sh -c 'basename $(dirname $(realpath /sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/device)) > /sys/bus/usb/drivers/ftdi_sio/unbind'' failed with exit code 1.
Oct 27 11:45:21 ao20xa kernel: [73110.089464] ftdi_sio ttyUSB1: FTDI USB Serial Device converter now disconnected from ttyUSB1
Oct 27 11:45:21 ao20xa kernel: [73110.089536] ftdi_sio 3-4:1.1: device disconnected
Oct 27 11:45:21 ao20xa kernel: [73110.089818] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
Oct 27 11:45:21 ao20xa kernel: [73110.089865] ftdi_sio 3-4:1.0: device disconnected
Oct 27 11:45:21 ao20xa snapd[16139]: hotplug.go:199: hotplug device add event ignored, enable experimental.hotplug
Oct 27 11:45:21 ao20xa upowerd[1835]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.0
Oct 27 11:45:21 ao20xa snapd[16139]: hotplug.go:199: hotplug device add event ignored, enable experimental.hotplug
Oct 27 11:45:21 ao20xa upowerd[1835]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.1
Oct 27 11:45:21 ao20xa systemd-udevd[18701]: Process '/bin/sh -c 'basename $(dirname $(realpath /sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/device)) > /sys/bus/usb/drivers/ftdi_sio/unbind'' failed with exit code 1.
Oct 27 11:45:21 ao20xa upowerd[1835]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb3/3-4
Oct 27 11:45:21 ao20xa ModemManager[1044]: <info> (tty/ttyUSB0): released by device '/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4'
Oct 27 11:45:21 ao20xa ModemManager[1044]: <info> (tty/ttyUSB1): released by device '/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4'
Oct 27 11:45:21 ao20xa ModemManager[1044]: <info> Couldn't check support for device '/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4': Operation was cancelled
Oct 27 11:45:21 ao20xa upowerd[1835]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.0
Oct 27 11:45:21 ao20xa upowerd[1835]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.1
So, I wonder if any one could help fixing this problem.
In my case, my user wasn't in the group dialout. When I added:
sudo adduser <my_user> dialout
And logged out and in, finally after the hours of looking for the answer I managed to connect to the serial.
As mentioned in the comments by Ian Abbot and Abady, running:
grep -l ftdi_sio /etc/udev/rules.d/*.rules
and commenting out the lines there helped. For me they were:
#lattice
#BUS=="usb", ACTION=="add", ATTRS{idVendor}=="1134", ATTRS{idProduct}=="8001", MODE=="0666", GROUP=="plugdev", SYMLINK+="lattice-%n"
#FTDI
#SUBSYSTEM=="usb", ACTION=="add", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6010", MODE=="0666", GROUP=="plugdev", SYMLINK+="ftdi-%n"
#SUBSYSTEM=="usb", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6010", RUN+="/bin/sh -c 'basename %p >/sys/bus/usb/drivers/ftdi_sio/unbind'"
It seems there was a rule which was causing the disconnect (renaming the ttyUSB* to ftdi-*)
I'm not sure if this is the write place to write my question, but here it is.
Before a week i updated my macbook pro early 2015 with manjaro gnom.
All good, but the bluetooth is not working.
I tried with bluetooth-manager but it's not opening and inside the journalctl -f it's showing
Oct 15 20:08:59 PPeev systemd[1095]: Started Application launched by gnome-shell.
Oct 15 20:09:00 PPeev blueman-manager.desktop[5014]: blueman-manager 20.09.00 ERROR Manager:118 on_dbus_name_appeared: Default adapter not found, trying first available.
Oct 15 20:09:00 PPeev blueman-manager.desktop[5014]: blueman-manager 20.09.00 ERROR Manager:122 on_dbus_name_appeared: No adapter(s) found, exiting
Oct 15 20:09:00 PPeev blueman-manager.desktop[5014]: blueman-manager version 2.1.3 starting
Oct 15 20:09:00 PPeev systemd[1095]: gnome-launched-blueman-manager.desktop-5014.scope: Succeeded.
Oct 15 20:09:04 PPeev systemd[1095]: gnome-terminal-server.service: Succeeded.
Also when i check the status systemctl status bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2020-10-15 19:52:23 EEST; 19min ago
Docs: man:bluetoothd(8)
Main PID: 1083 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 9413)
Memory: 2.3M
CGroup: /system.slice/bluetooth.service
└─1083 /usr/lib/bluetooth/bluetoothd
Oct 15 19:52:23 PPeev bluetoothd[1083]: src/main.c:parse_controller_config() Key file does not have key “LEScanIntervalConnect” in group “Controller”
Oct 15 19:52:23 PPeev bluetoothd[1083]: src/main.c:parse_controller_config() Key file does not have key “LEScanWindowConnect” in group “Controller”
Oct 15 19:52:23 PPeev bluetoothd[1083]: src/main.c:parse_controller_config() Key file does not have key “LEMinConnectionInterval” in group “Controller”
Oct 15 19:52:23 PPeev bluetoothd[1083]: src/main.c:parse_controller_config() Key file does not have key “LEMaxConnectionInterval” in group “Controller”
Oct 15 19:52:23 PPeev bluetoothd[1083]: src/main.c:parse_controller_config() Key file does not have key “LEConnectionLatency” in group “Controller”
Oct 15 19:52:23 PPeev bluetoothd[1083]: src/main.c:parse_controller_config() Key file does not have key “LEConnectionSupervisionTimeout” in group “Controller”
Oct 15 19:52:23 PPeev bluetoothd[1083]: src/main.c:parse_controller_config() Key file does not have key “LEAutoconnecttimeout” in group “Controller”
Oct 15 19:52:23 PPeev systemd[1]: Started Bluetooth service.
Oct 15 19:52:23 PPeev bluetoothd[1083]: Starting SDP server
Oct 15 19:52:23 PPeev bluetoothd[1083]: Bluetooth management interface 1.17 initialized
Is running.
try disabling and re-enabling the bluetooth from the bios menu.
I checked some threads, and the only working option i got is this.
You may try this. I guess it will work for you too.
I've setup an Ubuntu 16.04 EC2 t2.medium server and followed the instructions here http://docs.bigbluebutton.org/2.0/20install.html to install BigBlueButton 2.0-beta.
When I log into the Demo Meeting room and select Microphone it says calling... then changes to connecting... and then I get a message saying:
WebRTC Audio Failure
Detected the following WebRTC issue: Error 1010: ICE negotiation
timeout. Do you want to try Flash instead?
Here is the output from the console:
BigBlueButton call accepted
bbb_webrtc_bridge_sip.js?v=591:497 Waiting for ICE negotiation
sip.js?v=591:2900 Thu Sep 21 2017 11:27:19 GMT+0800 (WITA) | sip.invitecontext.mediahandler | stream added: fuEOgOt7p5aHrW58wGtGVszgTdGBcNKi
sip.js?v=591:2900 Thu Sep 21 2017 11:27:24 GMT+0800 (WITA) | sip.invitecontext.mediahandler | RTCIceChecking Timeout Triggered after 5000 milliseconds
bbb_webrtc_bridge_sip.js?v=591:499 5 seconds without ICE finishing
bbb_webrtc_bridge_sip.js?v=591:119 Stopping webrtc audio test
bbb_webrtc_bridge_sip.js?v=591:555 Hanging up current session
sip.js?v=591:2900 Thu Sep 21 2017 11:27:24 GMT+0800 (WITA) | sip.inviteclientcontext | terminating Session
sip.js?v=591:2900 Thu Sep 21 2017 11:27:25 GMT+0800 (WITA) | sip.transport | sending WebSocket message:
BYE sip:919673089#172.31.36.135:5060;transport=udp SIP/2.0
Via: SIP/2.0/WSS msk2aa46iuih.invalid;branch=z9hG4bK7275105
Max-Forwards: 70
To: <sip:919673089#staging.bigbluebutton.xxxxxx.com>;tag=SBBF64e6999Hm
From: "w_zqmgpmdukz39-bbbID-Mikhail" <sip:w_zqmgpmdukz39-bbbID-Mikhail#staging.bigbluebutton.xxxxxx.com>;tag=d6e9kj05rj
Call-ID: epjgsffnq2hi688jlvgl
CSeq: 9777 BYE
Supported: outbound
User-Agent: BigBlueButton
Content-Length: 0
bbb_webrtc_bridge_sip.js?v=591:465 call ended null
sip.js?v=591:2900 Thu Sep 21 2017 11:27:25 GMT+0800 (WITA) | sip.inviteclientcontext | closing INVITE session epjgsffnq2hi688jlvglj9cdnvthcr
sip.js?v=591:2900 Thu Sep 21 2017 11:27:25 GMT+0800 (WITA) | sip.invitecontext.mediahandler | closing PeerConnection
sip.js?v=591:2900 Thu Sep 21 2017 11:27:25 GMT+0800 (WITA) | sip.dialog | dialog epjgsffnq2hi688jlvgld6e9kj05rjSBBF64e6999Hm deleted
sip.js?v=591:2900 Thu Sep 21 2017 11:27:25 GMT+0800 (WITA) | sip.ua | user requested closure...
sip.js?v=591:2900 Thu Sep 21 2017 11:27:25 GMT+0800 (WITA) | sip.ua | closing registerContext
sip.js?v=591:2900 Thu Sep 21 2017 11:27:25 GMT+0800 (WITA) | sip.registercontext | already unregistered
LoggerFactory.print # sip.js?v=591:2900
LoggerFactory.(anonymous function) # sip.js?v=591:2917
Logger.(anonymous function) # sip.js?v=591:2911
unregister # sip.js?v=591:3579
close # sip.js?v=591:3570
UA.stop # sip.js?v=591:8929
(anonymous) # bbb_webrtc_bridge_sip.js?v=591:505
setTimeout (async)
(anonymous) # bbb_webrtc_bridge_sip.js?v=591:498
EventEmitter.emit # sip.js?v=591:115
accepted # sip.js?v=591:5641
onSuccess # sip.js?v=591:6851
Promise resolved (async)
receiveInviteResponse # sip.js?v=591:6832
receiveResponse # sip.js?v=591:3784
InviteClientTransaction.receiveResponse # sip.js?v=591:7832
onMessage # sip.js?v=591:8566
ws.onmessage # sip.js?v=591:8424
sip.js?v=591:2900 Thu Sep 21 2017 11:27:25 GMT+0800 (WITA) | sip.transport | received WebSocket text message:
SIP/2.0 200 OK
Via: SIP/2.0/WSS msk2aa46iuih.invalid;branch=z9hG4bK7275105;received=52.51.xx.xx;rport=38902
From: "w_zqmgpmdukz39-bbbID-Mikhail" <sip:w_zqmgpmdukz39-bbbID-Mikhail#staging.bigbluebutton.xxxxxx.com>;tag=d6e9kj05rj
To: <sip:919673089#staging.bigbluebutton.xxxxxx.com>;tag=SBBF64e6999Hm
Call-ID: epjgsffnq2hi688jlvgl
CSeq: 9777 BYE
User-Agent: FreeSWITCH-mod_sofia/1.9.0+git~20170822T213300Z~2ebdf42f2c~64bit
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY
Supported: timer, path, replaces
Content-Length: 0
sip.js?v=591:2900 Thu Sep 21 2017 11:27:25 GMT+0800 (WITA) | sip.transport | closing WebSocket wss://staging.bigbluebutton.xxxxxx.com/ws
sip.js?v=591:2900 Thu Sep 21 2017 11:27:25 GMT+0800 (WITA) | sip.transport | WebSocket disconnected (code: 1000)
sip.js?v=591:2900 Thu Sep 21 2017 11:27:25 GMT+0800 (WITA) | sip.ua | connection state set to 1
sip.js?v=591:2900 Thu Sep 21 2017 11:27:25 GMT+0800 (WITA) | sip.transaction.ict | transport error occurred, deleting INVITE client transaction z9hG4bK9694442
I've searched for anything related to bigbluebutton error 1010 but can't find anything.
Please check your firewall :
TCP ports 80, 443,and 1935 are accessible.
TCP port 7443 is accessible if you intend to configure SSL (recommended), otherwise port 5066 is accessible.
UDP ports 16384 - 32768 are accessible.
Port 80 is not in use by another application.
the problem is your sip ip and port.
Check /opt/freeswitch/etc/freeswitch/sip_profiles/external.xml settings firstly.
ws-binding: :5066
wss-binding: :7443
change it to like this:
ws-binding: your_external_ip_address:5066
wss-binding: your_external_ip_address:7443
Your external ip address is same with external_sip_ip address.
Then check your 5066 and 7443 port if you use firewall.
Then dont forget to restart bbb (bbb-conf --restart)
I am using gammu-smsd 1.31.90, I made a udev rule for my USB 3g dongle but gammu-smsd can not connect to device. It says DEVICEOPENERROR[2].
How can I fix it?
udev-rule in /etc/udev/rules.d/10-rules.local
SUBSYSTEMS=="usb", ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1001", SYMLINK+="phone", GROUP="dialout"
Gammu log:
Wed 2016/03/09 15:57:58 gammu-smsd[2466]: Starting phone communication...
Wed 2016/03/09 15:57:58 gammu-smsd[2466]: gammu: [Gammu 1.31.90 built 08:54:06 May 23 2012 using GCC 4.6]
Wed 2016/03/09 15:57:58 gammu-smsd[2466]: gammu: [Connection - "at"]
Wed 2016/03/09 15:57:58 gammu-smsd[2466]: gammu: [Connection index - 0]
Wed 2016/03/09 15:57:58 gammu-smsd[2466]: gammu: [Model type - ""]
Wed 2016/03/09 15:57:58 gammu-smsd[2466]: gammu: [Device - "/dev/phone"]
Wed 2016/03/09 15:57:58 gammu-smsd[2466]: gammu: [Running on - Linux, kernel 3.4.103 (#4 SMP PREEMPT Thu Dec 18 12:55:58 CST 2014)]
Wed 2016/03/09 15:57:58 gammu-smsd[2466]: gammu: [System error - tcgetattr in serial_open, 25, "Inappropriate ioctl for device"]
Wed 2016/03/09 15:57:58 gammu-smsd[2466]: gammu: Init:GSM_TryGetModel failed with error DEVICEOPENERROR[2]: Error opening device. Unknown, busy or no permissions.
Wed 2016/03/09 15:57:58 gammu-smsd[2466]: Can't open device: Error opening device. Unknown, busy or no permissions. (DEVICEOPENERROR[2])
You Have to config 2 files and edite 'port' and 'Connection' fields.
gammu-config
This config file is in '/home/$YOUR_USER_NAME/.gammurc'
and config this one too:
nano /etc/gammu-smsdrc
set your connection field to 'at' and port field to 'ttyUSBx' which appear your system.
Restart your gammu-smsd service, and if it's active it should work.
service gammu-smsd restart
service gammu-smsd status
● gammu-smsd.service - SMS daemon for Gammu
Loaded: loaded (/lib/systemd/system/gammu-smsd.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2017-12-11 00:02:06 IRST; 10h ago
Docs: man:gammu-smsd(1)
Main PID: 650 (gammu-smsd)
Memory: 1.8M
CPU: 3min 8.684s
CGroup: /system.slice/gammu-smsd.service
└─650 /usr/bin/gammu-smsd --pid=/var/run/gammu-smsd.pid --daemon
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
I have a single instance of MongoDB 2.4.8 running on Windows Server 2012 R2. MongoDB is installed as a Windows Service. I have journalling enabled.
The MongoDB documentation suggests that the MongoDB service should just be shut down via the Windows Service Control Manager:
net stop MongoDB
When I did this recently, the following was logged and I ended up with a non-zero byte mongod.lock file on disk. (I used the --repair option to fix this but it turns out this probably wasn't necessary as I had journalling enabled.)
Thu Nov 21 11:08:12.011 [serviceShutdown] got SERVICE_CONTROL_STOP request from Windows Service Control Manager, will terminate after current cmd ends
Thu Nov 21 11:08:12.043 [serviceShutdown] now exiting
Thu Nov 21 11:08:12.043 dbexit:
Thu Nov 21 11:08:12.043 [serviceShutdown] shutdown: going to close listening sockets...
Thu Nov 21 11:08:12.043 [serviceShutdown] closing listening socket: 1492
Thu Nov 21 11:08:12.043 [serviceShutdown] closing listening socket: 1500
Thu Nov 21 11:08:12.043 [serviceShutdown] shutdown: going to flush diaglog...
Thu Nov 21 11:08:12.043 [serviceShutdown] shutdown: going to close sockets...
Thu Nov 21 11:08:12.043 [serviceShutdown] shutdown: waiting for fs preallocator...
Thu Nov 21 11:08:12.043 [serviceShutdown] shutdown: lock for final commit...
Thu Nov 21 11:08:12.043 [serviceShutdown] shutdown: final commit...
Thu Nov 21 11:08:12.043 [conn1333] end connection 127.0.0.1:51612 (18 connections now open)
Thu Nov 21 11:08:12.043 [conn1331] end connection 127.0.0.1:51610 (18 connections now open)
...snip...
Thu Nov 21 11:08:12.043 [conn1322] end connection 10.1.2.212:53303 (17 connections now open)
Thu Nov 21 11:08:12.043 [conn1337] end connection 127.0.0.1:51620 (18 connections now open)
Thu Nov 21 11:08:12.839 [serviceShutdown] shutdown: closing all files...
Thu Nov 21 11:08:14.683 [serviceShutdown] Progress: 5/163 3% (File Closing Progress)
Thu Nov 21 11:08:16.012 [serviceShutdown] Progress: 6/163 3% (File Closing Progress)
...snip...
Thu Nov 21 11:08:52.030 [serviceShutdown] Progress: 143/163 87% (File Closing Progress)
Thu Nov 21 11:08:54.092 [serviceShutdown] Progress: 153/163 93% (File Closing Progress)
Thu Nov 21 11:08:55.405 [serviceShutdown] closeAllFiles() finished
Thu Nov 21 11:08:55.405 [serviceShutdown] journalCleanup...
Thu Nov 21 11:08:55.405 [serviceShutdown] removeJournalFiles
Thu Nov 21 11:09:05.578 [DataFileSync] ERROR: Client::shutdown not called: DataFileSync
The last line is my main concern.
I'm also interested in how MongoDB is able to take longer to shut down than Windows normally allows for service shutdown? At what point is it safe to shut down the machine without checking the log file?