Picking up call results in hearing 3CX Voicemail

[Alphabetic]

A continuation from this, the issue still exists.

https://www.3cx.com/community/threa...ittently-hearing-voicemail.84311/#post-394766

At the moment it's happening for 1 person only (AFAIK).

will be doing more tests tomorrow.

 

[ChrisC_3CX]

I have to say, this sounds like something you would possibly need to take up with our Support Team as it would definitely need reviewing a packet capture and verbose logs to figure out what's happening exactly.

If it is indeed only affecting one specific person trying to figure out what's different about that extension's configuration or what the user does differently compared to others may be key to identifying the cause.

 

[Alphabetic]

I have to say, this sounds like something you would possibly need to take up with our Support Team as it would definitely need reviewing a packet capture and verbose logs to figure out what's happening exactly.

If it is indeed only affecting one specific person trying to figure out what's different about that extension's configuration or what the user does differently compared to others may be key to identifying the cause.

I was trying not to waste their time.

It's a new site (one of many we've installed) but we put in a managed PoE switch so i'm going to look here first before I raise a ticket.

 

[ChrisC_3CX]

Understood, if you're familiar with wireshark you could try and capture such an event and look at the whole sip flow including the one following up to the specific call. Hopefully this might shed some light on the matter. I'd also recommend enabling Verbose Logging mode on the PBX, et least until you capture the call to have the logs fill in any gaps if needed.

 

[Alphabetic]

So i've just installed the latest firmware on the TP Link PoE managed switch and i'll see how it goes.

Time was wrong too on there, not sure if that makes a difference.

 

[Alphabetic]

Hi Support

Just a question regarding the SBC (Pi).

If I want to run a trace do I need to run pcap on the Pi or does the verbose logging from mgmt turn this on?

 

[ChrisC_3CX]

If I want to run a trace do I need to run pcap on the Pi or does the verbose logging from mgmt turn this on?

To run a packet capture on the pi you need to do it manually, we usually recommend tshark but you can of course use another linux tool for packet captures if you prefer.

To clarify a few things regarding logs and packet captures:

PBX

• Enabling Verbose Logging for the PBX is done via "Dashboard >> Activity Log >> Settings". This will enable verbose logging for the PBX's logs only. Does not affect packet captures.

• To run a packet capture on the PBX you have to go to "Dashboard >> Activity Log >> click on 'Capture'". If you want to capture SBC traffic too you will have to select all interfaces, as the SBC traffic is encapsulated in the 3CX tunnel and therefore can only be seen on the loopback interface. IF the PBX is running on a windows machine you have to install wireshark and make sure that the npcap driver is also installed to allow packet captures on the loopback interface.

SBC

• To enable verbose logging on the SBC you will have to navigate to "SIP Trunks >> Edit the SBC >> Settings >> Change Logging Level to Verbose and save(OK)". Go back to SIP Trunks, selectthe SBC and click on "Push Config" above. This should take care of the SBC's logs verbosity but has nothing to do with the packet capture.

• To run a packet capture on the SBC you will have to manually connect to the SBC (SSH, etc) and use a tool such as tshark to start , stop, save the packet capture. This cannot be managed via the 3CX Management Console.

 

[Alphabetic]

To run a packet capture on the pi you need to do it manually, we usually recommend tshark but you can of course use another linux tool for packet captures if you prefer.

To clarify a few things regarding logs and packet captures:

PBX

• Enabling Verbose Logging for the PBX is done via "Dashboard >> Activity Log >> Settings". This will enable verbose logging for the PBX's logs only. Does not affect packet captures.

• To run a packet capture on the PBX you have to go to "Dashboard >> Activity Log >> click on 'Capture'". If you want to capture SBC traffic too you will have to select all interfaces, as the SBC traffic is encapsulated in the 3CX tunnel and therefore can only be seen on the loopback interface. IF the PBX is running on a windows machine you have to install wireshark and make sure that the npcap driver is also installed to allow packet captures on the loopback interface.

SBC

• To enable verbose logging on the SBC you will have to navigate to "SIP Trunks >> Edit the SBC >> Settings >> Change Logging Level to Verbose and save(OK)". Go back to SIP Trunks, selectthe SBC and click on "Push Config" above. This should take care of the SBC's logs verbosity but has nothing to do with the packet capture.

• To run a packet capture on the SBC you will have to manually connect to the SBC (SSH, etc) and use a tool such as tshark to start , stop, save the packet capture. This cannot be managed via the 3CX Management Console.

Thanks.

Where on the Pi would verbose logs end up?

 

[ChrisC_3CX]

The 3CX SBC Logs on a raspberry Pi should be in the following directory:

/var/log/3cxsbc/