[VoiceOps] Unique DIDs vs. Custom extensions

Peter Beckman beckman at angryox.com
Tue Sep 15 21:13:48 EDT 2015

Jared --

Can you explain in detail how a two-B-channel transfer would prevent Rafael
from having to pay for so many minutes?

The calls are terminating to a phone on the PSTN; you'd still have to pay
someone for the originating leg and terminating leg. You're just taking
Asterisk out of the middle once the two legs are up. While that allows you
to handle more calls on Asterisk, what I understand is that you are still
paying for the two legs.


On Tue, 15 Sep 2015, Jared Smith wrote:

> On Tue, Sep 15, 2015 at 11:58 AM, Rafael Possamai <rafaelpossa at gmail.com>
> wrote:
>> With all of this in mind, I'd like to know if anyone here has done a
>> similar project and would be willing to share their experience. I am trying
>> to accomplish everything with the minimum amount of resources as possible
>> (money and DIDs, etc).
> I helped consult on a similar system eight or nine years ago -- at the
> time, my client used Asterisk with PRI channels instead of SIP channels,
> because of the ability to do a two-B-channel transfer and cut himself out
> of the middle of the call after the connecting the caller to the called
> party.  Asterisk can initiate the two-B-channel transfer, but as far as I
> know doesn't yet do anything with the message coming back down the PRI
> letting it know when the call has terminated.  (Well, that's not entirely
> true -- Asterisk logs an error message, so I assume it wouldn't be too hard
> to actually connect that up to some sort of better logging to be able to
> determine the call duration.)
> It may not make sense in your situation, but I thought I'd pass that along
> as one way of not having to pay for so many minutes.
> --
> Jared Smith

Peter Beckman                                                  Internet Guy
beckman at angryox.com                                 http://www.angryox.com/
-------------- next part --------------
VoiceOps mailing list
VoiceOps at voiceops.org

More information about the VoiceOps mailing list