Debugging Call Failure

Occasionally calls will fail for a range of reasons. The best way to start debugging calls failing is with a PCAP trace. Further once the release reason is understood you can make adjustments to your call or you can raise a ticket with us and we can provide advice. 

Tracing a Call

A trace can be taken from your own switching platform to ensure delivery. The application used for making traces can vary between systems and application. Wireshark, Tcpdump, TShark, etc. These are different applications for capturing and displaying network packet captures. This will enable to look at what the call is doing on the wire. Often these facilities are built into switches or are provided as part of the debugging package supplied by a provider. 

A command will often look like the following and can be started from most nix based systems command line. 

tcpdump -w trace.pcap -i any

This simple command will produce a trace of all packets for any port on any interface and put it in a file called trace.pcap for use in a program like Wireshark for decoding the information. 

Raise an Issue with cloudnumbering

When raising an issue with cloudnumbering support, we require the following information to investigate issues with calls. 

To number

From number

UTC Timestamp of call

Error received

Preferably we require 3 examples of the failures in case we require to escalate with any of our providers.