Solved 1300 number in Outbound caller ID

[Mike-2Gen]

Hi folks,

I've set up a new 3CX client on v18 and got everything done and working as expected but ran into an issue with outbound caller ID's. I've entered their (new) 1300 number into the caller ID field in the SIP trunk and in testing, the 1300 number shows up as expected when calling into OUR 3CX system (so, 3CX to 3CX) but when calling a mobile phone, it comes up as "No Caller ID". To further test, I used the client's local number instead and that shows up fine.

I am not overly familiar with the intricate setup options of 3CX, never had to worry about issues like this before, any pointers? I don't have much hair left to pull out.

Thanks in advance for any assistance!

Mike

 

[NickD_3CX]

Hi!

By the time the correct number is showing when calling 3CX to 3CX, it means that 3CX is sending what you told it to send.

Now, why it is not showing when calling other numbers, I am suspecting that maybe your Provider requires that you input the number in 3CX is a specific format.
I'd try E164 format for the number as well in the 3CX settings.

As a last repost, maybe contact your provider and they could give you a hint as to why this is happening, and depending on what they say, we could act accordingly.

 

[leejor]

Most providers are "cracking down" on any caller ID that is not in a "standard" national format, primarily because of the outcry, to do something, about the amount of SPAM calls these days

In some countries, this is now a requirement, and providers simply have to comply with the regulations. If you have found that putting 1300 into the outbound caller ID field is needed for (what i assume are) Bridge trunk calls, then you may have to create a separate outbound rule, for normal outgoing calls, restricted to each extension, that adds their full DID number. Of course this is going to get complicated, for a large number of extensions.

You might also want to try putting the Full PSTN number, in the outbound caller ID field, for the extension see if that is, in fact, sent to the other 3CX PBX. It may be possible ,depending on the format of other incoming caller ID, to modify only calls over the bridge trunk, removing all, but the last four digits of the CID.

 

[Mike-2Gen]

Thanks for the feedback Nick/Lee. I DID try E164 and that didn't help, may have to call provider and see what they recommend... after I get back from leave.... gotta have priorities! ;-)

Thanks again and I'll update if / when resolution is found.

Mike

 

[Mike-2Gen]

Quick update: Still investigating. Had another client who experienced the same outbound caller ID issue on their LOCAL number. Calls to landllines presented the caller ID as expected but calls to mobile showed "No Caller ID". This is a new issue for them and nothing had been changed. I entered in their local number CID into an extension as well and that fixed the issue. So sounds like the global outbound caller ID settings may not be working.... BUT...

The 1300 CID number I originally posted about here now WORKS to mobile devices... I haven't even touched it as I was away last week.

Still investigating, very odd. Up to 3 clients now with Outbound CID issues to mobile devices. But sometimes working, sometimes not.

 

[Mike-2Gen]

Okay, question answered. Based on what I was told by our 1300 provider, you cannot set a 1300 # as an outbound CID number. It worked a couple time for me until 3CX "caught me out" then blocked further outbound calls from any extension with the 1300 Outbound CID, as soon as I changed it to client's regional #, worked fine. So, no 1300 #'s can be used in outbound CID's.

 

[YiannisH_3CX]

3CX does not have such limitations. If you set it up to send a 1300# then it will. I think it worked until your provider blocked you and then it stopped. So if your provider does not allow you to send a 1300# as caller ID then i guess you have your answer.