Trixbox + Avaya Definity Integration
Submitted by dkelm on Tue, 06/12/2007 - 6:52am.
Before I go into the details on this system, I just want to say how easy overall it was to get this going using Trixbox. Also it was much easier getting Trixbox to talk to our Avaya system then getting the Avaya system working with Trix.
Anyway on to the story. About 3 months ago we needed to add another pri line to our Avaya Definity System. We are a call center with over 100 phones in addition to predictive dialers at this site. We needed this because we where running out of lines.
After going over the cost of the of just adding a board and increasing port licenses, versus the first steps in getting off the Definity (cost reasons these things are reliable but expensive as hell) we decieded to go the Asterisk/Trixbox route. I had to really push this idea through, but at this point they are very glad I did.
What we did was order a nice supermicro dual xeon board w/ a 3U case and added 2 Quad Core Xeons (1.6ghz) and 4 GB of ram, put in a LSI SAS controller and used western digital raptors and 500 gb wd drives for call record storage. We split the main OS in raid 1, Asterisk in Raid 1 and apache and mysql on a Raid 1 array. We also purchased a Sangoma 108 and 101 board for interconnections.
We have 4 PRI lines coming out of our Defintiy into our Trixbox server and 4 pri lines coming into our Trixbox machine. We are using Trixbox for Call Queues, IVR, Call Recording and new extensions as we add them. We also have a Point-To-Point between our office and another office using the A101.
We are now also running 20 Polycom IP 320 phones and 1 Aastra 57i.
We currently has 75 extensions that are set to always call record. We are handling this by using a ram drive and then running a script that moves and then compresses the files down to mp3 files.
The last major thing that we did was write a wrapper around our contact system and setup buttons to initiate calls and leave messages through the asterisk machine.
Overall the response has been very positive and the system has been very stable. The load average has not gotten above 2.0.
We are currently running Trixbox 2.2
If anyone would like more information on our integration setup I would be happy to share.
Thanks.
Here is a site that was
Thu, 06/14/2007 - 12:55pm
Here is a site that was pretty helpful to me on the Avaya side of things:
http://blog.random-ether.net/weblogs/lock/2005/12/avaya_definity_...
This site doesn't really cover the other side of things with Trixbox so I will go into some detail there.
As I said above we have a Sangoma A108 that we are using with 4 PRI lines coming in and 4 PRI lines from it connecting the Trixbox machine and the Definity. The first thing you want to make sure is that you have the card clocking the 4 links to the Definity off of 1 on the incoming PRI lines. If you don't do that you will get so clocking problems after the machine has been up awhile.
I have all calls routing through the Trixbox machine to the Definity. What I do is setup an extension on the trixbox machine for each extension on the Definity and assign it as ZAP/g2/extension# as a ZAP device. This will cause Trixbox to call the first available channel in Zap group 2 (my trunks that link the 2 systems). I do this because I want to record all the inbound to most my extensions. I also setup a second group of extensions that contain the DID that the phones send out from the Definity. This can be changed, but mine are all set to the DID so I didn't change it. I did it this way because I am not the strong on the Definity side of things, just good at figuring things out as I need to.
If you need more help let me know and I can try and provide it.
Thanks for sharing the info.
Thu, 06/21/2007 - 10:37am
Avaya <-> Asterisk
Sun, 07/08/2007 - 3:54pm
I have integrated Avaya CM 3.x on S87XX's with Asterisk using h.323. I'm working on building a document with screenshots, but for those looking for a quick answer here is the short story...
Avaya needs minimum 1 C-Lan and 1 Medpro. Build a signaling group using h.323 as the medium. Use C-lan as the near end and asterisk as the far end, port 1720 both sides...
Build a trunk group on avaya (type=isdn and ip as the medium). Use the UDP table to get calls routed towards this tg. make sure you modify ip-network-region and ip-codec-set to match asterisk codec set. If your on a lan, set ip-codec set to g.711u, works great.
Asterisk is very simple... grab the ooh323.conf file from the /etc/asterisk/samples directory and place it in /etc/asterisk. Use an example from the bottom of the file and just plug in your avaya information, host ip, etc. Also, make sure you comment out allow=gsm as avaya does not like it. Create custom trunk and in the custom dial string add.. OOH323/$OUTNUM$@your.avaya.ip.address:1720 ( the c-lan ip address).
- Matt
More info Please
Tue, 07/24/2007 - 3:42pm
Thanks for sharing the info on the interconnect you did with the T1's. Do you or anyone else have any recommendations on interconnecting with a Sangoma A102 dual E1 card in the Asterisk box to an Avaya Definity?
The first question I have is should this be just straight TDM or TDM & WAN support?
Second, what is the signalling from the Avaya for E1/PRI?
Any help would be appreciated.
Regards,
C
h.323 trixbox to definity
Fri, 11/23/2007 - 7:30am
hi!
we've been trying to trunk trixbox and an avaya 8300. we were successful in linking the 2 machines BUT can only have audio one way. the avaya extensions can hear the trixbox audio but the the trixbox can not hear the avaya phones. can i ask for your complete screenshots and configs?
how do i find and "make sure you modify ip-network-region and ip-codec-set to match asterisk codec set"
codec set
Fri, 11/23/2007 - 8:19am
< disclaimer > well, first make sure if your "testing" this out that you dont mess up your existing network region or codec sets... The last thing you want to do is bring your avaya production system down or cripple it. < / disclaimer >
when you specified the c-lan card in the signaling group, that board is in an "ip-network-region"...
do a "display or change ip-network-region x", ip codec set is listed near the top left.
when you do a "display ip-codec x" it will list your existing codec sets and in the order they should be tried.
avaya has g.729 built in, but trixbox doesnt, ..trixbox has gsm built in, but avaya doesnt, so save yourself some time/energy and set the first code to 711u (avaya side) and allow=ulaw(trixbox side)
UPDATE---- My success was limited to the phones/trunks being in the same G650 cabinet as the MedPro AND C-Lan board. If a call was sent to a phone or trunk located in another cabinet, resulting in the use of another Medpro, 1 way audio occurs. After spending days on this issue with no resolution, I've set the project aside.
- Matt Mitchell
VoipGarageSale.com Sell Your Unused Voip Equip.
TyCal.com Avaya & Asterisk Communications My Jeep -> powered by TB 2.2.8
avaya s8300/g700
Mon, 11/26/2007 - 8:32pm
hi matt!
just to let you know, we are using a S8300 installed in a G700. according to our tech guys, the s8300 has a built in LAN and there is no Medpro involved and everything is indeed inside one chassis. i am hopeful this gives you an idea of the setting here. we followed exactly the settings and instructions on this link: http://www.tek-tips.com/viewthread.cfm?qid=1163320&page=5
as previously discussed, we got the phones to connect but audio is only one way. the trixbox to trixbox phones do not have a problem. trixbox can hear avaya but not the other way around. still hoping you can send the configs that you have so we can try it out ourselves... at this point anything that may work will be tried.
by the way, we are based in Cebu, Philippines and any help would be greatly appreciated.
thanks ....jojo
I'll get you my config's
Mon, 11/26/2007 - 10:01pm
I'll send you the config's that I have ... the setup is different between a G650 and G700, but the premise is the same.... we'll see... I wont have access to them until about 11am EST...
- Matt Mitchell
VoipGarageSale.com Buy - Sell Your Unused Voip Equip.
TyCal.com Avaya & Asterisk Communications
My Jeep -> powered by TB 2.2.8
no audio trouble?
Tue, 11/27/2007 - 1:24am
configs Avaya & Trixbox
Tue, 12/18/2007 - 7:09pm
Hi Matt:
I was wondering if you can send the configs for Avaya & Trixbox integration. And also some screenshots if available....
Do you have any idea how can I record calls with trixbox for the avaya extensions, using a trunk-to-trunk configuration (no E1/T1 card between boxes) ?
Thanks in advanced. Your help will be very appreciated.
Hector Bravo
hbravo@newtechgt.com
Just did this integration with a Definity G3 / TE110p over PRI
Fri, 04/25/2008 - 11:52am
I know some of this integration has involved H.323 trunking, but if that is not an option for your Avaya, the PRI integration is possible.
This guide is spot on for how to do it:
http://www.voip-info.org/wiki-Asterisk+Avaya
A couple notes that would have saved me lots of time:
1. You need a T1-crossover cable between the TN464 (or equivalent) Avaya PRI card and the Asterisk card to make this work. Be careful with how you wire this. Between the two systems, pins 1 and 2 need to be crossed with 4 and 5. Some telco guys wire the cross directly onto the back of the amphenol connector. Don't cross your cross!
For reference, on a 50 pin telco connector, the wires line up as follows:
Cat 5 -> 50 pin telco / Amphenol
Pin 1 -> Pin 22
Pin 2 -> Pin 47
Pin 4 -> Pin 23
Pin 5 -> Pin 48
If you don't get a yellow light on the TN464 and a green one on the TE110p (without configuring any of the software yet), you are having layer 1 issues. Check your cable.
2. Avaya is extremely restrictive in handing rights out to their switches (such as rights to busyout trunks, ports, or DS1s). To do this with minimal pain, set up both ends as the guide suggests, try to bring them up, and then pull the TN464 card out for 30 seconds and re-seat both it and the amphenol connector on the back. That should bring up the D channel.
Josh
Member Since:
2007-03-21