Call Bluebox External DID number from internal device without going out to provider

[Travis]

What is the proper way to setup Bluebox so that when I call one of my
External DID numbers (assigned in Bluebox) that the calls do no go out
to my provider and come back. I want the configured External numbers
to ring the associated devices directly so I'm not being billed if
someone calls a DID that is already in Bluebox.

[Darren Schreiber]

Change your trunk configuration contexts to NOT have Outbound Routes in
them.

In Trunk Manager, click Edit, and UNCHECK the Outbound Routes box.

--
Darren Schreiber
CEO / Co-Founder

[Travis]

Hi Darren,

I don't want to prevent outbound calls, I want to prevent calls to my
own DIDs (configured as External numbers in Number Manager in Bluebox)
from going out my outbound Trunk. Calls to such numbers should ring
directly to the assoicated devices.

Travis

On May 1, 1:54 pm, Darren Schreiber <dar...@2600hz.com> wrote:
> Change your trunk configuration contexts to NOT have Outbound Routes in
> them.
>
> In Trunk Manager, click Edit, and UNCHECK the Outbound Routes box.
>
> --
> Darren Schreiber
> CEO / Co-Founder
>

[Darren Schreiber]

Whoops, sorry, you're right. I gave the wrong instructions.

Here's the correct setup:

1. In the Trunk Manager, edit your trunk
2. In the "Made from these contexts..." section check ONLY Outbound Routes
(not INBOUND Routes) <-- this is opposite what I just told you, sorry
3. Save the trunk
4. On each DEVICE ensure the device is set to make calls via the OUTBOUND
Routes context.

That should do what you're requesting.

[Travis]

Still no luck, here are some details that may be helpful. Everything
is functioning but I do not want to pay for calls to my own DIDs
initiated from an internal extension.

I have 2 Trunks configured
Outbound:
Route Outbound Calls Matching... 10 Digits
Made from These Contexts... Outbound Routes

Inbound
Route Outbound Calls Matching... None Selected
Made from These Contexts... Outbound Routes (Previously tried
Outbound & Inbound)

I have my DID in Number Manager
Number: 3334445555
Type: External
Route: Device 2001
Contexts: Inbound Routes (Previously tried this on Outbound Routes and
it generates 5+ call sessions for a single incoming call and I'm
billed for all)

On May 1, 2:21 pm, Darren Schreiber <dar...@2600hz.com> wrote:
> Whoops, sorry, you're right. I gave the wrong instructions.
>
> Here's the correct setup:
>
> 1. In the Trunk Manager, edit your trunk
> 2. In the "Made from these contexts..." section check ONLY Outbound Routes
> (not INBOUND Routes)    <-- this is opposite what I just told you, sorry
> 3. Save the trunk
> 4. On each DEVICE ensure the device is set to make calls via the OUTBOUND
> Routes context.
>
> That should do what you're requesting.
>
> --
> Darren Schreiber
> CEO / Co-Founder
>

[Darren Schreiber]

ahh,, so you are calling from an on-net device to a 10-digit number that
is also on-net? I see now.

In the number manager, for the 10-digit DIDs you've defined, at the
bottom, are BOTH contexts checked? I think that's all which is required...

[Travis]

Sorry about that I forgot to include that important detail :) When
it's setup as Type: External I can only select a single context.
Configured this according to the wiki

Current call flow for calls to my DID through Vitelity
PSTN call to my DID -> Vitelity > Freeswitch -> Internal Device 2001
**This behaves as expected
Internal Device 2002 call to my DID -> Freeswitch -> Vitelity ->
Freeswitch -> Internal Device 2001 **This is my issue where I'm being
charged for an outbound and inbound call by Vitelity since it's going
through there trunk

On May 1, 2:49 pm, Darren Schreiber <dar...@2600hz.com> wrote:
> ahh,, so you are calling from an on-net device to a 10-digit number that
> is also on-net? I see now.
>
> In the number manager, for the 10-digit DIDs you've defined, at the
> bottom, are BOTH contexts checked? I think that's all which is required...
>
> --
> Darren Schreiber
> CEO / Co-Founder
>

[Travis]

Found a different example on 2600hz but something is still not right
http://wiki.2600hz.org/display/bluebox/Quick+start+configuration. I
changed the DID number type to Internal and selected both Incoming and
Outgoing contexts. These are the cdr records generated when calling
my DID from internal extension 2004 and DID should ring 2001.

"88220946-93d5-11e1-a2cd-
f50b2776c408","","inbound","3124445555","3124445555","","2012-05-01
17:35:11","0","","","64.2.142.15","false",""
"88038174-93d5-11e1-a2c9-f50b2776c408","880269b0-93d5-11e1-a2c4-
f50b2776c408","outbound","2004_john_doe","3124445555","","2012-05-01
17:35:12","0","","","64.2.142.29","false","trunk_5"
"88404c8a-93d5-11e1-a2d5-f50b2776c408","880269b0-93d5-11e1-a2c4-
f50b2776c408","outbound","2004_john_doe","2001_john_doe","","2012-05-01
17:35:17","0","","","222.222.222.222","false",""
"884069e0-93d5-11e1-a2db-f50b2776c408","880269b0-93d5-11e1-a2c4-
f50b2776c408","outbound","2004_john_doe","2001_john_doe","","2012-05-01
17:35:17","0","","","222.222.222.222","false",""
"880269b0-93d5-11e1-a2c4-
f50b2776c408","","inbound","2004_john_doe","3124445555","2012-05-01
17:35:17","2012-05-01
17:35:26","9","2004_john_doe","","77.77.77.77","false",""

[Travis]

Setting the DID to type Internal results in inbound calls to the DID
from the PSTN breaking.

Maybe I need to add the DID extensions to the top of the Outbound
context so that it does not continue if matched?

On May 1, 4:48 pm, Travis <tlangh...@gmail.com> wrote:
> Found a different example on 2600hz but something is still not righthttp://wiki.2600hz.org/display/bluebox/Quick+start+configuration.  I

[Darren Schreiber]

I think you've nailed it - if you set it to external then it makes it
publicly accessible but you can't change the context to more then one...

Soooo... I guess what you're trying to do isn't possible without adding on
the internal context an extra DID definition. Which would be a duplicate
:-)

I think you're SOL on this. it will require a patch to allow multiple
contexts for outbound numbers.