Trace server - A Better Way to Debug PortSIP UC
Last updated
Last updated
PortSIP has been building its SIP Trace Server base on the open-source project , which provides key information in troubleshooting SIP Trunks, SIP endpoints, and other SIP related issues. It provides a place to:
Access singularly to retrieve SIP captures via Web UI
Centrally store SIP capture data across many hosts
More intuitively filter SIP capture data and correlate the data to the dialog/transactions each request/response is part of (this is immensely useful!)
Gracefully age dated capture data you don’t want to persist for very long (though persisting longer term can be configured very easily)
Charts! glorious charts!
CentOS: 7.9
Ubuntu: 18.04, 20.04
Debian: 10.x
Only supports 64bit OS
Since the Trace server usually will take large CPU and memory resources, we recommend below hardware specifications for the SIP Trace Server:
CPU: 2-4 cores
Memory: 2G - 4G
CPU: 4 cores
Memory: 4G
CPU: 8 - 10 cores
Memory: 8G
CPU: 16 - 20 cores
Memory: 16G
The firewall and cloud platform security group must allow the ports listed below.
Port 9061 on TCP
Port 9060 on TCP
Ensure server date-time is synced correctly
Must perform all Linux commands by the root user, please su root first
After the PortSIP Trace Server is successfully installed, you can access the trace server Web Portal by below URL:
http://trace-server-ip:9080
The user name is admin, the password is admin
Sign in the PortSIP PBX Web Portal, click the menu "Advanced" > "Settings", on the "Advanced" page, enter the trace server information for the "Custom Options" field as below:
Please see the below screenshot.
After successfully set up the SIP trace server information in the "Custom Options" field and clicked the "Apply" button, the PBX will send all SIP messages to the trace server.
Click the menu "Advanced" > "Settings", on the "Advanced" page, delete all text content in the "Custom Options" field, and click the "Apply" button, the PortSIP PBX will stop to send the SIP message to trace server.
Important: SIP Trace should be off most of the time and only enabled when troubleshooting is required.
You can choose to display the registration messages or the call SIP messages on the SIP Trace Server Web Portal, as seen in the screenshot below; the "Home" is for calls, and the "REGISTRATION" is for the REGISTER messages.
You can view the details of a message by clicking on the method name, as shown in the screenshot below.
There is the way to check the call-id, X-Session-Id, and X-CID of the SIP message are as follows:
call-id, X-Session-Id, and X-CID can now be used to search SIP messages.
From the messages list, we can see the call flow by clicking the Session ID.
