At step 80B, a diagnostics (e.g., troubleshooting) mode may be initiated. Step 80B may include initiating storage of data associated with the SIP trunk 29 in memory, such as the buffer(s) 56. The data may be copied to the buffer 56. The buffer 56 may be operable to store a copy of calls, events and/or other communications across the trunk 29. In implementations, an end user such as a client SIP administrator may interact with the user interface 44 to initiate the diagnostic mode. The diagnostics environment 40 may be operable to connect to the buffer 56 and consume events (e.g., calls) associated with the trunk 29.

At step 80C, communications may be initiated. Step 80C may include attempting to communicate over the trunk 29. The communications may include one or more calls between the client server 26 and one or more devices associated with the telephone network 32. The call may be initiated with a VoIP phone and/or another computing device.

At step 80D, data associated with the trunk 29 may be accessed. In implementations, step 80D may include accessing the data from the buffer(s) 56. The data may correspond to actual and/or virtual call activity during the diagnostics mode. The buffer 56 may store a copy of traffic associated with one or more calls between the trunk 29 and telephone network 32.