Receiving someone else's calls

[cobaltit]

So you are interested in the lines before the first one. That line is where 3CX has already made a decision on where to send the call (107). Below that line you should see the SIP Invite with something like this:

Contact: <sip:[email protected]:5060>
To: <sip:[email protected]>
From: "CALLER ID NAME " <sip:[email protected]>;tag=as7031a8fd

In that snip you can see the To User Part (5551212) is the number that was called and the From User part (8675309) is the number that called me. In your case if it says anonymous then there might not be a from user part but there should be a To user part which is likely how your instance is making the routing decision. The To User part is typically what your inbound rules would match for DID based routing or the From User part for CID based routing.

 

[leejor]

More information logs not related to a specific incoming call.

28/08/2017 10:16:07 - Update MWI info for Extn:107: new=1; total=2 (an update to to message waiting indicator)
28/08/2017 10:15:20 - [Flow] Endpoint Extn:107 has no forwarding rule on reason 'All calls' (information about the forwarding options on that extension)
28/08/2017 10:15:20 - OverrideExt.107 has no profile override, RG calls are enabled (more information about options on that extension)
28/08/2017 10:15:20 - [Flow] Target endpoint for 107 is Extn:107 (Ext 107 is going to be the destination, but no info, in this line,on the originator)

Nothing that shows a specific incoming call terminating on a specific extension, along with the routing that was taken

 

[Peter Richardson]

I received yet another call today from a mobile phone that was not meant to go to me. 3CX in all their wisdom have decided to disable logging unless you enable it manually, so I had to ask the guy to bear with me while I log into the system, enable the logging, then ask him to call me back and hopefully it would happen again. Luckily it did, so I have a log of it.

2 things: 1) what do I do with the .pcap file and 2) what possible reason would there be for disabling logging? The only thing I can think of is reducing load on the CPU, which is virtually zero anyway, so why make it even harder to diagnose intermittant problems????

 

[YiannisH_3CX]

Threads now lock after 30 days of inactivity that is why the thread was locked. Logging is set to low by default to reduce the load on the system. On busy systems verbose logging can eat up too much disk space and even affect audio quality. If you need verbose logging you need to manually set it and restart services if you face issues that need troubleshooting.
You can send me the pcap file in a private message along with the support files of the PBX. To generate the support files please navigate to the top right of the management console and click on generate support info. Upload the files to web transferring service and send me the link so i can download the files