Ticket Options
Question Details
TICKET ARCHIVE -> modem protocol: v.90 or v92?
pinax - May 24, 2006 - 6:55 pm
I live in a rural area and unfortunately dial-up service is the only way to access the Internet. The line is noisy: my connection maxes out at 28.8k and usually negotiates a 26.4k connection.
Fortunately my iBook's modem can use the v.92 protocol, which lets me enable modem-on-hold, so I can connect with my ISP and not worry about missing phone calls without having to set up a separate phone line dedicated to data connections.
My problem is this: I've done some testing (by asking friends to call me) and have discovered that the modem-on-hold feature sometimes isn't working. It often does work (no reason to think there's a hardware issue), it's enabled in the Network pref pane, and I have verified with my ISP that that my dial-up numbers go to v.92-enabled modems. So I can only conclude that what's happening is that the line is sometimes noisy enough during the modem handshake negotiation that the modem I'm calling in to downgrades the connection and switches to the v.90 protocol, which doesn't support modem-on-hold and makes me miss phone calls. My ISP people say this is entirely possible.
It's impossible to predict when it will use v.90 and when it will use v.92. So what I want to know is if there's some way--using System Profiler or something else--to find out which protocol is being used during any given modem session. That way I can dial-up and first verify whether the connection is using v.92. If not, I can just hang up and dial in again until I see that v.92 is being used and can rest assured that I won't miss phone calls.
My ISP support people know how to do this with PCs, but couldn't answer how to do this on Macs. I would appreciate any help you might provide. Many thanks!
Fortunately my iBook's modem can use the v.92 protocol, which lets me enable modem-on-hold, so I can connect with my ISP and not worry about missing phone calls without having to set up a separate phone line dedicated to data connections.
My problem is this: I've done some testing (by asking friends to call me) and have discovered that the modem-on-hold feature sometimes isn't working. It often does work (no reason to think there's a hardware issue), it's enabled in the Network pref pane, and I have verified with my ISP that that my dial-up numbers go to v.92-enabled modems. So I can only conclude that what's happening is that the line is sometimes noisy enough during the modem handshake negotiation that the modem I'm calling in to downgrades the connection and switches to the v.90 protocol, which doesn't support modem-on-hold and makes me miss phone calls. My ISP people say this is entirely possible.
It's impossible to predict when it will use v.90 and when it will use v.92. So what I want to know is if there's some way--using System Profiler or something else--to find out which protocol is being used during any given modem session. That way I can dial-up and first verify whether the connection is using v.92. If not, I can just hang up and dial in again until I see that v.92 is being used and can rest assured that I won't miss phone calls.
My ISP support people know how to do this with PCs, but couldn't answer how to do this on Macs. I would appreciate any help you might provide. Many thanks!
DeltaMac - May 24, 2006 - 9:54 pm
If you live in a rural area, with poor lines, it's unlikely that you will reliably connect at either v.92, or even v.90
If your connection is never above 28.8, then you aren't getting a v.90 (or v.92) connection, ever. You modem auto-negotiates to v.34 in that slow speed.
I think it's just wishful thinking to expect modem-on-hold to work in your situation, other than very intermittently.
Most people that I try to help in a similar situation end up choosing to lock the modem into v.34.
Your modem will often connect more reliably, but will be limited to 28.8, which is about what you get now. Of course, modem-on-hold will continue to elude you.
If your connection is never above 28.8, then you aren't getting a v.90 (or v.92) connection, ever. You modem auto-negotiates to v.34 in that slow speed.
I think it's just wishful thinking to expect modem-on-hold to work in your situation, other than very intermittently.
Most people that I try to help in a similar situation end up choosing to lock the modem into v.34.
Your modem will often connect more reliably, but will be limited to 28.8, which is about what you get now. Of course, modem-on-hold will continue to elude you.
pinax - May 24, 2006 - 10:13 pm
Well, all I can say is that I've had an account with Toast.net, which I picked mainly because they had a large number of local dial-up numbers, several of which used v.92. I've had them for at least a year, probably more, and the modem-on-hold has worked pretty well. Obviously, it's impossible to tell when it's *not* working, unless someone who's trying to call me complains that I never pick up the phone… But it worked on a regular basis, regular enough for me to think of it as reliable. I'd say connections were negotiated at 28.8k about 10% of the time, with 26.4k the rest. It *never* got over 28.8 for local calls. Yet, as far as I can tell, modem-on-hold worked more often than not.
I switched ISPs because the new one bundles the Propel accelerator with basic service at a rate cheaper that what Propel charges for an independent account. The propel accelerator has a *way* better Mac interface (a really nice one, in fact) than Toast.net's (which I think was "Slipstream" or something--a crappy Windows port, at any rate).
Except now it seems that even though the modem is connecting at the same speeds as with the old service, MOH isn't really working.
So let me try to get something straight: does MOH work *only* with a v.92 connection, or does it *sometimes* work with v.34 or v.90, even if rarely?
And is there some kind of inspector, either built-in to the OS (via System Profiler or even a Terminal command) or 3rd-party that will provide some sort of diagnostic on an active connection, telling me what the protocol, rate, etc. are?
Thanks again!
I switched ISPs because the new one bundles the Propel accelerator with basic service at a rate cheaper that what Propel charges for an independent account. The propel accelerator has a *way* better Mac interface (a really nice one, in fact) than Toast.net's (which I think was "Slipstream" or something--a crappy Windows port, at any rate).
Except now it seems that even though the modem is connecting at the same speeds as with the old service, MOH isn't really working.
So let me try to get something straight: does MOH work *only* with a v.92 connection, or does it *sometimes* work with v.34 or v.90, even if rarely?
And is there some kind of inspector, either built-in to the OS (via System Profiler or even a Terminal command) or 3rd-party that will provide some sort of diagnostic on an active connection, telling me what the protocol, rate, etc. are?
Thanks again!
DeltaMac - May 24, 2006 - 11:19 pm
MOH is part of the v.92 protocol. AFAIK, it's not available if you do not make a v.92 connection.
My opinion (FWIW) - your poor connection of 28.8 or less, may mean that the Propel Accelerator may be working against other features (such as MOH) while trying to do the best it can.
Do you ever get any improvement by simplifying your modem connection?
Such as - connecting modem directly to your network (phone) interface with a new phone line, and nothing else connected in your house (just as a test for the best possible connection at you location) OR, have you ever called a complaint to your local phone company about noise on your line? They can test and repair, if possible - or tell you (again!) that your location is far in the future for upgrades (as one of my customers was told recently, also several miles out of town)
I wish you luck
- Dale
My opinion (FWIW) - your poor connection of 28.8 or less, may mean that the Propel Accelerator may be working against other features (such as MOH) while trying to do the best it can.
Do you ever get any improvement by simplifying your modem connection?
Such as - connecting modem directly to your network (phone) interface with a new phone line, and nothing else connected in your house (just as a test for the best possible connection at you location) OR, have you ever called a complaint to your local phone company about noise on your line? They can test and repair, if possible - or tell you (again!) that your location is far in the future for upgrades (as one of my customers was told recently, also several miles out of town)
I wish you luck
- Dale
IF THIS IS YOUR QUESTION AND YOU WISH TO RESPOND, LOGIN HERE FIRST.
