 Type=DIALPEER_INFO_SPEECH By using the show dialplan number number-string command, you can see how and if your dial peers are matching. This command doesn't actually dial anything, but just reports on which dial peers have matched your number string. The output can be ex- tensive, but it's easy to find the relevant information. Here's an example from when our system was configured to use POTS dial peers: Troubleshooting R1-PBX#sho dialplan number 92111111111 Macro Exp. : 92111111111 VoiceEncapPeer100 peer type = voice, system default peer = FALSE, information type = voice, description = tag = 100, destination-pattern = `9[2-9] voice reg type = 0, corresponding tag = 0, allow watch = FALSE answer-address =``, preference=0, CLID Restriction = None CLID Network Number = [--output truncated- ] Here's the same command run with only the VoIP dial peers enabled: R1-PBX#sho dialplan number 92111111111 Macro Exp. : 92111111111 VoiceOverIpPeer90 peer type = voice, system default peer = FALSE, information type = voice, description = tag = 90, destination-pattern = `9..........', voice reg type = 0, corresponding tag = 0, allow watch = FALSE answer-address = `', , preference=0, CLID Restriction = None CLID Network Number = To see if your SIP endpoints are registered, use the show sip-ua register status com- mand. Since we're using SIP only for our trunks and we've used the no-reg keyword on our ephone-DNs, that's all we see. If we were using SIP phones, we'd see those numbers registered here as well: R1-PBX#sho sip-ua reg status expires (sec) registered P-Associated-URI 557333333 608222222 To see all the messages that SIP sends and receives, use the debug ccsip messages com- mand. This is a fabulous tool that will show you every bit of SIP communication from phone and trunk registrations to INVITES, CANCELs, BYEs, and all their associated responses. If you've got a problem with your SIP trunks, this is the command that will show you exactly what's going on: R1-PBX#debug ccsip messages SIP Call messages tracing is enabled To