ā08-30-2022 08:10 PM - edited ā08-30-2022 08:13 PM
All was good until a major power failure. No one was onsite and battery backups went down due to power outage length. When system came back up outbound from IP Phones worked theough SIP Trunk. However inbound calls all fail.
Flow is through ASA5506 (IP:Port to 2821) - 2821 - Voice Dial Peer - UCM10.5 - CTI RT PT - CUC10.5 - System Call Handler
When I call the Call Handler from an internal IP PHONE I hear the CUC recorded System Call Handler message
Checking 2821 DialPeer I see incoming dialpeer match however UCM is never contacted and therfore CUC System Call Handler does not start
Here is a piece of debug voip dialpeer inout when the number is called. This log goes on until the call fails and the Calling - Called Number eventually become blank
010694: Aug 31 02:58:56.424: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Calling Number=, Called Number=, Voice-Interface=0x0,
Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
010695: Aug 31 02:58:56.424: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=NO_MATCH(-1) After All Match Rules Attempt
010696: Aug 31 02:58:56.424: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=-1
010697: Aug 31 02:58:56.424: //-1/B035244E897A/DPM/dpAssociateIncomingPeerCore:
Calling Number=, Called Number=, Voice-Interface=0x0,
Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
010698: Aug 31 02:58:56.424: //-1/B035244E897A/DPM/dpAssociateIncomingPeerCore:
Result=NO_MATCH(-1) After All Match Rules Attempt
010699: Aug 31 02:58:56.424: //-1/B035244E897A/DPM/dpMatchSafModulePlugin:
dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=-1
010700: Aug 31 02:58:58.160: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Calling Number=5856725663, Called Number=5856725663, Peer Info Type=DIALPEER_INFO_SPEECH
010701: Aug 31 02:58:58.160: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=5856725663
010702: Aug 31 02:58:58.160: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
010703: Aug 31 02:58:58.160: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
dialstring=5856725663, saf_enabled=1, saf_dndb_lookup=1, dp_result=0
010704: Aug 31 02:58:58.160: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=92
2: Dial-peer Tag=10
Here are the dialpeers
dial-peer voice 92 voip
SIP-UA info
sip-ua
no remote-party-id
retry invite 2
retry register 2
retry options 1
timers connect 100
registrar dns:sip34.vitelity.net expires 3600
sip-server dns:sip34.vitelity.net
host-registrar
Voice and SIP info
voice service voip
ip address trusted list
ipv4 66.241.99.181 255.255.255.255
ipv4 64.2.142.189 255.255.255.255
clid network-provided
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
no supplementary-service sip refer
no supplementary-service sip handle-replaces
redirect ip2ip
fax protocol pass-through g711ulaw
no fax-relay sg3-to-g3
h323
h450 h450-2 timeout T1 1000
h450 h450-3 timeout T1 1000
h225 timeout ntf 500
h225 display-ie ccm-compatible
h225 connect-passthru
h245 passthru all
modem passthrough nse codec g711ulaw
sip
registrar server expires max 600 min 60
early-offer forced
midcall-signaling passthru
no call service stop
Any thoughts on how to proceed are welcomed.
Solved! Go to Solution.
ā08-31-2022 11:18 AM - edited ā08-31-2022 11:30 PM
My response posted with such a long delay that it no longer applies since Carl already replaced the original dial-peers. Since I canāt delete my post, I removed the suggested changes using edit.
That being said, I agree with TechLvrās suggestion.
ā08-31-2022 11:11 PM
@Carl Fitzsimmons I would advise you to keep the dial peers as you have entered them as based on @b.winter suggestion instead of making additional changes as suggested in this reply from @RezaNazari3290. The other suggested alterations are absolute applicable and advisable.
ā09-01-2022 12:00 AM
You got so much help and support Carl! I agree with @Roger Kallberg on dial-peer advices in last post. Please do not have destination-pattern .T on inbound dial-peers and keep config advised by @b.winter . Please publish logs with current config. Are you sure that CUCM side is setup correctly? Do you have check box "Run On All Active Unified CM Nodes" on SIP trunk? How many call processing nodes do you have (Subscribers) in CUCM cluster? The reason why I am asking is that in the only debug you attached CANCEL came from CUCM.
ā09-01-2022 07:22 AM - edited ā09-01-2022 07:25 AM
Yes I have and it has enabled almost full use. I am processing what I thought would be an easy pickup verses what has happened after power outage. To your questions
One UCM Pub (10.8.32.20) and no Subs
One CUC Pub (10.8.32.30) no Subs
"Run On All Active Unified CM Nodes" is checked on SIP TRUNK
Getting debug now and will post config
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide