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

Thu Mar 5 18:08:26 EST 2015

You could try just resetting the hunt list first.

On Thu, Mar 5, 2015 at 5:35 PM, ROZA, Ariel <Ariel.ROZA at la.logicalis.com>
wrote:

>  Thanks. So, the short term workaround would be to restart the CCM
> Service, until I can apply the latest service release. Right?
>
>
>
> *From:* bmeade90 at gmail.com [mailto:bmeade90 at gmail.com] *On Behalf Of *Brian
> Meade
> *Sent:* jueves, 05 de marzo de 2015 07:15 p.m.
> *To:* ROZA, Ariel
> *Cc:* Ryan Ratliff (rratliff); cisco-voip voyp list
>
> *Subject:* Re: [cisco-voip] Errors 18 and 19 on incoming call only
> through subscriber
>
>
>
> Hunt Lists use the RouteListControl process as well so definitely could be
> the issue.
>
>
>
> On Thu, Mar 5, 2015 at 5:13 PM, ROZA, Ariel <Ariel.ROZA at la.logicalis.com>
> wrote:
>
> I think I may be hitting this bug:
>
> https://tools.cisco.com/bugsearch/bug/CSCtr83193
>
>
>
> It applies to Route Lists instead of Hunt Lists, but the symptoms look
> similar, and the CUCM version matches..
>
>
>
> What do you think?
>
>
>
> Regards,
>
> *Ariel Roza*
> *Service Delivery Consultant  / Argentina*
> *Logicalis *
>
> Tel: +54 11 5282 - 0458
> ariel.roza at la.logicalis.com
>
> Peru 327 – CABA – Argentina – C1067AAG
>
> www.la.logicalis.com
> *________________________*
> *_________________________ **Business and technology working as one*
>
>
>
> *Síguenos en:* [image: Description: Descripción: Descripción:
> Descripción: Descripción: Descripción: Descripción: tw]
> <http://twitter.com/LogicalisLatam> [image: Description: Descripción:
> Descripción: Descripción: Descripción: Descripción: Descripción: fb]
> <http://es-es.facebook.com/pages/Logicalis-Latam/234648439078> [image:
> Description: Descripción: Descripción: Descripción: Descripción:
> Descripción: Descripción: yt] <http://www.youtube.com/logicalislatam>
> <http://www.slideshare.net/logicalis> [image: Description: Descripción:
> cid:image005.jpg at 01CCDC0C.A5297E60] <http://www.cxounplugged.com/>
>
> [image: Description: Descripción: Descripción: Descripción:
> http://www.estudioponzo.com.ar/firma.gif]
>
>
>
>
>
>
>
> *From:* cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] *On Behalf
> Of *ROZA, Ariel
> *Sent:* jueves, 05 de marzo de 2015 06:56 p.m.
> *To:* Ryan Ratliff (rratliff); Brian Meade
> *Cc:* cisco-voip voyp list
>
>
> *Subject:* Re: [cisco-voip] Errors 18 and 19 on incoming call only
> through subscriber
>
>
>
> 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:rratliff at cisco.com
> <rratliff at 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 <bmeade90 at 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) <
> rratliff at 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 <bmeade90 at 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.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
>
>
>
> _______________________________________________
> 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/20150305/b9f83c1c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 1384 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150305/b9f83c1c/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.jpg
Type: image/jpeg
Size: 3975 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150305/b9f83c1c/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.jpg
Type: image/jpeg
Size: 849 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150305/b9f83c1c/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 1467 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150305/b9f83c1c/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.jpg
Type: image/jpeg
Size: 863 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150305/b9f83c1c/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 1469 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150305/b9f83c1c/attachment-0002.png>