Author |
Post |
|
#1 Sat Dec 18, 2010 21:11, 173 months ago.
|
Member
Registered: Dec 2010
Location: United States of America
|
Operating system name and version: Ubuntu Server 10.10 Version of smsd: 3.1.14 Name and model of a modem / phone: (3) Option ICON 322 Interface: USB I'm having trouble with sending and receiving from multiple modems. I searched the forums and have tried different configurations and I cannot get the receiving message to go to the correct GSM device My config file: When a message is spooled it goes in the correct GSM folder to be queued but when the message reaches my phone it keeps defaulting to GSM1. These are what is in the sent folder: Everything seems to be working. I've rebooted and restarted the service multiple times. And I also know that the /dev/tty* locations are correct because I've tested them without all the queues and the message sends out to the right number. My goal is to receive a message from GSM1 and send back out to GSM1, receive from GSM2 and send back out to GSM2, etc. Thanks in advanced!! 
|
|
#2 Sun Dec 19, 2010 13:12, 173 months ago.
|
Administrator
Registered: May 2009
Location: Jyväskylä, Finland
|
Your messages show that both GSM2 and GSM3 have the same IMSI. Do you surely have SIM cards with different GSM numbers?
|
|
#3 Sun Dec 19, 2010 19:24, 173 months ago.
|
Member
Registered: Dec 2010
Location: United States of America
Topic owner
|
I have 3 gsm modems with 3 different activated sims. The IMSI number that it's pulling I think is from GSM1 because when it sends back out it's defaulting to GSM1
|
|
#4 Sun Dec 19, 2010 19:37, 173 months ago.
|
Administrator
Registered: May 2009
Location: Jyväskylä, Finland
|
I do not understand... Of course you have 3 modems, and SIM in each of them. But does those SIM's have different GSM number for each? Or do you use some "parallel SIM cards" ("MultiSIM" or something like that), which all serves the same number? If you connect only one modem and send a message, you can see the GSM number of sender. If you then connect another modem with another SIM, but only one modem, what is the number of sender?
|
|
#5 Sun Dec 19, 2010 20:29, 173 months ago.
|
Member
Registered: Dec 2010
Location: United States of America
Topic owner
|
They are 3 different numbers
|
|
#6 Mon Dec 20, 2010 12:29, 173 months ago.
|
Administrator
Registered: May 2009
Location: Jyväskylä, Finland
|
chadpriddle wrote When a message is spooled it goes in the correct GSM folder to be queued but when the message reaches my phone it keeps defaulting to GSM1.
Have I understood you correctly?: When you receive a message to your phone, it seems that it was sent by GSM1. And when you use GSM2 to send the message, still the message is received from a number which belongs to SIM card in GSM1 device? You could change the loglevel to 7. After you restart the smsd, all modems will report GCSN (serial number) and IMSI in the log. Those should be all different. Are they? Your setup looks correct. Perhaps you have meant that only GSM3 runs eventhandler, but it has nothing to do with this issue. All modems have different device setting. However, based on your two messages with the same IMSI, it may be possible that all processes are still serving the same modem. In this case there should be some errors listed in the log.
|
|
#7 Tue Dec 21, 2010 09:04, 173 months ago.
|
Member
Registered: Dec 2010
Location: United States of America
Topic owner
|
keke wrote Have I understood you correctly?: When you receive a message to your phone, it seems that it was sent by GSM1. And when you use GSM2 to send the message, still the message is received from a number which belongs to SIM card in GSM1 device?
Yes exactly. keke wrote You could change the loglevel to 7. After you restart the smsd, all modems will report CGSN (serial number) and IMSI in the log. Those should be all different. Are they?
Yes, I'm getting different CGSN and IMSI numbers in the log per modem. When I originally looked in the smsd.log it was about 3mb of text and towards the bottom a lot of little image boxes like it couldn't read the text. So I just copied the file over and deleted everything in the log and restarted the service and then the log seemed to be running more smoothly. Any reasons as to why it got corrupt? Or is that a common thing?
|
|
#8 Tue Dec 21, 2010 10:54, 173 months ago.
|
Member
Registered: Dec 2010
Location: United States of America
Topic owner
|
I figured it out! It WAS an issue with the device mapping on the USB BUS. I read on a lot of different forums with people having issues with USB devices getting swapped around because every time udev gets restarted it might reassign it a new tty* ID. And it also does not help that I am using a 7 port USB powered hub and it also doesnt help that my ICON Option 322 GSM modems don't provide a unique serial number per device when I get the udev info, and my specific USB modems create 5 different tty* mounts per modem; example: ttyHS1 = Control, ttyHS2 = Application, ttyHS4 = Diagnostic2, ttyHS5 = Modem, ttyHS6 = Diagnostic. My solution is to create symlinks for each kernel that maps to the BUS and then to the specific port on the hub. So as long as I label my modems and plug them into the right port everything should sync up the way it was intended. Create a new rule file: /etc/udev/rules.d/65-gsm-modems.rules Create a symlink per line in the file: As in the example above my hub is plugged into the "3" BUS on my motherboard and then the following number "1" is the port number and then the "1.0" is just the modem specific modes (Control). You might have to restart your server to get the new symlink rules to get working. Info on how udev works: http://reactivated.net/writing_udev_rules.html#udevinfoTo figure out the variables that you need to find, type this: This will output your USB devices This will output the devices that are available to choose from. In my case they were the "ttyHS0" through "ttyHS15" Now what is probably the easiest is to plug one USB modem in and then repeat this process on each port to get the kernel values, they should be towards the beginning of the output. And then update your smsd.conf file: Restart sms3 Hope this helps someone else as it was really frustrating me!! No fault to keke or the sms3 software and my configuration was correct too but the devices paths were screwed up.
|
|
#9 Tue Dec 21, 2010 11:20, 173 months ago.
|
Administrator
Registered: May 2009
Location: Jyväskylä, Finland
|
Thank you very much for the information.
I'm sure that this will help other users.
|