Displaying 20 results from an estimated 6000 matches similar to: "[tzafrir.cohen@xorcom.com: Re: [asterisk-dev] Proposal for DAHDI-trunk: deprecate old kernels]"
2005 Feb 06
0
Xorcom Rapid 1.0 released
Hi folks
Xorcom Rapid 1.0 is avilable for download
Q: 1.0?
A: Sure, better than 0.9.1:
* Asterisk 1.0.5
* Base packages upgraded
* Built with SpanDSP support
* Improved Zaptel detection
* ast-cmd with some useful command-line abilities provided
* ssh installed by default
* putty.exe is included on the CD
* music-on-hold files removed due to potential licensing
issues
2005 Jan 11
0
test source for current xorcom rapid
Hi
I put a snapshot of our current packages updates.xorcom.com . They are
available from the deb source
deb http://updates.xorcom.com/test sarge main
(this is s/rapid/test/ of the name of the source of the stable version)
Changes include:
* Fixed and simplified zaptel detection
* Support for spandsp: compiled but not yet tested
* IAX extensions
* Mail server configuration
* The script
2005 Jul 22
0
Xorcom Rapid 1.1
Hi all
Xorcom Rapid 1.1 is here.
* Asterisk 1.0.9
* Flash Operator Panel
* improved Zaptel hardware detection: should hopefully detect E1, T1
ZapHFC and qozap. No more channel numbers guessing in
zapata/zaptel.conf
* and much of the "extra" software available for it
You can get the full details at
http://www.xorcom.com/rapid
so I'll just highlight the points that I
2004 Dec 09
1
Xorcom Rapid 0.9.0
Hi
Version 0.9.0 of Xorcom Rapid Debian/GNU/Linux/Asterisk has just been
released.
Main changes:
* A decent version of Asterisk/Zaptel (1.0.2) is provided
* Includes a better default configuration
* Automatic detection of the most common Zaptel cards
* Contains more optional software (apache, MySQL, Webmin and others) -
available via menu
You can get it from:
2011 Jun 14
1
Dahdi 2.4.0 and Squeeze [SOLVED]
After a reboot, I can't reproduce the problem anymore which is quite
frustating.
2011/6/14 Tzafrir Cohen <tzafrir.cohen at xorcom.com>
> On Tue, Jun 14, 2011 at 03:44:32PM +0200, Olivier wrote:
> > Hi,
> >
> > I'm using a two-years old installation script for the first time on a
> > Squeeze (linux 2.6.32) platform.
> > For an unknown reason (might
2010 Oct 31
0
Junghanns douBRI miniPCI (b559) DAHDI drivers
Hi
I got a simple patch (merely extra PCI IDs for Junghanns douBRI miniPCI:
https://issues.asterisk.org/view.php?id=18169
Sadly the reporter did not follow up on the report. I'd like to get at
least one positive report before I commit this. Anybody has this device
and wants it to work with DAHDI? Please update the bug report.
--
Tzafrir Cohen
icq#16849755
2017 Mar 14
2
How to install and configure Dahdi from Debian Stretch repo ?
2017-03-14 13:08 GMT+01:00 Tzafrir Cohen <tzafrir.cohen at xorcom.com>:
> On Tue, Mar 14, 2017 at 11:10:57AM +0100, Olivier wrote:
> > Hello,
> >
> > After all these years installing from source, I'm giving Dahdi package
> > installation a try on a recent Stretch box.
> >
> > Google over the web, I didn't find too many doc on this topic.
>
2017 Mar 21
2
How to install and configure Dahdi from Debian Stretch repo ?
On Tue, Mar 21, 2017 at 09:36:21AM +0100, Olivier wrote:
> Thanks to Tzafrir help, Now I have an Asterisk-Dahdi system installed from
> Stretch repository.
> This system has a Digium HX8 card with BRI modules, Asterisk 13.14.0, Dahdi
> 2.11.1.
> BRI spans appears as up and active but I've not tested them yet:
> CLI> pri show spans
> PRI span 1/0: Up, Active
> PRI
2010 Jan 23
1
Xorcom problem after update from zaptel to dahdi-2.2.1
Hello,
I am trying to update to dahdi 2.2.1. But somehow the xorcom (2BRI)
device does not want to work.
I pasted below the information I have.
pbx at loicvoip1:~# /usr/share/dahdi/xpp_fxloader reset
pbx at loicvoip1:~# /usr/share/dahdi/xpp_fxloader usb
'xpp_fxloader'[4937]: --------- FIRMWARE LOADING: (usb) [1 devices]
..Got all 1 devices
'xpp_fxloader'[5003]: ---------
2007 Jul 12
0
No subject
such file or directory" on pure-IP platform in which I installed
asterisk-libpri-dahdi trilogy.
Maybe, it's me while following README instructions, maybe README
instructions could be improved or maybe it's wrongly labeled messages ?
That's why I told myself : I'm waiting too much from doc ? is a pure-IP
platform too specific ? what is the official policy ?
README starts with
2017 Mar 20
2
How to install and configure Dahdi from Debian Stretch repo ?
2017-03-14 15:26 GMT+01:00 Tzafrir Cohen <tzafrir.cohen at xorcom.com>:
> On Tue, Mar 14, 2017 at 02:58:07PM +0100, Olivier wrote:
> > 2017-03-14 13:08 GMT+01:00 Tzafrir Cohen <tzafrir.cohen at xorcom.com>:
> >
> > > On Tue, Mar 14, 2017 at 11:10:57AM +0100, Olivier wrote:
> > > > Hello,
> > > >
> > > > After all these years
2007 Jul 12
0
No subject
static void senddialevent(struct ast_channel *src, struct ast_channel *dst)
{
manager_event(EVENT_FLAG_CALL, "Dial",
"Source: %s\r\n"
"Destination: %s\r\n"
"CallerID: %s\r\n"
"CallerIDName: %s\r\n"
"SrcUniqueID: %s\r\n"
"DestUniqueID: %s\r\n"
"CDRUserfield: %s\r\n",
src->name,
2014 Jan 20
1
What is dahdi.auto_assigned_spans and why should you care?
What is dahdi.auto_assign_spans and why should you care?
In later versions the kernel module dahdi[Q] includes a new parameter:
auto_assign_spans. It defaults to 1, and if you set it to 0, DAHDI can
start behaving in strange and completely expected ways. Chances are the
default will be set to 1 in a future version. Here is why you'll want to
set it yourself.
Up until DAHDI 2.5, hardware
2009 Jan 16
0
No subject
About the IVR, are u using Asterisk?
Regards
Bilal
> ------------------------------
>
> Message: 17
> Date: Wed, 18 Feb 2009 12:23:41 +0200
> From: Tzafrir Cohen <tzafrir.cohen at xorcom.com>
> Subject: Re: [asterisk-users] Credit Card processing
> machines
> To: asterisk-users at lists.digium.com
> Message-ID: <20090218102341.GD21440 at xorcom.com>
>
2007 Oct 02
0
Selecting a specific line from Zap/g And secondary dial tone
Dear List;
Thanks alot for the help.
But how can I let the second dial tone (after pressing
the extension to select that FXO port) to be
difference than normal dial tone?
Regards
Bilal Ghayad
--------------------------
Correction, on FXO port not FXS,
second, read his email first:
"Also, how it will be possible to assign an dedicated
line (connected to FXO) to an
button on the Polycom IP
2007 Oct 04
0
Fwd: [asterisk-dev] chan_h323 and chan_oh323 compatibilities
---------- Forwarded message ----------
From: Tzafrir Cohen <tzafrir.cohen at xorcom.com>
Date: Oct 4, 2007 12:56 PM
Subject: Re: [asterisk-dev] chan_h323 and chan_oh323 compatibilities
To: asterisk-dev at lists.digium.com
Hi
On Thu, Oct 04, 2007 at 11:46:30AM -0300, Caciano Machado wrote:
> I'm receiving a lot of warning messages from my Asterisk
> 1.2.5/chan_oh323 every time
2007 Jul 12
0
No subject
, address 2
Dec 30 21:42:08 wedekindpbx1 kernel: [ 3746.344611] ERR-xpp_usb: XBUS-00: x=
usb_listen: usb_submit_urb failed: -19
Dec 30 21:42:08 wedekindpbx1 kernel: [ 3746.353325] INFO-xpp: XBUS-00: [] D=
isconnecting
Dec 30 21:42:08 wedekindpbx1 kernel: [ 3746.353373] Zaptel: Master changed =
to XBUS-00/XPD-01
Dec 30 21:42:08 wedekindpbx1 kernel: [ 3746.353382] Zaptel: Master changed =
to
2007 Jan 17
0
Re: [asterisk-dev] Question about FXO/FXS device.
Okay, i'll move my discuss to asterisk-users.
Thank you.
On 1/17/07, Tzafrir Cohen <tzafrir.cohen@xorcom.com> wrote:
>
>
> On Wed, Jan 17, 2007 at 04:39:03PM +0800, ??? wrote:
> > Jonson Player wrote:
> > > Hello, I intend to buy a FXO/FXS device from Linksys.
> > > I'm thinking about SPA3102. What you guys thik about it.
> > > Is ok, is
2006 Apr 08
0
Re: [asterisk-dev] bug or bad chan_sip.c
Tzafrir,
How did you set sip:tzafrir@local.xorcom.com
I use ser----asterisk
look at my sip.conf and extensions.conf
Regards
Harry
////////////////////////////////////////////////////
[general]
context=sip
realm=nxs.yi.org
bindport=5050
bindaddr=nxs.yi.org
srvlookup=yes
tos=lowdelay
maxexpirey=3600
defaultexpirey=1000
allow=all
musicclass=default
language=fr
insecure=very
allowguest=yes
2006 Apr 08
0
Re: [asterisk-dev] bug or bad chan_sip.c
Tzafrir,
How did you set sip:tzafrir@local.xorcom.com
I use ser----asterisk
look at my sip.conf and extensions.conf
Regards
Harry
////////////////////////////////////////////////////
[general]
context=sip
realm=nxs.yi.org
bindport=5050
bindaddr=nxs.yi.org
srvlookup=yes
tos=lowdelay
maxexpirey=3600
defaultexpirey=1000
allow=all
musicclass=default
language=fr
insecure=very
allowguest=yes