[Asterisk-Users] Asterisk & Avaya Legend

[Sean Cook]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
Yeah... we went through the same thing... our problem was working with
asterisk it was "Oh cool!" then trying to make the legend work was "WTF!".

Our setup is on the back side... legend still connects via PRI to the
PSTN, but we have asterisk running as a tandem off a third PRI.  Many
of the challenges are the same.  I wish we had put the money up and
gotten a 4-port T1 card and done things the way you are.  We would
have caller id and our voicemail would be much more transparent.  We
had to put a channel bank with FXO to replace the Audix voicemail
system.  While it works better than the audix system, there are some
things that I wish it did that asterisk does natively.

Sean

Lacy Moore - Aspendora wrote:

> Thanks Sean!
>
> Fortunately, I don't think I will have to worry about passing
> extensions back and forth between Asterisk and the Legend. But,
> I'm glad to know that it is possible, if the situation arises. We
> don't have that many users. My concern is just making sure that
> the two can coexist for a while. We're going to use the savings
> from switching to the PRI to purchase the rest of the equipment,
> and I'll be keeping everyone connected to the Legend. Once we are
> able to start purchasing the IP phones, I'll move one company at a
> time over. During this transition, we shouldn't have to worry
> about extension to extension going through both.
>
> Light bulb just went off. Looking at this:
>
> [from-pstn] exten => 482,1,Dial(Zap/g0/482)
>
> So if I have all 10 digits being passed and someone placed a call
> to one of our DIDs, for example, 281-604-0532, the dial plan would
> look like:
>
> [from-pstn] exten => 2816040532,1,Dial(Zap/g0/2816040532)
>
> If so, I sure wish the Legend was that easy to setup! I'll
> probably have to get someone to set it up. The card came in
> yesterday for the Asterisk server, so I'll be able to start playing
> with things. I'm guessing I can send my own DID information to the
> Legend so that before the PRI even gets installed I can have
> everything set up and waiting.
>
> Honestly, working with Asterisk is one of the "Oh cool!" moments.
>
> On 3/23/06, *Sean Cook* <scook at kinex.net <mailto:scook at kinex.net>>
> wrote:
>

>
>> Now, here is what I'm not sure of at this moment. For the time
>> being, is it possible to just pass the PRI through the Asterisk
>> to the Legend? Will there by any type of dialplans or anything
>> that need to be created? Will it pass the DID information
>> through? I was trying to look at this from the perspective that
>> the Legend will be a channel bank, but I don't think that's a
>> correct assumption. I think this more closely fits tying two
>> Asterisk servers together with a T1, but I haven't been able to
>> find any info on this.
>
> basically you will receive the DID information and pass it straight
> through to the DS1
>
> [from-pstn] exten => 482,1,Dial(Zap/g0/482)
>
> It should be pretty straight forward... our setup is similar but
> the asterisk system is configured internally not between the telco
> and legend.
>
>> Can anyone offer any pointers, or maybe point out anything
>> obvious that I am missing? Or, even confirm that what I'm trying
>> to do is possible. I have the two port card on order and would
>> like to play with it before the PRI gets installed. I don't like
>> working in theory on this, I'd feel much better with the
>> equipment in hand, even without the PRI, I can still setup a VoIP
>> account and make sure that I can pass the call through the
>> Asterisk into the
> Legend.
>
> The only thing that I am not sure of is how the legend will be
> passing additional extension across the PRI so that you can dial a
> local extension that is on the Asterisk side... I suppose if you
> set up 4000-4999 in UDP and pass it on the PRI you should be pretty
> good to go, provided that you have did's for every extension set up
> within the legend. (even if they are fake did's not necessarily
> from the telco)
>
>
>> Assuming all this works, I think just having Asterisk in there
>> would solve one problem. It seems that I could set up a dial plan
>> so that if I dial 9 it would use the caller ID of one company,
> dial
>> 8 to use the caller ID of another, etc. On the user side, they
>> would have to dial 9 twice to place an outgoing call (since the
>> Legend requires a 9 for an outside line), but I think I could
>> also set the dialplan up so that if the number dialed is a
>> standard number, it would just use a generic caller ID number.
>
> Right but the legend also provides UDP that will allow you to
> specify a range for extensions to be passed back and forth... users
> that dial 9 and get an outside trunk will be able to match with
> your dialplan
>
> [from-merlin] exten => 9NXXXXXX,1,Dial(ZAP/g1/${EXTEN:-1}) ; where
> group=1 is your telco trunk exten => 4001,1,Dial(SIP/4001)
>
>
>
>
>> I guess I'm still confused as whether Asterisk will pass the DID
>> information onto the Legend. If someone could point me in a
>> direction regarding this, I'd appreciate it. I haven't found
>> anything, which makes me worried this isn't possible (whether
>> because of technology or Asterisk).
>
>
> All you need to know is the digits that are being passed and how
> they are mapped in the legend... asterisk can mimic this however
> you want...
>
>

_______________________________________________
- --Bandwidth and Colocation provided by Easynews.com
<http://easynews.com/> --

Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users



> ----------------------------------------------------------------------
> _______________________________________________ --Bandwidth and
> Colocation provided by Easynews.com --

> Asterisk-Users mailing list To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-users
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
 
iD8DBQFEI/J0y9wPyZpnL2URAjUnAKClnFqxZvp7urn+EvFC3H2eYyWIjwCgjMid
bW8MAbFNvvwal7ABHfOVPZc=
=GJa/
-----END PGP SIGNATURE-----