Garbled responses from the VARA modem.

I mentioned in previous postings elsewhere, some of us are receiving strange reply messages from the VARA modem. An example that I posted earlier:
I'm running BPQ v. 6.0.17.1 with VARA v.2.2.1 and I notice in the BPQ
VARA Modem monitor and in the bpq bbs log, the following entry:

?

181124 11:43:35 |N9LYA???? Connecting to BBS N9LYA
181124 11:43:35 <N9LYA???? *** CONNECTED
181124 11:43:35 >N9LYA???? ATTACH 9
181124 11:43:36 <N9LYA???? HLSBHF:W7EES-1} Ok
181124 11:43:36 >N9LYA???? MAXCONREQ=10
181124 11:43:36 <N9LYA???? VARA} OK
181124 11:43:36 >N9LYA???? RADIO 7.101 USB 1 D
181124 11:43:37 <N9LYA???? Frequency and Mode Set OK
181124 11:43:37 ?N9LYA???? Script PAUSE 3
181124 11:43:40 <N9LYA???? Pause Ok
181124 11:43:40 >N9LYA???? C N9LYA
181124 11:44:47 <N9LYA???? VARA} Failure with W7EES N9LY
181124 11:44:47 |N9LYA???? N9LYA Disconnected

?

Note the entry at 11:44:47 - VARA} Failure with W7EES N9LY

?

The connect request initiated with C N9LYA in the BBS connect script and
as shown in the log does not include W7EES, yet it appears in the VARA}
response. Is this being sent by the VARA modem to the sound card that
way? It may explain why I'm not connecting to N9LYA. (More likely,
propagation, but it's odd.) Exchanges with other stations do not include
W7EES in the string.

?

181124 12:32:42 |K7GJT???? Connecting to BBS K7GJT
181124 12:32:42 <K7GJT???? *** CONNECTED
181124 12:32:42 >K7GJT???? ATTACH 9
181124 12:32:43 <K7GJT???? HLSBHF:W7EES-1} Ok
181124 12:32:43 >K7GJT???? MAXCONREQ=10
181124 12:32:43 <K7GJT???? VARA} OK
181124 12:32:43 >K7GJT???? RADIO 3.592 USB 1 D
181124 12:32:44 <K7GJT???? Frequency and Mode Set OK
181124 12:32:44 ?K7GJT???? Script PAUSE 3
181124 12:32:47 <K7GJT???? Pause Ok
181124 12:32:47 >K7GJT???? C K7GJT
181124 12:33:52 <K7GJT???? VARA} Failure with K7GJT
181124 12:33:52 |K7GJT???? K7GJT Disconnected

?

I have searched high and low for erroneous entries with no success.
Where else might this be coming from ?

To update this - I had previously thought this was caused by overrunning the text comment field limit in bpq32.cfg, VARA port setup. It turns out that it is not. I see, today, after calling N9LYA and receiving a Failed to connect message:

181125 17:41:53 |N9LYA     Connecting to BBS N9LYA

181125 17:41:53 <N9LYA     *** CONNECTED 

181125 17:41:53 >N9LYA     ATTACH 9

181125 17:41:53 <N9LYA     HLSBHF:W7EES-1} Ok

181125 17:41:53 >N9LYA     MAXCONREQ=10

181125 17:41:54 <N9LYA     VARA} OK

181125 17:41:54 >N9LYA     RADIO 7.101 USB 1 D

181125 17:41:55 <N9LYA     Frequency and Mode Set OK

181125 17:41:55 ?N9LYA     Script PAUSE 3

181125 17:41:58 <N9LYA     Pause Ok

181125 17:41:58 >N9LYA     C N9LYA

181125 17:43:07 <N9LYA     VARA} Failure with W7EES N9LYN-

181125 17:43:07 |N9LYA     N9LYA Disconnected

Note in the second from the last line above, VARA is reporting Failure with W7EES N9LYN-

So, it would appear that the source of this entry remains a mystery.

- Dave - W7EES
Join [email protected] to automatically receive all group messages.
开云体育

Garbled responses from the VARA modem.
