![]() |
> Feb 15 00:31:17.11: [ 650]: REMOTE NSF "=1B+FCI:" 744 7753"=14+= > FIS:1," > Feb 15 00:31:17.11: [ 650]: --> [37:,0,2,0,0,0,4=FF=FF=80=EF=FF=FF=10=FF= > =FF=FF =FF=FF=FF=FF=FF=FF=FF=FF =FF=80=FF=FF=80] This does look like the USR bug. I believe there is more than one set of broken firmware and some versions can only be cured by operating exclusively in Class 1. I wonder if USR dumped the remaining chips with this version of the problem onto the generic modem manufacturers. (The USR ones I've seen recently have rather more legitimate characters mixed in with the bogus ones, so it doesn't look like the recent USR reports, but it certainly is in the right place for the USR problem.) We'd need a log with the modified initialisation string being issued to be sure that you had entered this correctly.