[cisco-voip] Errors 18 and 19 on incoming call only through subscriber

[Brian Meade]

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.ROZA at 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 at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150210/238a35f1/attachment.html>