Actually this *was* very common for me, until I upgraded to the version that did away with astdb. In the new version, the half-dozen proxy connects that I have done - using a couple of different proxy servers - all announced my call correctly - AND - I was able to get connected as fast as I could work the mouse. No more waiting 5 minutes. 73 Ken 27021 W4BRM/R
-----Original Message----- From: app_rpt-users-bounces@qrvc.com [mailto:app_rpt-users- bounces@qrvc.com] On Behalf Of "Jeremy R. Geeo [KDØEAV]" Sent: Tuesday, October 26, 2010 3:38 PM To: app_rpt-users@qrvc.com Subject: Re: [App_rpt-users] ID Question
2) Anyone had an issue with it saying the wrong callsigns on EchoLink? KB1PSB connected the other day, and it announced KT0EE. It has done this with a few different call signs, afaik all of them on mobile devices.
This is very common - and almost makes the announcements pointless -
vc.com/mailman/listinfo/app_rpt-users