[Asterisk-Users] Avaya/Lucent Definity -> Asterisk interop question

[Steve Kann]

Robert,

    I'm actually looking into the same thing as you.
   
    I have (and have had) them talking to each other OK for some time.  
The Wiki describes how to do that.

    The basic setup will allow calls from asterisk -> Definity OK.  I 
have some outgoing calls routed to asterisk via ARS on the definity side.

    I'd really like to figure out a way to map a set of extensions on 
the definity to automatically be handed off to asterisk.   For example, 
have all extensions in the range 4900-4999 end up being calls to 
asterisk with the extension number.

    I don't see an easy way to do that, though.  The best idea I have so 
far is to make a whole set of extensions in that range with "X" ports, 
make an ARS route which maps 1-200-999-XXXX to get rewritten to XXXX and 
get routed via the Asterisk-bound PRI, and then manually set 
call-forwarding for each of the 49XX extensions to 1-200-999-49XX.

But, this seems like quite a PITA to have to make all those extensions 
and call-forwarding rules.  I'm also not sure what else I'm missing by 
doing this, how these extensions will act in a hunt group, etc.


Here's my config, if you like.

non-commented lines in /etc/zaptel.conf:

    span=1,1,0,esf,b8zs
    bchan=1-23
    dchan=24

    loadzone = us
    defaultzone=us


non-commented lines in /etc/asterisk/zapata.conf:


    [channels]
    context=incoming
    switchtype=national

    signalling=pri_net
    rxwink=300              ; Atlas seems to use long (250ms) winks
    usecallerid=yes
    hidecallerid=no
    callwaiting=yes
    callwaitingcallerid=yes
    threewaycalling=yes
    transfer=yes
    cancallforward=yes
    callreturn=yes
    echocancel=yes
    echocancelwhenbridged=yes
    rxgain=0.0
    txgain=0.0
    group=1
    immediate=no



    context = incoming
    channel => 1-23



-SteveK




Robert.Kelly at ebimed.com wrote:

>Calling all Definity admins,
>Got a few questions about Definity -> Asterisk interoperability.
>1) What are the options for integration? Can I hand off extensions from the
>Definity and vice versa?
>2) Anybody have any working configs they would like to post?
>
>I've found and read the legacy integration on the wiki about the two
>systems. I've also googled and found a few threads that were cured by
>finding working hardware.
>I know our hardware works.
>I've got a box running Suse 9.1 (2.6.5 kernel) with a CVS of zaptel, libpri
>and asterisk.
>Everything compiled and installed fine and yes I did a 'make linux26' for
>zaptel.
>The box has a T100P card hooked up to a csu on the Definity with a patch
>cable.
>When I load wct1xxp and zaptel and do a ztcfg -v all channels come up, but
>I get a pulsing orange light. (normal ?)
>On the Definity side, the 464 has red lights pulsing on 2 and 4.
>
>Disclaimer: I'm not the Definity admin so I barely know what I'm talking
>about on that side.
>The idea is to hook up the two using pri and hand off some extensions to
>asterisk for ivr, iax etc. and to have some sip clients route calls to the
>Definity.
>Any help through configs, urls on either end would be greatly appreciated.
>
>Thanks in advance,
>Rob
>                                   
>  Robert Kelly                     
>                                   
> Communications                    
>    Manager                        
>  Information                      
>    Systems                        
>                                   
> (Embedded      EBI L.P.           
> image moved to Parsippany, NJ     
> file:          07054              
> pic29463.jpg)  973·299·9300 x2015 
>                                   
>                                   
>                                   
>
>
>
>  
>
>
> ------------------------------------------------------------------------
>

-------------- next part --------------
Skipped content of type multipart/related