My suggestion would be to review detailed CCM traces and ccsip debug output from your CUBE. The examples you listed below seem pretty accurate, but getting a concrete answer about why you receive a 404 when dialing a valid telephone number would only be possible through detailed CCM SDI/SDL traces and debugs off the gateway. With so many variables that can alter your call between CUCM and CUBE, SDI/SDL traces and ccsip debugging will provide you with accurate data about what's occurring within your environment.
The high level steps I would take after setting CCM traces to detailed and recreating the 404: 1. Use Notepad++ to open your SDI/SDL traces. 2. Use a style token to highlight your Call-ID headers for your test call 3. Follow related SIP events until you find your 404 4. Review SDI/SDL signaling that's printed in traces just before the 404 is generated. Do you see a failure on LBM (location bandwidth manager) bandwidth reservation? Do you see Digit Analysis returning with a "No Potential Matches" in the DA response? Do you see the 404 being received by CUCM from CUBE? If so then you'll have to review output of ccsip debugging off CUBE to see if the 404 is being generated by the ITSP or your CUBE router. 5. If generated by CUBE then I would place another test call while running a debug of the ccapi to determine what dial-peers are being match, if there's a match failure, incorrect/misconfigured sip profiles or voice translation rules, etc. Obviously this is a very high level description and the methods used to review CCM traces is dependent on the number of CUCM nodes, where your devices are registered, and if you're on CUCM 9x or on a version below, etc.. I hope this helps. - Daniel -----Original Message----- From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Mahudeswaran A Sent: Sunday, April 27, 2014 3:57 AM To: sip-implementors-ow...@lists.cs.columbia.edu; discuss...@sipforum.org; sip-implementors@lists.cs.columbia.edu Subject: [Sip-implementors] more 404-Not Found calls Hello All, Would like to clarify under what circumstances UAC gets "404-NOT Found---Reason=unallocated number" for an INVITE request; Sip trunk established between UAC & Cisco call manager; Call path: UAC -----> cisco cm ----> voice gateway ------> (ITSP) We captured wireshark traces for 404-Not Found messages and some phone numbers are actually invalid numbers and some phone numbers are valid; The INVITE request having timeout set as 'SIP header ==Expires: 180'. This is as suggested & being asked us to put in here for the calls to work; We did faced more calls getting 404-NotFound response. So trying to find what are all the possible scenarios the cisco cm could send the 404-NotFound error response; Some reason like 1. The dialling number itself is invalid and service provider plays the message saying "like...number is invalid.." 2. Due to not enough bandwidth between voice gateway & ITSP 3. Due to not enough bandwidth between cisco cm & voice gateway --- (This is least option if all the ports in gateway are busy.... The cm should send busy instead of 404-NotFound..) 4. Comments from other team says the UAC is sending something wrong here because of which more 404-NotFound; --- randomly we picked some 404-NotFound numbers and tested by manual dialling and found those were valid numbers. Any other reasons for 404-NotFound?? -- How to troubleshoot these issues; Regards Mahu _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
