Hi, Guys… I restarted RIS on both nodes and did not do a thing, so I guess Ryan might be right. What´s the alternative? Restarting the Callmanager Service? Rebooting the whole sub? Both Sub and Pub?
I have h225, h245 and full ccm traces if there´s any use for them. Regards, Ariel. From: Ryan Ratliff (rratliff) [mailto:rratl...@cisco.com] Sent: miércoles, 11 de febrero de 2015 11:23 a.m. To: Brian Meade Cc: ROZA, Ariel; cisco-voip voyp list Subject: Re: [cisco-voip] Errors 18 and 19 on incoming call only through subscriber RIS shouldn’t be involved in that flow, though it does read from the same shared memory segment that the ccm process does so unless RIS itself is screwed I’d expect if ccm doesn’t know a remote phone’s registration status RIS on that node won’t either. -Ryan On Feb 10, 2015, at 5:19 PM, Brian Meade <bmead...@vt.edu<mailto:bmead...@vt.edu>> wrote: Right, could be an SDL link down. I've seen this caused by RIS issues where the node receiving the call doesn't think the phone is registered (can't find the LineControl process). Restarting RISDC usually fixes it. On Tue, Feb 10, 2015 at 4:26 PM, Ryan Ratliff (rratliff) <rratl...@cisco.com<mailto:rratl...@cisco.com>> wrote: How would this be RIS? More like an SDL connection that’s down, or leaked a call on the sub. Register a phone to the sub and see if you can call to/from another phone registered to the pub. -Ryan On Feb 10, 2015, at 10:32 AM, Brian Meade <bmead...@vt.edu<mailto:bmead...@vt.edu>> wrote: Usually this is a RISDC problem. Check database replication is working okay and then restart RISDC on all nodes. On Tue, Feb 10, 2015 at 9:06 AM, ROZA, Ariel <ariel.r...@la.logicalis.com<mailto:ariel.r...@la.logicalis.com>> wrote: Guys, I am having and odd situation: I have a CUCM cluster ( Pub & 1 Sub) where i have set up a new branch office with an H323 Gateway and several phones. The config template is similar to other already working branches, but in this particular branch incoming calls are behaving strangely. PSTN calls come through a FXO port, pass an autoattendant TCL script on the GW and get routed to CUCM via two identical dialpeers ¡, one for the Sub and one for the Pub. Debugs show that if calls use the Dialpeer to the Pub, the call goes fine, and the receiver phone answers the call. But if the call uses the Subs dialpeer, it fails with a Disconnect Cause code 18 (user busy) or 19 (user busy - user alerted). The destination in both cases is the same: a Hunt List that is reachable via any internal phone. DNA shows the logic is ok, and debugs on both, the gateway and CUCM show the same results, so conectivity should not be an issue. Does anyone have any suggestion, besides rebooting the Subs? CUCM version is 8.6.2 The Pub and the Subs are in different subnets. Regards, Ariel. _______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> https://puck.nether.net/mailman/listinfo/cisco-voip _______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net<mailto: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
