how to change ISP specific modem,
Joel Dorfan
the modem was purchased.
Is there anything that can be done to the modem to make it work with other
ISP's??
Thanks
Mike Daniel
says...
I've never heard of an analog modem being locked to a provider. A modem
is a modem. Assuming you're using Win9x, go to my computer, dialup
networking, and create a connection to your new ISP. Then go to your
mail program and change the mail server settings.
Mike
Franc Zabkar
<bdo...@FRED.icon.co.za> put finger to keyboard and composed:
-- Franc Zabkar
Please remove one 'g' from my address when replying by email.
Franc Zabkar
<bdo...@FRED.icon.co.za> put finger to keyboard and composed:
>I have a Dynalink V1456VQE. I no longer have an acount with the ISP from who
Have you tried flashing your modem with international firmware?
http://www.askey.com/drivers/v90.htm
My Dynalink internal modem is not flashable as it has a PROM (part
number 27xxxx), not an EEPROM (p/n 29xxxx or 28xxxx).
Paul Holloway
I"ve never heard of a modem that was proprietary to a particular ISP.
If it's running any of the standard protocols (v.32, v.34, kflex, x2,
v.90) then it should have no problem connecting to any ISP.
"May you always have fair winds and following seas..."
Paul Holloway
Franc Zabkar
finger to keyboard and composed:
>On Tue, 10 Apr 2001 12:55:45 +0200, "Joel Dorfan"
><bdo...@FRED.icon.co.za> wrote:
>
>>I have a Dynalink V1456VQE. I no longer have an acount with the ISP from who
>>the modem was purchased.
>>
>>Is there anything that can be done to the modem to make it work with other
>>ISP's??
>I"ve never heard of a modem that was proprietary to a particular ISP.
>If it's running any of the standard protocols (v.32, v.34, kflex, x2,
>v.90) then it should have no problem connecting to any ISP.
JD is not the first person to ask this question. As strange as it may
be, it appears that this modem may be looking for a specific remote
server ID, or something of that nature. Prior posts suggest that the
ISP lock is not related to a specific phone number, nor to any
particular dialer S/W, or OS. For example, the same lock appears in
Linux. I wonder if ISP locks are an optional feature of ConfigurACE,
Conexant's OEM modem configurator program.
In troubleshooting this "problem", I would open a direct-to-COM
session in HyperTerminal, or a DOS based comms app, and dial in to the
ISP. Ensure that command echo (ATE1) and verbal report codes (ATV1)
are enabled. After hanging up, issue the AT#UD, AT&V2, and AT&V1
commands.
#UD = unimodem diagnostics
&V2 = Rockwell diagnostics (detailed)
&V1 = post-call statistics (brief)
To analyse this numeric data, use these utilities:
http://collage.etel.ru/fileechos/hardware/xhrdidc/ud-1014.zip
http://collage.etel.ru/fileechos/hardware/xhrdidc/s1-1018.zip
ed...@mweb.co.za
On 2001-04-12 franc...@dinggoblue.net.au said:
>On Wed, 11 Apr 2001 12:22:18 GMT, pau...@exis.net (Paul Holloway)
>put finger to keyboard and composed:
>>On Tue, 10 Apr 2001 12:55:45 +0200, "Joel Dorfan"
>><bdo...@FRED.icon.co.za> wrote:
>>>I have a Dynalink V1456VQE. I no longer have an acount with the
>>>ISP from who the modem was purchased.
>>>Is there anything that can be done to the modem to make it work
>>>with other ISP's??
>>I"ve never heard of a modem that was proprietary to a particular
>>ISP. If it's running any of the standard protocols (v.32, v.34,
>>kflex, x2, v.90) then it should have no problem connecting to any
>ISP.
>JD is not the first person to ask this question. As strange as it
>may be, it appears that this modem may be looking for a specific
>remote server ID, or something of that nature. Prior posts suggest
>that the ISP lock is not related to a specific phone number, nor to
>any particular dialer S/W, or OS. For example, the same lock
>appears in Linux. I wonder if ISP locks are an optional feature of
>ConfigurACE, Conexant's OEM modem configurator program.
For interest the major South African ISPs servicing dial-up users have
all adopted ISP-specific modems for marketing purposes, these being
offered together with a variable free access period at prices well below
the modems' local retail prices. Equivalent to US$10-30 as against
current retail cost of $70-80. In all cases these are external modems
OEM'd by Askey ( V1456VQE ) and a local manufacturer, Duxbury.
>In troubleshooting this "problem", I would open a direct-to-COM
>session in HyperTerminal, or a DOS based comms app, and dial in to
>the ISP. Ensure that command echo (ATE1) and verbal report codes
>(ATV1) are enabled. After hanging up, issue the AT#UD, AT&V2, and
>AT&V1 commands.
>#UD unimodem diagnostics
>&V2 rockwell diagnostics (detailed)
>&V1 post-call statistics (brief)
>To analyse this numeric data, use these utilities:
>http://collage.etel.ru/fileechos/hardware/xhrdidc/ud-1014.zip
>http://collage.etel.ru/fileechos/hardware/xhrdidc/s1-1018.zip
I append below the &V2 and #UD results using an ISP-specific modem
connecting to its home ISP and to one other ISP. Nothing immediately and
obviously hinting at the ISP lock mechanism is apparent. Normal protocol
recognition and negotiation leading to a full technical connect proceeds
in both cases, after which the connection is dropped on the non-linked
ISP. The termination reason is shown as " INACTIVITY TIMER " and "
Inactivity Timer Expired ".
Examination of the data transmitted from the ISP shows that the linked
ISP sends an ISP-specific text message immediately after the normal
" CONNECT xxxx " output whereas this is not received from the non-linked
ISP. The latter drops the connection +/- 2 secs after the " CONNECT " is
received. Although the termination reason is cited as expiration of
inactivity period this is seemingly independent of the S30 register
inactivity control which is set to 0 - Disabled.
The recognition signal is obviously sent after the protocol and of
necessity to allow full use by modems other the ISP-specific model has
to be neutral to them. Equally it has to be something which the
ISP-specific modem is set to expect failing which it disconnects. As
suggested it may be such as a server ID or could it be the specific text
message?
Don Black
*********
A.Connect to modem's specific ISP ( Cisco RAS )
--------------------------------
Rockwell Diagnostics/W32, version 1.0.1.8, compiled at Dec 26 2000 16:19:50
(c) 2000 Stanislav V. Mekhanoshin (ramp...@tu.spb.ru, 2:5030/172.9@fidonet)
----------------------------------------------------------------------------
Connection time : 00:02:59
TX Rate (Last/Init/Min/Max) : 28800/28800/28800/28800
RX Rate (Last/Init/Min/Max) : 45333/45333/45333/45333
Modulation/Protocol/Compression : V.90/LAP-M/V.42bis
TX Symbol rate : 3200
Signal Level (TX/Power Drop), -dB : 7/1
RX Signal Level (Last/Min/Max), -dB : 18/18/18
Band Edge Lower/Upper, Hz : 150/3825
Round trip delay, ms : 5.063
EQM Value (Last/Min/Max/Negative) : 30/26/40/0
EQM Samples Running Sum : 00D4
EQM Last 10 Readings : 30 28 29 31 31 29 31 31 31 29
SNR Ratio (Last/Min/Max), dB : 46/46/46
TX Non-linear Encoding : OFF
TX Precoding : OFF
TX/RX Constellation Shaping : OFF/OFF
TX Trellis Encoding : 16 state
TX Pre-emphasis : 2
TX/RX state (Max TX/RX, Last TX/RX) : 67H/67H, 67H/67H
Dual PCM/120 Hz detection : No/Yes
V.90 Digital Pad/A-law/HighPowerSrv : 0dB/No/No
Retrains (Issued/Granted/Fast) : 0/0/0
Renegs (Issued/Granted) : 0/0
Retrans per frame/Frames rejected : 1/0
Last Retrain/Reneg reason : Retrain/rate reneg successful
Disconnect reason : LOCAL REQUEST
Remote Manufacturer/Licensee Code : Conexant/Conexant
Remote Manufacturer's Product Caps : K56Flex, V.90
Remote V.8bis caps (type) : Digital (Server)
Remote V.8bis caps (K56Flex mode) : K56Flex prototype mode not supported
Remote V.8bis caps (K65Flex version): 1.1
Remote K65Flex RAM version supported: 70
Remote Coding used/forced by server : A-law/Yes
Remote controller version number : 0
Remote supports symbol rate (1,2,5) : 2743:ON 2800:ON 3429:ON 3429-TX:ON
Remote supports symbol rate (3,4) : 3000-L:ON 3000-H:ON 3200-L:ON 3200-H:ON
Remote power drop support : ON
Remote max symbol rate difference : 0 steps
Remote is a CME modem : No
Remote supports V.34bis : Yes
Remote frequency source : Internal
------
Unimodem Diagnostics/W32, version 1.0.1.4, compiled at Jan 28 2001 19:53:30
(c) 2000 Stanislav V. Mekhanoshin (ramp...@tu.spb.ru, 2:5030/172.9@fidonet)
----------------------------------------------------------------------------
Diag Command Specification rev.: 1.0
Call Setup Result code : Data Answering signal detected
Multi-media mode : Data Only
DTE-DCE interface mode : Async data
TX/RX signal power level, -dBm : 15/18
Estimated noise level, -dBm : 27
TX/RX Negotiation : V.90 Issue 1 (asymmetric)/V.90 Issue 1 (asymme
TX/RX Symbol Rate : 3200/8000
TX/RX Carrier frequency, Hz : 1920/0
TX data rate (Last/Init) : 28800/28800
RX data rate (Last/Init) : 45333/45333
Temporary carrier loss count : 0
Carrier Rate Re-neg count : 0
Retrains Requested/Granted : 0/0
Protocol/Compression : V.42 LAPM/V.42bis
Error control frame size, bytes: 128
Error control timeouts in TX : 0
Error control NAKs received : 0
TX/RX flow control : V.24 ckt 106/133 / V.24 ckt 106/133
TX/RX chars sent : 5/262
TX/RX chars lost (data overrun): 0/0
TX/RX I-Frame count : 3/7
TX/RX I-Frame error count : 0/0
Termination Cause : Call is still in progress
B. Connect to non-linked ISP (Lucent Portmaster PM3 RAS)
----------------------------
Rockwell Diagnostics/W32, version 1.0.1.8, compiled at Dec 26 2000 16:19:50
(c) 2000 Stanislav V. Mekhanoshin (ramp...@tu.spb.ru, 2:5030/172.9@fidonet)
----------------------------------------------------------------------------
Connection time : 00:00:03
TX Rate (Last/Init/Min/Max) : 31200/31200/31200/31200
RX Rate (Last/Init/Min/Max) : 45333/45333/45333/45333
Modulation/Protocol/Compression : V.90/LAP-M/V.42bis
TX Symbol rate : 3200
Signal Level (TX/Power Drop), -dB : 7/0
RX Signal Level (Last/Min/Max), -dB : 15/15/15
Band Edge Lower/Upper, Hz : 150/3825
Round trip delay, ms : 17.875
EQM Value (Last/Min/Max/Negative) : 0/NA/0/0
EQM Samples Running Sum : 00D4
EQM Last 10 Readings : NA
SNR Ratio (Last/Min/Max), dB : 41/41/41
TX Non-linear Encoding : OFF
TX Precoding : OFF
TX/RX Constellation Shaping : ON/OFF
TX Trellis Encoding : 16 state
TX Pre-emphasis : 10
TX/RX state (Max TX/RX, Last TX/RX) : 67H/67H, 67H/67H
Dual PCM/120 Hz detection : No/Yes
V.90 Digital Pad/A-law/HighPowerSrv : 0dB/Yes/No
Retrains (Issued/Granted/Fast) : 0/0/0
Renegs (Issued/Granted) : 0/0
Retrans per frame/Frames rejected : 1/0
Last Retrain/Reneg reason : None
Disconnect reason : INACTIVITY TIMER
Remote supports symbol rate (1,2,5) : 2743:ON 2800:ON 3429:ON 3429-TX:OFF
Remote supports symbol rate (3,4) : 3000-L:OFF 3000-H:OFF 3200-L:ON 3200-H:ON
Remote power drop support : ON
Remote max symbol rate difference : 0 steps
Remote is a CME modem : No
Remote supports V.34bis : Yes
Remote frequency source : Internal
-----
Unimodem Diagnostics/W32, version 1.0.1.4, compiled at Jan 28 2001 19:53:30
(c) 2000 Stanislav V. Mekhanoshin (ramp...@tu.spb.ru, 2:5030/172.9@fidonet)
----------------------------------------------------------------------------
Diag Command Specification rev.: 1.0
Call Setup Result code : Data Answering signal detected
Multi-media mode : Data Only
DTE-DCE interface mode : Async data
TX/RX signal power level, -dBm : 7/15
Estimated noise level, -dBm : 24
TX/RX Negotiation : V.90 Issue 1 (asymmetric)/V.90 Issue 1
(asymmetric)
TX/RX Symbol Rate : 3200/8000
TX/RX Carrier frequency, Hz : 1920/0
TX data rate (Last/Init) : 31200/31200
RX data rate (Last/Init) : 45333/45333
Temporary carrier loss count : 0
Carrier Rate Re-neg count : 0
Retrains Requested/Granted : 0/0
Protocol/Compression : V.42 LAPM/V.42bis
Error control frame size, bytes: 128
Error control timeouts in TX : 0
Error control NAKs received : 0
TX/RX flow control : V.24 ckt 106/133 / V.24 ckt 106/133
TX/RX chars sent : 0/0
TX/RX chars lost (data overrun): 0/0
TX/RX I-Frame count : 0/0
TX/RX -Frame error count : 0/0
Termination Cause : Inactivity Timer Expired
Net-Tamer V 1.12.0
Bob Starnes
What's the 120 Hz detection for?
Franc Zabkar
and composed:
>For interest the major South African ISPs servicing dial-up users have
>all adopted ISP-specific modems for marketing purposes, these being
>offered together with a variable free access period at prices well below
>the modems' local retail prices. Equivalent to US$10-30 as against
>current retail cost of $70-80. In all cases these are external modems
>OEM'd by Askey ( V1456VQE ) and a local manufacturer, Duxbury.
<snip>
>I append below the &V2 and #UD results using an ISP-specific modem
>connecting to its home ISP and to one other ISP. Nothing immediately and
>obviously hinting at the ISP lock mechanism is apparent. Normal protocol
>recognition and negotiation leading to a full technical connect proceeds
>in both cases, after which the connection is dropped on the non-linked
>ISP. The termination reason is shown as " INACTIVITY TIMER " and "
>Inactivity Timer Expired ".
>
>Examination of the data transmitted from the ISP shows that the linked
>ISP sends an ISP-specific text message immediately after the normal
>" CONNECT xxxx " output whereas this is not received from the non-linked
>ISP. The latter drops the connection +/- 2 secs after the " CONNECT " is
>received. Although the termination reason is cited as expiration of
>inactivity period this is seemingly independent of the S30 register
>inactivity control which is set to 0 - Disabled.
>
>The recognition signal is obviously sent after the protocol and of
>necessity to allow full use by modems other the ISP-specific model has
>to be neutral to them. Equally it has to be something which the
>ISP-specific modem is set to expect failing which it disconnects. As
>suggested it may be such as a server ID or could it be the specific text
>message?
>
>Don Black
>*********
<snip>
I don't have a solution but I would start by trying to understand the
"problem" a little better. Here are some suggestions:
(1) Set up a direct cable connection between your problem modem and a
standard one. Use HyperTerminal to send the required ISP-specific text
string after connect, presumably as a text file.
(2) To get a feeling for the origin of the ISP message, disable result
codes (ATQ1), or attempt to switch to their numeric form (ATV0).
(3) What messages, if any, do you see when connecting with an unlocked
modem?
(4) A Microsoft spec indicates that the AT#UD command supports up to
128 "manufacturer proprietary keys" numbered from 80h to FFh. For
example, a prior post from a USR owner shows that key #FF identifies
the manufacturer:
DIAG <2A4D3263 FF="3COM-USROBOTICS">
Whether this refers to the client or the server modem is unclear.
I suggest you view the raw AT#UD listing, and take note of keys 80-FF,
if any. It's possible that Stas M's software may not decode all the
proprietary keys. It's also possible that the modem may detect
ISP-specific keys, but not display them. Try connecting to the locked
ISP using a modem that supports AT#UD, eg a USR. Do you see any
mysterious proprietary keys?
(5) Dump the contents of the firmware using a device programmer. Look
for the ISP string. Replace the firmware with that from an unlocked
modem. Check the part number of your PROM/EEPROM - 28xxxx or 29xxxx
devices are flashable, while 27xxxx are not.
ed...@mweb.co.za
On 2001-04-19 don't...@reply.com said:
<snipped>
>> Rockwell Diagnostics/W32, version 1.0.1.8, compiled at Dec 26
>>2000 16:19:50 (c) 2000 Stanislav V. Mekhanoshin (ramp...@tu.spb.
>>ru, 2:5030/172.9@fidonet)
>>-------------------------------------------------------------------
>>--------- Connection time : 00:00:03 TX Rate
>> Dual PCM/120 Hz detection : No/Yes
>What's the 120 Hz detection for?
Sorry .. I haven't a clue on this. In truth I was hoping somebody else
could explain.
Don Black
Net-Tamer V 1.12.0 - Test Drive