outbound route different for dialed calls vs transferred calls?

[blackened]

In an effort to save a little money, I configured my dial plans such that, if the number is local to the POTS line we have interfaced to our PBX through an SPA3102, it will dial through that instead of using our VoIP provider at roughly a penny a minute.

This works great even though the Caller ID going out will be that of the POTS line and not our main number, because calls coming into the POTS line go to our PBX anyway and can be handled like any other call.

The problem we have is when we have, for instance, a user with follow-me settings that go to an external phone that is local to us. It will send it over the POTS line which always has that same caller ID (cannot be configured as I assume the phone company just knows what number it is and sends that out without thinking twice). So, if a caller calls in on our VoIP line, and then gets externally transferred, the Caller ID info is lost and the receiving phone (usually a cell) will show it coming from our office land line instead of the caller who called.

Is there some way to set a dial plan to only be used on external transfers, or only to be used when dialed from an actual phone? In other words, can I separate the two actions out?

Thanks,
Scott

 

[da1Bear]

Why not set up a Google Voice number and use it for transfers? It can be configured to retain the original caller id. (I am assuming you're located in the USA).

 

[Bitnetix]

Barring using an external forwarding service like Google Voice, you might have to get complex with your dial plan to have outbound calling from within the Follow-Me code of FreePBX use a custom outbound route, rather than people simply dialing. This would separate from-internal into, say, from-internal and from-internal-follow-me (or whatever you want to call it).

The problem is, it will most likely get overwritten with each reconfiguration within FreePBX, since I believe you're going to want to modify the follow-me code, which is buried in their dialplan.

I suggest you take this to the FreePBX forums (freepbx.org/forums) and ask there, since it's a FreePBX question and not a real PIAF one. You're likely to get faster responses with meat.

 

[jroper]

Hi

Would you be happy with using steering digits, e.g. prefix with say 80, when transferring, then set up an outbound route that goes out via your SIP provider selected with 80.

Joe

 

[blackened]

Why not set up a Google Voice number and use it for transfers? It can be configured to retain the original caller id. (I am assuming you're located in the USA).

Indeed that would be a good choice, but the same dilemma applies. We don't want to call out the Google Voice number because, at least at the moment, we cannot set the outbound caller ID. We don't want it to show the Google Voice number, rather our VoIP.ms DID (or the local POTS line if going out that is fine too).

But I am curious, if the PBX initiates a Google Voice connection on an external transfer, what would the receiving phone see for Caller ID? The Google Voice number, or the original caller's number? Wouldn't that leg be considered the "Outbound" which would show the Google Voice number, right?

 

[blackened]

Hi

Would you be happy with using steering digits, e.g. prefix with say 80, when transferring, then set up an outbound route that goes out via your SIP provider selected with 80.

Joe

Yeah I like that idea. Then I just have to train users to put that in front on their follow me external numbers, right? As far as dialing out is concerned, everything would be the same except I would be able to force a call out my SIP provider by prefixing 80.

Thanks Joe!

 

[jroper]

Hi

That is correct, however, if you are not using 9 for an outside line, it may be easier to use 9 for transfers as the steering digit, as it may be more familiar to the users (in strange sort of way)

Alternatively, if you are using 9 for an outside line, you could use no prefix to select the SIP trunk.

Joe