[cisco-voip] ELAI Avaya Look Ahead with Cisco CUBE in between?

[Nick Matthews]

The real problem is that they return a 486 busy.  This can be a really bad
idea depending on how complex the dial plan is.  For instance, say numbers
1000-1999 are at PBX A, and 1500 goes to PBX B.  If you enable re-routing on
busy, then the more specific match is B, returns busy, and matches the less
specific route to A.  You could enable 'huntstop' on all the dial peers to
avoid this, or design the dial plan to have no more than 1 match for numbers
that should not re-route.

The recording I have no real good ideas for.  The only way to make a new
call is to put a loopback T1 on the router, where then it is doing TDM-SIP
conversion again.  Otherwise you're looking at a custom TCL application.

-nick

On Wed, Dec 15, 2010 at 6:08 PM, Erin Mikelson <ekmikelson at hotmail.com>wrote:

>  Interesting scenario:
>
> Calls delivered by Avaya A to Toll Free number. Avaya A wants look head
> enabled so that if they deliver to the first route group, and call does not
> complete (i.e. agents are busy or unavailable) the call is sent to the other
> route group. Route group in this case is another Avaya system.
>
> Calls come in via TDM to an AS5400. the AS5400 converts to SIP and sends to
> Avaya. Avaya sends a SIP 486 busy here message when an agent is unavailable.
> The AS5400 relays back and the caller hears a busy message. Instead, they
> want to be able to forward the message to another system to be answered by
> an agent.
>
> Apparently, they are looking for a specific UUI message to handle the call.
> Also, apparently, this works in a pure TDM environment.
>
> To throw in another loop, we want the capability to record the call, which
> uses SIP as well, and terminates the first leg of the call, creates a new
> call and sends the call to Avaya.
> Meaning, the LAI won't work.
>
>
> any ideas? I'm a cisco person, not an Avaya person.
>
> Thanks!
> Erin
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20101215/93b3d5c0/attachment.html>