some binkp capable mailers send PHN with their phone/domain/IP...
binkd doesn't appear to have this capability...
it would be nice if a config verb "phone" or similar was introduced so
we could configure binkd to transmit this information... it would be
some binkp capable mailers send PHN with their phone/domain/IP...
binkd doesn't appear to have this capability...
It has the "nodeinfo" config verb. It is a free form field.
It has the "nodeinfo" config verb. It is a free form field.
I don't think it is the same thing...
Taurus shows NDL and PHN. How can you do that with Binkd?
It has the "nodeinfo" config verb. It is a free form field.
I don't think it is the same thing...
Taurus shows NDL and PHN. How can you do that with Binkd?
Look in the binkd log of 221/360 for an incoming call fom 280/5556
280/5556
No PHN line.
some binkp capable mailers send PHN with their phone/domain/IP...
binkd doesn't appear to have this capability...
It has the "nodeinfo" config verb. It is a free form field.
it would be nice if a config verb "phone" or similar was introduced
so we could configure binkd to transmit this information... it would
be
Seems to me, what you request is already covered by the nodeinfo keyword.
binkd doesn't appear to have this capability...
It has the "nodeinfo" config verb. It is a free form field.
nodeinfo generally carries the nodelist flags and connection speed...
it would be nice if a config verb "phone" or similar was
introduced so we could configure binkd to transmit this
information... it would be
Seems to me, what you request is already covered by the nodeinfo
keyword.
not really...
binkd doesn't appear to have this capability...
It has the "nodeinfo" config verb. It is a free form field.
nodeinfo generally carries the nodelist flags and connection speed...
The PhoneNumber is not nodelist information?
sysopsSeems to me, what you request is already covered by the nodeinfo
keyword.
not really...
What you requested was that binkd could be configured tp transmit the information. "nodeinfo" can do that. All that is needed is that the
adds the iformation to the "nodeinfo" line in his/her binkd config.
What you requested was that binkd could be configured tp transmit
the information. "nodeinfo" can do that. All that is needed is
that the sysops adds the iformation to the "nodeinfo" line in
his/her binkd config.
that does not cause binkd to transmit a PHN line like other systems
do... how hard is this to understand???? :sigh:
What you requested was that binkd could be configured tp transmit
the information. "nodeinfo" can do that. All that is needed is
that the sysops adds the iformation to the "nodeinfo" line in
his/her binkd config.
that does not cause binkd to transmit a PHN line like other systems
do... how hard is this to understand???? :sigh:
The PHN line obviously is a relic from the POTS age.
PLONK!
20:11 [17428] SYS RBB/2
20:11 [17428] ZYZ Tommi Koivula
20:11 [17428] LOC Lake Ylo, Finland
20:11 [17428] NDL IBN,CM
20:11 [17428] PHN rbb.fidonet.fi
20:11 [17428] TIME Wed, 19 Jun 2019 20:11:26 +0300
20:11 [17428] VER binkd/1.1a-99.1/OS2 binkp/1.1
20:11 [17428] addr: 2:221/0@fidonet
20:11 [17428] addr: 2:221/1@fidonet
20:11 [17428] addr: 2:221/360@fidonet
=== Cut ===
There. :)
On 2019 Jun 19 20:12:08, you wrote to me:
20:11 [17428] SYS RBB/2
20:11 [17428] ZYZ Tommi Koivula
20:11 [17428] LOC Lake Ylo, Finland
20:11 [17428] NDL IBN,CM
20:11 [17428] PHN rbb.fidonet.fi
20:11 [17428] TIME Wed, 19 Jun 2019 20:11:26 +0300
20:11 [17428] VER binkd/1.1a-99.1/OS2 binkp/1.1
20:11 [17428] addr: 2:221/0@fidonet
20:11 [17428] addr: 2:221/1@fidonet
20:11 [17428] addr: 2:221/360@fidonet
=== Cut ===
There. :)
8) :) :) :)
patch please!
20:11 [17428] PHN ...
patch please!
:)patch please!
:-) I wouldn't use it. It resembles a Russian word meaning a crime boss.
patch please!
The only thing I did was adding one line to protocol.c :
:)20:11 [17428] PHN ...
patch please!
:-) I wouldn't use it. It resembles a Russian word meaning a crime boss.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 409 |
Nodes: | 16 (3 / 13) |
Uptime: | 47:10:05 |
Calls: | 8,570 |
Calls today: | 10 |
Files: | 13,222 |
Messages: | 5,929,003 |