Closed GoogleCodeExporter closed 9 years ago
AT+CCWA?
check call waiting status, not enable or disable this feature.
AT+CCWA? executed long time because ask network for value.
may be gsm still not registered at time of AT+CCWA?
I try move CCWA setting and status checking to moment when GSM registration
done.
Original comment by bg_...@mail.ru
on 4 Dec 2010 at 10:34
yes, looks so....
Original comment by pag...@gmail.com
on 4 Dec 2010 at 10:37
r67 getting worst ;(
test*CLI> datacard show devices
ID Group State RSSI Mode Submode Provider Name Model
Firmware IMEI IMSI Number
datacard3 0 Not connec 25 0 0 NONE
Unknown
datacard2 0 Not connec 99 0 0 NONE
Unknown
datacard1 0 Free 18 0 0 vodafone ES K3520
11.315.05.00.00 353284027028680 214060400091558 +699887766
datacard0 0 Not connec 26 0 0 NONE
Unknown
-- Datacard datacard3 trying to connect on /dev/ttyUSB11...
-- Datacard datacard3 has connected, initializing...
-- Datacard datacard2 trying to connect on /dev/ttyUSB8...
-- Datacard datacard2 has connected, initializing...
-- Datacard datacard0 trying to connect on /dev/ttyUSB2...
-- Datacard datacard0 has connected, initializing...
-- Datacard datacard3 initialized and ready
-- Datacard datacard0 initialized and ready
[Dec 4 16:55:07] ERROR[4500]: at_response.c:329 at_response_error: [datacard3]
Command 'AT+CCWA?' failed
-- Datacard datacard3 has disconnected
[Dec 4 16:55:07] ERROR[4502]: at_response.c:329 at_response_error: [datacard0]
Command 'AT+CCWA?' failed
-- Datacard datacard0 has disconnected
-- Datacard datacard2 initialized and ready
[Dec 4 16:55:07] ERROR[4501]: at_response.c:329 at_response_error: [datacard2]
Command 'AT+CCWA?' failed
And so on... no way to recover those 3 modems...
Original comment by pag...@gmail.com
on 4 Dec 2010 at 3:42
Original comment by bg_...@mail.ru
on 4 Dec 2010 at 4:02
upload r69, try, i now has't devices for test
Original comment by bg_...@mail.ru
on 4 Dec 2010 at 4:33
looks fixed!!!
thanks again....
Original comment by pag...@gmail.com
on 4 Dec 2010 at 4:40
Also in r70 errors in response of AT+CCWA= AT+CCWA? not cause disconnection
from device.
Original comment by bg_...@mail.ru
on 4 Dec 2010 at 4:44
just seen that after module unload chan_datacard.so and module load
chan_datacard.so... I have some
[Dec 4 17:58:42] ERROR[6181]: at_response.c:329 at_response_error: [datacard3]
Command 'AT+CCWA?' failed
but not causing disconnection from device...
Original comment by pag...@gmail.com
on 4 Dec 2010 at 4:47
check debug output for device responses, may be device really response ERROR on
AT+CCWA=1,2,1 or chan_datacard can't parse response
Original comment by bg_...@mail.ru
on 4 Dec 2010 at 5:10
also how has command
CLI> datacard callwaiting enable|disable device
instead of 'datacard ccwa'
Original comment by bg_...@mail.ru
on 4 Dec 2010 at 5:11
Heh, call waiting is service provided by network, may be some networks not
allow this completely?
Original comment by bg_...@mail.ru
on 4 Dec 2010 at 5:18
Umhhh, this feature seems to be a mess...
Look, 2 different hardware
A-> debian squeeze on x86
-------------------------
debian*CLI> datacard show devices
ID Group State RSSI Mode Submode Provider Name Model
Firmware IMEI IMSI Number
datacard1 0 Free 13 5 4 vodafone ES K3520
11.315.05.00.00 353284026345333 214060400091567 Unknown
datacard0 0 Free 16 0 0 vodafone ES K3520
11.315.05.00.00 353284026357577 214060400091561 +634000000
debian*CLI> datacard callwaiting enable datacard0
[datacard0] Call-Waiting commands queued for execute
debian*CLI> datacard callwaiting enable datacard1
[datacard1] Call-Waiting commands queued for execute
[Dec 4 18:16:45] ERROR[7039]: at_response.c:334 at_response_error: [datacard0]
Command 'AT+CCWA?' failed
[Dec 4 18:16:47] ERROR[7059]: at_response.c:334 at_response_error: [datacard1]
Command 'AT+CCWA?' failed
B-> debian squeeze on ARM sheevaplug
-------------------------------
see log
Not very important, but still a bit messy
Original comment by pag...@gmail.com
on 4 Dec 2010 at 5:27
Attachments:
Enable debug
core set debug 5
edit logger.conf for debug save to file.
and check commands and responses
looks like
[Dec 3 16:41:21] DEBUG[9904] at_queue.c: [datacard0] write command 'AT+CLIR'
expected response 'OK' length 10
[Dec 3 16:41:21] DEBUG[9904] at_queue.c: [datacard0] [AT+CLIR=2
]
[Dec 3 16:41:21] DEBUG[9841] at_read.c: [datacard0] receive 6 byte, used 6,
free 4090, read 0, write 6
[Dec 3 16:41:21] DEBUG[9841] at_read.c: [datacard0] [
OK
]
Original comment by bg_...@mail.ru
on 4 Dec 2010 at 5:40
attached new log... I removed some lines to clearly identify CCWA process...
Original comment by pag...@gmail.com
on 4 Dec 2010 at 5:51
Attachments:
logs looks good, if registration process done
and device said 'ERROR' i would hardly help that :)
AT+CCWA=1,1,1
OK
enable call waiting for voice
AT+CCWA=1,2,1
ERROR
can't check call waiting status for voice
but next i see AT+CCWA=1,1,1 and AT+CCWA=1,2,1 is ok response.
Its on same device?
Original comment by bg_...@mail.ru
on 4 Dec 2010 at 6:26
I think it could be a problem from network operator... I'm using Virtual Mobile
Operator and the behaviour is a bit random on two different locations...
by the moment, if nobody reports any additional error... I think this should be
closed.
thanks
Original comment by pag...@gmail.com
on 4 Dec 2010 at 6:35
ok, wait some time :)
Original comment by bg_...@mail.ru
on 4 Dec 2010 at 6:53
Original comment by pag...@gmail.com
on 7 Dec 2010 at 9:42
Original issue reported on code.google.com by
pag...@gmail.com
on 3 Dec 2010 at 11:43