05-08-2016 12:46 AM - edited 03-18-2019 11:58 AM
Hey folks,
Am doing a FAC test. I have 1 Partition with 1 CSS with 2 difft. 10 digit extensions (55522220001 and 5553333001). Route Pattern: 9.555XXXXXXX pointing to Voice gateway. On Voice Router I have configured 2 dial-peers for incoming and outgoing.
FAC: 1224 Authorization lvl 10. FAC enabled on route pattern 9.555XXXXXXX.
DP-1
dest-pattern 555222T
session proto sipv2
session transport udp
dtmf-relay sip-notify
codec g711ulaw
no vad
DP-2
dest-pattern 5553333T
session proto sipv2
session atrget ipv4: 192.168.83.248 (CUCM IP address)
session transport udp
dtmf-relay sip-notify
codec g711ulaw
no vad
While debuging I get Q.850 SIP 404 Not found with cause code 1. Pls suggest.
regards,
Ritesh Desai.
Solved! Go to Solution.
05-08-2016 04:57 AM
Did you reset the trunk after putting the CSS on it? I am still seeing no CSS:
00515041.007 |16:44:11.349 |AppInfo |Digit analysis: match(pi="2",fqcn="", cn="5552222002", plv="5", pss="", TodFilteredPss="", dd="5553333001",dac="0")
00515041.008 |16:44:11.349 |AppInfo |Digit analysis: potentialMatches=NoPotentialMatchesExist
05-08-2016 01:21 AM
You need to explain the call flow in detail..where these 2 ten digits extensions exist ? In dial peer 1 you have not mentioned session target :-)
Suresh
05-08-2016 02:01 AM
Good catch, Suresh (+5)
Also, there is a typo for the session target on dial-peer 2 which would prevent the router from taking the command if this was copied and pasted into the router's CLI:
"session atrget ipv4: 192.168.83.248"
Please rate helpful content (i.e. videos, documents, comments). Also, please select the correct answer(s) if any comment(s) answer your question otherwise the questions remains on the support forums as unanswered.
05-08-2016 02:02 AM
If possible, please run these debugs on the router and place a test call. Once done, post the logs so we can take a look.
debug voip ccapi inout
debug ccsip messages
I suggest reading this before enabling the debugs:
https://supportforums.cisco.com/document/62906/how-properly-and-safely-collect-debugs-ios-router
Please rate helpful content (i.e. videos, documents, comments). Also, please select the correct answer(s) if any comment(s) answer your question otherwise the questions remains on the support forums as unanswered.
05-08-2016 02:24 AM
Guyz,
Okey. calls are locally OnNet calls. Components involved are CUCM and Voice Gateway.
Extn-1 5552222002 dials Extn-2 5553333001
FAC Enabled on RP: 9.555XXXXXXX having RL which is mapped to SIP Trunk having destination IP Address of Router 192.168.83.242
Attached is Dialpeer config and debug logs as you suggested.
regards,
Ritesh Desai
05-08-2016 02:30 AM
Thank you for the data. I am about to look at the debugs; however, you have 7 voip dial peers and only two have the session target listed:
-------------
Please rate helpful content (i.e. videos, documents, comments). Also, please select the correct answer(s) if any comment(s) answer your question otherwise the questions remains on the support forums as unanswered.
-------------
05-08-2016 02:34 AM
Pkinane,
Am having UCCE dial-peers as well. Concerned is dial-peer voice 1005. I have mistake of configuring parameter incoming called number 5553333001 in DP 1005. Am removing it.
regards,
Ritesh Desai
05-08-2016 03:08 AM
I saw dial-peer 1005 was matched as the incoming dial-peer and outgoing dial-peer. Having that config for incoming called-number doesn't break it in this scenario. I provided the debug analysis that shows this 404 is coming from the CUCM.
05-08-2016 03:36 AM
Pkinane,
Yes you are right, I also checked in CUCM logs. I see in CUCM traces, CUCM is sending 404 error first. Can you suggest which other places so i need to check?
FYI, w/o FAC am able to call extn to extn.
regards,
Ritesh Desai
05-08-2016 03:05 AM
It seems the 404 not found is coming from the far end of the router and not the router itself.
192.168.83.248 = CUCM
192.168.83.242 = Router
I see the following:
##### May 8 09:48:48.985 || Received || INVITE || 5553333001 || 5552222002 || Call-ID: 35940880-72f1035e-42-f853a8c0@192.168.83.248
May 8 09:48:48.985: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:5553333001@192.168.83.242:5060 SIP/2.0Via: SIP/2.0/TCP 192.168.83.248:5060;branch=z9hG4bK4d56eb9376From: <sip:5552222002@192.168.83.248>;tag=308~00b81cc1-99b7-4170-8919-dbbafb4838a9-28409034To: <sip:5553333001@192.168.83.242>Date: Sun, 08 May 2016 09:14:06 GMTCall-ID: 35940880-72f1035e-42-f853a8c0@192.168.83.248Supported: timer,resource-priority,replacesMin-SE: 1800User-Agent: Cisco-CUCM10.0Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFYCSeq: 101 INVITEExpires: 180Allow-Events: presenceSupported: X-cisco-srtp-fallback,X-cisco-original-calledCall-Info: <urn:x-cisco-remotecc:callinfo>;x-cisco-video-traffic-class=VIDEO_UNSPECIFIEDCisco-Guid: 0898893952-0000065536-0000000034-4166232256Session-Expires: 1800P-Asserted-Identity: <sip:5552222002@192.168.83.248>Remote-Party-ID: <sip:5552222002@192.168.83.248>;party=calling;screen=yes;privacy=offContact: <sip:5552222002@192.168.83.248:5060;transport=tcp>Max-Forwards: 70Content-Length: 0
##### May 8 09:48:48.989 || Incoming Dial-peer=1005 || Called Number=5553333001
May 8 09:48:48.989: //-1/359408800000/CCAPI/cc_api_call_setup_ind_common:
Interface=0x29954528, Call Info(
Calling Number=5552222002,(Calling Name=)(TON=Unknown, NPI=Unknown, Screening=User, Passed, Presentation=Allowed),
Called Number=5553333001(TON=Unknown, NPI=Unknown),
Calling Translated=FALSE, Subscriber Type Str=Unknown, FinalDestinationFlag=TRUE,
Incoming Dial-peer=1005, Progress Indication=NULL(0), Calling IE Present=TRUE,
Source Trkgrp Route Label=, Target Trkgrp Route Label=, CLID Transparent=FALSE), Call Id=38
##### May 8 09:48:48.993 || Sent: || 100 Trying
May 8 09:48:48.993: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 TryingVia: SIP/2.0/TCP 192.168.83.248:5060;branch=z9hG4bK4d56eb9376From: <sip:5552222002@192.168.83.248>;tag=308~00b81cc1-99b7-4170-8919-dbbafb4838a9-28409034To: <sip:5553333001@192.168.83.242>Date: Sun, 08 May 2016 09:48:48 GMTCall-ID: 35940880-72f1035e-42-f853a8c0@192.168.83.248CSeq: 101 INVITEAllow-Events: telephone-eventServer: Cisco-SIPGateway/IOS-12.xContent-Length: 0
##### May 8 09:48:48.993 || List of Matched Outgoing Dial-peer || Tag=1005
May 8 09:48:48.993: //-1/359408800000/DPM/dpMatchPeersMoreArg:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=1005
dial-peer voice 1005 voip
description Outbound calls to CUCM
destination-pattern 5553333T
session protocol sipv2
session target ipv4:192.168.83.248
session transport udp
incoming called-number 5553333001
dtmf-relay rtp-nte
codec g711ulaw
no vad
##### May 8 09:48:49.833 || Received: || 404 Not Found || Call-ID: E5F260DA-143811E6-808D9696-7B7C00C0
May 8 09:48:49.833: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 404 Not FoundVia: SIP/2.0/UDP 192.168.83.242:5060;branch=z9hG4bK769From: <sip:5552222002@192.168.83.242>;tag=1E3AABE0-1EBATo: <sip:5553333001@192.168.83.248>;tag=309~00b81cc1-99b7-4170-8919-dbbafb4838a9-28409035Date: Sun, 08 May 2016 09:14:06 GMTCall-ID: E5F260DA-143811E6-808D9696-7B7C00C0@192.168.83.242CSeq: 101 INVITEAllow-Events: presenceReason: Q.850;cause=1Server: Cisco-CUCM10.0Content-Length: 0
Please make another test call and gather the CUCM traces. Provide the calling number, called number, and the time stamp of the call. Thank you.
-------------
Please rate helpful content (i.e. videos, documents, comments). Also, please select the correct answer(s) if any comment(s) answer your question otherwise the questions remains on the support forums as unanswered.
-------------
05-08-2016 03:23 AM
Pkinane,
Please find the CUCM traces. Timestamp: 3:41pm. as said, i have removed incoming called-number 555333 from DP-1005. Additionally i have checked Media Termination required in SIP trunk.
regards,
Ritesh Desai.
05-08-2016 03:27 AM
as said, i have removed incoming called-number 555333 from DP-1005. Additionally i have checked Media Termination required in SIP trunk.
I don't think you needed to do either. I will look at the traces. It is only one file so hopefully we have the whole call there (or enough of it since it should fail outright when going back to CUCM).
05-08-2016 03:37 AM
##### 15:41:01.358 || Incoming || INVITE || from 192.168.83.242 || Call-ID: D9314B54-144011E6-80B19696-7B7C00C0@192.168.83.242
00504573.002 |15:41:01.358 |AppInfo |//SIP/SIPUdp/wait_SdlDataInd: Incoming SIP UDP message size 845 from 192.168.83.242:[56361]:
[992,NET]
INVITE sip:5553333001@192.168.83.248:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.83.242:5060;branch=z9hG4bKD4BD
Remote-Party-ID: <sip:5552222002@192.168.83.242>;party=calling;screen=yes;privacy=off
From: <sip:5552222002@192.168.83.242>;tag=1E6EC610-536
To: <sip:5553333001@192.168.83.248>
Date: Sun, 08 May 2016 10:45:43 GMT
Call-ID: D9314B54-144011E6-80B19696-7B7C00C0@192.168.83.242
Supported: timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 0689155584-0000065536-0000000040-4166232256
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1462704343
Contact: <sip:5552222002@192.168.83.242:5060>
Expires: 60
Allow-Events: telephone-event
Max-Forwards: 69
Session-Expires: 1800
Content-Length: 0
##### 15:41:01.359 || Outgoing || 100 Trying || to 192.168.83.242 || Call-ID: D9314B54-144011E6-80B19696-7B7C00C0@192.168.83.242
00504577.001 |15:41:01.359 |AppInfo |//SIP/SIPUdp/wait_SdlSPISignal: Outgoing SIP UDP message to 192.168.83.242:[5060]:
[993,NET]
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.83.242:5060;branch=z9hG4bKD4BD
From: <sip:5552222002@192.168.83.242>;tag=1E6EC610-536
To: <sip:5553333001@192.168.83.248>
Date: Sun, 08 May 2016 10:11:01 GMT
Call-ID: D9314B54-144011E6-80B19696-7B7C00C0@192.168.83.242
CSeq: 101 INVITE
Allow-Events: presence
Content-Length: 0
##### 15:41:01.360 || Digit analysis || fqcn="", cn="5552222002" || dd="5553333001" || pss="", TodFilteredPss=""
00504594.007 |15:41:01.360 |AppInfo |Digit analysis: match(pi="2",fqcn="", cn="5552222002", plv="5", pss="", TodFilteredPss="", dd="5553333001",dac="0")
00504594.008 |15:41:01.360 |AppInfo |Digit analysis: potentialMatches=NoPotentialMatchesExist
##### 15:41:01.360 || CI=28409066 || Block NoPotentialMatchesExist
00504595.000 |15:41:01.360 |SdlSig |DaRes |setup_da |Cdcc(1,100,219,170) |Da(1,100,211,1) |1,100,10,1.32^192.168.83.242^* |[R:N-H:0,N:0,L:0,V:0,Z:0,D:0] CI=28409066 Block NoPotentialMatchesExist OnNetpatternUsage =2requestID =0
##### 15:41:01.360 || CcDisconnReq || cv=1
00504596.000 |15:41:01.360 |SdlSig |CcDisconnReq |restart0 |SIPD(1,100,81,9) |Cdcc(1,100,219,170) |1,100,10,1.32^192.168.83.242^* |[R:N-H:0,N:0,L:0,V:0,Z:0,D:0] CI=28409066 CI.branch=0 clearType=0 c.l=1 c.cid=8 c.cs=0 c.lc=0 c.r=0 cv=1 FDataType=0opId=0ssType=0 SsKey=0invokeId=0resultExp=Fbpda=F OnBehalf=Device rfr=0 localPatternUsage=2 connectedPatternUsage=2 rdDestPart= rdDestPatt= rdDestCdpn=pi=0si1 lrnCepn= redDestName=locale: 1 Name: UnicodeName: pi: 0 annId=0 lHPMemCEPN= cHPMemCEPN= dtmCall=F dtmDisconn=F dtmMcNodeId=0 forcedClear=F TransparentData=null CanSupportSIPTandN=false TransId=0 AllowBitMask=0x0 UserAgentOrServer= OrigDDName=locale: 1 Name: UnicodeName: pi: 0 mCallerId= mCallerName= mediaCause=0 CAL={v=ffffffff, m=ffffffff, tDev=F, res=F, devType=0} CAL={v=fffffff6, m=ffffffff, tDev=F, res=F, devType=0}
##### 15:41:01.361 || Outgoing || 404 Not Found || to 192.168.83.242 || Call-ID: D9314B54-144011E6-80B19696-7B7C00C0@192.168.83.242 || Reason: Q.850;cause=1
00504599.001 |15:41:01.361 |AppInfo |//SIP/SIPUdp/wait_SdlSPISignal: Outgoing SIP UDP message to 192.168.83.242:[5060]:
[994,NET]
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 192.168.83.242:5060;branch=z9hG4bKD4BD
From: <sip:5552222002@192.168.83.242>;tag=1E6EC610-536
To: <sip:5553333001@192.168.83.248>;tag=321~00b81cc1-99b7-4170-8919-dbbafb4838a9-28409066
Date: Sun, 08 May 2016 10:11:01 GMT
Call-ID: D9314B54-144011E6-80B19696-7B7C00C0@192.168.83.242
CSeq: 101 INVITE
Allow-Events: presence
Reason: Q.850;cause=1
Server: Cisco-CUCM10.0
Content-Length: 0
##### 15:41:01.367 || Incoming || ACK || from 192.168.83.242 || Call-ID: D9314B54-144011E6-80B19696-7B7C00C0@192.168.83.242
00504648.001 |15:41:01.367 |AppInfo |//SIP/SIPUdp/wait_SdlDataInd: Incoming SIP UDP message size 435 from 192.168.83.242:[56361]:
[997,NET]
ACK sip:5553333001@192.168.83.248:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.83.242:5060;branch=z9hG4bKD4BD
From: <sip:5552222002@192.168.83.242>;tag=1E6EC610-536
To: <sip:5553333001@192.168.83.248>;tag=321~00b81cc1-99b7-4170-8919-dbbafb4838a9-28409066
Date: Sun, 08 May 2016 10:45:43 GMT
Call-ID: D9314B54-144011E6-80B19696-7B7C00C0@192.168.83.242
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Content-Length: 0
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/service/8_6_1/cdrdef/cdradmin/cdrcodes.html
This is what CV 1 is:
1 |
Unallocated (unassigned) number |
Try adding 5553333001 as a directory number on a phone in the CUCM.
-------------
Please rate helpful content (i.e. videos, documents, comments). Also, please select the correct answer(s) if any comment(s) answers your question otherwise the question remains on the support forums as unanswered.
-------------
05-08-2016 03:51 AM
Pkinane,
Thanks for support.
Already I said, 5553333001 is directory number on phone.
Do I need to share RP, SIP Trunk snaps for more idea?
Also, I found similar on forum. https://supportforums.cisco.com/discussion/12527936/cucm-sends-404-incoming-call-sip-trunk
regards,
Ritesh Desai.
05-08-2016 03:51 AM
Then put a CSS on the trunk so it can view the partition where the DN is. Right now it seems you have no CSS for inbound calls.
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