|Summary||This document is directly based upon MyForce's SIP validation template. This trimmed down version will enlist the same steps.|
|Keywords||CTArchitect; SIP ; Gateway ; servers ; telephony|
Our telephony partners, MyForce, do provide a telephony environment validation service.
However, if your IT teams wish to configure a new environment, here is a checklist for them to make sure that CTArchitect is correctly hooked up to your system.
- Verify SIP registration. In case SIP registration is used instead of trusting. This can be done in CTArchitect by checking the IP Registrations Window.
Note: it can take a few minutes before this registration shows up as successful.
- Make test calls using the following codecs G711A and G729 (optional, if the compression option has been purchased)
- CLI masking.
- Check whether calls can be made without providing a CLI.
- Try to make a call and provide a CLI that lies outside the range of the SIP trunk.
- Check whether calls over 30 minutes are possible. Some SIP trunk providers and gateways are configured by default to cut calls over 30 minutes.
- Check basic voice quality. Is the voice clear and latency reasonable enough to do have a conversation?
- Set up an international call.
- Outbound disconnect causes.
It is important for CTArchitect that disconnect causes are given by out-of-band disconnect codes and that these codes are received within reasonable time. This is especially important when using the CTArchitect as an outbound dialer. This is checked by taking wireshark traces and looking at the SIP packets directly.
- Busy disconnect cause
- Unused number
- Incomplete number (too short)
- A number that is too long
- DTMF tones. Are DTMF tones sent correctly and received on CTArchitect? This is done by simply listening whether DTMF tones are received on the phone.