CID outbound formatter

Status
Not open for further replies.

alberto464

Free User
Advanced Certified
Joined
Jul 26, 2022
Messages
8
Reaction score
0
Hi,
I'm trying to understand how the CID formatter works within the trunk (https://www.3cx.com/docs/cid-reformatting/)
I would like to have "39" added in front of all outgoing calls, what formula should I put?
 
Do you use CID reformatting

Use outbound rules and prepend 39 in the rule
 
I tried to put it in the outbound rules, but then the customer in the call logs finds all the numbers starting with 39 and he didn't want to.
 
Try source patten (.*) , replace pattern 39\1
 
Try source patten (.*) , replace pattern 39\1

I entered the pattern as you say:

Schermata 2022-07-26 alle 11.37.10.png
But the call does not go out with 39 in front:

Code:
07/26/2022 11:39:37 AM - [CM503003]: Call(C:25): Call to <sip:[email protected]:5060> has failed; Cause: 404 Cant find destination prefix

Maybe I need to change some settings here too?

Schermata 2022-07-26 alle 11.37.51.png
 
Your sip provider does not recognise 39 as valid number. you have to supply valid numbers to your sip provider.

Check activity log to see if 39 is being added to the number

What is the reason for adding 39 to every number ?
 
My provider require the 39 in front, which is the Italian country code.
If you see the screen reject all calls that do not have 39 in front, in fact in the error string you see that the number called does not contain 39 in front even if the rules are set:

Code:
07/26/2022 11:39:37 AM - [CM503003]: Call(C:25): Call to <sip:[email protected]:5060> has failed; Cause: 404 Cant find destination prefix

The error here is the PBX that does not add 39, I don't understand why.
 
Outbound CID Reformating only applies to cases where the inbound call comes into the system and gets forwarded out again, as it works only with the originator caller ID. It won't work in cases where the extension dials the outbound number directly.
  • Outbound Caller ID reformatting requires using the “OriginatorCallerID” to be active in the SIP Trunk “Outbound Parameters” settings.
https://www.3cx.com/docs/cid-reformatting/#h.k46xo2iwbtql

For your requirement, I would suggest using outbound rules, where you would create one to process calls from either extension or extension groups or based on the number of digits dialed and then prepend 39.
 
Outbound CID Reformating only applies to cases where the inbound call comes into the system and gets forwarded out again, as it works only with the originator caller ID. It won't work in cases where the extension dials the outbound number directly.
  • Outbound Caller ID reformatting requires using the “OriginatorCallerID” to be active in the SIP Trunk “Outbound Parameters” settings.
https://www.3cx.com/docs/cid-reformatting/#h.k46xo2iwbtql

For your requirement, I would suggest using outbound rules, where you would create one to process calls from either extension or extension groups or based on the number of digits dialed and then prepend 39.

Thanks for the answer, but so in this case in the call logs there will always be the number with 39 in front, isn't there a way to avoid it?
 
Not if that is the way the number is required to be dialed.

The caller ID re-formatting is just that, it re-formats caller ID, not a dialed number. It is handy if people want to redial the number as shown on their caller Id display, as it usually requires additional digits (or digits removed), before being accepted as a valid number by the provider. Modifying a number ,as dialed from an extension, will require using the options in the outbound rules. The customer will just have to deal with it somehow.
 
Last edited:
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
112,324
Messages
591,897
Members
165,476
Latest member
awan05