Re: Huawei E220 + Data Connection Manager
Hi Mitsutaka, > > so this is the interesting part. We don't wanna use the magic *99* magic > > and actually use the proper GPRS AT command for connecting the context. > > Yes. I know dialup call is different in each carrier. Most data > connection dial number's are fixed. so I think it needs to add a new > context parametor 'dial number'. That is actually not correct. ATD*99 is a form used for backward compatibility. It is described in Section 10.2 of 3GPP 27.007. This form is frequently used as a shortcut and known by most users. It is however not the 'proper' way to establish a GPRS context. The proper way is actually a bit more involved, but offers greater flexibility. This is what oFono will use. > > > But then we have to talk PPP. That is currently work in progress as an > > extension to GAtChat. > > Yeah, I thought data connection needs PPP(pppd). My image of > implementation is as wvdial configuration. We will not use pppd. We're working on our own ppp solution for oFono. This is a work in progress and thus ppp devices are not yet supported. Regards, -Denis ___ ofono mailing list ofono@ofono.org http://lists.ofono.org/listinfo/ofono
Re: Huawei E220 + Data Connection Manager
Hi, Marcel
On 03:17 Wed 02 Dec , Marcel Holtmann wrote:
> Hi Mitsutaka,
>
> > I'm trying to implement for Huawei E220 using Data Connection
> > Manager. I understand GPRS data conneciton is working in progress. But
> > I don't know much connection sequence that.
> >
> > So I'd like to tell me how should I approach. and I guess data
> > connection in the following. If I mistake, please point out.
> >
> > 1. Launch ofonod, plug-in the modem.
> > 2. Enable modems for getting modem information, Model, Manufacture, Serial
> > and so on(test/enable-modem).
> >
> > 3. Create a context(org.ofono.PrimaryDataContext) according to
> > doc/dataconnectionmanager-api.txt
> >ex. Japanese carrier
> > % ./test/list-contexts
> > [ /huawei1 ]
> > [ /huawei1/primarycontext1 ]
> > Username = em
> > Name = Example
> > Settings = { }
> > Active = 0
> > AccessPointName = 1
> > Password = em
> > Type = internet
> >
> > 4. Activate it. but currently it can not be atacched
> > Traceback (most recent call last):
> > File "./test/activate-context", line 38, in
> > context.SetProperty("Active", dbus.Boolean(1))
> > File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 68, in
> > __call__
> > return self._proxy_method(*args, **keywords)
> > File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 140, in
> > __call__
> > **keywords)
> > File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 622, in
> > call_blocking
> > message, timeout)
> > dbus.exceptions.DBusException: org.ofono.Error.NotAttached: GPRS is not
> > attached
> >
> > 5. Dialup using ATDT (this case is support only Tone)
> >ATDT*99***1#
> >CONNECT
> > 6. ppp0 interface up
> > 7. Authenticate EAP, PAP or CHAP using Username, Passowrd
> > 8. Getting IP Address, Netmask, Gateway from APN(?)
>
> so this is the interesting part. We don't wanna use the magic *99* magic
> and actually use the proper GPRS AT command for connecting the context.
Yes. I know dialup call is different in each carrier. Most data
connection dial number's are fixed. so I think it needs to add a new
context parametor 'dial number'.
> But then we have to talk PPP. That is currently work in progress as an
> extension to GAtChat.
Yeah, I thought data connection needs PPP(pppd). My image of
implementation is as wvdial configuration.
ex. wvdial connection
1. wvdial settings
2. Run wvdial using /etc/wvdial.conf
3. Run pppd from wvdial
ex. ofono connection
1. ofono settings to the D-Bus
2. Activate context and connection
3. Run pppd from ofonod
Thanks,
--
Mitsutaka Amano
___
ofono mailing list
ofono@ofono.org
http://lists.ofono.org/listinfo/ofono
Re: question for concatenated message
Hi Zhigang, > According to 23.040: > The maximum length of an uncompressed concatenated short message is 39015 > (255*153) default alphabet characters, 34170 (255*134) octets or 17085 > (255*67) UCS2 characters. The structure of UD when concatentation is used is like this: [UDH length][IEI1][IEI1LEN][IEI1DATA]PAYLOAD One can use two header types for concatenation. 16 bit sequence and 8 bit sequence. 16 Bit sequence uses 4 bytes while 8 bit sequence uses 3 bytes. So the total overhead is: 1 byte for udhl + 1 byte for iei + 1 byte for length + 3|4 bytes = 7 for 16 bit header and 6 bytes for 8 bit header. So the you provide above numbers are correct for the 8bit case, but not correct for 16 bit case. In 16 bit case we can encode 255 * 152 GSM characters and 255 * 66 UCS2 characters (the UCS2 characters cannot be split in the middle). > > But in oFono didn't match above: > For UCS2 is (255 * 66), default alphabet is (253* 153) oFono uses 16 bit sequence by default, so at least in the case of UCS2 it is correct. For 7bit case you need to limit the payload to 255 * 152 characters. 253*153 will in fact result in 255 segments when using 16 bit headers. Regards, -Denis ___ ofono mailing list ofono@ofono.org http://lists.ofono.org/listinfo/ofono
Re: Huawei E220 + Data Connection Manager
Hi Mitsutaka,
> I'm trying to implement for Huawei E220 using Data Connection
> Manager. I understand GPRS data conneciton is working in progress. But
> I don't know much connection sequence that.
>
> So I'd like to tell me how should I approach. and I guess data
> connection in the following. If I mistake, please point out.
>
> 1. Launch ofonod, plug-in the modem.
> 2. Enable modems for getting modem information, Model, Manufacture, Serial
> and so on(test/enable-modem).
>
> 3. Create a context(org.ofono.PrimaryDataContext) according to
> doc/dataconnectionmanager-api.txt
>ex. Japanese carrier
> % ./test/list-contexts
> [ /huawei1 ]
> [ /huawei1/primarycontext1 ]
> Username = em
> Name = Example
> Settings = { }
> Active = 0
> AccessPointName = 1
> Password = em
> Type = internet
>
> 4. Activate it. but currently it can not be atacched
> Traceback (most recent call last):
> File "./test/activate-context", line 38, in
> context.SetProperty("Active", dbus.Boolean(1))
> File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 68, in
> __call__
> return self._proxy_method(*args, **keywords)
> File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 140, in
> __call__
> **keywords)
> File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 622, in
> call_blocking
> message, timeout)
> dbus.exceptions.DBusException: org.ofono.Error.NotAttached: GPRS is not
> attached
>
> 5. Dialup using ATDT (this case is support only Tone)
>ATDT*99***1#
>CONNECT
> 6. ppp0 interface up
> 7. Authenticate EAP, PAP or CHAP using Username, Passowrd
> 8. Getting IP Address, Netmask, Gateway from APN(?)
so this is the interesting part. We don't wanna use the magic *99* magic
and actually use the proper GPRS AT command for connecting the context.
But then we have to talk PPP. That is currently work in progress as an
extension to GAtChat.
Regards
Marcel
___
ofono mailing list
ofono@ofono.org
http://lists.ofono.org/listinfo/ofono
question for concatenated message
HI, According to 23.040: The maximum length of an uncompressed concatenated short message is 39015 (255*153) default alphabet characters, 34170 (255*134) octets or 17085 (255*67) UCS2 characters. But in oFono didn't match above: For UCS2 is (255 * 66), default alphabet is (253* 153) I file a bug to track this, let me know if it's invalid. http://bugzilla.moblin.org/show_bug.cgi?id=8352 Thanks Zhigang ___ ofono mailing list ofono@ofono.org http://lists.ofono.org/listinfo/ofono
Huawei E220 + Data Connection Manager
Hi,
I'm trying to implement for Huawei E220 using Data Connection
Manager. I understand GPRS data conneciton is working in progress. But
I don't know much connection sequence that.
So I'd like to tell me how should I approach. and I guess data
connection in the following. If I mistake, please point out.
1. Launch ofonod, plug-in the modem.
2. Enable modems for getting modem information, Model, Manufacture, Serial and
so on(test/enable-modem).
3. Create a context(org.ofono.PrimaryDataContext) according to
doc/dataconnectionmanager-api.txt
ex. Japanese carrier
% ./test/list-contexts
[ /huawei1 ]
[ /huawei1/primarycontext1 ]
Username = em
Name = Example
Settings = { }
Active = 0
AccessPointName = 1
Password = em
Type = internet
4. Activate it. but currently it can not be atacched
Traceback (most recent call last):
File "./test/activate-context", line 38, in
context.SetProperty("Active", dbus.Boolean(1))
File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 68, in __call__
return self._proxy_method(*args, **keywords)
File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 140, in __call__
**keywords)
File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 622, in
call_blocking
message, timeout)
dbus.exceptions.DBusException: org.ofono.Error.NotAttached: GPRS is not attached
5. Dialup using ATDT (this case is support only Tone)
ATDT*99***1#
CONNECT
6. ppp0 interface up
7. Authenticate EAP, PAP or CHAP using Username, Passowrd
8. Getting IP Address, Netmask, Gateway from APN(?)
I guess Carriers and device obtained by different methods in 7, 8. But
I don't think that using AT commands.
Thanks,
--
Mitsutaka Amano
___
ofono mailing list
ofono@ofono.org
http://lists.ofono.org/listinfo/ofono
Re: oFono running on new Freerunner distribution
Hi Dario, > I also noticed a missing line in the plugins/calypso.c file which > differs from 0.7 to 0.8-0.11, I added in the 0.11 release but without > results, but if it can be useful to debug the line is: > > ofono_devinfo_create(modem, 0, "atmodem", data->dlcs[AUX_DLC]); It isn't missing, it has been moved to pre_sim function. Actually all of calypso.c atom setup was completely wrong. It suffered some bit-rot. I've fixed up calypso plugin and tested it running natively on my Freerunner. I can now dial -> alerting -> hangup, and also dial -> accept -> hangup. Hopefully third time is the charm. Let me know if it still doesn't work. Regards, -Denis ___ ofono mailing list ofono@ofono.org http://lists.ofono.org/listinfo/ofono
Re: oFono running on new Freerunner distribution
Hi Denis, attached is a correct log with the AT debug lines, sorry for the mistake, the patch didn't achieve any results though... For what regards the "second call not possible after the first one hangup" I noticed the first version on which appears the problem is 0.8, the one where the muxer support was introduced. I can confirm 0.7 works great, I can do as many calls I want without problems (even if the "can't hangup while alerting" does occur). I also noticed a missing line in the plugins/calypso.c file which differs from 0.7 to 0.8-0.11, I added in the 0.11 release but without results, but if it can be useful to debug the line is: ofono_devinfo_create(modem, 0, "atmodem", data->dlcs[AUX_DLC]); at row 446 in fuction: calypso_post_sim(struct ofono_modem *modem) it was present (without muxer support of course) in 0.7. Hoping to be useful, best regards. Dario. ofonod[765]: oFono version 0.10 Using **pending_return in dbus_connection_send_with_reply_setup() without pending_setup is deprecated and strongly discouraged Using **pending_return in dbus_connection_send_with_reply_setup() without pending_setup is deprecated and strongly discouraged ofonod[765]: src/plugin.c:__ofono_plugin_init() ofonod[765]: src/modem.c:ofono_modem_driver_register() driver: 0x68f8c, name: palmpre ofonod[765]: plugins/hfp.c:hfp_init() ofonod[765]: src/modem.c:ofono_modem_driver_register() driver: 0x68f38, name: hfp ofonod[765]: src/modem.c:ofono_modem_driver_register() driver: 0x68f04, name: novatel ofonod[765]: src/modem.c:ofono_modem_driver_register() driver: 0x68ed0, name: huawei ofonod[765]: src/modem.c:ofono_modem_driver_register() driver: 0x68e9c, name: hso ofonod[765]: src/modem.c:ofono_modem_driver_register() driver: 0x68e60, name: mbm ofonod[765]: src/modem.c:ofono_modem_driver_register() driver: 0x68e2c, name: calypso ofonod[765]: src/modem.c:ofono_modem_driver_register() driver: 0x68df8, name: g1 ofonod[765]: src/modem.c:ofono_modem_driver_register() driver: 0x68dc4, name: atgen ofonod[765]: src/modem.c:ofono_modem_driver_register() driver: 0x68d90, name: phonesim ofonod[765]: src/modem.c:ofono_modem_create() calypso ofonod[765]: src/modem.c:set_modem_property() modem 0x71b90 property Device ofonod[765]: plugins/calypso.c:calypso_probe() ofonod[765]: src/modem.c:get_modem_property() modem 0x71b90 property Device ofonod[765]: plugins/calypso.c:calypso_probe() /dev/ttySAC0 ofonod[765]: src/gprs.c:ofono_gprs_context_driver_register() driver: 0x68d44, name: hso ofonod[765]: src/gprs.c:ofono_gprs_context_driver_register() driver: 0x68d18, name: mbm ofonod[765]: src/voicecall.c:ofono_voicecall_driver_register() driver: 0x68c50, name: hfpmodem ofonod[765]: src/network.c:ofono_netreg_driver_register() driver: 0x68ca0, name: hfpmodem ofonod[765]: src/call-volume.c:ofono_call_volume_driver_register() driver: 0x68cd8, name: hfpmodem ofonod[765]: src/voicecall.c:ofono_voicecall_driver_register() driver: 0x68bf0, name: calypsomodem ofonod[765]: src/voicecall.c:ofono_voicecall_driver_register() driver: 0x68aa8, name: atmodem ofonod[765]: src/modem.c:ofono_devinfo_driver_register() driver: 0x68b54, name: atmodem ofonod[765]: src/call-barring.c:ofono_call_barring_driver_register() driver: 0x68b00, name: atmodem ofonod[765]: src/call-forwarding.c:ofono_call_forwarding_driver_register() driver: 0x68990, name: atmodem ofonod[765]: src/call-meter.c:ofono_call_meter_driver_register() driver: 0x689b8, name: atmodem ofonod[765]: src/call-settings.c:ofono_call_settings_driver_register() driver: 0x688e4, name: atmodem ofonod[765]: src/phonebook.c:ofono_phonebook_driver_register() driver: 0x68b20, name: atmodem ofonod[765]: src/ssn.c:ofono_ssn_driver_register() driver: 0x68b48, name: atmodem ofonod[765]: src/ussd.c:ofono_ussd_driver_register() driver: 0x68a8c, name: atmodem ofonod[765]: src/sms.c:ofono_sms_driver_register() driver: 0x6892c, name: atmodem ofonod[765]: src/sim.c:ofono_sim_driver_register() driver: 0x68a40, name: atmodem ofonod[765]: src/network.c:ofono_netreg_driver_register() driver: 0x68a00, name: atmodem ofonod[765]: src/cbs.c:ofono_cbs_driver_register() driver: 0x6897c, name: atmodem ofonod[765]: src/call-volume.c:ofono_call_volume_driver_register() driver: 0x68b70, name: atmodem ofonod[765]: src/gprs.c:ofono_gprs_driver_register() driver: 0x68b98, name: atmodem ofonod[765]: src/gprs.c:ofono_gprs_context_driver_register() driver: 0x68bbc, name: atmodem ofonod[765]: src/modem.c:ofono_devinfo_driver_register() driver: 0x68630, name: isimodem ofonod[765]: src/phonebook.c:ofono_phonebook_driver_register() driver: 0x68620, name: isimodem ofonod[765]: src/network.c:ofono_netreg_driver_register() driver: 0x6864c, name: isimodem ofonod[765]: src/voicecall.c:ofono_voicecall_driver_register() driver: 0x68674, name: isimodem ofonod[765]: src/sms.c:ofono_sms_driver_register() driver: 0x686bc, name: isimodem ofonod[765]: src/cbs.c:ofono_cbs_driver_register() driver: 0x686d4, name: isi
