Review DTMF compatibility on common call paths
Check keypad input on routes that use different codecs or providers.
From the blog
Anonymised incident analyses and field notes showing how VoIP and telephony problems were investigated.
Check keypad input on routes that use different codecs or providers.
Compare a failed IVR input with the DTMF method negotiated on each call leg.
Confirm the agreed DTMF method across phone, PBX and provider legs.
Find rules that no longer match the provider's documented voice path.
Compare SIP setup with media packets on both sides of the firewall.
Document the signalling and media path before opening ports or altering NAT.
Look for changes in rejection and timeout patterns without treating every code as an incident.
Use the complete request and response sequence to interpret a SIP code.
Define the expected response and call outcome before changing a SIP route or policy.
Check whether documented voice paths still match active switch, IP, DNS and call-service settings.
Compare physical link, addressing, name resolution, signalling and media evidence before changing settings.
Locate the device, network and application handoffs affected by a voice-network change.