On 04/10/2013 03:28 PM, Dan Williams wrote:
> On Wed, 2013-04-10 at 15:20 -0400, Nate Pleasant wrote:
>> On 04/03/2013 03:50 PM, Nate Pleasant wrote:
>>> On 04/03/2013 03:43 PM, Dan Williams wrote:
>>>> On Wed, 2013-04-03 at 14:05 -0500, Dan Williams wrote:
>>>>> On Tue, 2013-03-26 at 10:39 -0400, Nate Pleasant wrote:
>>>>>> I know this is not a feature that is currently impelemented into
>>>>>> ModemManager,
>>>>>> but I'm hoping that once we get this solved, we can work on getting it
>>>>>> added into
>>>>>> the project.
>>>>>>
>>>>>> I'm running into an issue when trying to obtain from the Pantech UML290
>>>>>> the
>>>>>> current data usage on the Verizon network. According to Verizon, you
>>>>>> can dial
>>>>>> a special number "#DATA" and then they will send a SMS message to the
>>>>>> Pantech
>>>>>> UML290 with the current network usage. See these links for more details:
>>>>>>
>>>>>> http://support.verizonwireless.com/clc/features/calling_features/number_features.html
>>>>>> http://news.verizonwireless.com/news/2011/07/pr2011-07-01d.html
>>>>>>
>>>>>> The issue I have is I cannot dial "#DATA" using standard AT commands. I
>>>>>> can
>>>>>> use the ATD#777 and ATD*99***1# to establish a 3G and 4G network
>>>>>> connection,
>>>>>> respectively; so I know that the UML290 responds to my AT commands
>>>>>> correctly.
>>>>>> However, when I try dialing "ATD#DATA", I immediately get an ERROR
>>>>>> returned.
>>>>>> I've also tried establishing a network connection using the QMI
>>>>>> interface and
>>>>>> then dialing #DATA, but I get the same error.
>>>>> Same here. ATD#DATA returns ERROR.
>>>>>
>>>>> I don't think the UML290 supports this feature via the AT port.
>>>>> VZAccess requests data usage via the WMC port using command 0x56, which
>>>>> I haven't gotten around to reverse engineering yet. In fact, VZAccess
>>>>> doesn't use the UML290's AT port at all, just QMI and WMC. So you're
>>>>> kinda out of luck here, at least controlling it with the AT port.
>>>> To clarify, it appears that if you send an SMS to the number
>>>> "900080004008" with the content "POUND_DATA", you'll get a reply back
>>>> with your data usage. This is what VZAccess does using the WMC port and
>>>> proprietary WMC commands. It works for SMS too though on /dev/ttyACM0.
>>>> Where the following says <ctl+z>, you do really want to hold down the
>>>> Ctrl key and hit the Z key; that's how AT+CMGS works in text mode.
>>>>
>>>> AT+CMGF=1
>>>> OK
>>>> AT+CMGS="900080004008"
>>>>> POUND_DATA<ctl+z>
>>>> +CMGS: 19809
>>>>
>>>> OK
>>>>
>>>> <wait 5 seconds>
>>>>
>>>> AT+CMGL="ALL"
>>>> +CMGL: 4,"REC UNREAD","xxxxxxxxxx","13/04/03,14:37:15+00"
>>>> Est as of 04/03 2:49PM: Data Usage: 0.001GB.
>>>> +CMGL: 2,"STO SENT","900080004008","13/04/03,19:37:13+00"
>>>> POUND_DATA
>>>>
>>>> OK
>>>>
>>>> Dan
>>>>
>>> Dan,
>>>
>>> Great find! I'll do a USB sniff on my UML290 to see if the VZAccess
>>> Manager sends the SMS to the same phone number.
>>>
>>> Nate
>>> Nathaniel J. Pleasant | Accelerated Concepts | Developer | 1-813-279-2557
>>> www.acceleratedconcepts.com
>> Dan,
>>
>> I confirmed with my UML290 that VZAccess is sending the POUND_DATA
>> command to the same number you listed. It'd be interesting to find out
>> what that number is and if there are other numbers like it that Verizon
>> uses for various features; it's definitely not a regular US phone number.
>>
>> Anyway, I'm now able to successfully get the current network usage from
>> Verizon by sending the appropriate SMS message. Thanks again for all
>> your help!
>>
>> As a side note, I'm also working with the new Verizon Pantech UML295
>> modem, which is turning out to be vastly different than the UML290. You
>> can see the work I've done so far in the link below.
>>
>> https://bitbucket.org/accelecon/modemmanager/wiki/PantechUML295
> Oh fun, one of those. Does it support QMI or AT or DIAG at all, or is
> it solely Web-based?
>
> Dan
>
Dan,
I don't believe it supports any of those. All I get is an eth interface
for the device. Below is the dmesg and lsusb output relative to the UML295.
$ dmesg
[197342.916415] usb 1-2.2: new high-speed USB device number 17 using
ehci-pci
[197343.026546] scsi18 : usb-storage 1-2.2:1.0
[197344.029607] scsi 18:0:0:0: CD-ROM PANTECH
CD-ROM 0000 PQ: 0 ANSI: 2
[197344.031698] sr1: scsi3-mmc drive: 24x/24x xa/form2 caddy
[197344.032194] sr 18:0:0:0: Attached scsi CD-ROM sr1
[197354.965613] usb 1-2.2: USB disconnect, device number 17
[197355.276456] usb 1-2.2: new high-speed USB device number 18 using
ehci-pci
[197355.388668] cdc_ether 1-2.2:1.0 eth2: register 'cdc_ether' at
usb-0000:00:02.1-2.2, CDC Ethernet Device, d0:57:85:69:f6:36
[197355.396540] hid-generic 0003:10A9:6064.0007: hiddev0,hidraw2: USB
HID v2.00 Device [Pantech, Incorporated PANTECH UML295] on
usb-0000:00:02.1-2.2/input2
[197355.398296] hid-generic 0003:10A9:6064.0008: hiddev0,hidraw3: USB
HID v2.00 Device [Pantech, Incorporated PANTECH UML295] on
usb-0000:00:02.1-2.2/input3
[197355.473783] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
[197356.613488] IPv6: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready
$ lsusb -v -d 10a9:6064
Bus 001 Device 020: ID 10a9:6064 SK Teletech Co., Ltd
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 2 Communications
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x10a9 SK Teletech Co., Ltd
idProduct 0x6064
bcdDevice 2.28
iManufacturer 1
iProduct 2
iSerial 3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 144
bNumInterfaces 4
bConfigurationValue 1
iConfiguration 4
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 2 Communications
bInterfaceSubClass 6 Ethernet Networking
bInterfaceProtocol 0
iInterface 5
CDC Header:
bcdCDC 1.10
CDC Union:
bMasterInterface 0
bSlaveInterface 1
CDC Ethernet:
iMacAddress 7 (??)
bmEthernetStatistics 0x00000000
wMaxSegmentSize 1514
wNumberMCFilters 0x0000
bNumberPowerFilters 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 9
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 6
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 8
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 2.00
bCountryCode 1 Arabic
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 28
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 3
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 9
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 2.00
bCountryCode 2 Belgian
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 28
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Nate
Nathaniel J. Pleasant | Accelerated Concepts | Developer
www.acceleratedconcepts.com
_______________________________________________
networkmanager-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/networkmanager-list
