freebsd-isdn Digest, Vol 225, Issue 3
freebsd-is...@freebsd.org
freebs...@freebsd.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-isdn
or, via email, send a message with subject or body 'help' to
freebsd-is...@freebsd.org
You can reach the person managing the list at
freebsd-i...@freebsd.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-isdn digest..."
Today's Topics:
1. Re: isdntrace - getting old output format back?
(Torfinn Ingolfsen)
2. Re: isdntrace - getting old output format back?
(Hans Petter Selasky)
3. Re: isdntrace - getting old output format back?
(Torfinn Ingolfsen)
4. Re: isdntrace - getting old output format back? (Volker)
5. Re: isdntrace - getting old output format back?
(Torfinn Ingolfsen)
----------------------------------------------------------------------
Message: 1
Date: Thu, 26 Jun 2008 19:25:55 +0200
From: "Torfinn Ingolfsen" <tin...@gmail.com>
Subject: Re: isdntrace - getting old output format back?
To: freebs...@freebsd.org
Message-ID:
<ef8c8a880806261025x12d...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Hi,
On Mon, Jun 23, 2008 at 12:01 AM, Hans Petter Selasky <hsel...@c2i.net> wrote:
> Hi again,
>
> I think this issue has been fixed, but you need to use to stuff from SVN. The
> 1.5.10 package is too old! And you need to use FreeBSD 6+ .
Ok, I finally got the old machine[1] upgraded to FreeBSD 6.3-stable,
and installed the latest ISDN4BSD from svn (revision 755).
Both isdntrace and isdndecode still uses the new output format
(text-formatted hexdump with annotations). I tried all switches /
options on isdndecode but couldn't get it to output the old text
format. Is there something I have overlooked?
To be precise, the call-logd script expects strings like the following
(it greps for them):
called party number: 99999999
calling party number: 99999999
where '99999999' will be the actual number calling / called.
Is it possible to get either isdntrace or isdndecode to output that format?
References:
1) machine used: http://tingox.googlepages.com/dp686t3_freebsd
--
Regards,
Torfinn Ingolfsen,
Norway
------------------------------
Message: 2
Date: Thu, 26 Jun 2008 22:19:31 +0200
From: Hans Petter Selasky <hsel...@c2i.net>
Subject: Re: isdntrace - getting old output format back?
To: freebs...@freebsd.org
Message-ID: <200806262219....@c2i.net>
Content-Type: text/plain; charset="iso-8859-1"
On Thursday 26 June 2008, Torfinn Ingolfsen wrote:
> Hi,
>
> On Mon, Jun 23, 2008 at 12:01 AM, Hans Petter Selasky <hsel...@c2i.net>
wrote:
> > Hi again,
> >
> > I think this issue has been fixed, but you need to use to stuff from SVN.
> > The 1.5.10 package is too old! And you need to use FreeBSD 6+ .
>
> Ok, I finally got the old machine[1] upgraded to FreeBSD 6.3-stable,
> and installed the latest ISDN4BSD from svn (revision 755).
> Both isdntrace and isdndecode still uses the new output format
> (text-formatted hexdump with annotations). I tried all switches /
> options on isdndecode but couldn't get it to output the old text
> format. Is there something I have overlooked?
>
> To be precise, the call-logd script expects strings like the following
> (it greps for them):
> called party number: 99999999
> calling party number: 99999999
>
> where '99999999' will be the actual number calling / called.
>
> Is it possible to get either isdntrace or isdndecode to output that format?
> References:
> 1) machine used: http://tingox.googlepages.com/dp686t3_freebsd
Hi Torfinn,
I think I patched "isdnd" some time back. The logfiles from "isdnd" should
have that format.
BTW: It is not very difficult to write a small CAPI 2.0 application that
listens for calls and then prints them out in any format you like. I can make
such an application in no time. How about "capimonitor" ?
--HPS
------------------------------
Message: 3
Date: Fri, 27 Jun 2008 00:30:08 +0200
From: "Torfinn Ingolfsen" <tin...@gmail.com>
Subject: Re: isdntrace - getting old output format back?
To: freebs...@freebsd.org
Message-ID:
<ef8c8a880806261530i79a...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Hi,
On Thu, Jun 26, 2008 at 10:19 PM, Hans Petter Selasky <hsel...@c2i.net> wrote:
> I think I patched "isdnd" some time back. The logfiles from "isdnd" should
> have that format.
OK, so the answer to my question is "no, you can't get the old output
format back".
Well, I'll have to change the call-logd script then.
> BTW: It is not very difficult to write a small CAPI 2.0 application that
> listens for calls and then prints them out in any format you like. I can make
> such an application in no time. How about "capimonitor" ?
So I'll end up with isdnd + capimonitor instead of isdnd + isdntrace?
As long as it doesn't add complexity to the setup, I would be happy
to have capimontor. And grateful.
I will have to chenge the call-logd script anyway.
--
Regards,
Torfinn Ingolfsen
------------------------------
Message: 4
Date: Fri, 27 Jun 2008 00:40:11 +0200
From: Volker <vol...@vwsoft.com>
Subject: Re: isdntrace - getting old output format back?
To: Torfinn Ingolfsen <tin...@gmail.com>
Cc: freebs...@freebsd.org
Message-ID: <48641ACB...@vwsoft.com>
Content-Type: text/plain; charset=ISO-8859-1
On 06/27/08 00:30, Torfinn Ingolfsen wrote:
> Hi,
>
> On Thu, Jun 26, 2008 at 10:19 PM, Hans Petter Selasky <hsel...@c2i.net> wrote:
>> I think I patched "isdnd" some time back. The logfiles from "isdnd" should
>> have that format.
>
> OK, so the answer to my question is "no, you can't get the old output
> format back".
> Well, I'll have to change the call-logd script then.
>
>> BTW: It is not very difficult to write a small CAPI 2.0 application that
>> listens for calls and then prints them out in any format you like. I can make
>> such an application in no time. How about "capimonitor" ?
>
> So I'll end up with isdnd + capimonitor instead of isdnd + isdntrace?
> As long as it doesn't add complexity to the setup, I would be happy
> to have capimontor. And grateful.
>
> I will have to chenge the call-logd script anyway.
>
Torfinn,
so, you're upgrading your OS, changing the i4b subsystem and doing a lot
of other stuff to just not change a script? ;)
Anyway, I've never tried HPS' isdn4bsd but if isdnd is nearly
compatible, you may want to try to use the regexpr/regprog functionality
and call your script (or a wrapper for it) from there.
Volker
------------------------------
Message: 5
Date: Fri, 27 Jun 2008 09:00:59 +0200
From: "Torfinn Ingolfsen" <tin...@gmail.com>
Subject: Re: isdntrace - getting old output format back?
To: freebs...@freebsd.org
Message-ID:
<ef8c8a880806270000u789...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Hi
On Fri, Jun 27, 2008 at 12:40 AM, Volker <vol...@vwsoft.com> wrote:
> so, you're upgrading your OS, changing the i4b subsystem and doing a lot
> of other stuff to just not change a script? ;)
It may look like that now, but it was sort of the other way around. :-)
This machine was running 5.3 / 5.4-prerelease. Once that "branch" was
EOL'ed (ok, some time after in fact) it got harder to support the
ports on the machine, as the ports infrastructure remove support for
unsupported branches (which is very wise, I might add).
So I was really looking to upgrade the os (and the ports) on the machine anyway.
HPS' ISDN4BSD stack has always been needed to support my isdn card.
I was just trying to do as little as I could by just upgrading to
5.5-stable. Had I known that I would get hit by these changes, I would
just have backed up the database and installed 6.3-stable directly, it
would have saved some time.
The machine is running callid[1] (which is where the call-logd script
comes from) and a few other ports.
> Anyway, I've never tried HPS' isdn4bsd but if isdnd is nearly
> compatible, you may want to try to use the regexpr/regprog functionality
> and call your script (or a wrapper for it) from there.
calling the script isn't the problem. call-logd calls isdntrace and
reads the output from it. The problem is that somewjere along the
development path for HPS' isdn4bsd stack, the output format of
isndtrace changed from a pure text-based output (which is easily
parsed by a program) to a text formatted "hexdump with annotations"
format which is much harder to parse.
Anyway, now the machine is upgraded to 6.3-stable and HPS has offered
to "fix" the isdn4bsd stack - we'll see how it goes. It seems like I
will be submitting a PR for a change to the callid port in the near
future.
References:
1) callid - http://www.freshports.org/misc/callid/
--
Regards,
Torfinn Ingolfsen,
Norway
------------------------------
End of freebsd-isdn Digest, Vol 225, Issue 3
********************************************