login | register
Wed 09 of Jul, 2008 [04:46 UTC]

voip-info.org

Discuss [13] History

Asterisk Avaya

Created by: mbranton,Last modification on Wed 17 of Aug, 2005 [20:15 UTC] by jpersofsky

Asterisk and Lucent Definity Integration release 6+


A quick and dirty explanation on how to integrate Asterisk with a Lucent Definity System via a PRI-ISDN connection.

This was initially done on a release 6 g3si, connecting to a stock Asterisk 0.7.0 system with Zaptel hardware.

On the Lucent you need an available TN464 circuit pack hooked up directly to the Zaptel hardware via crossover to a 120A2 CSU module, or use your own direct crossover cable. I recommend the csu if you have it.

On my system the TN464 circuit pack was installed at 01B15, replace as necessary.

T1 (24 channels)


1) After hooking up the Asterisk and Lucent hardware.

  • change ds1 01b15
  • framing mode: d4
  • line coding: b8zs
  • set the signaling mode to isdn-pri
  • set the connect: Network
  • Set protocol version to B (national)
  • Interface Companding: mulaw
  • near-end csu type: Other (for the crossover)

2) Add a new Trunk group.

  • add trunk-group next
  • direction: 2 way
  • service-type: tie
  • queue: 23
  • Tac: 7 (or an appropriate access code for your dialplan)

3) Add a signalling group to the Lucent

  • add signaling-group next
  • set the primary d-channel to the 24 line of your card, i.e 01B1524

4) Add the appropriate ports to the Trunk specification

  • add ports 01b1501 through 01b1523 with signaling-group set to the one previously defined.

5) Add the trunk to your dialplan

  • change dialplan

6) Configure Caller ID on the trunk

  • on rev 6 - change isdn pub

Now configure the Asterisk box


1) In zaptel.conf specify the channels i.e

 span=1,1,0,d4,b8zs
 bchan=1-23
 dchan=24
 defaultzone=us

2) zapata.conf

 switchtype = national
 overlapdial = yes
 signalling = pri_net
 channel => 1-23

Restart Asterisk and enjoy!
(:biggrin:)

Several important changes to note, protocol B is equivalent to national (set the switchtype to national)
Protocol A is equivalent to ni1 (national one)
5ESS switchtype does work with my revision Definity, but National is proving to be less troublesome.

If anyone has questions you can reach me at mab (at) pipeline (dot) com

E1 (32 channels):

At Avaya

1) After hooking up the Asterisk and Lucent hardware.

  • change ds1 01b15
  • line coding: hdb3
  • set the signaling mode to isdn-pri
  • set the connect: line-side
  • Set protocol version to B (national)
  • CRC: Y
  • Interface Companding: mulaw
  • near-end csu type: Other (for the crossover)

3) Add a signalling group to the Lucent

  • add signaling-group next
  • set the primary d-channel to the 16 line of your card, i.e 01B1516

4) Add the appropriate ports to the Trunk specification

  • add ports 01b1501 through 01b1515 and 01b1517 to 31 with signaling-group set to the one previously defined.

The rest of the configuration is the same.
At Asterisk:

1) In zaptel.conf specify the channels i.e

 span=1,1,0,ccs,hdb3,crc4
 bchan=1-15
 dchan=16
 bchan=17-31
 defaultzone=us

2) zapata.conf

 switchtype = national
 overlapdial = yes
 signalling = pri_net
 group = 1
 channel => 1-15
 channel => 17-31

Using the Avaya in DS1FD stations mode:

Use this mode if you want to transfer the call back into your Avaya switch (using Asterisk as an IVR)

The DS1 should be configured:

B8ZS
ESF
Robbed Bit
120A CSU

24 DS1FD stations...
I didn't try to get it working with E1 mode.

zaptel.conf (2 TE110P cards in T1 mode)
loadzone=us
defaultzone=us

span=1,0,0,esf,b8zs #card 1 TE100P
fxsks=1-24
span=2,0,0,esf,b8zs #card 2 TE100P
fxsks=25-48


zapata.conf (you may want to change some options)
[trunkgroups]

[channels]

language=en
usecallerid=no
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=no
echotraining=800
rxgain=0.0
txgain=0.0
group=0
callgroup=1
pickupgroup=1
immediate=yes
signalling=fxs_ks
switchtype=national
prilocaldialplan=unknown
context=from-avaya
group=1
channel => 1-48




Comments

Comments Filter
222

333hi there.... asterisk and avaya g3si r11

by digo1006, Thursday 24 of May, 2007 [11:54:12 UTC]
Is it possible to tie asterisk box with TDM 400P (2 FXO and 2 FXS) into a tie trunk of AVAYA PABX G3si r 11 using CO trunk... If yes, please guide me and post a procedure here in integration of the system. I need it badly.. Thanks in advance...
222

333hi there.... asterisk and avaya g3si r11

by digo1006, Thursday 24 of May, 2007 [11:38:29 UTC]
Is it possible to tie asterisk box with TDM 400P (2 FXO and 2 FXS) into a tie trunk of AVAYA PABX G3si r 11 using CO trunk... If yes, please guide me and post a procedure here in integration of the system. I need it badly.. Thanks in advance...
222

333Troubleshooting Asterisk and Avaya Connectivity

by dtennant, Saturday 03 of March, 2007 [05:02:05 UTC]
I am newbie at both Asterisk and Avaya and got both connected with the help of these pages. Thanks guys. However, the road was still a bit bumpy and so I'd like to share a few troubleshootings tips for the uniniated. Using AsteriskNOW (with single port t1 card( and Avaya Defnity G3siv9 (TN767E card). Our purpose for this integration is three-fold: 1. Use the Asterisk as centralized Voicemail to exising Avaya users, 2. IAX-enable Avaya Definity and use as gateway for new Asterisk deployments to existing voice network. 3. Compare the availability/performance of Asterisk vs. Avaya.

Tip 1. Use the zttool utility. It let's you know if your cards are talking properly and have sync'd up with/without any alarms. If you have a RED alarm, wiring's no good. YEL alarm suggests something's happening. OK {ie no alarms} indicates your wiring is perfect. If the alarm toggles between OK/YEL alarm over say a 30 second period adjust the wiring until there's no toggling and OK remains. For my Definity circuit pack TN767E wired to a S110 block, I obtained steady OK with (T568B wiring) WHT/BLU:BLU at position/pair 22 and WHT/ORG:ORG at position/pair 23. The end at the S110 was a straight T568B wiring

Tip 2. Check the LEDs. Layer 1 gave me a bit of a trouble and the LEDs gave good visual clues about what was happening. Reseating Avaya card TN767E in its slot helped too. Also verify that the amphenol cable is well connected and observe the third LED from top on the card for some sign that it is has initialized completely and when initialized, that it attempts to sync with the Asterisk card. If it lights up a steady ORANGE you're good to go; if not your are not seeing the Asterisk card and Layer 1 issues still persist.

Tip 3. UDP not required. We simply do digit manipulation on the trunk and route-pattern to exchange calls between the PBXes.

End.

222

333TN464F, TN464GP or TN464HP

by jeffwells, Tuesday 12 of December, 2006 [03:29:03 UTC]
Are there any differences in these cards or is it just a revision difference?

Now I have a Definity G3 R11. Does it qualify for a HP? Do I really need a HP for connection to an Asterisk? TN464F are much cheaper on the refurbished market.

Regards,
Jeff
222

333Connect Avaya TN464 and TE110P

by TheBigOne, Thursday 04 of May, 2006 [13:37:23 UTC]
Hi to all,
i want to know what is the pin configuration to connect by amphenol cable to TE110P. I think that make mistake about connection because signaling group on Avaya don't stay up (seems that DS1 doesn't sync with PRI Card).

Thanks for any help
Emanuele
222

333simplest and most effective integration IMO

by dolesec, Saturday 11 of March, 2006 [16:14:47 UTC]
we've published our experiences here

http://www.landair.com/docs/asterisk-definity.htm


222

333DTMF Tones Missing or Not Detected

by kebl0155, Friday 24 of February, 2006 [18:53:47 UTC]
We had an issue connecting * to an Avaya InDEX switch (release 9.1) over E1 ISDN PRI here in the UK.

We managed to get calls going through the system, but could not get * to recognise DTMF on calls origniating from the Avaya switch.

At first we thought it was the Avaya switch not sending tones, but closer inspection revealed that * was simply ignoring the first 31 tones (exactly) in any call sent.

We solved the problem using Translation in the Avaya Route List to send an extra 31 DTMF '1' tones before user tones were entered.

Weird, huh?
222

333No UDP

by dolesec, Tuesday 24 of January, 2006 [04:21:57 UTC]
anyone done this without using the Uniform Dial Plan
222

333Got it working!

by skirk, Thursday 08 of December, 2005 [16:53:42 UTC]
SUCCESS! The notes pages here got me started, but by far were not complete enough for someone who's somewhat new but a quick learner (me). Asterisk was a cinch for me, but I was weak on the Definity side. Working with my telecom vendor (who maintains our Definity) for about 20 mins on the phone I got Asterisk fully integrated with my Definity!

TN767E card, PRI-crossover to a Wildcard TE110P.

I've recorded my experiences & a full walk-through here.

Steve
222

333Re: Re: Uniform Dialing plan:

by elchubi, Tuesday 05 of July, 2005 [18:20:32 UTC]
I have a tn2464 DS1 card. G3 software version is 11

REgards,