We provide you with extensive faulting tools to allow you to investigate any issues prior to contacting us.  Below are a list of checks required to be performed prior to Raising A Fault Ticket:

1. Access and review the PBX in question

PBX logs can be extremely useful and attaching a PBX log file for an issue or call is very useful.  Please do also confirm hat the call definitely routed via our service: it may be that we have legitimately barred the call, for example, whereupon the PBX may be automatically attempting to send the call via alternative / back-up route.

2. Check internet connectivity and ensure there aren't any service affecting issues with your ISP

If there is any suspicion that the internet service may have been a reason for an issue / failed call(s) please check your / your client's in-house monitoring system to check if there was an internet service issues / drop at the time of the issue / call. If you do not have such monitoring systems then check the router’s log files.

3. Check if you can access the SIP Trunk Plus portal

In the unlikely event that there is an issue affecting our platform, we will immediately update our service notification icon (green: no issues; amber: minor service affecting issue; red: major service affecting issue) and associated notification message.  Please do check and follow portal status notifications by Setting Up A Service Alert 'System Status' Notification.  Via the portal:

(a) check to see if the trunk(s) are registered via the 'Registrations' tab

(b) for outbound call related issues, check the Barred Calls Log

(c) if you have previously set one up for the PBX IP address, please review the MTR Report link to go here to MTR Reports solution

(d) for call related issues, check the 'VM' ('VoIP Monitor') link for affected calls on the 'CDR' tab link to go here to VoIP Monitor CDR Link solution

For all other issues you should supply a SIP trace (e.g Wireshark or similar network protocol analyser tool) that captures the issue in question (if the issue is connectivity or call related).

If you or your technically able third parties have actioned each of the above and you can see a issue that is directly attributable to our service, please refer to Raising A Fault Ticket
 and provide the information detailed in points '1 - 9' therein as this information is required in order to investigate any issues.