I entered
at@n0=1
at*1@n0=1
at*2@no=1
This turned on the caller ID logging for all ports. I then issued a
at&w0 to save the config in NVM.
When the TA gets powered down only the at@no=1 gets saved. The logging
options for the two
voice ports are reset to 0. I called motorola, they had no idea...
Anybody got any ideas?
: I entered
: at@n0=1
: at*1@n0=1
: at*2@no=1
: This turned on the caller ID logging for all ports. I then issued a
: at&w0 to save the config in NVM.
You need to do a at*&W0 and an at*2&W0 to save the config for each POTS
port also. It's nice to have this so if you get a call waiting or something
you can just bring up your favorite terminal prog and to an AT*@L2 to see
the number even if it was repeated over the POTS port to your CID boxes.
Good Luck,
Matthew Roth
mdr"at"count.com
To reply via e-mail please remove "NO|SPAM" from the To: line header.
It is unfortuante that people have to do this but after being hit by numerous
spam mailings every day it has become necessary. Sorry for any inconvience.
> Terry Fischer (tfis...@bellsouth.net) wrote:
> : I have a Bitsurfer Pro external. I am tring to get the caller ID
> : parameters set and saved.
>
> : I entered
> : at@n0=1
> : at*1@n0=1
> : at*2@no=1
>
> : This turned on the caller ID logging for all ports. I then issued a
> : at&w0 to save the config in NVM.
> You need to do a at*&W0 and an at*2&W0 to save the config for each POTS
> port also.
This brings up an interesting point. I've gone over the Moto Bitsurfr Pro
manual at some length, and have yet to find the place where it tells you
exactly what parameters are saved by exactly what command. It talks about
'global parameters', for example, but then never defines what they are.
One of the worst manuals in 35+ year computing career, IMHO.
>I have a Bitsurfer Pro external. I am tring to get the caller ID
>parameters set and saved.
>I entered
>at@n0=1
>at*1@n0=1
>at*2@no=1
>This turned on the caller ID logging for all ports. I then issued a
>at&w0 to save the config in NVM.
>When the TA gets powered down only the at@no=1 gets saved. The logging
>options for the two
>voice ports are reset to 0. I called motorola, they had no idea...
>Anybody got any ideas?
What ideas are you looking for? That's the way it is.
I have a little keyboard macro that resets the BSPro should it be turned off
(a rare event). Or you could write a boot program to do the same thing each
time you start the computer.
Neither one is a big deal.
=================
/Bob Thompson/
thom...@mcs.com
=================
I just bought the Moto Bitsurfer Pro EZ yesterday....
...and it came new out of a shrink wrapped box w/o a manual...
All I got was a cheezy cd-rom with documentations on the cdrom. What a
joke. You pay $300.00 a piece of hardware and it doesnt even come with a
pre-printed manual. Motorola, what were you thinking?
Everyone including Motorola knows that their products are not 100%
configured for optimal performance out of the box. So, after you get
tired of tring to find what you are looking for in a file of a cdrom,
you are forced to print this huge manual on your printer.
Hope you have a printer, and about 2 hours to to waste.
Needless to say, the Motorola Bitsurfer Pro will be going back to store,
due the fact that a $80 Philips EZ ISDN Pro out performs the Moto by at
least 10-20%.
For anyone thinking about getting ISDN, go with an Internal TA.
You will be much happier.
Jason.
http://www.netnutz.com
I should not need a boot program...
Bob Thompson wrote:
> In article <33E3A505...@bellsouth.net> Terry Fischer
> <tfis...@bellsouth.net> writes:
>
> >I have a Bitsurfer Pro external. I am tring to get the caller ID
> >parameters set and saved.
>
> >I entered
> >at@n0=1
> >at*1@n0=1
> >at*2@no=1
>
> >This turned on the caller ID logging for all ports. I then issued a
>
> >at&w0 to save the config in NVM.
Hello:
I had the same problem back in February. I am using the latest revision
K. I called Motorola and spent several hours on the phone with their
high level techs who were able to duplicate the same problem on their
end. They assured me there would be a fix within a month or so.
By April I called them and they told me the new release with these bug
fixes would be out by May 1. They said the new revision would have many
great new features as well.
Here we are in August, 7 months later and they have still not released a
fix to this problem. I am really disgusted with Motorola over this
matter and have not even bothered to call them since.
I hope this helps
Larry