search for: wanpipe3

...n bad channel 0/30 on span 3 [Oct 6 10:55:55] WARNING[9794]: chan_zap.c:8074 pri_fixup_principle: Can't fix up channel from 63 to 92 because 92 is already in use And eventually no more calls can be placed from swyx to asterisk... time for some configs... and before anyone says something about wanpipe3 and 4 having dchan=0, i tried with dchan=16 and no calls can be placed... I hope someone can point me in the right direction as we're trying to get rid of swyx since we're tied down by limiting software and excessive licensing costs. Thanks! Geraint pri show spans shows all spans as up...

...874% --- Results after 2 passes --- Best: 100.000 -- Worst: 99.993 -- Average: 99.996193, Difference: 99.996683 [root at sitges bin]# service wanrouter stop Shutting down asterisk: [ OK ] Stopping Asterisk... Shutting down wanpipe4 interface: w4g1 Shutting down wanpipe3 interface: w3g1 Shutting down wanpipe2 interface: w2g1 Shutting down wanpipe1 interface: w1g1 Shutting down device: wanpipe4 Shutting down device: wanpipe3 Shutting down device: wanpipe2 Shutting down device: wanpipe1 No devices running, Unloading Modules [root at sitges bin]# service wanrouter st...

...0/0/1) -- Executing [691918892 at pbx1:2] Hangup("SIP/xtravoip200-009d24b0", "") in new stack == Spawn extension (pbx1, 691918892, 2) exited non-zero on 'SIP/xtravoip200-009d24b0' wanrouter status: wanrouter status Devices currently active: wanpipe1 wanpipe2 wanpipe3 wanpipe4 wanpipe5 wanpipe6 wanpipe7 wanpipe8 Wanpipe Config: Device name | Protocol Map | Adapter | IRQ | Slot/IO | If's | CLK | Baud rate | wanpipe1 | N/A | A101/1D/A102/2D/4/4D/8| 17 | 4 | 1 | N/A | 0 | wanpipe2 | N/A | A101/1D/A102/2D/4/4D/8| 17...

...dahdi_tool or dahdi_scan. I've just put a hardware loop on port 1. All the other ports are open. wanrouter status shows the expected result: Device name | Protocol | Station | Status | wanpipe1 | AFT TE1 | N/A | Connected | wanpipe2 | AFT TE1 | N/A | Disconnected | wanpipe3 | AFT TE1 | N/A | Disconnected | wanpipe4 | AFT TE1 | N/A | Disconnected | However: # dahdi_scan 2 [2] active=yes alarms=OK description=wanpipe2 card 1 name=WPE1/1 manufacturer= devicetype= location= basechan=1 totchans=31 irq=0 type=digital- syncsrc=0 lbo=0 db (CSU)/0-133 feet (...

...es=yes callwaitingcallerid=yes threewaycalling=yes transfer=yes canpark=yes cancallforward=yes callreturn=yes echocancel=yes echocancelwhenbridged=yes relaxdtmf=yes rxgain=0.0 txgain=0.0 group=1 callgroup=1 pickupgroup=1 immediate=no ;Sangoma A104 port 3 [slot:1 bus:1 span:3] <wanpipe3> context=from-cb group=3 echocancel=yes signalling=fxo_ls channel => 49-72 immediate=yes Extensions.conf: [from-cb] exten => s,1,DISA,no-password|internal [internal] include => sip-stations include => iax-trunks include => outbound [out...

...> 94-108, 110-124 the channel status *CLI> zap show status Description Alarms IRQ bpviol CRC4 wanpipe1 card 0 OK 0 0 0 wanpipe2 card 1 RED 0 0 0 wanpipe3 card 2 RED 0 0 0 wanpipe4 card 3 RED 0 0 0 1 19:33:14 NOTICE[17314]: chan_zap.c:6342 handle_init_event: Alarm cleared on channel 1 Mar 1 19:33:14 NOTICE[17314]: chan_zap.c:6342 handle_init_eve...

...to be safe I loaded the dahdi_dummy too *CLI> dahdi show status Description Alarms IRQ bpviol CRC4 wanpipe1 card 0 OK 0 0 0 wanpipe2 card 1 RED 0 0 0 wanpipe3 card 2 RED 0 0 0 wanpipe4 card 3 RED 0 0 0 DAHDI_DUMMY/1 (source: HRtimer) 1 UNCONFIGUR 0 0 0 The unreachable part is rather odd given that the two apps are...

I am connecting to a siemens hipath 4000 with dahdi 2.1.0.4 and asterisk 1.4.23 using a Te210P card. the phone guy is saying that the lines are reporting always BUSY. however on my end the status shows OK. Anyone seen this? Is there something different about connecting PRI to siemens hipath? system.conf shows: loadzone=us defaultzone=us span=1,1,6,esf,b8zs bchan=1-5 dchan=24

I'm trying to send CallerID info to a MetaSwitch system over a PRI. The MetaSwitch gets the info exactly as it is sent by Asterisk, but I think it might be having trouble with the Hexadecimal b1 that is being sent just before the first character of the CallerID Name. Does anyone know what the significance is of the b1 being sent here? Or, is there a way to make Asterisk not send the b1

...> > the channel status > > *CLI> zap show status > Description Alarms IRQ bpviol > CRC4 > wanpipe1 card 0 OK 0 0 0 > wanpipe2 card 1 RED 0 0 0 > wanpipe3 card 2 RED 0 0 0 > wanpipe4 card 3 RED 0 0 0 > > > > 1 19:33:14 NOTICE[17314]: chan_zap.c:6342 handle_init_event: Alarm cleared > on channel 1 > Mar 1 19:33:14 NOTICE[17314]: chan_zap.c:6342 h...