Trixbox 1.1 / Digium TE110P / AdTran 750 / AP 1200

hello, i think you check the FXO and outbound trunks first. if still can not do that, please contact me:[email protected]. maybe ssh is a way to check that.
regards!
james.zhu

james

to be sure i did the right thing.

Thru freepbx i deleted the outbound trunk and updated. Then i re-create the outbound routes again and update again. i still get

-- Executing Macro("Zap/24-1", "hangupcall") in new stack
-- Executing ResetCDR("Zap/24-1", "w") in new stack
-- Executing NoCDR("Zap/24-1", "") in new stack
-- Executing Wait("Zap/24-1", "5") in new stack
== Spawn extension (macro-hangupcall, s, 3) exited non-zero on 'Zap/24-1' in macro 'hangupcall'
== Spawn extension (macro-hangupcall, s, 3) exited non-zero on 'Zap/24-1'
-- Hungup 'Zap/24-1'

i am emailing you my log in for ssh

thanks

James

thanks for coming into my box.

I did took up your recommendation in downloading trixbox-openvox.

During installation, trixbox-openvox did find AP1200 and TE110P. however minor modification needed to be done on the TE110P. I am using Adtran 750 so my signalling is fxo_ks.

Everything is working fine now, however there is one minor problem though.

When i reboot my box initially, trixbox failed to detect AP1200 but successfully detect TE110P. Subsequent reboot trixbox found both cards.

thanks

hello, hb:
it is a good news that eventually your system starts running. As what you mentioned about the a1200p driver detection problems, i think the a1200p device id can not be found in your server. it is due to server hardware design. it will start for first time, but not for second boot. subsequently, third time, the system be back to normal. We will solve that problem soon. you also can check that using: lspci -vvvvvvvvv,

it will show different device IDs for A1200P:

---

00:0a.0 Communication controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface
Subsystem: Unknown device 95d9:0003
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (250ns min, 32000ns max)
Interrupt: pin A routed to IRQ 11
Region 0: I/O ports at 9400
Region 1: Memory at de001000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI+ D1- D2+ AuxCurrent=55mA PME(D0+,D1-,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

---

Show IDs here:
0x9100,
0x9519,
0x95D9,
0x9500,
0x8519.
if the ID is not one of those IDs, please report to us. we will patch to new driver. the picture shows that there are two A1200P cards in this system and also shows the device IDs.
Regards!
james.zhu

I did a lspci -vvvvvvv and i got the following

05:02.0 Communication controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface
Subsystem: Unknown device 9100:0003
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64 (250ns min, 32000ns max)
Interrupt: pin A routed to IRQ 177
Region 0: I/O ports at d800
Region 1: Memory at fe6be000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI+ D1- D2+ AuxCurrent=55mA PME(D0+,D1-,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME+

05:04.0 Network controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface
Subsystem: Unknown device 795e:0001
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64 (250ns min, 32000ns max)
Interrupt: pin A routed to IRQ 161
Region 0: I/O ports at dc00
Region 1: Memory at fe6bf000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI+ D1- D2+ AuxCurrent=55mA PME(D0+,D1-,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-


again, i have 2 cards. 1 x TE110P and 1x 12 Port A1200P FXO

hello, hb:
if you got the Subsystem: Unknown device 9100:0003. it should work. you can check the status that the system does not detect A1200P and in that environment, you check the ｄｅｖｉｃｅ ID　again.　if the device ID　is one of those IDs i given you, please report us.
Regards!
james.zhu