asterisk users - Jul 2019 - Doing weird bouncing of IAX trunk calls on purpose

Ok, so this might seem weird, but hang with me on this. I have two sites, Indy
and Lafayette that each have their own Asterisk server. They each have their own
outside PRI line. They are also trunked internally via and IAX tunnel over a
private fiber line.

I've recently been asked to have the calls incoming to Indy, forwarded to a
group in Lafayette (only during the day, so can't be permanent) to answer
the incoming calls. Well naturally, more of the calls are then attended
forwarded/blind forwarded back down to the Indy server.

So we basically have a call coming into the Indy asterisk, being forwarded via
IAX to Lafayette, answered, then forwarded back down to Indy.

Most of it seems to work fine, as you'd expect. I'm getting some grief
from users saying there are weird things happening. My gut feeling, knowing the
people involved, is that it's a user issue.

Does it keep all the connections open every which way, or can the Indy server be
smart enough to just join the two channels and take Lafayette out of the loop?

Thanks!

Travis
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20190726/87975111/attachment.html>

Just had our IAX tunnels from the main server go bad again. Basically it thinks
it can't reach them on the network anymore to register. IAX reload does
nothing to help. Reloading/restarting asterisk service fixes it instantly. I
notice a couple channels on the IAX tunnel are stuck on in "core show
channels" and can't be hung up.

Any ideas? This just started a month or so ago when we started forwarding all
calls as stated below. /shrug

From: asterisk-users <asterisk-users-bounces at lists.digium.com> On
Behalf Of Ryan, Travis
Sent: Friday, July 26, 2019 11:01 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion <asterisk-users
at lists.digium.com>
Subject: [asterisk-users] Doing weird bouncing of IAX trunk calls on purpose

Ok, so this might seem weird, but hang with me on this. I have two sites, Indy
and Lafayette that each have their own Asterisk server. They each have their own
outside PRI line. They are also trunked internally via and IAX tunnel over a
private fiber line.

I've recently been asked to have the calls incoming to Indy, forwarded to a
group in Lafayette (only during the day, so can't be permanent) to answer
the incoming calls. Well naturally, more of the calls are then attended
forwarded/blind forwarded back down to the Indy server.

So we basically have a call coming into the Indy asterisk, being forwarded via
IAX to Lafayette, answered, then forwarded back down to Indy.

Most of it seems to work fine, as you'd expect. I'm getting some grief
from users saying there are weird things happening. My gut feeling, knowing the
people involved, is that it's a user issue.

Does it keep all the connections open every which way, or can the Indy server be
smart enough to just join the two channels and take Lafayette out of the loop?

Thanks!

Travis
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20190731/1ad5172e/attachment.html>

Not to divert the thread from the original question. But have you
considered switching the trunk to SIP? It's highly personal preference. But
I haven't used IAX2 between asterisk boxes in years simply because of
weird™ issues. SIP being more widely accepted protocol from all points of
reference (Like router manufactures SIP ALG..etc).


On Wed, Jul 31, 2019 at 10:49 AM Ryan, Travis <RyanT at oscarwinski.com>
wrote:
> Just had our IAX tunnels from the main server go bad again. Basically it
> thinks it can’t reach them on the network anymore to register. IAX reload
> does nothing to help. Reloading/restarting asterisk service fixes it
> instantly. I notice a couple channels on the IAX tunnel are stuck on in
> “core show channels” and can’t be hung up.
>
>
>
> Any ideas? This just started a month or so ago when we started forwarding
> all calls as stated below. /shrug
>
>
>
> *From:* asterisk-users <asterisk-users-bounces at lists.digium.com>
*On
> Behalf Of *Ryan, Travis
> *Sent:* Friday, July 26, 2019 11:01 AM
> *To:* Asterisk Users Mailing List - Non-Commercial Discussion <
> asterisk-users at lists.digium.com>
> *Subject:* [asterisk-users] Doing weird bouncing of IAX trunk calls on
> purpose
>
>
>
> Ok, so this might seem weird, but hang with me on this. I have two sites,
> Indy and Lafayette that each have their own Asterisk server. They each have
> their own outside PRI line. They are also trunked internally via and IAX
> tunnel over a private fiber line.
>
>
>
> I’ve recently been asked to have the calls incoming to Indy, forwarded to
> a group in Lafayette (only during the day, so can’t be permanent) to answer
> the incoming calls. Well naturally, more of the calls are then attended
> forwarded/blind forwarded back down to the Indy server.
>
>
>
> So we basically have a call coming into the Indy asterisk, being forwarded
> via IAX to Lafayette, answered, then forwarded back down to Indy.
>
>
>
> Most of it seems to work fine, as you’d expect. I’m getting some grief
> from users saying there are weird things happening. My gut feeling, knowing
> the people involved, is that it’s a user issue.
>
>
>
> Does it keep all the connections open every which way, or can the Indy
> server be smart enough to just join the two channels and take Lafayette out
> of the loop?
>
>
>
> Thanks!
>
>
>
> Travis
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> Check out the new Asterisk community forum at:
> https://community.asterisk.org/
>
> New to Asterisk? Start here:
>       https://wiki.asterisk.org/wiki/display/AST/Getting+Started
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20190731/e95886a1/attachment.html>