Solved 3CX server claims that the desk phone is spam?!??

[DrewVIT]

Howdy all, long time user, first time poster! Big fan!

I am not sure where this should be posted, so I will start here.

We have an office with roughly five or so phones (Yealink T54W's), all connected to the same network wired, with PC's attached to their data port, all are provisioned by the same 3CX server, all are leaning on a 3CX SBC. I believe that the SBC is a Raspberry Pi 4 4GB.

One of the five cannot make outbound calls.

When a call is attempted from the back room to the user's personal cellphone, it says "The number you are calling from has been labeled as spam."
The user goes up to the front desk and calls the their personal cellphone again, the call goes through without issue.

Other than a span of roughly thirty or so feet, there is no electrical difference between the two phones.
Also there is roughly about one to five minutes, between the first call from the back room and the front desk.

I tried to factory reset the 'back phone':

• Done

Tried to reprovision the 'back phone':

• Worked without issue

Had the user try to call their cell from the 'back phone':

• "The number you are calling from has been marked as spam."

I did see where I can change outbound CID in the SIP Trunk section, but that would do this for every line. Which doesn’t sound like it’s the problem.

I have tried to ask search engines in the internets, but they keep giving me is "3CX block spam calls" and the like.

I honestly have zero intention of rebuilding their phone server, so any guidance would be welcomed with cake and pie!

 

[SteveITS]

So are all the calls coming from the same caller ID? The lookup is based on caller ID...

 

[DrewVIT]

Well don't I feel silly!

I thought I looked at each line's CID, but glanced over it.
Thank you, SteveITS!!!!

The 'back room' phone did not have an outbound CID set, like the four others.
Each one had a special outbound CID specified.

I just set the outbound CID to the same as the rest.

Now that I can 'bypass' the account's outbound CID with "per line" CID.

Now that I ASSUME that this resolves the issue......I'm seriously wondering why 3CX, or the SIP provider is telling the account that they are spam, but changing their outbound CID bypasses that filter????

 

[SteveITS]

I would think, the default caller ID on the SIP service is not the one the other four are using, and that's the problem number.

 

[leejor]

It is probably the mobile provider giving the spam message based on an "unusual" or no caller ID being received. In most cases, your VoIP provider will not permit the call, to begin with, if the sent caller ID is unacceptable.

 

[DrewVIT]

Thank you both so very much!

I will need to investigate this with the SIP trunk.

Imma figure out how to close this post.