Re: 3g command line
On 2 December 2010 10:32, Lennert Jansen wrote: > Hi there, > > As I'm completely new & surprised by network manager, my option GMT 382E > umts card got working instantly, 3g with Proximus in Belgium. > However, I'd like to use these kind of card with ubuntu server install, and > would like to know the commands to get this working from the command-line. > > Any tips are welcome, seems I can't figure this out... > > > Lennert. > > Hi Lennert, If you want a minimal install you need something like the hso_connect.sh script which is available in the HSO driver packages from Option. You can locate the latest script here: http://www.pharscape.org/forum/index.php/topic,821.0.html Cheers, Paul -- www.pharscape.org ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: OT: 3G Modem - Any voice applications?
On 12/10/2010 13:32, Ma Begaj wrote: > hi, > > off topic question: > do you know linux applications which could be used to make voice calls > through 3G modem > and a headset. I am not talking about VOIP but about standard voice > call like on your phone. > > gnome-phone-manager is probably able to send text messages through 3G > modem but I was > not able to find any voice call (dialer) for linux. windows had > "dialer.exe" which was/is a > program which allows a user to dial an outgoing voice call via his > computer, if the modem > supports both voice and data. > > there are a lot of ppp dialer for linux but only with data support > > any ideas? > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > Hi, I don't think a general solution is possible. I am not aware of any standard USB modem that supports voice communication via the host computer. They don't have a mechanism (channel/codec) to get the voice data to the host computer and most don't have voice enabled firmware. Some modules (I know of Option modules) have pcm interfaces for the voice data and a suitably configured host (hardware and software) can make voice calls. If you have an old PCcard modem with a headphone socket (such as some older Option GPRS/3G cards and a few Huawei cards) then it is possible to make voice calls using basic AT commands. The difference between dialing a circuit switched modem data link and dialling a voice call is just a semi-colon at the end of the telephone number. Paul http://www.pharscape.org http://www.pharscape.org/forum ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworkManager doesn't connect to my Mobile Broadband connection
On 15/07/2010 19:45, Tassilo Horn wrote: > Hi all, > > I have a Huawang E160 UMTS USB Stick. I think I've installed and > configured it correctly. At least NetworkManager 0.8 recognizes it. I > entered the relevant settings, and I can see NetworkManager trying to > connect. > > Unfortunately, it never succeeds, but it also doesn't tell my why. > Here's the cutout from /var/log/messages that I got when trying to > connect: > > --8<---cut here---start->8--- > Jul 15 18:59:46 thinkpad NetworkManager: Activation (ttyUSB0) > starting connection 'Nicoles O2 Stick' > Jul 15 18:59:46 thinkpad NetworkManager: (ttyUSB0): device state > change: 3 -> 4 (reason 0) > Jul 15 18:59:46 thinkpad NetworkManager: Activation (ttyUSB0) Stage 1 > of 5 (Device Prepare) scheduled... > Jul 15 18:59:46 thinkpad NetworkManager: Activation (ttyUSB0) Stage 1 > of 5 (Device Prepare) started... > Jul 15 18:59:46 thinkpad NetworkManager: (ttyUSB0): device state > change: 4 -> 6 (reason 0) > Jul 15 18:59:46 thinkpad NetworkManager: Activation (ttyUSB0) Stage 1 > of 5 (Device Prepare) complete. > Jul 15 18:59:46 thinkpad NetworkManager: Activation (ttyUSB0) Stage 1 > of 5 (Device Prepare) scheduled... > Jul 15 18:59:46 thinkpad NetworkManager: Activation (ttyUSB0) Stage 1 > of 5 (Device Prepare) started... > Jul 15 18:59:46 thinkpad NetworkManager: (ttyUSB0): device state > change: 6 -> 4 (reason 0) > Jul 15 18:59:46 thinkpad NetworkManager: Activation (ttyUSB0) Stage 1 > of 5 (Device Prepare) complete. > Jul 15 18:59:46 thinkpad NetworkManager: stage1_enable_done(): GSM > modem enable failed: (32) SIM PIN required > Jul 15 18:59:46 thinkpad modem-manager: (ttyUSB0) opening serial device... > Jul 15 18:59:46 thinkpad modem-manager: Modem > /org/freedesktop/ModemManager/Modems/4: unlock no longer required > Jul 15 18:59:46 thinkpad modem-manager: (ttyUSB0) closing serial device... > Jul 15 18:59:46 thinkpad NetworkManager: Activation (ttyUSB0) Stage 1 > of 5 (Device Prepare) scheduled... > Jul 15 18:59:46 thinkpad NetworkManager: Activation (ttyUSB0) Stage 1 > of 5 (Device Prepare) started... > Jul 15 18:59:46 thinkpad NetworkManager: Activation (ttyUSB0) Stage 1 > of 5 (Device Prepare) complete. > Jul 15 18:59:46 thinkpad modem-manager: (ttyUSB0) opening serial device... > Jul 15 18:59:46 thinkpad modem-manager: Modem > /org/freedesktop/ModemManager/Modems/4: state changed (disabled -> enabling) > Jul 15 18:59:47 thinkpad modem-manager: (ttyUSB1) opening serial device... > Jul 15 18:59:47 thinkpad modem-manager: Modem > /org/freedesktop/ModemManager/Modems/4: state changed (enabling -> enabled) > Jul 15 18:59:47 thinkpad modem-manager: Registration state changed: 2 > Jul 15 18:59:47 thinkpad modem-manager: Modem > /org/freedesktop/ModemManager/Modems/4: state changed (enabled -> searching) > Jul 15 18:59:53 thinkpad kernel: option: option_instat_callback: error -71 > Jul 15 18:59:54 thinkpad kernel: option: option_instat_callback: error -71 > Jul 15 18:59:54 thinkpad kernel: option: option_instat_callback: error -71 > Jul 15 18:59:54 thinkpad kernel: option: option_instat_callback: error -71 > Jul 15 18:59:54 thinkpad kernel: option: option_instat_callback: error -71 > Jul 15 18:59:54 thinkpad kernel: option: option_instat_callback: error -71 > Jul 15 18:59:55 thinkpad kernel: option: option_instat_callback: error -71 > Jul 15 18:59:55 thinkpad kernel: option: option_instat_callback: error -71 > Jul 15 18:59:55 thinkpad kernel: option: option_instat_callback: error -71 > Jul 15 18:59:55 thinkpad kernel: option: option_instat_callback: error -71 > Jul 15 18:59:55 thinkpad kernel: option: option_instat_callback: error -71 > Jul 15 18:59:56 thinkpad kernel: option: option_instat_callback: error -71 > Jul 15 18:59:56 thinkpad kernel: option: option_instat_callback: error -71 > Jul 15 18:59:56 thinkpad kernel: option: option_instat_callback: error -71 > Jul 15 18:59:56 thinkpad kernel: option: option_instat_callback: error -71 > Jul 15 18:59:56 thinkpad kernel: option: option_instat_callback: error -71 > Jul 15 18:59:56 thinkpad kernel: option: option_instat_callback: error -71 > Jul 15 18:59:57 thinkpad kernel: option: option_instat_callback: error -71 > Jul 15 18:59:57 thinkpad kernel: option: option_instat_callback: error -71 > Jul 15 18:59:57 thinkpad kernel: option: option_instat_callback: error -71 > Jul 15 18:59:57 thinkpad kernel: option: option_instat_callback: error -71 > Jul 15 18:59:57 thinkpad kernel: option: option_instat_callback: error -71 > Jul 15 18:59:58 thinkpad kernel: usb 2-2: USB disconnect, address 17 > Jul 15 18:59:58 thinkpad kernel: option: option_instat_callback: error -108 > Jul 15 18:59:58 thinkpad kernel: option1 ttyUSB0: GSM modem (1-port) > converter now disconnected from ttyUSB0 > Jul 15 18:59:58 thinkpad kernel: option 2-2:1.0: device disconnected > Jul 15 18:59:58 thinkpad kernel: option1 ttyUSB1: GSM modem (1-port) > con
Re: Avoiding 3G roaming costs
Gianluca Sforna wrote: On Wed, Sep 23, 2009 at 8:51 AM, Dan Williams wrote: We can hack something together with F11 perhaps, and on F12 it's even easier. You can try to enter your providers' MCC/MNC (a 6-digit number for the US, 5 digits for everywhere else) in the connection editor in the "Network" entry and NM will direct the modem to register *only* on your providers network and thus not roam, but there are certainly improvements we can do. The obvious improvement I can think of, assuming the 5/6 digits codes you mention are stored in the providers database, is to add a checkbox "allow roaming" to the edit connection page... do we have such codes? if not, where should I look for? By the way, thanks for replying, I thought mailman redirected the message to /dev/null ;) Ideally the user should be warned when the registration state of the device becomes set to roaming. Roaming is a big an issue where a user operates within their own country but close to the border of another country (In Europe this is a significant issue). In poor signals conditions the foreign network can be found before the local network and the user will be roaming without leaving his country. When users persistently operate in these regions the usual recommendation is to manually select the network to their home network. When you are deliberately travelling abroad you may also need to select the Service Provider to use. While most Service Providers allow their systems to be used for voice and SMS the data connections will often fail if there is no agreement between them and your Service Provider. Some of the larger Service Provider groups use SIMs that intelligently manage registration for you with lookup tables etc to ensure that only partner networks are used if available. But that is not universal for all SIMs. Just to add a little insight ... I have a UK Vodafone account.and I have noticed that when I roam from the UK to Belgium my Vodafone SIM will keep me connected to Proximus (the local Vodafone group member) if possible and when I query the registration state I am not roaming but it is a different MNC. But I am charged a higher tariff for data! If I travel to a location in Belgium where Proximus is not available then my phone will register with one of the other two networks. The tarifs are *much* higher and one of them cannot support 3G data at all and refuses to make the data connection. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
