Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 12 Jul 2007 08:18:30 +0200
From:      Hans Petter Selasky <hselasky@c2i.net>
To:        freebsd-isdn@freebsd.org
Subject:   Re: Digium b410p with i4b
Message-ID:  <200707120818.30352.hselasky@c2i.net>
In-Reply-To: <46955E2F.6040405@wanagain.net>
References:  <4665CAFA.3080801@wanagain.net> <200706061455.21425.hselasky@c2i.net> <46955E2F.6040405@wanagain.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 12 July 2007 00:48, Mikael Batard wrote:
> Hi,
>
> I have some problems with incoming calls with digium b410p and i4b.
>
> Sometimes it doesn't work and I don't know why.
> Hardphones doesn't ring at all, but I can see that these missed calls
> are handle by asterisk.
> But they're not handle normally by chan_capi.
>
> Here's the log for a missed call (verbose+debug+capi debug) :
>
> Jul 12 00:26:24 DEBUG[2917] channel.c: Set channel CAPI/ISDN3/0987-0 to
> write format slin
> Jul 12 00:26:24 DEBUG[2917] res_musiconhold.c: CAPI/ISDN3/0987-0 Opened
> file 0 '/usr/local/share/asterisk/mohmp3/Pilot'
> Jul 12 00:26:24 WARNING[2917] interface.c: Junk at the beginning of
> frame 49443303
> Jul 12 00:26:24 VERBOSE[2917] logger.c:   ==
> chan_capi_write:4799:ENTRY=ISDN3:PLCI=0x360a:PBX_CHAN=CAPI/ISDN3/0987-0:
>    ==
>
> /// Lots of "chan_capi_write" lines same as the one above ///
>
> Jul 12 00:31:42 VERBOSE[2917] logger.c: CAPI_INFO_IND {
>   header {
>    WORD       wLen                = 0x000f
>    WORD       wApp                = 0x0000
>    WORD       wCmd                = 0x8492
>    WORD       wNum                = 0x0000
>    DWORD      dwCid               = 0x0000380a
>   }
>   data {
>    WORD       wInfoNum            = 0x805a
>    STRUCT     InfoElement.ptr     = 0x00 '?'.
>   }
> }
>

Hi Mikael,

wInfoNum equal to 0x805A means RELEASE_COMPLETE

This message is sent two times:

1) When a call is disconnected.

You can run "isdndecode -u 0 -i -o -x" to get debugging information 
from "controller 0". "isdndecode -u 1 -i -o -x" will get you debugging 
information from "controller 1" and so on. Send me a log from ISDN-decode, 
and I will check who is disconnecting the call.

2) When another CAPI application has answered the call.

Check if there is another CAPI application or I4B application (isdnd) running, 
that listenes for calls.

--HPS



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200707120818.30352.hselasky>