Reformatting incoming caller id from Skyetel to 3cx v20

[dynamiq]

Hello to other 3cx Partners and users!

I wanted to post how to change the Skyetel incoming caller id format for anyone else who needs this, because I did not find anything of use anywhere. If it's there, I could not find it.

We had a customer that needed the incoming caller id to be in the format of x(xxx)-xxx-xxxx. Skyetel delivers the number as +xxxxxxxxxxx(even if your SIP format in the phone number settings on their website portal is different, i.e. xxxxxxxxxxx or xxxxxxxxxx). Apparently Skeytel's format for the "invite" is always in the +xxxxxxxxxxx, then the "request received" is in the format you chose on their portal.

After trying lots of different things that did not work, here is what I found that works.

In 3cx, under the tab Voice & Chat, then the Options tab, then chose Reformat inbound or outbound caller id. Click on "Add+", then under Source Pattern type +1(...)(...)(....) and under Replace Pattern type (\1)-\2-\3 (or whatever format you need it in). This will get you an incoming caller id showing on your phone in the x(xxx)-xxx-xxxx format. **** THIS WILL NOT WORK IF YOU USE "Convert inbound caller ID to E164 number format" ***********************************************
Make sure E164 conversion is TURNED OFF.

I hope this is helpful to others that are working to give their customers what they need.

 

[vipin.rathore@thetelephon]

Thanks for sharing this. The note about disabling "Convert inbound caller ID to E164 number format" is particularly useful, as that's often the setting that causes the reformat rule to be ignored.


We've run into similar situations where carriers deliver the SIP INVITE in E.164 format regardless of the formatting selected in their portal, which can make troubleshooting confusing when the signaling doesn't match what's expected.


One additional thing worth mentioning for anyone testing this: if the caller ID still doesn't appear as expected after applying the rule, it's a good idea to capture a SIP trace and confirm exactly what format 3CX is receiving in the From header. In some cases, carriers may send numbers with a different country code pattern or additional prefixes, requiring a slightly different source pattern.


Appreciate you posting the solution. It will definitely save others some time.