On Wed, 1 Mar 2006, Ralf Schlatterbeck wrote:
On Tue, Feb 28, 2006 at 04:21:57PM +0100, Armin Schindler wrote:
On Tue, 28 Feb 2006, Ralf Schlatterbeck wrote:
On Tue, Feb 28, 2006 at 02:32:27PM +0100, Armin Schindler wrote:
On Tue, 28 Feb 2006, Ralf Schlatterbeck wrote:
Maybe
On Wed, Mar 01, 2006 at 09:03:20AM +0100, Armin Schindler wrote:
The reason why it is not working for you is, that mISDN is not sending the
calledpartynumber IE as INFO_IND, which should be done in PtP mode.
Karsten already contacted me and he said that this missing and needs to be
added.
In
On Wed, 1 Mar 2006, Ralf Schlatterbeck wrote:
On Wed, Mar 01, 2006 at 09:03:20AM +0100, Armin Schindler wrote:
The reason why it is not working for you is, that mISDN is not sending the
calledpartynumber IE as INFO_IND, which should be done in PtP mode.
Karsten already contacted me and he
On Wed, Mar 01, 2006 at 12:14:16PM +0100, Armin Schindler wrote:
No, this is callingpartynumber and is not needed. We need calledpartynumber.
That was it. After Karsten sent me a new patch that sends the correct
INFO_IND, I'm now seeing the call in asterisk. IT'S WORKING! Thanks for
your
On Wed, 1 Mar 2006, Ralf Schlatterbeck wrote:
On Wed, Mar 01, 2006 at 10:08:13AM +0100, Armin Schindler wrote:
On Wed, 1 Mar 2006, Ralf Schlatterbeck wrote:
On Wed, Mar 01, 2006 at 09:03:20AM +0100, Armin Schindler wrote:
The reason why it is not working for you is, that mISDN is not
On Fri, Feb 24, 2006 at 10:43:31AM +0100, Armin Schindler wrote:
On Fri, 24 Feb 2006, Ralf Schlatterbeck wrote:
On Thu, Feb 23, 2006 at 02:45:25PM +0100, Armin Schindler wrote:
Interesting is, that I receive an INFO_IND *before* the CONNECT_IND.
This looks like an interesting
On Tue, 28 Feb 2006, Ralf Schlatterbeck wrote:
On Fri, Feb 24, 2006 at 10:43:31AM +0100, Armin Schindler wrote:
On Fri, 24 Feb 2006, Ralf Schlatterbeck wrote:
On Thu, Feb 23, 2006 at 02:45:25PM +0100, Armin Schindler wrote:
Interesting is, that I receive an INFO_IND *before* the
On Tue, Feb 28, 2006 at 09:20:05AM +0100, Armin Schindler wrote:
OK, I've reported a bug to mISDN. With the patch from the Karsten Keil
in the mantis tracker:
issue: https://www.isdn4linux.de/mantis/view.php?id=40
I'm now gettig connect_ind and info_ind in the correct order (asterisk
On Tue, 28 Feb 2006, Ralf Schlatterbeck wrote:
On Tue, Feb 28, 2006 at 09:20:05AM +0100, Armin Schindler wrote:
OK, I've reported a bug to mISDN. With the patch from the Karsten Keil
in the mantis tracker:
issue: https://www.isdn4linux.de/mantis/view.php?id=40
I'm now gettig
On Tue, Feb 28, 2006 at 10:46:40AM +0100, Armin Schindler wrote:
Ah, I see. Not very nice to send such a confusing log ;-)
I'm sorry.
Anyway, your config is set to DID mode. So chan_capi will wait for more
digits (an INFO_IND with called-party-number) and if the already given
destination
On Tue, 28 Feb 2006, Ralf Schlatterbeck wrote:
On Tue, Feb 28, 2006 at 10:46:40AM +0100, Armin Schindler wrote:
Ah, I see. Not very nice to send such a confusing log ;-)
I'm sorry.
Anyway, your config is set to DID mode. So chan_capi will wait for more
digits (an INFO_IND with
On Tue, Feb 28, 2006 at 02:32:27PM +0100, Armin Schindler wrote:
On Tue, 28 Feb 2006, Ralf Schlatterbeck wrote:
On Tue, Feb 28, 2006 at 10:46:40AM +0100, Armin Schindler wrote:
Anyway, your config is set to DID mode. So chan_capi will wait for more
digits (an INFO_IND with
On Tue, 28 Feb 2006, Ralf Schlatterbeck wrote:
On Tue, Feb 28, 2006 at 02:32:27PM +0100, Armin Schindler wrote:
On Tue, 28 Feb 2006, Ralf Schlatterbeck wrote:
On Tue, Feb 28, 2006 at 10:46:40AM +0100, Armin Schindler wrote:
Anyway, your config is set to DID mode. So chan_capi will wait
On Tue, 28 Feb 2006, Ralf Schlatterbeck wrote:
...
- But I guess the workaround would yield to my current situation (I'm
running a patched version of 0.35 currently as mentioned at the start
of this tread): When a caller uses overlap sending (e.g from a POTS
line) instead of block
On Tue, Feb 28, 2006 at 07:55:50PM +0100, Armin Schindler wrote:
On Tue, 28 Feb 2006, Ralf Schlatterbeck wrote:
...
- But I guess the workaround would yield to my current situation (I'm
running a patched version of 0.35 currently as mentioned at the start
of this tread): When a caller
On Tue, Feb 28, 2006 at 04:21:57PM +0100, Armin Schindler wrote:
On Tue, 28 Feb 2006, Ralf Schlatterbeck wrote:
On Tue, Feb 28, 2006 at 02:32:27PM +0100, Armin Schindler wrote:
On Tue, 28 Feb 2006, Ralf Schlatterbeck wrote:
Maybe chan_capi should have a timeout waiting for more info_ind
On Thu, Feb 23, 2006 at 02:45:25PM +0100, Armin Schindler wrote:
Hello Armin, hello List
I'm trying to get chan_capi working with asterisk from debian stable
(asterisk 1.0.7, the debian version number is 1:1.0.7.dfsg.1-2).
I managed to get it compiled by providing my own version of
On Fri, 24 Feb 2006, Ralf Schlatterbeck wrote:
On Thu, Feb 23, 2006 at 02:45:25PM +0100, Armin Schindler wrote:
Hello Armin, hello List
I'm trying to get chan_capi working with asterisk from debian stable
(asterisk 1.0.7, the debian version number is 1:1.0.7.dfsg.1-2).
I managed to
On Fri, Feb 24, 2006 at 10:43:31AM +0100, Armin Schindler wrote:
Interesting is, that I receive an INFO_IND *before* the CONNECT_IND.
This looks like an interesting variation of Austrian ISDN to me.
Maybe it is a variation of the ISDN line, but the driver should fix that.
Sending
On Thu, 23 Feb 2006, Ralf Schlatterbeck wrote:
Hello Armin, hello List
I'm trying to get chan_capi working with asterisk from debian stable
(asterisk 1.0.7, the debian version number is 1:1.0.7.dfsg.1-2).
I managed to get it compiled by providing my own version of
ast_copy_string.
Hmm, this
20 matches
Mail list logo
