vicidial.org

Hello everybody, does someone know if bri cards are compatible with vicidial's auto-dial (recognize NA, answer, busy, etc)?

We have this card:
http://www.openvox.com.cn/products_deta ... =32&id=103

and these are the features:
Features:
* 8 integrated S/T interfaces
* ITU-T I.430 and TBR 3 certified S/T ISDN support in TE and NT mode
* Integrated PCI bus interface (Spec.2.2) for 3.3V and 5V signal environments
* DTMF detection on all B-channels
* Multi party audio conferences bridge
* Onboard power feeding for 8 NT Port
* PCM bus connectors daisy chaining
* Each of the 8 ports can be independently configured for TE or NE mode
* Application ready: Use Asterisk to build your IP-PBX/Voicemail system

Good question, I have never tried one so I don't know. There is really no easy method to do this in the USA where we are located.

Wow, so I will be the first!
Theorically they have to work: they use the same techology of PRI lines

In ISDN, there are two types of channels, B (for "Bearer") and D (for "Delta"). B channels are used for data (which may include voice), and D channels are intended for signaling and control (but can also be used for data).

There are two ISDN implementations. Basic Rate Interface (BRI), also called Basic Rate Access (BRA) in Europe — consists of two B channels, each with bandwidth of 64 kbit/s, and one D channel with a bandwidth of 16 kbit/s. Together these three channels can be designated as 2B+D. Primary Rate Interface (PRI), also called Primary Rate Access (PRA) in Europe — contains a greater number of B channels and a D channel with a bandwidth of 64 kbit/s

is this the same one?

Does VICIDIAL work with BRIstufft Asterisk installations?
Yes, but because of the way that the BRIstufft changes the formatting of the Asterisk uniqueid for calls you have to execute the following MySQL statements to alter the database to allow the longer uniqueids:

ALTER TABLE live_inbound MODIFY uniqueid VARCHAR(40) NOT NULL;
ALTER TABLE live_inbound_log MODIFY uniqueid VARCHAR(40) NOT NULL;
ALTER TABLE live_inbound_log MODIFY uniqueid VARCHAR(40) NOT NULL;
ALTER TABLE vicidial_manager MODIFY uniqueid VARCHAR(40) NOT NULL;
ALTER TABLE vicidial_live_agents MODIFY uniqueid VARCHAR(40) NOT NULL;
ALTER TABLE vicidial_auto_calls MODIFY uniqueid VARCHAR(40) NOT NULL;
ALTER TABLE call_log DROP PRIMARY KEY;
ALTER TABLE call_log DROP INDEX uniqueid;
ALTER TABLE call_log MODIFY uniqueid VARCHAR(40) PRIMARY KEY UNIQUE NOT NULL;
ALTER TABLE park_log DROP PRIMARY KEY;
ALTER TABLE park_log DROP INDEX uniqueid;
ALTER TABLE park_log MODIFY uniqueid VARCHAR(40) PRIMARY KEY UNIQUE NOT NULL;
ALTER TABLE vicidial_log DROP PRIMARY KEY;
ALTER TABLE vicidial_log DROP INDEX uniqueid;
ALTER TABLE vicidial_log MODIFY uniqueid VARCHAR(40) PRIMARY KEY UNIQUE NOT NULL;


or not?

BRIstufft does not necessarily use BRI lines, they person using it that I posted that too was actually using SIP trunks only.

Maybe this can help?
B800P-User-Manual-bristuff
http://www.openvox.com.cn/downloadsFile/1195091231.pdf

But I was thinking... If I use this card on a pure asterisk where I create a SIP/IAX trunk to vicidial?
In this way Vicidial will see only a sip trunk leaving the card management to the other asterisk!

Thats a good idea anyway.

Just create a gateway.