asterisk users - Oct 2006 - Problems with chan-capi and Eicon Diva 4BRI

Hi!

This weekend we had a problem with our Asterisk Box which ran flawlessly 
for nearly 4 weeks. The Asterisk server sits between the PSTN and a 
Siemens PBX and bridges 2 BRI lines. No calls, not incoming, not 
outgoing. The admin rebooted the Dell Box and then everything worked 
fine again.

Now, I'm analyzing log files to find the cause. During the Asterisk 
outage the logfiles only show incoming (PSTN->Asterisk->PBX) calls, no 
outgoing. Thus I suspect that the Asterisk<-->PBX link was broken.

In the Asterisk message file I only see "Recovery on timer expiry" 
errors, like below:

Oct 20 17:18:18 VERBOSE[19772] logger.c:   == ISDN2#02: Incoming call 
'347xxxxx' -> '32xx'
Oct 20 17:18:18 VERBOSE[19772] logger.c:     -- ISDN2#02: Updated 
channel name: CAPI/ISDN2/32xx-8ab6
Oct 20 17:18:18 VERBOSE[2663] logger.c:     -- Executing 
Dial("CAPI/ISDN2/32xx-8ab6", "CAPI/g2//b|90") in new stack
Oct 20 17:18:18 VERBOSE[2663] logger.c:     -- Called g2//b
Oct 20 17:18:19 VERBOSE[19772] logger.c:     -- ISDN2#02: Updated 
channel name: CAPI/ISDN2/32xx11-8ab8
Oct 20 17:18:19 VERBOSE[2663] logger.c:     -- ISDN4#02: Updated channel 
name: CAPI/ISDN4/1-8ab9
Oct 20 17:18:19 VERBOSE[2663] logger.c:     -- ISDN4#02: Updated channel 
name: CAPI/ISDN4/11-8aba
Oct 20 17:18:26 VERBOSE[19772] logger.c:        > ISDN4#02: CAPI INFO 
0x34e6: Recovery on timer expiry
Oct 20 17:18:26 VERBOSE[2663] logger.c:   == ISDN4#02: CAPI Hangingup 
for PLCI=0x104 in state 4
Oct 20 17:18:26 VERBOSE[2663] logger.c:   == Everyone is busy/congested 
at this time (1:0/0/1)
Oct 20 17:18:26 VERBOSE[2663] logger.c:     -- Executing 
Hangup("CAPI/ISDN2/32xx11-8ab8", "") in new stack
Oct 20 17:18:26 VERBOSE[2663] logger.c:   == Spawn extension (frompstn, 
32xx, 2) exited non-zero on 'CAPI/ISDN2/32xx11-8ab8'
Oct 20 17:18:26 VERBOSE[2663] logger.c:   == ISDN2#02: CAPI Hangingup 
for PLCI=0x202 in state 7
Oct 20 17:18:26 VERBOSE[19772] logger.c:        > ISDN2#02: CAPI INFO 
0x34e6: Recovery on timer expiry


What does the timer expiry exactly mean? Was it a Layer2 or Layer 3 
problem? How can I find out more or how can I activate more BRI 
debugging for the case it happens again?

Are there any known problems? We are using:
Asterisk 1.2.12.1
chan_capi-0.7.0
divas4linux-melware-3.0.3-106.650-1
Diva Server 4BRI-8M 2.0 PCI

Thanks
Klaus

Hi Klaus.

I'm not sure about the timer expiry meaning,
but you could use the xlog command (usually found
in /usr/lib/eicon/divas)

Just run it as root indicating which span (1..4)
you want to trace:

./xlog -c 2

that shoud show you layer 1 & layer 2
dump

Alberto.

Klaus Darilion ha scritto:
> Hi!
>
> This weekend we had a problem with our Asterisk Box which ran 
> flawlessly for nearly 4 weeks. The Asterisk server sits between the 
> PSTN and a Siemens PBX and bridges 2 BRI lines. No calls, not 
> incoming, not outgoing. The admin rebooted the Dell Box and then 
> everything worked fine again.
>
> Now, I'm analyzing log files to find the cause. During the Asterisk 
> outage the logfiles only show incoming (PSTN->Asterisk->PBX) calls,
no
> outgoing. Thus I suspect that the Asterisk<-->PBX link was broken.
>
> In the Asterisk message file I only see "Recovery on timer
expiry"
> errors, like below:
>
> Oct 20 17:18:18 VERBOSE[19772] logger.c:   == ISDN2#02: Incoming call 
> '347xxxxx' -> '32xx'
> Oct 20 17:18:18 VERBOSE[19772] logger.c:     -- ISDN2#02: Updated 
> channel name: CAPI/ISDN2/32xx-8ab6
> Oct 20 17:18:18 VERBOSE[2663] logger.c:     -- Executing 
> Dial("CAPI/ISDN2/32xx-8ab6", "CAPI/g2//b|90") in new
stack
> Oct 20 17:18:18 VERBOSE[2663] logger.c:     -- Called g2//b
> Oct 20 17:18:19 VERBOSE[19772] logger.c:     -- ISDN2#02: Updated 
> channel name: CAPI/ISDN2/32xx11-8ab8
> Oct 20 17:18:19 VERBOSE[2663] logger.c:     -- ISDN4#02: Updated 
> channel name: CAPI/ISDN4/1-8ab9
> Oct 20 17:18:19 VERBOSE[2663] logger.c:     -- ISDN4#02: Updated 
> channel name: CAPI/ISDN4/11-8aba
> Oct 20 17:18:26 VERBOSE[19772] logger.c:        > ISDN4#02: CAPI INFO 
> 0x34e6: Recovery on timer expiry
> Oct 20 17:18:26 VERBOSE[2663] logger.c:   == ISDN4#02: CAPI Hangingup 
> for PLCI=0x104 in state 4
> Oct 20 17:18:26 VERBOSE[2663] logger.c:   == Everyone is 
> busy/congested at this time (1:0/0/1)
> Oct 20 17:18:26 VERBOSE[2663] logger.c:     -- Executing 
> Hangup("CAPI/ISDN2/32xx11-8ab8", "") in new stack
> Oct 20 17:18:26 VERBOSE[2663] logger.c:   == Spawn extension 
> (frompstn, 32xx, 2) exited non-zero on 'CAPI/ISDN2/32xx11-8ab8'
> Oct 20 17:18:26 VERBOSE[2663] logger.c:   == ISDN2#02: CAPI Hangingup 
> for PLCI=0x202 in state 7
> Oct 20 17:18:26 VERBOSE[19772] logger.c:        > ISDN2#02: CAPI INFO 
> 0x34e6: Recovery on timer expiry
>
>
> What does the timer expiry exactly mean? Was it a Layer2 or Layer 3 
> problem? How can I find out more or how can I activate more BRI 
> debugging for the case it happens again?
>
> Are there any known problems? We are using:
> Asterisk 1.2.12.1
> chan_capi-0.7.0
> divas4linux-melware-3.0.3-106.650-1
> Diva Server 4BRI-8M 2.0 PCI
>
> Thanks
> Klaus
>
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users

-- 
--
Alberto Pastore
B-Press Srl - Gruppo MSoft
P.IVA 01697420030
P.le Lombardia, 4 - 28100 Novara - Italy
Tel. 0321-499508 
Fax 0321-492974
http://www.msoft.it

Hello,

I've posted this at the trixbox and freepbx forums and haven't been able
to get an answer. I thought perhaps the guru's here might be able to 
help me out :)

I'm having some issues with setting caller IDs. There are 2 problems 
that I would like to solve.

1. I have a DID pointing to a ring group. The only 'extension' in that 
ring group is an external number (cell phone). So essentially the DID 
fwds to a cell phone. The problem is that the CID that shows up on the 
Cell phone is the number that's set on the outgoing trunk the the 
CALLERS #. Is there a simple way to override this? Or better yet, is 
there a prefered method for forwarding calls out with freePBX?


2. I have sevaral trixbox installs connected through DUNDI. The DUNDI 
works very well.. I can call local extensions from every PBX. The PBX's 
are connected via an IAX trunk. In freePBX I've created a custom trunk 
that accepts a 4 digit extension and puts the call into a 'trydundi' 
context. The problem I'm having is that whenever someone calls from an 
extension at one location to an extension at another location the 
CallerID that shows up at the other location is the one set either in #1 
The custom trunk, or #2 in the 'Outbound CID' field in the users screen.
What I WANT this to be set to is the Name of the extension ie. just like 
local calls are. Is there a way to do this painlessly. Is it possible to 
hook dundi into a different context so that it would think all calls are 
local.. I'm kinda guessing here.


Sorry about the length of these descriptions and thanks for any advice!

Do any *UK* users have an SPA3102 (the newer version of the 
SPA3000/Sipura SPA3000) correctly detecting when an incoming PSTN call 
has hung up?

I've read everything I can find, including an SPA3000 UK setup PDF that 
lists UK ring etc tone settings, port impedances, disconnect tone 
settings and so on, but I'm still not getting PSTN hangup detection to work.

Any help would be appreciated.

Thanks,

Faris.

On Mon, 23 Oct 2006, Klaus Darilion wrote:
> Hi!
> 
> This weekend we had a problem with our Asterisk Box which ran flawlessly
for
> nearly 4 weeks. The Asterisk server sits between the PSTN and a Siemens PBX
> and bridges 2 BRI lines. No calls, not incoming, not outgoing. The admin
> rebooted the Dell Box and then everything worked fine again.
> 
> Now, I'm analyzing log files to find the cause. During the Asterisk
outage the
> logfiles only show incoming (PSTN->Asterisk->PBX) calls, no outgoing.
Thus I
> suspect that the Asterisk<-->PBX link was broken.
> 
> In the Asterisk message file I only see "Recovery on timer
expiry" errors,
> like below:
...
> Oct 20 17:18:26 VERBOSE[19772] logger.c: ISDN4#02: CAPI INFO 0x34e6:
Recovery on timer expiry
>
> What does the timer expiry exactly mean? Was it a Layer2 or Layer 3
problem?
Actually I don't know the reason for this, but it looks like it is coming 
from the connected device.
> How can I find out more or how can I activate more BRI debugging for the
case
> it happens again?
Use
  divactrl mlog -c X -o >file.txt
to get full log on port X.
It also includes d-channel trace with description.
 
> Are there any known problems? We are using:
> Asterisk 1.2.12.1
> chan_capi-0.7.0
> divas4linux-melware-3.0.3-106.650-1
> Diva Server 4BRI-8M 2.0 PCI
No, this is mainly the same configuration I use for each installation these 
days.

Armin