I just copied it over the old .exe file. I don't think it actually "installs" since only the .exe file was included in the zip file.
--
73's de KA5GIL
--
- gil -
Musings and Meanderings at http://captjustice.com
Tweeting at http://twitter.com/captainjustice -- only occasionally because I don't understand what that's all about!  :-)

Lynn,

Should the existing original version of APRSIS/32 be completely
un-installed first before installing the new windows version ?

Regards,
Jerome
WD4CWG

m6xsd wrote:

It's great toget the NMEA support, I am running it on my Desktop with a Haicom GPS connected to COM2 with an external antenna (just looking out of our front window).
It shows my location fine (although it seems to think I'm on the opposite side of the street most of the time, probably due to the GPS antenna location) on it's own map but asyet it doesn't seem to be reporting my location tothe outside world. I have only quickly set it up, so have I missed a setting I should have set?
I am currently using 'M6XSD-1' some if anyone sees me today I would like a report of when & where.

If you could e-mail your APRSIS32.XML file to ldeffenb@arrl.net I'll take a look at it and see if anything jumps out. I think you only need to have Enables/Tracking Enabled along with a good GPS Fix. Also, the Min and Max Times under the Genius configuration button might make a difference, but you should have at least gotten a packet when the fix was first acquired. What does the line under "APRS OK" say?

http://aprs.fi/?c=raw&;call=M6XSD-1 shows telemetry coming through which indicates that the APRS-IS password is not an issue.

If I get time today I will see if I can emulate a KISS TNC on my Laptop & see if I can get RF to work. I will use a different SSID for RF, so again if anyone sees me 'M6XSD-#' with any SSID I would like to know.

APRSIS32 only supports one callsign per instance. I haven't yet sorted through the callsign uniqueness requirements across the various ports. To run a different call on the RF, you'll need to put a copy of APRSIS32 in a different default directory which will then prompt for new configuration information. Multiple instances can share an OSM directory, but you might have to man-handle the configuration to avoid a second OSMTiles directory tree within your original OSMTiles directory. I don't remember if I fixed that for multiple instances yet or not.

When you say "emulate a KISS TNC", can I inquire as to what you'll actually be running? There's so many options out there, I'm certain I haven't heard of them all yet!

I will let you know how I get on.

I'm looking forward to your status! Especially on the RF front!

Lynn (D) - KJ4ERJ

Hi Lynn,

It's great toget the NMEA support, I am running it on my Desktop with a Haicom GPS connected to COM2 with an external antenna (just looking out of our front window).
It shows my location fine (although it seems to think I'm on the opposite side of the street most of the time, probably due to the GPS antenna location) on it's own map but asyet it doesn't seem to be reporting my location tothe outside world. I have only quickly set it up, so have I missed a setting I should have set?
I am currently using 'M6XSD-1' some if anyone sees me today I would like a report of when & where.
If I get time today I will see if I can emulate a KISS TNC on my Laptop & see if I can get RF to work. I will use a different SSID for RF, so again if anyone sees me 'M6XSD-#' with any SSID I would like to know.

I will let you know how I get on.


73,
Colin
M6XSD.

Oh, and one more thing. If you DO have (mobile) Internet capability and configure a KISS or AGW RF interface, APRSISCE/32 will act as a (currently receive-only) IGate! Whatever is received on the RF port(s) is gated to APRS-IS. A future version will make this a configurable option as well as adding the ability to gate messages from -IS to RF for "recently" heard "local" stations on an RF channel. A much more distant future version may even support digipeating, but for now I'll just leave that up to the TNCs themselves.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

PS. I've got AGEPEpro set up with an iCom 706 listening to 30m APRS on 10.147.60 USB. A copy of APRSIS32 running as KJ4ERJ-1 is acting as an HF IGate during the day. I'm also tinkering with WSPR receiving at night, so the IGate goes down. You can see the stations I've heard at:

http://ldeffenb.dnsalias.net:3000/catchall?FormName=RealMain&;CellCount=48&MinutesPerCell=30&RfOnly=1&GateID=KJ4ERJ-1

or

http://ldeffenb.dnsalias.net:3000/catchall?FormName=RFTRAFFIC&;Action=Display&IGates=KJ4ERJ-1

What's with this new feature of "Prefetching" OSM Map Tiles? Why would I want to clutter up my hard drive with such stuff? Why not just let them download when they're needed?

Well, with the new KISS and AGW interfaces, APRSISCE/32 has moved beyond the assumption of Internet connectivity. In an RF-only APRS environment, it would still be nice to see the OSM map tiles; hence the prefetch option.

To use it, simply zoom in or out and pan around until your map view shows the area whose maps you want to prefetch. Then simply select View/Map/Prefetch. APRSISCE/32 will calculate how many tiles will be necessary to have the current zoom and two additional zoom levels at the current size of your window. When you accept this confirmation, ALL of those tiles are queued for fetching and you get to watch an expanding circle moving slower than you've probably seen it move to date. Don't be alarmed if the number of tiles queued doesn't match the original estimate. The second number takes into account tiles that were already resident in your tile cache.

After prefetching the tiles for a fairly large area, I zoom down a bit and continue prefetching more details and panning around fetching more and more details. It is, however, important to wait for each prefetch to complete before dragging the map around. APRSISCE/32 is smart enough to think that you've moved the map, so you must not need the stuff that was queued, so it will flush the queue and start over at the new location. Probably not what you want.

When you DO go mobile without an Internet connection, just toggle off Enables/OSM Fetch Enabled and APRSISCE/32 will not attempt to load any additional tiles. If you zoom in further than you did while prefetching, APRSISCE/32 will simplly stretch the closest available tile resulting in a grainier looking map than you would otherwise have, but at least you have a map!

Again, let me know if any of you are using this feature and how I can make it better (other than making the prefetch-queued tiles not flush when you pan around to queue more). BTW, double-clicking an empty space on the map will tell you how many tiles covering how much space you currently have on your machine as well as how long it has been since they've been referenced (since creation currently on Windows Mobile). The XML configuration file has a parameter called OSM.RetainDays. If this is set to zero, tiles will never be purged. Probably a good idea for a normally-disconnected machine on which a prefetch has been done.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

Ok, so the new release is out and your first question is: How do I configure a port and what in the world does TCP/IP have to do with KISS and NMEA?

APRSISCE/32 supports two different ways of connecting to serial devices. The "normal" expected one would be via a "normal" Windows COM port with baud rates, parity, stop bits and such. However, I also support connected to a TCP/IP source of this same data. This allows the client to connect to remotely served TCP/IP serial ports which may or may not be virtualized by Windows. I also happen to have some TCP/IP servers that remotely serve out COM ports from one Windows machine to another. So...

When you click the KISS or NMEA buttons on the new configuration dialog, you will be asked if you want to "Configure As a TCP/IP Port?". Most of you will probably want to click "No". At that point, a Port Configuration dialog will appear with drop-downs of the known COM ports and support baud rates along with radio buttons for Parity and Data/Stop bits. (Ignore the Xmit checkbox). When you have things set up for your GPS or KISS TNC, click OK.

After configuring a COM port, the KISS or NMEA button will take you directly back to the Port Configuration dialog. If you clear the COM port and click OK, the next time you configure that port, the TCP/IP question will be asked.

The AGW interface only support TCP/IP connections to AGWPE. The TCP Configuration dialog prompts for an IP address or DNS name of the host where AGEPE is executing. Port 8000 is the default for AGW and should not be changed unless you know what you're doing. Again, ignore the Xmit checkbox.

After configuring the appropriate port(s), you can then enable whichever feature you want to use. If any communications errors are encountered, you may need to disable and re-enable the feature to get things moving again. I need to do more work on failure recovery.

If you are using a Bluetooth serial adapter for either KISS or NMEA GPS connections (I use a Delorme BlueLogger as my GPS), you'll need to go through the pairing and assign a COM port outside of the APRSISCE/32 client. Once you know the port number assigned to the device, you can configure it in the client and the Bluetooth connection should be established whent he feature is enabled.

Drop a note to the list if you are using any of these new features. I'm anxious to see how they work out and won't know if they're working or not if you don't tell me!

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

Here's what's new in the APRSISCE6P100209.zip and APRSIS32100209.zip -
Now available in the Files section at:

http://groups.yahoo.com/group/aprsisce/files/

Short version:

1) Win32 version supports NMEA GPS

2) Both versions support KISS TNCs

3) Both versions support receive-only AGWPE (all ports)

4) OSM Maps can be pre-fetched and the fetcher can be disabled

5) UTF-8 characters are supported in Addresses, Messages, and Comment texts

Longer version:

1) Support UTF-8 characters in Address information

2) Initial support for AGW's Packet Engine (Receive-Only via "m" monitor
command)

3) New configuration parameters for (at least in XML file!):
Enables for AGW, KISS, and OSMFetch
Outbound Beacon Path (defaults to WIDE1-1,WIDE2-1)
Preferred map view
GPS, AGW, and KISS Ports (Com or TCP)
Telemetry Interval

4) Com port configuration dialog (used for NMEA GPS and KISS)
This may not show all of your Bluetooth ports (yet)

5) TCP IP/Port configuration dialog (used for AGW, NMEA GPS, and KISS)

6) Corrected truncation issue on additional Filter text and comments

7) Configuration Dialog now has AGW, KISS, and NMEA buttons

8) Support UTF-8 characters in APRS Messaging and Station Comments

9) Tweak EarthRadius from 3,959.0 miles to 3958.76 miles

10) Stretch OSM tiles if a correct one isn't available (will resolve as
soon as fetched)

11) Support zooming in further than actual OSM maps support (important
for geocaching)

12) Support prefetching OSM tiles along with disabling fetching
on-the-fly (allows for offline operations)

13) Provide age-bucketed count and size of cached OSM tiles

14) Only purge old OSM tiles if fetching is enabled

15) Support NMEA GPS (only on Win32 currently)

16) Support KISS TNCs via serial (hardwire or Bluetooth) or TCP/IP port
Currently sends the following hard-coded command sequence:
KISSCommand(&cp, "\r");
KISSCommand(&cp, "\r");
KISSCommand(&cp, "XFLOW OFF\r");
KISSCommand(&cp, "KISS ON\r");
KISSCommand(&cp, "RESTART\r");
Otherwise, it expects the TNC to already be in KISS mode

17) New View/Map/Prefetch menu option - This prefetchs 3 zoom levels of
OSM tiles covering the entire visible map when selected. Note: You
better be on a fast connection when you do this!

18) View/Preferred/Restore and Save - This will allow you to save a
center point and zoom level for later recall. If one is saved, the
program starts in the preferred view. Double-clicking the Scale number
restores the preferred view.

19) View RF/All, Direct, or Local - Filters the display to stations
received over RF, either All, or Direct (0 hops), or Local (up to 2 hops).

20) Double-clicking the Battery Bar (extreme right edge) now shows the
power status of the machine.

21) Telemetry is now possible from Win32 (especially useful for mobile
laptops)

22) APRSISCE/32's window title now reflects the configured callsign

23) Handle "rej" packets and stop retransmitting an outbound message

24) Auto-respond to various queries:
?APRSD - send a list of "recently" directly heard stations
?APRSL - send a list of "recent" "local" stations
?IGATE - Transmit a Capabilites packet
?APRSP or ?APRS - Force a position packet (if Tracking enabled)

25) If you are tracking a station and drag the screen, the tracked
station's beacon points remain highlighted.

26) Double-clicking the GPS heading window will return center to a
tracked station. Double-clicking it again will return tracking to your
station.

27) Telemetry is only defined once, instead of every time the client
starts. Telemetry version is tracked in the configuration file so that
it will be re-defined as version upgrade what is being logged.

28) Station Popup now shows lots more stuff:
Station Status seperate from Comment
Capabilities (if ever received)
-IS vs RF paths (or both) over which packet was received
Title reflects # of Hops or IGate

29) Include station comment in Address lookup popup

30) Pending messages now show retry information and allow starting the
retries over or aborting a message

31) Double-clicking on the +/- zoom bar will directly set the zoom

32) Station Usage popup shows RF counts (local and direct) if any

33) The scrolling station list shows a * for RF-received stations and a
count after the * for duplicate packets received

34) Double-clicking the map now shows OSM tile statistics. These may
not be available until the client has run for at least 5 minutes.

35) The right edge of the satellites in use and in view bars now shows
the count of satellites in that list.

36) BitBlt errors are no longer displayed when a laptop lid is closed
with the client running (for instance)

37) Slightly improved logic to get the initial center position set on
first client execution.

Note: Any packets transmitted by APRSISCE/32 currently go out ALL
enabled ports. This includes beacons, messages, and acknowledgements.
Telemetry, however, is only sent via APRS-IS if that connection is good.

APRS Packet Parser updates:

1) Parse 3rd party sender out of APRS-IS packets

2) Parse Capabilities (<) packets

3) Parse Status (>) packets & Display on station popup

4) Extend comment text from 80 to 128 characters

5) Better duplicate packet detection using CRCs

6) Support new Overlayed symbol names (not icons) per
http://www.aprs.org/symbols/symbols-new.txt

7) Better handle parsing direct (pathless) packets (important for
RF-received packets)

8) Hop count = 2 for 3rd party traffic (not sure which path would be valid!)

9) Default symbol to red dot per spec

10) Default weather data to Weather Station symbol per spec

11) Default $ data symbol to red cross (no symbol) per spec

12) Support ToCall symbol specifications if no explicit symbol in packet

13) Use -SSID implied symbol if none specified anywhere else

14) Reject packets with invalid N/S E/W for coordinates

15) Don't parse compressed lat/lon unless it's really there!

To Dos: (Still Incomplete and getting LONGER instead of SHORTER!)

Wade through pending APRSISCE e-mails and expand the ToDo List!

Support checking revision of tiles when loading, via OpenStreetMap.org's
/status URL.
Find a way to mark tiles referenced on Windows Mobile without slowing
down map loading (queue references to fetcher thread?).
Use HTTP/1.1 in OSM Tile Fetcher to improve throughput (multiple tile
fetches on a single connection).
Implement a compass direction/distance screen for homing in on GeoCaches.
NMEA serial (BlueTooth) GPS support for Windows Mobile.
Update Bluetooth Port Enumerator to show all under Windows Mobile
KISS TNC initialization files (adopt UI-View syntax)
Remember and provide for re-display of received messages.
If target station's platform is known, format message sending screen
accordingly.
Optionally transmit either 1 or 2 !DAO! digits.
Parse and display Frequency object information
Support the -180/180 latitude wrap with closest display tile
Find a better icon scaling algorithm based on screen size & scale
Allow non-initial (re)configuration of location for OSMTiles cache (w/o
editing XML)
Allow configuration of date/time display & GMT vs local (Dave N8PU)
Allow configurable removal of some screen elements (Satellites, John N8JJ)
Record/Recall last DNS/IP for OSM/APRS-IS (in config file, for
connecting without DNS)
Asynchronous TCP/IP connections & reading (solves hangs)
Timeout on OSM Tile fetcher (solves stalls)
Implement whatever results from the Zoom +/- Poll

Make Local Hops, Recent Minutes, and Duplicate Seconds configuration options
Make Message Retry parameters configuration options

Split ?APRSD and ?APRSL lists into multiple messages
Support more ?APRSx queries

Add RF traffic and IGate rates to Telemetry

Win32 client only for the following:
Simultaneously track multiple targets in separate circles

Detect and highlight source of delayed duplications
Additional View/Filter options based on symbol types

Feed-through APRS-IS with local filters (for multiple instances of Win32
version with a single full feed to APRS-IS).

Lynn,

I missed seeing the
track real-time, but just remembered to go check on it and saw these graphs.

I'll return to Osaka using Shinkansen around 2/4 0am@UTC (or 2/3 noon@UTC).

The beacon setting is
Min 30sec, Max 30min,
Heading Change 45 deg,
Forecast error 3 1/10mi,
Max distance 100 1/10mi.

Now I think this is best setting for me.
I'll continue to choose best beacon setting.

Thanks.

2010/2/3 Lynn W. Deffenbaugh <kj4erj@arrl.net>:

Check out JG2RZF-12's station information graphs at aprs.fi!
(Particularly the third graph of reported speed)

http://aprs.fi/info/graphs/JG2RZF-12

I noticed this APRSISCE user with a Jogger symbol earlier in the day and
commented to him about being a fast jogger.  He told me he was on a
train that made perfect sense.  He then mentioned that he would be on
the "Shinkansen" train possibly maxing at 270km/h.  I missed seeing the
track real-time, but just remembered to go check on it and saw these graphs.

Pretty cool stuff!

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32



------------------------------------

Yahoo! Groups Links

--
FUJIURA Toyonori mailto:toyokun@gmail.com

Check out JG2RZF-12's station information graphs at aprs.fi! (Particularly the third graph of reported speed)

http://aprs.fi/info/graphs/JG2RZF-12

I noticed this APRSISCE user with a Jogger symbol earlier in the day and commented to him about being a fast jogger. He told me he was on a train that made perfect sense. He then mentioned that he would be on the "Shinkansen" train possibly maxing at 270km/h. I missed seeing the track real-time, but just remembered to go check on it and saw these graphs.

Pretty cool stuff!

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

Save your time in looking for the "Transmit" menu option. I got my cart ahead of my horse on that one as it's currently only in the Windows Mobile client. It will appear in the Win32 client when NMEA GPS support is released. However, the sequence below still applies to collect a debugging long when having problems....

Lynn (D) - KJ4ERJ

1) Turn on Enables/Debug Logging
2) Close the client
3) Restart the client
4) Wait a few minutes and/or hit the Transmit menu option (if enabled)
5) Turn off Enables/Debug Logging
6) Close the client. APRSIS32.LOG and APRSIS32.XML should be in the
directory with APRSIS32.EXE. Email those files to KJ4ERJ@arrl.net.

Phillip wrote:

Hi Lynn,
Thanks for your efforts..
How do I send a beacon I have my Lat/Long set I am connected to the APRS-IS

If you have your lat/lon set and the correct APRS-IS password
configured, APRSIS32 should be sending beacons. Please do the following
steps and e-mail the resulting APRSIS32.LOG along with your APRSIS32.XML
file to KJ4ERJ@arrl.net:

1) Turn on Enables/Debug Logging
2) Close the client
3) Restart the client
4) Wait a few minutes and/or hit the Transmit menu option (if enabled)
5) Turn off Enables/Debug Logging
6) Close the client. APRSIS32.LOG and APRSIS32.XML should be in the
directory with APRSIS32.EXE. Email those files to KJ4ERJ@arrl.net.

1/ Documentation ( Help file )

On the list, but probably not very high as things are still changing
pretty quickly. I'm thinking of an annotated screen that describes the
visual functions well in advance of any formal documentation.

2/ Be nice to see either AGW or BPQ support or both for the desk top version, this will allow multiple ports
BPQ is being updated all the time

I'm not familiar with BPQ. Can you provide a link to developer's
information on interfacing to it? I've got some idea of how to use AGW,
but KISS will definitely be released first.

3/ Be able to configure all settings via pop up windows

I've got plans for this one, but for normal users, the parameters
presented currently are all that should need to be changed. I'm
planning an "advanced" configuration that will walk through ALL of the
parameters of the XML file with some short textual description of what
the parameter does. At least you won't have to close the client, edit
the XML, re-start the client!

4/ Allow for more than 1 selected APRS-IS so that if 1 disappears the program will move to the next

If you use one of the rotate DNS names (rotate.aprs.net or
rotate.aprs2.net) or one of the regional names
(http://www.aprs2.net/#regional), rotation will be automatic. I'll add
this to the list, however, for those that want tighter control of which
APRS-IS servers to use. (For those that didn't know, the default
APRS-IS server is rotate.aprs2.net). The upcoming release will show the
configured and current APRS-IS server/port in the Info popup of your own
station ("Me").

5/ Selectable Miles or Kilometres etc

On the list and raising in priority....Just don't ask me for
internationalized languages any time soon. That's MUCH more complex
than I plan to get anytime soon. I'm too impatient of a coder to not
put quoted strings directly in the source code!

Keep the suggestions coming!

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

Hi Lynn,                Thanks for your efforts..   How do I send a beacon I have my Lat/Long set I am connected to the APRS-IS     1/ Documentation ( Help file )   2/ Be nice to see either AGW or BPQ support or both for the desk top version, this will allow multiple ports     BPQ is being updated all the time   3/ Be able to configure all settings via pop up windows   4/ Allow for more than 1 selected APRS-IS so that if 1 disappears the program will move to the next     5/ Selectable Miles or Kilometres etc    73 Phillip ZL2TZE

Phillip wrote:

Hi Lynn,
Just to let you know I have the Win32 aprsisce on test here
looks good ..

Thanks for the feedback. If you see anything you'd like changed please mention it here. Even if it's been mentioned by others. It'll help me set my development priorities.

Awaiting more inovations etc

I had hoped to have the KISS/NMEA GPS support out by now, but my day job has been stretching into the evening for the past several weeks. I did take a mobile APRSISCE (yes, the Windows Mobile version) IGate on a road trip this past Saturday and Sunday. The IGate was running as KJ4ERJ-12 and was co-resident in our Safari van which tracks (RF-only) as KJ4OVQ-9. I guess it's not surprising that KJ4ERJ-12 gated most of KJ4OVQ-9's packets for the trip, given that the two antennas were only 4 feet apart.

The setup was:

KJ4ERJ-12 was APRSISCE running on an AT&T Tilt phone
BlueTooth serial link from phone to an IOGear GBS301 BT to Serial
GBS301 plugged into a T2-135 TNC embedded in an Alinco DR-135 radio
Borrowed dual-bander 1/4 wave mag mount on the roof

KJ4OVQ-9 is the standard tracker in the Safar
Nuvi 350 hooked to a T2-135 embedded in another Alinco DR-135 radio
1/2 wave mounted on fender so it looks like a redundant FM radio antenna

While on that test run, I uncovered an apparent issue in APRSISCE. It runs for about 1-2 hours with full gating before freezing the program. I can force the program to close without rebooting the phone, but there's definitely some sort of leak in the KISS or IGate support. Now I have to embed some diagnostics in the program to figure out what's going worng.

Once I get that debugged, and get a configuration dialog on the serial port configuration (BlueTooth serial ports are harder to discover under Windows Mobile than they are on Win32), I should be able to get it released.

Anyway, that's the state of the code at this point. Let me know what else you'd like in the next release and I'll see what I can do! Hopefully soon I'll be able to update my ToDo list so you know what's been suggested already!

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

Hi Lynn,
Just to let you know I have the Win32 aprsisce on test here
looks good ..

Awaiting more inovations etc

73 Phillip
ZL2TZE

Lynn, I haven't had a chance to test it out yet on my e830 or my e805, but I'll do it once I get some time to. I think it is another user who was asking about CE platform.

I do not own any CE platform devices at the moment (well, there is one, but not being used: it is a Clarion AutoPC 310C, which is the AutoPC (now defunct) platform based on Windows CE 2.0, I used to use it in my old car, running Odyssey 2000 navigation package).

The reason I asked about e830 and e805 is that both units have a 4.0" large LCD, and they are not being used right now so it's a bit of a waste (too lazy to sell them). I might be selling my HTC Advantage x7501 so even though it'll work fine I might not be able to enjoy it. The MWg 503g's screen is a bit small so I might not be using it either.

I also acquired a MID lately: BenQ S6 running Win XP, and will test your win32 version soon (once I set up the unit w/ other things first).

Thanks!

73,
David

Hi Lynn,

I have been running a Sprint Touch Pro which has the d-pad (circle multi-function button) like the AT&T Tilt. It functioned with up/down for zoom in/out and left/right for map transparency.

I have recently upgraded to the Sprint Touch Pro 2 which no longer has the d-pad. It only has a zoom in/out slider as seen at the very bottom of this photo: http://www.htc.com/us/content/images/phones/touch-pro2-sprint-Support-124.png

Is there any way to assign this 'zoom bar' (I guess you would call it) to be able to easily zoom the map in and out as opposed to having to open up the slider keyboard and use the arrows?

Thanks for any input you may have.

Other than that minor issue, APRSISCE is running like a champ on this phone. Even better yet, I don't seem to have the heat issue the Touch Pro/Tilt is so famous for. Plus it's a much bigger screen.

73, Jason, K2ENG (APRSISCE: K2ENG-12)

While the Socks proxy is supposed to be invisible, if APRSISCE is using NetTCPBinding it doesn't support proxies. Here is a quote from a Microsoft thread:

"I have a program written with .Net 2.0 by me using normal tcp sockets and which I can tunnel through socks proxy, but after upgrading to .NET 3.5 (and still using sockets) my used tool can't grab the traffic. I'm using "proxifier" but there are many other capture tools, also some free."

Maybe this will help Lynn. Socks proxies were supposed to be invisible to applications but with the continual evolution of TCP stacks, APIs, etc., there may be issues with certain configurations.

73,

Pete AE5PL

--- In aprsisce@yahoogroups.com, FUJIURA Toyonori <toyokun@...> wrote:

I didn't run both AGWTracker and APRSISCE same time.
So why APRSISCE doesn't connect to APRS server?

I can't answer that because see below...

When I set proxy server in connection setting,
is the socks handled by the socket API or the application like Pocket IE?
If Socket API, I think the APRSISCE should run.
If the application, I think the application support is needed.

It is the socket API. The design of the Socks Proxy is to go between the TCP stack and the application and be invisible to the application. I don't know why AGWTracker connects and APRSISCE doesn't. I recommend looking closely at your server and port definitions in AGWTracker and APRSISCE and make sure they are exactly the same.

73,

Pete AE5PL

Dear Pete,

I didn't run both AGWTracker and APRSISCE same time.
So why APRSISCE doesn't connect to APRS server?

When I set proxy server in connection setting,
is the socks handled by the socket API or the application like Pocket IE?
If Socket API, I think the APRSISCE should run.
If the application, I think the application support is needed.

Thanks.

2010/1/31 ae5pl <pete@ae5pl.net>:

--- In aprsisce@yahoogroups.com, FUJIURA Toyonori <toyokun@...> wrote:

Thanks reply and I understood, but it is very inconvenience.
Because not only putty but also AGWTracker support it.
Please add it in your plan..

My phone prover is EMOBILE.
http://www.gsmworld.com/Roaming/Gsminfo/net_jpem.shtml
And MMS connection requres the following settings.
wm.internal.emnet.ne.jp / 8080 (HTTP proxy) 1080 (Socks proxy)

Fujiura,

APRSISCE does not need to do anything to support the Socks proxy.  It is "transparent" to the application.  In other words, you don't do anything in putty or AGWTracker to accomodate the Socks proxy.  It is up to you to ensure that the Socks proxy properly intercepts the port you are connecting to in APRS-IS as a telnet type port.

The Socks proxy is very old technology put in place to help restrict normal non-HTTP TCP traffic.  It affects all non-HTTP applications on a device and must be configured to allow individual port connections.  My guess is that your cell phone provider uses it to restrict type of access to streaming sites and "banned" sites.  It should not interfere with APRSISCE if AGWTrackerPocket works as they both use the same TCP socket API.

73,

Pete AE5PL



------------------------------------

Yahoo! Groups Links

--
FUJIURA Toyonori mailto:toyokun@gmail.com