[VoiceOps] CLID weirdness

[Dave Brockman]

On 9/21/2023 6:34 PM, Carlos Alvarez via VoiceOps wrote:
> Let me make sure I read this correctly.  You can send any CLID and it 
> works, except if you send one specific number it comes up as private?  
> Or did I misread it?

I can send the CLID of any DID on the SIP trunk, and it works, except 
the one DID in question that comes up as private.  I cannot set CLID to 
any arbitrary value, $LocalTeleco drops the call if I present a CLID not 
assigned to the client's SIP trunk.

> In 3CX, I assume you are you setting the problem CLID at the extension 
> level, right?  And the main CLID for the system is the company’s mail 
> number?  Have you tried setting the problem CLID in the main settings to 
> see what happens?

The Trunk CLID is set to the main (problem) DID.  This is the default 
unless overridden at the extension or outbound route.  For my tests, I 
have a singular extension that I set to different DIDs (including the 
main) and/or send the Trunk default.  Same results either way.  Main DID 
comes across as private, other DIDs come across correct.

> The MCI line *probably* uses ANI, which cannot be blocked, not CLID.

I had some suspicion, but am not knowledgeable enough about ANI/CLID to 
make any assumptions.

Did that answer your questions?

With Gratitude,

Dave Brockman
Senior Network Engineer
Gig City Cloud, LLC

> On Sep 21, 2023 at 3:26:56 PM, Dave Brockman via VoiceOps 
> <voiceops at voiceops.org <mailto:voiceops at voiceops.org>> wrote:
>> Hello,
>>   First, please forgive me, I am a network engineer by trade, I am not
>> extremely well-versed in telephony.  Please forgive me if I use the
>> wrong terminology or otherwise misstate something.  It is not intended
>> and does not come from malicious intent.
>>   I have a customer with a SIP trunk from $LocalTeleco.  We send our
>> own CLID out from our (3CX) PBX.  For one specific DID (which also
>> happens to be the office main number /sigh) everywhere I can see it
>> calling, shows up as "Restricted, Anonymous, or Private".  However, I
>> can call MCI at 800.444.4444 and they tell me the correct CLID digits.
>> I have several hundred other DIDs that I can present, and appear
>> correctly at the same receiving carriers that show
>> restricted/anonymous/private on the main DID, and MCI will read back the
>> expected digits.
>>   Would anyone more versed in this side of things be willing to let me
>> make a couple of test calls, and you tell me if you see anything strange
>> that I can take back to $LocalTeleco?  This has been working as expected
>> for about 3 years, somewhere in the past couple of months, something has
>> changed (and not on our end).  $LocalTeleco says everything looks fine
>> to them, but I think they are not super well versed in their Phone
>> switch (mostly by listening to them confer with colleagues and looking
>> up documentation while I'm on the phone with them).
>>
>> With Gratitude,
>>
>> Dave Brockman
>> Senior Network Engineer
>> Gig City Cloud, LLC
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
>> https://puck.nether.net/mailman/listinfo/voiceops 
>> <https://puck.nether.net/mailman/listinfo/voiceops>
> 
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops