| Author |
Message |
Franc Zabkar
Guest
|
 Posted:
Mon Sep 12, 2005 8:20 am Post subject:
Re: Zoom 3025c AT+VLS Problem when answering voice |
|
|
On 11 Sep 2005 11:58:31 -0700, "DaveJ" <dj.google@jayedee.com> put
finger to keyboard and composed:
| Quote: | Hi Matthias,
As you suggested, I then used hyperterminal to try out the command
sequence on voice answer as defined in the INF file:
at+fclass=8
at+vtd=10
at+vsm=130,8000,0,0
at+vit=0
at+vls=1
I opened hyperterminal, and created a new connection using the zoom
modem.
After entering all the above commands (up until at+vit), all returned
'OK' as expected.
Then after entering at+vls=1, the line was connected and 'OK' was
returned. This was the point that I normally discovered that 'ERROR'
was being returned.
|
Maybe the secret is in the caller ID data??? Can you get the modem to
behave if you turn off caller ID, at least for troubleshooting
purposes? If so, then perhaps you could edit the registry to add
"at+vcid=0" to the start of the "voice answer" command string at this
registry key (or whatever is appropriate for your OS):
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Modem\0000\VoiceAnswer
Or maybe you could force the modem to go off-hook (and stop the
ringing) before it starts processing the voice commands. Try adding
ATH1 as the first command in the string.
I would edit the registry by first Exporting the VoiceAnswer branch to
a file, say VoiceAnswer.reg, rename the branch to, say, VoiceAnswe_,
edit the reg file with Notepad, and then Import the edited file back
into the registry. Collapse and expand the Modem branch to refresh it,
and there you have it. You can restore the original branch by renaming
it, and you can now more easily edit the new branch in situ in the
registry.
-- Franc Zabkar
Please remove one 'i' from my address when replying by email. |
|
| Back to top |
|
 |
Franc Zabkar
Guest
|
| Posted:
Mon Sep 12, 2005 8:20 am Post subject:
Re: Zoom 3025c AT+VLS Problem when answering voice |
|
|
On 11 Sep 2005 11:58:31 -0700, "DaveJ" <dj.google@jayedee.com> put
finger to keyboard and composed:
| Quote: | Hi Matthias,
As you suggested, I then used hyperterminal to try out the command
sequence on voice answer as defined in the INF file:
at+fclass=8
at+vtd=10
at+vsm=130,8000,0,0
at+vit=0
at+vls=1
I opened hyperterminal, and created a new connection using the zoom
modem.
After entering all the above commands (up until at+vit), all returned
'OK' as expected.
Then after entering at+vls=1, the line was connected and 'OK' was
returned. This was the point that I normally discovered that 'ERROR'
was being returned.
|
The only difference that I can see is that this time the line is not
ringing. Your second modemlog shows three RINGs about 3 secs apart. Is
that what you hear, or do you hear more than three?
This may be another furphy, but I noticed that the RINGs in your first
"faulty" log were about 3.8 secs apart. In the second they were only
2.95 secs apart. Both logs ERRORed approximately two "ring cycles"
after the last logged RING.
-- Franc Zabkar
Please remove one 'i' from my address when replying by email. |
|
| Back to top |
|
|
DaveJ
Guest
|
| Posted:
Wed Sep 21, 2005 3:41 pm Post subject:
Re: Zoom 3025c AT+VLS Problem when answering voice |
|
|
Hi Franc,
Sorry I haven't been back to the group lately, I've been on holiday.
I have been following directions from Matthias and have discovered
exactly what you have suspected.
I found that when AT+VCID=1 is issued (EnableCallerID), this causes
problems when a voice call is answered and AT+VLS=1 is issued (last
command for VoiceAnswer).
I simply altered the INF file to:
1) change the EnableCallerID to NOT enable caller id (AT instead of
AT+VCID=1; I probably could remove this entry altogether and will
attempt this at some point)
HKR, EnableCallerID,1,,"at<cr>" <<< Changed - NOOP
2) add caller id enable to the init section- this is called when the
device needs to be initialised (before first call and after all calls).
This means that the call id information will be correctly received and
interogated by the modem and driver:
HKR, Init, 1,, "AT<cr>"
HKR, Init, 2,, "AT&FE0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;W0<cr>"
HKR, Init, 3,, "at+vcid=1<cr>" <<< Added
3) add caller id DISABLE to the start of the VoiceAnswer section
(and renumbered the existing entries). By this point the caller id
information will have been captured (in UK at least where it is sent
before the first ring), so we can safely switch caller id off for the
rest of the call:
HKR, VoiceAnswer, 1,, "at+vcid=0<cr>" <<< Added
HKR, VoiceAnswer, 2,, "at+fclass=8<cr>"
HKR, VoiceAnswer, 3,, "at+vtd=10<cr>"
HKR, VoiceAnswer, 4,, "at+vsm=130,8000,0,0<cr>"
HKR, VoiceAnswer, 5,, "at+vit=0<cr>"
HKR, VoiceAnswer, 6,, "at+vls=1<cr>"
So - it looks like the problem was indeed related to caller id after
all.
Many Thanks,
Dave J |
|
| Back to top |
|
|
DaveJ
Guest
|
| Posted:
Wed Sep 21, 2005 3:43 pm Post subject:
Re: Zoom 3025c AT+VLS Problem when answering voice |
|
|
Hi Matthias,
Many thanks for your help. As you can see below I discovered the
problem.
Serial monitor was a great help.
Regards,
Dave J |
|
| Back to top |
|
|
Matthias Moetje
Guest
|
| Posted:
Wed Sep 21, 2005 4:20 pm Post subject:
Re: Zoom 3025c AT+VLS Problem when answering voice |
|
|
Dave,
glad to hear you solved the problem. Thanks for your feedback!
Best regards,
Matthias Moetje
-------------------------------------
TERASENS GmbH
Ackermannstraße 3
80797 München
-------------------------------------
Fon: +49 89 143370-0
Fax: +49 89 143370-22
e-mail: moetje at terasens dot de
www: www.terasens.de
-------------------------------------
"DaveJ" <dj.google@jayedee.com> wrote in message
news:1127299407.556308.176740@g47g2000cwa.googlegroups.com...
| Quote: | Hi Matthias,
Many thanks for your help. As you can see below I discovered the
problem.
Serial monitor was a great help.
Regards,
Dave J
|
|
|
| Back to top |
|
|
Franc Zabkar
Guest
|
| Posted:
Thu Sep 22, 2005 2:21 am Post subject:
Re: Zoom 3025c AT+VLS Problem when answering voice |
|
|
On 21 Sep 2005 03:41:20 -0700, "DaveJ" <dj.google@jayedee.com> put
finger to keyboard and composed:
| Quote: | I found that when AT+VCID=1 is issued (EnableCallerID), this causes
problems when a voice call is answered and AT+VLS=1 is issued (last
command for VoiceAnswer).
I simply altered the INF file to:
1) change the EnableCallerID to NOT enable caller id (AT instead of
AT+VCID=1; I probably could remove this entry altogether and will
attempt this at some point)
HKR, EnableCallerID,1,,"at<cr>" <<< Changed - NOOP
2) add caller id enable to the init section- this is called when the
device needs to be initialised (before first call and after all calls).
This means that the call id information will be correctly received and
interogated by the modem and driver:
HKR, Init, 1,, "AT<cr>"
HKR, Init, 2,, "AT&FE0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;W0<cr>"
HKR, Init, 3,, "at+vcid=1<cr>" <<< Added
3) add caller id DISABLE to the start of the VoiceAnswer section
(and renumbered the existing entries). By this point the caller id
information will have been captured (in UK at least where it is sent
before the first ring), so we can safely switch caller id off for the
rest of the call:
HKR, VoiceAnswer, 1,, "at+vcid=0<cr>" <<< Added
HKR, VoiceAnswer, 2,, "at+fclass=8<cr>"
HKR, VoiceAnswer, 3,, "at+vtd=10<cr>"
HKR, VoiceAnswer, 4,, "at+vsm=130,8000,0,0<cr>"
HKR, VoiceAnswer, 5,, "at+vit=0<cr>"
HKR, VoiceAnswer, 6,, "at+vls=1<cr>"
So - it looks like the problem was indeed related to caller id after
all.
Many Thanks,
Dave J
|
I've no experience in this area, but I'd be a little wary of setting
at+vit=0. What would happen if the PC crashed before it could
terminate the call? Would the modem remain off-hook? Would a non-zero
value for the voice inactivity timer guarantee that the modem would
hang up in the absence of voice data?
Anyway, congratulations on an excellent hack. What alerted me to the
possibility of a caller ID issue was the timing between the last RING
and the ERROR. The fact that the delay amounted to approximately two
RING cycles suggested to me that the modem may still have been
monitoring the ringing signal for caller ID data. These data must
arrive at the modem's DSP via a path that is different to the normal
voice/fax/data path, ie not via the hook relay. Perhaps the +vls=1
command is telling the modem to divert its attention to the hook-relay
data path, but the modem is preoccupied with the caller ID data path
???
-- Franc Zabkar
Please remove one 'i' from my address when replying by email. |
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in