For this case, I am using these example extensions.
1500: 3CX user extension that has Ring My Mobile enabled
1600: 3CX user extension
8475551212: PSTN caller
When my SIP Trunk Outbound Parameter for "From: User Part" is set to "OriginatorCallerId" the following two scenarios occur:
#1 External PSTN inbound caller 8475551212 rings extension 1500 and 8475551212 displays as CallerID. The mobile phone begins to ring and 8475551212 also displays. All works well.
#2 Internal user 1600 dials 1500. 1500 rings and displays 1600 as CallerId. The mobile phone never rings, a SIP Trunk error event is generated. VoxTelesys tells me that the CallerID being sent to the trunk for the mobile call is "1600" which causes a failure for the call to setup. This happens even though 1600 has "+18476661600" set as their profile's Outbound CallerId.
When my SIP Trunk Outbound Parameter for "From: User Part" is set to "OutboundCallerId" the following two scenarios occur:
#1 External PSTN inbound caller 8475551212 rings extension 1500 and 8475551212 displays as CallerID on the 3CX phone. The mobile phone begins to ring and 8476661500 displays as CallerID on the mobile phone.We would very much prefer that the originator's CallerID comes through so the mobile user actually knows who is calling. Right now they always see the same phone number display in CallerId no matter who is calling them.
#2 1600 dials 1500. 1500 rings and displays 1600 as CallerId, all good. The mobile phone begins to ring and 8476661600 displays as CallerID on the mobile phone. This works as expected.
Is there a way to have the best of both scenarios? On an inbound call from the PSTN, the originator's CallerID displays on both the 3CX phone and the mobile phone? And, when an internal caller dials an extension the 3CX phone displays the caller's extension and the CallerID on the mobile phone displays the internal caller's CallerID that's set on their profile?
1500: 3CX user extension that has Ring My Mobile enabled
1600: 3CX user extension
8475551212: PSTN caller
When my SIP Trunk Outbound Parameter for "From: User Part" is set to "OriginatorCallerId" the following two scenarios occur:
#1 External PSTN inbound caller 8475551212 rings extension 1500 and 8475551212 displays as CallerID. The mobile phone begins to ring and 8475551212 also displays. All works well.
#2 Internal user 1600 dials 1500. 1500 rings and displays 1600 as CallerId. The mobile phone never rings, a SIP Trunk error event is generated. VoxTelesys tells me that the CallerID being sent to the trunk for the mobile call is "1600" which causes a failure for the call to setup. This happens even though 1600 has "+18476661600" set as their profile's Outbound CallerId.
When my SIP Trunk Outbound Parameter for "From: User Part" is set to "OutboundCallerId" the following two scenarios occur:
#1 External PSTN inbound caller 8475551212 rings extension 1500 and 8475551212 displays as CallerID on the 3CX phone. The mobile phone begins to ring and 8476661500 displays as CallerID on the mobile phone.We would very much prefer that the originator's CallerID comes through so the mobile user actually knows who is calling. Right now they always see the same phone number display in CallerId no matter who is calling them.
#2 1600 dials 1500. 1500 rings and displays 1600 as CallerId, all good. The mobile phone begins to ring and 8476661600 displays as CallerID on the mobile phone. This works as expected.
Is there a way to have the best of both scenarios? On an inbound call from the PSTN, the originator's CallerID displays on both the 3CX phone and the mobile phone? And, when an internal caller dials an extension the 3CX phone displays the caller's extension and the CallerID on the mobile phone displays the internal caller's CallerID that's set on their profile?
