Setting Outbound CallerID

[shepds]

We are using 3CX SMB with Flowroute as our SIP Trunk Provider. I believe I have the outbound CallerID settings correct with both 3CX and Flowroute. However, when outbound calls are received from any of our DIDs, we are identified on the recipient's phone as "Unknown". If anyone can provide guidance on how to set this up properly, it would be greatly appreciated. Thanks in advance.

 

[NicholasP_3CX]

In what format is your caller ID defined. Providers usually require it in E164. But ask you rprovider.

In the case where the caller ID is in an incorrect format, the provider may mask, or even reject your outgoing calls.

 

[HelloMalz]

I cant seem to get CNAM or CLID to work reliably with Flowroute and 3CX free. Purchased a support ticket to find out that you can NOT submit a ticket if using a free product but there isnt a paid for product that is for under 10 users?

 

[fortech]

I cant seem to get CNAM or CLID to work reliably with Flowroute and 3CX free. Purchased a support ticket to find out that you can NOT submit a ticket if using a free product but there isnt a paid for product that is for under 10 users?

Hi, not sure if it is helpful, but
(1) some reseller might be OK to work with you for a smaller 3cx instance - 4SC is still legacy 'product that may be sold' / depending on the 3cx partner-reseller
and/or
(2) alternately I might suggest you try a simple 'test config use case' where you (a) purchase a SIP DID in your callerID/phone region of interest from a '3cx approved supplier SIP trunk vendor" - this can be done for a ~few dollars for a ~1mo DID fee - and then do a test setup in your config to link this new SIP trunk to your 3cx free instance. Then see if CallerID is behaving better when your calls route out via this sip trunk. It would be a straightforward way to evaluate if the issue is related to 3cx<>FlowrouteSipTrunkVendor (ie, either the 3cx<>Flowroute config file / config / or the way this carrier is dealing with the calls you route out to them?) and then possibly give you an option for how to move the topic forward. Worst case you can always port your DID away from FlowRoute to (DID provider that works better) in case this is a viable workaround solution to keep your DID(s) active / working with 3cx (Free) / with minimal drama.

--Tim