CallerID passthrough trunk to trunk

Goal :
Incoming call to IVR, option “3” destinated to a virual extension with FollowMe to a mobile number through a second trunk.
The called mobile should see the incoming caller CID
Trunks are both PJSIP on Freepbx (sip on the provider side)
Provider allows outgoing CID to be different from own phone number.

Are there any particular setting to achieve this ?

How do you identify yourself to the provider when making calls? Does the provider support P-Asserted-Identity or Remote-Party-ID?

Does incoming caller ID work from trunk to extensions?

Provider supports CID from PAI or RPID

<Does incoming caller ID work from trunk to extensions?> to be checked…

Just to know if it could work…
We are trying settings with provider
It uses MOR X16 platform with these possible settings for CLI :

Device callerid.png

A CallerID consists of two parts: Name and Number. The “Number” part is transferred by default by all technologies (GSM, PSTN, SIP etc), but the “Name” part is transferred only by some. The number you see on your mobile phone when someone is calling you is the “Number” part.

  • Name – the “Name” part of the CallerID.
  • Number – the “Number” part of the CallerID. Only numerical values can be entered in this field.

NOTE: if you leave these fields empty, the user can set the CallerID name by himself. Usually it is not advisable to allow the user do it on his own. If CallerID number field is empty, system will take device username as CallerID number (if device is username/password authenticated).

  • Number from DID - use the DID as the CallerID (only available when the device has DIDs), this option just sets CallerID Number to be equal to DID. Next time you will edit Device’s settings, first option - Number will be checked

  • Control by DIDs (CID from DIDs) – only available when the device has DIDs and “Number” field is empty.

This setting lets you control what a CID user can enter in his devices. CID numbers should be from the set of the device’s DIDs. They are mainly used when the user’s PBX is connected over Trunk and many DIDs are routed to this Trunk. Calls coming out from this PBX must have a CallerID Number from the set of DIDs assigned to this Trunk (PBX). If “CID from DIDs” is checked, the system checks whether the device’s CID number is from DIDs assigned to this device. If no DIDs are assigned, this value is ignored. In order for this setting to be active, CID Name/Number fields must be empty to allow the user to enter any CID number he wants. If “CID from DIDs” is checked and user enters any CID (not from his DIDs), the system will change his CID by his first available DID (selected from database by lowest ID). Original (non Localized) CallerID is used for DID matching.

  • Control by CIDs – system checks incoming CallerID (Device’s CallerID which is set on the Device). If CallerID matches one of the Device’s CIDs - then such CallerID will be allowed. If it does not match - it will be changed to the selected CID.

  • Control by Destination – This is advanced option which works by such algorithm:

  1. system checks Destination and checks DIDs assigned to calling Device. Then it finds ‘nearest’ DID to the Destination by subtracting DID from Destination in numerical form (Example, DID: 11111, Destination: 11112, |DID-Destination|=|1111-11112|=1) If Device has several DIDs - the lowest value is selected and this DID is set as CallerID.
  2. If Device has no DIDs - then User DIDs are used.
  3. If Device does not have DIDs and User has no DIDs, then CallerID set in Number field will be used.
  4. If nothing is set here - CallerID coming from Device will be used.

Note: behavior can be changed to search for best matching DID instead of nearest DID

  • Random Number from Number Pool – This functionality gives you an ability to send different caller number on each Call. Available from MOR X4. More information: Number Pool.
  1. Random - Send random CallerID.
  2. Pseudorandom with Deviation. Range can vary from 0 to 9999999. If 0 is chosen, then all numbers will be chosen same amount of times. If 9999999 is set, then numbers will be completely random.
  • Unknown - This option lets you set CallerID number to unknown and pass a custom CallerID in either RPID or PAI header:

Unknown cid rpid pai.png

  • Copy Leg A Name to Leg B Number – Leg A name will be used as Leg B number.

What solution should we choose ? Unknown with a custom CID ?

I think you need to ask Kolmisoft that.

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.