Skip to main content

Forward to 2 Mobile Numbers with Tag Option

Posted by etornetworks on Sat, 04/08/2017

I have a customer that uses a traditional ring group.
It's made of two extensions. Each extension is set to forward to their mobile numbers (2 different numbers).
They need to be able to tell when the call is coming from their business line vs. personal line.

I setup a Tag in the extensions- BUS for business, setup the calls to always forward from the user portal, but the Tag is not showing in the caller ID on the mobile phone.

Little help?


Submitted by thirdlane on Sun, 04/09/2017 Permalink

Tag is just tag, a piece of data that will be available in the dialplan, so you could use it to set caller id or for any other purpose. Caller id won't be set by the existing scripts automatically.

Submitted by etornetworks on Sun, 04/09/2017 Permalink

Is there a field to modify caller ID when a call is forwarded to an outside number?
Anything that could identify this call as a call from the office?

Submitted by etornetworks on Sun, 04/09/2017 Permalink

The tag feature works really well when the call is sent to the extension- the desk phone shows it. but once it's forwarded out, it looses the tag

Submitted by thirdlane on Tue, 04/11/2017 Permalink

The problem with callerid is that we can not "just allow" it to be set to any number including the inbound callers caller id - this is spoofing, and can cause calls not going through, at least with many providers in the US. That said, the internal rules on where to set and where not got a bit too complicated so we will be reviewing how we deal with this, and what we can do to add more flexibility.

Submitted by eeman on Tue, 04/11/2017 Permalink

the _only_ information you can pass to the PSTN is callerid NUMBER. So to answer your question...

how do I determine if the inbound call on the mobile device was a forwarded office call vs a call to the mobile TN? It is done by looking at the callers number. You will have no choice but to forfeit the preserving original callerID as that will make it indistinguishable. If your callerid is the Office or the overridden callerID for the extension then you know the call was not a call directly to your device.

Submitted by Dougster on Wed, 04/12/2017 Permalink

Erik's statement that "the _only_ information you can pass to the PSTN is callerid NUMBER" is true in the US, but not in the great white north. In Canada, the callerid name is also sent to the PSTN. There is no CNAM dip . Strange though it may seem, the name can be set to anything you choose and it will be passed through in exactly the same way as the number. This is not really handled very well by Thirdlane for forwarded calls at the moment for Canadian users. (We will have to modify the dialing scripts to fix it.)

Submitted by thirdlane on Wed, 04/12/2017 Permalink

To Erik's point - if you pass the original caller id (or callerid name) as is, then the mobile user won't be able to determine that the call was forwarded by the PBX.

The ability to specify caller id name opens possibilities as it allows passing both the name and an indicator that the call was forwarded. This will require more options in our scripts - i.e. keep original caller id name, prepend or append something to it, do not use original, use original id and not the name, etc. This may get even more complex depending on where we will allow this settings - tenant, did, individual user, huntlist, menu, etc. We would have to draw a line somewhere as this can get too hard to manage, explain, and be in confusing for both the administrators and users.

Our general assumption was that while this may be possible in some cases - like Canada, it is not a feature that can be safely relied on in other parts of the world, and this option will become less and less available. Would be interested to know more about other countries and also get your thoughts on this feature's granularity .

Submitted by eeman on Thu, 04/13/2017 Permalink

why would canada allow for such a blatant case of telephone fraud? I could easily call pretending to be law enforcement or their CitiBank asking for private information. Its tantamount to SSL certificates that are fully trusted based solely on the integrity of the scammer's running the website.

Submitted by netriplex on Thu, 04/13/2017 Permalink

I would not go quite that far. Updating CNAM records in the US is really not that difficult and many Voip providers allow customers to directly modify their CNAM records anyway.

Relying on CNAM information to determine whether or not to trust a caller is a severely bad practice and bad advice if you are advising anyone to look at the caller name to determine whether a call is legitimate or not.