if I understand your question correctly Yes, that's supported. When a call to a client's DID is forwarded by an extension to an external number (e.g. a mobile), the platform recognises it from the FusionPBX call record and bills it as one charge with two parts: the incoming part and the forwarded part. Each follows the number type's rules: the forwarded part can be priced like a normal call to that mobile from the rate plan, at a separate forwarding price, or not charged. The invoice shows both parts on one line, and the Calls page marks the call as diverted. Ring groups that include an external mobile are being verified against real FusionPBX records now.
Here's how I use it: I have an AU 1300 number. A call comes in on the 1300 number, goes to a local extension, and is forwarded to an external number (my mobile, or a landline). My plans are "all you can eat", so normal local, national and mobile calls aren't charged, and the forwarded leg isn't either.
For the 1300 number, the platform charges the monthly number rental plus a price for each incoming 1300 call that was forwarded externally. You can set that per call or per minute, with different prices for callers on a landline and on a mobile, and choose to charge only forwarded calls or all calls.
For example, with $10 a month for the 1300 number and 50c per forwarded call: 2 forwarded calls make $11 for the month, 10 make $15, and so on (plus GST or your country's applicable sale tax).
Individual scenarios might be different but above is how I plan to use it. one I put it i production. current stagging is still connected to my Production PBX Serevr but I am not worried since I am only reading from it.
Thanks for the feedback.
