asterisk users - Sep 2010 - [OT-FreePBX] Outbound calls check inbound routes to see if destination is local?

Greetings-

First, my apologies for the OT post. Yes, I understand this is not the
FreePBX-users mailing list. But, there are a large number of people that use
FreePBX and I'm hoping they can be of assistance.

I have a system running Asterisk 1.4.27 (see... relevance!!!) and FreePBX 2.6.0.
There are a large number of inbound routes configured for the various DID's
coming in via PRI, SIP, etc. If a user calls outbound to one of these numbers,
it goes out to the PSTN (using one channel of $0.0x/min), then comes back in on
another channel (using another $0.0x/min).

Obviously, the one call is costing 2x the per minute rate when it could be
costing nothing. Is there a way to tell FreePBX to check the inbound routes for
a match, and if found, route locally instead of using the default PSTN routes?

I appreciate any comments, suggestions.

--Tim

-----Original Message-----
From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Tim Nelson
Sent: Thursday, September 16, 2010 10:42 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: [asterisk-users] [OT-FreePBX] Outbound calls check inbound routes
to see if destination is local?

Greetings-

First, my apologies for the OT post. Yes, I understand this is not the
FreePBX-users mailing list. But, there are a large number of people that use
FreePBX and I'm hoping they can be of assistance.

I have a system running Asterisk 1.4.27 (see... relevance!!!) and FreePBX
2.6.0. There are a large number of inbound routes configured for the various
DID's coming in via PRI, SIP, etc. If a user calls outbound to one of these
numbers, it goes out to the PSTN (using one channel of $0.0x/min), then
comes back in on another channel (using another $0.0x/min).

Obviously, the one call is costing 2x the per minute rate when it could be
costing nothing. Is there a way to tell FreePBX to check the inbound routes
for a match, and if found, route locally instead of using the default PSTN
routes?

I appreciate any comments, suggestions.

--Tim

Make a calling rule to identify lines that can be reached locally.  My
assumption is that the reachable lines/extensions would be SIP, but hey,
that wouldn't be the first time I was wrong today.

On Thursday 16 Sep 2010, Tim Nelson wrote:
> I have a system running Asterisk 1.4.27 (see... relevance!!!) and FreePBX
> 2.6.0. There are a large number of inbound routes configured for the
> various DID's coming in via PRI, SIP, etc. If a user calls outbound to
one
> of these numbers, it goes out to the PSTN (using one channel of $0.0x/min),
> then comes back in on another channel (using another $0.0x/min).
>
> Obviously, the one call is costing 2x the per minute rate when it could be
> costing nothing. Is there a way to tell FreePBX to check the inbound routes
> for a match, and if found, route locally instead of using the default PSTN
> routes?
Create a context to use as the default for any extension which can do 
a "straight through" call  (i.e. not via the PSTN);  and which routes
calls
that can be routed straight through, straight through.

Include within this, a second context for extensions which need to go out via 
the PSTN.

Have a third context for incoming calls from the PSTN, with all
"inside"
extensions in it.  Optionally include the out-via-pstn context within this; 
although, logically, if someone arrived via the PSTN, they already have PSTN 
access and so should not need to go back out via the PSTN.

Note that when an extension could match one of several possible targets, 
Asterisk always prefers the most specific  (hardest to match)  over the 
vaguest.

So you should have something like this  (very very minimal example);

[in-via-pstn]
include=>internal-phones
exten=>00.,1,Play(int-barred)
.
.
.
[straight-through]
exten=>012345678[89][0-9],1,Dial(SIP/2${EXTEN}:9)
include=>internal-phones
include=>out-via-pstn
.
.
.
[internal-phones]
exten=>[2-6]XX,1,Dial(SIP/${EXTEN})
.
.
.
[out-via-pstn]
exten=>0[123]XX.,1,Dial(${TRUNK}/${EXTEN})
exten=>07XX.,1,Dial(${MOBILES}/${EXTEN})

-- 
AJS

On Thu, Sep 16, 2010 at 11:42 AM, Tim Nelson <tnelson at rockbochs.com>
wrote:
> First, my apologies for the OT post. Yes, I understand this is not the
FreePBX-users mailing list. But, there are a large number of people that use
FreePBX and I'm hoping they can be of assistance.
>
If you know this is off-topic, and not the FreePBX-users mailing list,
why did you even make the post? Regardless that your question is not
actually specific to FreePBX, they do have an large and active
community [1].

Warning people your post is off-topic and FreePBX related is a sure
way for people to ignore your post, or reply like I did.

[1] http://www.freepbx.org/community

-- 
Paul Belanger | dCAP
Polybeacon | Consultant
Jabber: paul.belanger at polybeacon.com | IRC: pabelanger (Freenode)
blog.polybeacon.com

----- "Paul Belanger" <paul.belanger at polybeacon.com>
wrote:
> On Thu, Sep 16, 2010 at 11:42 AM, Tim Nelson <tnelson at
rockbochs.com>
> wrote:
> > First, my apologies for the OT post. Yes, I understand this is not
> the FreePBX-users mailing list. But, there are a large number of
> people that use FreePBX and I'm hoping they can be of assistance.
> >
> If you know this is off-topic, and not the FreePBX-users mailing
> list,
> why did you even make the post? Regardless that your question is not
If you were to read the first line of my post which you so thoughtfully quoted,
the answer to your question would be undeniably clear.
> actually specific to FreePBX, they do have an large and active
> community [1].
Yes, I am aware of that. However, my experience has been a large number of
community members there are 'point and click' junkies that don't
understand the technology or how the software works. In my observations, the
asterisk-users list has more technical, experienced members.
> 
> Warning people your post is off-topic and FreePBX related is a sure
> way for people to ignore your post, or reply like I did.
Exactly. I put OT and FreePBX in the subject so anyone offended or annoyed could
"ignore your post, or reply like I did". Sound familiar?

--Tim