rdmackay Posted July 1, 2017 Report Share Posted July 1, 2017 I am trying to send the caller id of the inbound call to a call forwarded to a cell phone. My inbound trunk is vitelity and my outbound trunk is telnyx. I know it is possible because I had it working on a freepbx system. It would show the extension number if calling from internal extension as well as the caller id of the inbound call. Currently all calls forwarded to the cell phone show private number. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted July 1, 2017 Report Share Posted July 1, 2017 Can you get the INVITE from the old system that goes out to the telnyx trunk? Then we might be able to set it up the same way. Quote Link to comment Share on other sites More sharing options...
rdmackay Posted July 2, 2017 Author Report Share Posted July 2, 2017 thanks for the reply. I changed some of the caller id settings on the telnyx trunk and started to receive calls showing the trunk caller id. Then I removed the ani from the telnyx trunk and now showing the inbound call caller id. Quote Link to comment Share on other sites More sharing options...
chrispopp Posted July 3, 2017 Report Share Posted July 3, 2017 Setting the indication as Remote Party ID works for us. Quote Link to comment Share on other sites More sharing options...
cwernstedt Posted February 21, 2018 Report Share Posted February 21, 2018 One of our operators, Twilio, says it's OK with our PBX "spoofing" the CID when calling out on their trunks for as long as the CID belongs to someone calling into their system. This would enable us to forward the actual originating CID to our cell phones. Caller (CID#1) --> Twilio Trunk --> PBX --> Twilio Trunk -> Cell phone (sees CID#1) However a caveat is that CIDs from calls originating from non Twilio trunks as well as from internal extensions should not be spoofed (or can't be spoofed). I'm uncertain about how to configure trunks properly for this scenario. Any ideas? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted February 21, 2018 Report Share Posted February 21, 2018 In the latest (currently 59.8) we have revisited the header parameter "from" so that it should take it from the inbound trunk, if available. So if you want to try this again, our suggestion would be to move to 59.8 and use the {from} header in e.g. in the From header. There is also now a log available that shows all available variables, which should make ths trunk setup easier. Also there should be a drop down for setting up Twilio trunks that do it all for you, so you don't have to fiddle with the headers at all... Quote Link to comment Share on other sites More sharing options...
rdmackay Posted February 21, 2018 Author Report Share Posted February 21, 2018 Thanks for the reply. I had it working on version 58.0 When I upgraded to 59.0 it stopped working. I don't see the a 59.8 version link only the 59.0 Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted February 28, 2018 Report Share Posted February 28, 2018 We have now released 60.0. Quote Link to comment Share on other sites More sharing options...
rdmackay Posted March 2, 2018 Author Report Share Posted March 2, 2018 Upgraded to the 60.0 version and changed the source for caller-id information from remote party id to from and that fixed the problem. Thanks for the help. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.