开云体育

Don’t forget that ISDN, our belated attempt to bring data and multiple voice
to the public (under telco rules) in a new and faster? environment ncluded X.25
on the D Channel!??!

Historical perspective here ?

Keith Cheshire

On Jun 22, 2022, at 6:28 PM, john jones via groups.io <jjones3601=
[email protected]> wrote:

There isn't a hard line but telephony and VoIP are voice and X.25 is
definitely NOT that. Yes, the telephone companies carried the data circuits
and modems went over voice circuits but hopefully, you know what I mean. CNET
is many things to many people but for example, you won't see much conversation
about cell phones. I also wanted to calibrate to make sure there weren't a
bunch of folks that felt the CNET list was hijacked.

More importantly, to me at least, is some of these discussions might be good to
be "captured" on the x25.org list so that future folks interested in joining
the x25.org network can look back to the epoch of TELEBAHN and find these
conversations. Whether they are helpful or not.....

That being said, there seems to be a lot of people interested in the
conversation so we can keep it here.

John



-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Grant Taylor via
groups.io
Sent: Wednesday, June 22, 2022 5:20 PM
To: C-Netlist <[email protected]>
Subject: Re: [VoIP] ATTN Emily Post X.25 emails

On 6/22/22 2:34 PM, john jones via groups.io wrote:

I think we’ve moved beyond CNET over VoIP and can transition to the

X.25 email list if necessary.


I don't mind moving to a different mailing list if that's what the community
prefers.

However, I just re-read the C*NET (ckts.info) page again and I feel like
X.25 falls under the "pretty much anything telephony or VoIP related."
statement.

So I'm just curious if I'm misinterpreting or if the X.25 discussion is
something special.

Similarly, would discussions of ISDN telephony equipment be on or off topic?

I don't mind either way. I'm just trying to calibrate myself.



--
Grant. . . .
unix || die












--
Keith Cheshire

sorry if this topic feels offtopic for the c*net list, everyone.? :)

true fact: i started looking into x.25 because i was curious about
temporary signalling connections and how they work on the Definity.?
i
wondered whether it would be possible to bolt on a data network next
to the existing c*net voice network to facilitate transparent isdn
interworking.? sort of like how the PSTN was slowly transitioned from
vf-only to a dual vf/packet network with ss6 and later ss7.

my thinking went: if things can be made to work that way, two
c*net-connected pbxes, each with local pri's homing on router that
splits/recombines all the datastreams properly, might could think
they're speaking end-to-end isdn, not even noticing anything unusual!
that would be neat.

so i started gathering equipment and learning how it all fits
together.? got a bit sidetracked though, haven't yet gotten around to
answering that first question one way or the other.

it does seem that you can statically configure a set of Definity
pbx's
into a larger network in a non-isdn environment, using regular vf
telephone trunks and sending the signalling traffic over X.25.
haven't gotten that to work properly yet either but i'm pretty close.

Hi,

On Thu, Jun 23, 2022 at 01:02:16PM -0500, Wes Fisher wrote:

That sounds really cool! :D

SGI Indy's interestingly have ISDN modems built in. I always
thought
that might be a fun thing to tinker with.

Plesae note that within the OCTOI (Osmocom Community ISDN) project
we're currently building a distributed over-the-internet ISDN
network:


Currently there's no direct method for BRI interfacing (only PRI),
but we're working on
a BRI hardware and making progress with prototypes:


It's on the general TODO list to try to support X.31 (X.25 over ISDN)
in OCTOI
at some point... Not sure when we will get to it, though.