One way calling issue on CME
I ran into my first real issue this evening. I was trying to set up 2 SIP and 2 SCCP phones on CME. Everything was working except one SIP phone couldn’t receive calls from the other phones. It could make calls though. All calls to that particular SIP phone with extension 3005 would come up busy.
debug ccsip messages didn’t show anything useful. Neither did a whole lot of other debugs. On a whim, I looked at debug voip dial-peer:
BR2#debug voip dialpeer voip dialpeer default debugging is on BR2# Feb 15 01:24:31.677: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore: Calling Number=3005, Called Number=3005, Peer Info Type=DIALPEER_INFO_SPEECH Feb 15 01:24:31.677: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore: Match Rule=DP_MATCH_DEST; Called Number=3005 Feb 15 01:24:31.677: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore: Result=Success(0) after DP_MATCH_DEST Feb 15 01:24:31.677: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg: Result=SUCCESS(0) List of Matched Outgoing Dial-peer(s): 1: Dial-peer Tag=20002 2: Dial-peer Tag=40002
Now that doesn’t look right. Why would there be 2 matches? A SIP phone should create only 1 dial-peer in the 40,000 range. Sure enough, I accidentally created an SCCP entry via the ephone-dn command.
BR2#sh dial-peer voice summary dial-peer hunt 0 AD PRE PASS OUT TAG TYPE MIN OPER PREFIX DEST-PATTERN FER THRU SESS-TARGET STAT PORT 20001 pots up up 3001$ 0 50/0/1 20002 pots up up 3005$ 0 50/0/2 20003 pots up up 3002$ 0 50/0/3 40002 voip up up 3005 0 syst ipv4:10.10.202.54:50 40001 voip up up 3006 0 syst ipv4:10.10.210.251:8
Removing the offending ephone-dn resolved the issue. Well, that wasn’t really 2 hours wasted as I got a chance to look a little closer at many other useful debugs.
