Which field should I set to "OriginatorCallerID"

Status
Not open for further replies.

greychain

Gold Partner
Advanced Certified
Joined
Jul 13, 2018
Messages
779
Reaction score
122
I am trying to reformat outgoing numbers from E164 format to local format ie +85512345678 to 0122345678.

I have set my source pattern to +(855)(.*) and the replacement to 0\2. Then I need to do this

  • Outbound Caller ID reformatting requires the use of the “OriginatorCallerID” to be active in the SIP Trunk “Outbound Parameters” settings.
Currently I have tried
 

Attachments

  • 1699348105559.png
    1699348105559.png
    65.2 KB · Views: 10
Have you checked the SIP provider isnt forcing this format?
 
In Cambodia they don't support +855, only local number formatting 0xxxx.
 
This information is also included in the guideline.
 
I read the guideline, which is where I got the following information from, but it isn't clear which field.
  • Outbound Caller ID reformatting requires the use of the “OriginatorCallerID” to be active in the SIP Trunk “Outbound Parameters” settings.
 
It depends on which field the provider is expecting this information. This has to be clarified with the provider.
 
I cannot confirm which exactly, you need to test each one or clarify from the provider.
 
I tried forcing the Request Line URI : User Part to the number required an that is the parameter I need to change.

Is my number reformatting rule correct?
 
Yes the reformatting seems ok
 
Thanks. I change the Request Line URI : User Part to OriginatorCallerID it still sends out the number with +855
 
You can run a capture and check if it is sent and in which field. However this is an unsupported provider and you need to check with them.
 
Where can I check my number reformatting is being applied?
 
You can run a capture and check.
 
I was hoping there would be a log file like 3CXManagementConsole where it would say the number reformatting has been matched and applied. The Pcap only shows number dialed not rules
 
For this, you can check the sip server logs, which are the logs found in the support info after setting to verbose logging mode and replicating the issue. You may check this guide on how to do this: https://www.3cx.com/docs/3cx-log-viewer/
 
Thanks Charles, that is an interesting tool. I think I might have found the issue but I'll have to test more.

07/11/2023 17:13:27:108 | 10 | L:87.1[Line:10009<<++85587xxxxxx]: Terminating targets, reason: Q.850
 
It seems like an extra + is being added, recheck the configuration all the way through, TIP: Work backward, checking from the outbound rule first.
 
Status
Not open for further replies.

Forum statistics

Threads
111,974
Messages
590,081
Members
164,899
Latest member
mazet