[Enhancement Request] Allow Option to Turn Caller-ID E164 Format on or off

kenn10

New Member
Sep 11, 2018
6
0
1
69
For all phone numbers and outbound caller-id, allow an option to not have the outbound caller-id show +1. I can understand that might be necessary for other countries, but most of the USA just has the 10-digit caller-id and the E164 format is not required (or desired.) The outbound route handles a non-E164 format just fine.

I exported my destinations and extensions to spreadsheets and fixed the caller-id's manually and read them back into the system but an on/off E-164 option would be good to have. A possible location for the option might be on the phone numbers screen of FS PBX since all outbound caller-id is based on the phone numbers entered there.
 
Hi @kenn10, can you elaborate on why the E164 format is not desired? It's accepted everywhere.

If you really wish to change this, then dialplan modification is best. Find the Default Caller ID dialplan and make any changes you like to modify the numbers and strip +1
 
Most other systems, including FusionPBX, are not sending the +1 unless you tell it too. Yes, the +1 is accepted by most SIP vendors but is superfluous. It is especially annoying when someone on another system like a Cisco or Avaya switch has not prepared their systems to strip the +1 on an incoming call. If the caller-id display to a user comes in as +1-NXX-NXX-XXXX and they hit their call-back button, the + can prevent the call from going through.

I'm just thinking about call made from FS PBX to other people's PBX's.
 
The trunk provider on the other side usually overrides it and delivers the caller ID number if the format you desire. At least this is how it works in the US. I have not heard anyone say that E164 caller ID prevents other systems from accepting calls yet. I've been doing it for over 7 years like that, after I realized that 10-digit numbers cause issues when you try to call international numbers. Switching to e164 solved that and I've never looked back
 
Obviously, the outbound route can be modified as such and I have done that. The changing of the XML code is probably too much for novice users.

I'll leave it at that.
 
Last edited: