While it's important to rest your SIP trunks, else they become cranky, it's also important to reset them, sometimes more than once, to be sure it's properly initialized with all of the current settings, etc.
I have wasted enough time in the past, just to see that it works after a reset, that I now simply reset the trunk before spending anytime troubleshooting. Granted, this only applies to certain troubleshooting scenarios, like, if I had an existing/working SIP Trunk, and my call center script isn't working correctly, I'm not going to just go reset the SIP trunk. However, if I am integrating a new IP Faxing Server into the environment, and it has never worked before, then I will reset it. Knowing when to reset is a bit of an art, because editing a CSS partition order/member for your SIP Trunk does not require a reset, but editing the SIP profile does. Both are indirectly changing the SIP Trunk functionality, so in a way, should be the same, but they're not. On Thu, Apr 30, 2020 at 8:17 AM NateCCIE <natec...@gmail.com> wrote: > Have you been resting the trunk in cucm after each of your changes? > > Sent from my iPhone > > On Apr 30, 2020, at 7:08 AM, naresh rathore <nare...@hotmail.com> wrote: > > > hi > > > Pls find the attached ccsip messages and cube config. i will send voice > ccapi inout config tomorrow. outgoing call works fine but cucm respond with > 404 message during incoming call attempt > > > Regards > > > > ------------------------------ > *From:* Ryan Huff <ryanh...@outlook.com> > *Sent:* Thursday, April 30, 2020 10:50 PM > *To:* naresh rathore <nare...@hotmail.com> > *Cc:* Amit Kumar <amit3....@gmail.com>; cisco-voip@puck.nether.net < > cisco-voip@puck.nether.net> > *Subject:* Re: [cisco-voip] sip 404 not found for incoming calls > > Naresh, > > Any chance you could send a ccsip messages and a voice ccapi inout debug > from a failed inbound call? > > Sent from my iPhone > > On Apr 30, 2020, at 06:28, naresh rathore <nare...@hotmail.com> wrote: > > > hi > > > I tried both, via translation pattern or directly pointing a particular > number to phone but still the same result. > > Regards > > > ------------------------------ > *From:* Amit Kumar <amit3....@gmail.com> > *Sent:* Thursday, April 30, 2020 6:41 PM > *To:* naresh rathore <nare...@hotmail.com> > *Cc:* James B <james.buchan...@gmail.com>; cisco-voip@puck.nether.net < > cisco-voip@puck.nether.net> > *Subject:* Re: [cisco-voip] sip 404 not found for incoming calls > > Are you having a dn, exact to called number, of you are doing some > translation, then make sure route pattern incoming css shoold have access > to xlate pt. Nd xlate css shoud have access to phones pt. > > On Thu, Apr 30, 2020, 2:02 PM naresh rathore <nare...@hotmail.com> wrote: > > hi, > > > Thanks for the reply. > > > pls see following snapshot and attached gateway config. outgoing dialpeer > (200,201) is currently matching correctly to cucm (for incoming call) > > > > > > > > Regards > > Naray > ------------------------------ > *From:* James B <james.buchan...@gmail.com> > *Sent:* Thursday, April 30, 2020 5:39 PM > *To:* naresh rathore <nare...@hotmail.com>; cisco-voip@puck.nether.net < > cisco-voip@puck.nether.net> > *Subject:* RE: [cisco-voip] sip 404 not found for incoming calls > > > Hello, > > > > Can you send your gateway configuration and a screenshot of your CUCM > trunk configuration? That’d give us more to go off of. > > > > Thanks, > > > > James > > > > > > > > *From: *naresh rathore <nare...@hotmail.com> > *Sent: *30 April 2020 08:36 > *To: *cisco-voip@puck.nether.net > *Subject: *[cisco-voip] sip 404 not found for incoming calls > > > > hi, > > > > > > > > i have cucm version 12.0. outgoing call is working without any issue. but > incoming call is failing. the call request is received by cucm but its > responding with 404 not found. i checked CSS and also pointed call directly > to ip phone using significant digits and incoming css but still the same > issue. also sip uri have called number. not sure why 404 not found msg is > sent by cucm to cube. > > > > > > Regards > > > > Naray > > > _______________________________________________ > cisco-voip mailing list > cisco-voip@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-voip > <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7C01617e1596284dca88b408d7ecf129b1%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637238392830409694&sdata=hxzkpvvwAxXyygB9nHWJ9muvREigqaBddZmALmRdycw%3D&reserved=0> > > _______________________________________________ > cisco-voip mailing list > cisco-voip@puck.nether.net > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7C01617e1596284dca88b408d7ecf129b1%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637238392830439677&sdata=%2BBocnzBxzrQDeGY8H4FLLCSBtxWvNCm8i%2FY8km%2F3t7o%3D&reserved=0 > > <detailed ccsip messages.txt> > <gatewayconfig.txt> > _______________________________________________ > cisco-voip mailing list > cisco-voip@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-voip > > _______________________________________________ > cisco-voip mailing list > cisco-voip@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-voip >
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
