[Dxspider-support] TALKs with ">"

[John Buttery]

Colin was able to send from GB7ORH, using latest Spider, to GB7WDX, under
limited protocol, using ">" with no problem.  Is it just when it has to pass
'through' a spider node to the recipient that there is a problem?
Regards
John, G7OPJ

-----Original Message-----
From: dxspider-support-admin at dxcluster.org
[mailto:dxspider-support-admin at dxcluster.org]On Behalf Of John Clayton
Sent: 15 November 2001 11:08
To: DXSpider Support
Subject: [Dxspider-support] TALKs with ">"


Hi Dirk, I have raised this problem before(see below), but cannot trace
any answer.

I just tried to send T G3NOH > GB7DXH and got back from GB7BAA "Sorry
G3NOH is not online at the moment".  I know he is but for whatever
reason he is not showing on BAA or DXC.

Should be grateful if you could implement the old method of passing this
type of TALK on to the specified cluster node.

Many thanks.

PREVIOUS MESSAGE:

QUOTE

Hi Dirk, 
I am logged on to GB7DXC and just tried to send a TALK to a user on
GB7DXS who is connected to the network on a limited protocol connection.
(T G4PTJ > GB7DXS etc...)

As you know, GB7DXC is connected to GB7BAA.  My attempt as above got the
response from GB7BAA of "G4PTJ is not online at the moment" (presumably
because GB7BAA could not "see" G4PTJ).

Can you please mod the code so that when a routing (> GB7DXS) is given
for the TALK, Spider takes account of it and passes it on appropriately.

Many thanks.


Cheers for now de John, G4PDQ.
        
UNQUOTE 
-- 
John Clayton

_______________________________________________
Dxspider-support mailing list
Dxspider-support at dxcluster.org
http://www.tobit.co.uk/mailman/listinfo/dxspider-support


Disclaimer 

This email is confidential and intended solely for the use of the individual
to whom it is addressed.  Any views or opinions presented are those of the
author and do not necessarily represent those of Bridgwater College. If you
are not the intended recipient, be advised that any use, dissemination,
forwarding, printing, or copying of this email is strictly prohibited. If
you have received this email in error please contact the sender.