Hi,
I'm troubleshooting a SIP trunk-to-SIP trunk call on a 3CX SMB instance.
The call flow is:
PeopleFone SIP trunk → 3CX SMB → VAPI SIP trunk
The incoming call from PeopleFone reaches 3CX correctly. 3CX then routes the call to the VAPI SIP trunk.
The problem appears to occur around SIP ACK handling on the VAPI leg.
I'm trying to determine exactly what happens after the VAPI side returns 200 OK — specifically whether 3CX receives the 200 OK, whether 3CX generates the corresponding ACK on the VAPI leg, and where that ACK is being sent.
The problem is that I'm using 3CX SMB, and the Admin Console does not expose the detailed SIP Activity Log / Verbose logging or PCAP capture available on dedicated 3CX installations.
The available Event Log only shows high-level events and does not provide the per-call SIP signalling needed to investigate this. The normal Call History also doesn't expose the SIP transaction details for this trunk-to-trunk call.
Is there any way for an SMB administrator to obtain the detailed SIP signalling for a specific call, or can 3CX Support/Staff inspect the underlying SIP trace for a specific call?
Ideally, I would like to see the signalling on both legs:
PeopleFone ↔ 3CX
and
3CX ↔ VAPI
particularly the 200 OK and subsequent ACK.
/ If anyone has experience with this type of issue or this setup, I would also appreciate any support there
I'm happy to provide timestamps, Call-ID, trunk information, and sanitized SIP logs if that helps.
Note it would be the 1832 not the 1281, I am using the 1281 as control / testing.
Thanks.
I'm troubleshooting a SIP trunk-to-SIP trunk call on a 3CX SMB instance.
The call flow is:
PeopleFone SIP trunk → 3CX SMB → VAPI SIP trunk
The incoming call from PeopleFone reaches 3CX correctly. 3CX then routes the call to the VAPI SIP trunk.
The problem appears to occur around SIP ACK handling on the VAPI leg.
I'm trying to determine exactly what happens after the VAPI side returns 200 OK — specifically whether 3CX receives the 200 OK, whether 3CX generates the corresponding ACK on the VAPI leg, and where that ACK is being sent.
The problem is that I'm using 3CX SMB, and the Admin Console does not expose the detailed SIP Activity Log / Verbose logging or PCAP capture available on dedicated 3CX installations.
The available Event Log only shows high-level events and does not provide the per-call SIP signalling needed to investigate this. The normal Call History also doesn't expose the SIP transaction details for this trunk-to-trunk call.
Is there any way for an SMB administrator to obtain the detailed SIP signalling for a specific call, or can 3CX Support/Staff inspect the underlying SIP trace for a specific call?
Ideally, I would like to see the signalling on both legs:
PeopleFone ↔ 3CX
and
3CX ↔ VAPI
particularly the 200 OK and subsequent ACK.
/ If anyone has experience with this type of issue or this setup, I would also appreciate any support there
I'm happy to provide timestamps, Call-ID, trunk information, and sanitized SIP logs if that helps.
Note it would be the 1832 not the 1281, I am using the 1281 as control / testing.
Thanks.
