public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Padraig Brady <padraig@antefacto.com>
To: AstinusLists <AstinusLists@netcabo.pt>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ISDN CHANNEL-D
Date: Wed, 16 Jan 2002 20:58:02 +0000	[thread overview]
Message-ID: <3C45E95A.2010802@antefacto.com> (raw)
In-Reply-To: <001d01c19ec5$b6f8f740$d500a8c0@mshome.net>

AstinusLists wrote:

> Hello every one.
> 
> I've been earing some rumors, that i am quite sure that are turth about the
> isdn channel d.
> 
> As all of u know ( i think ) isdn cards have 3 channels: 2*64 and one time
> 16 kbs.
> 
> This last one is called channel D.
> Channel D is used to dial and to reply to tones and minor stuff like that.
> 
> The big deal here in my country is that u don't have to pay for the channel
> D traffic ( And it is legal to use it, i can assure that, cause i am well
> informed on that matter!)


Yes info is passed across the D channel in messages. There is a message

type called User User information that can be passed, but only with and
associated D channel call type, i.e. you must pay for it.

Also other "standard" messages like "call setup", "progress", ... can
contain user user info, but these can only be transfer after the call
is established.

In both cases an explicit call must be established first, so you're
billed for such traffic.

Now I suppose you could set specific bits in standard call setup 
messages for e.g. that could be used to transfer info between
users, but I'd say about 10bits max per call setup? which is not
interesting.

Search the net for Q931 for ISDN D channel protocol spec.

What does this have to do with Linux again?


Padraig.



  parent reply	other threads:[~2002-01-16 21:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-16 19:40 ISDN CHANNEL-D AstinusLists
2002-01-16 20:21 ` Kristian
2002-01-16 20:43   ` Rene Rebe
2002-01-16 20:58 ` Padraig Brady [this message]
2002-01-16 22:01   ` Sam Ravnborg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3C45E95A.2010802@antefacto.com \
    --to=padraig@antefacto.com \
    --cc=AstinusLists@netcabo.pt \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox