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

[ROZA, Ariel]

Hi, Robert

When the Gateways goes into SRST mode, IP Phones registered to it are able to call other phones with no issues.
The IP Phones are registered to the Subscriber
The Gateway´s Device Pool has the same CMG that every other phone in the company (The Subscriber is the first choice)
Database Replicaton is Ok. (Sub and Pub are at “2”). I already did a restart of the RIS Database service on both Sub & Pub.

I´ll gather the debugs & traces if can´t find another solution. (Don´t want to restart the servers…)

From: Schuknecht Robert [mailto:Robert.Schuknecht at logicalis.de]
Sent: martes, 10 de febrero de 2015 12:58 p.m.
To: ROZA, Ariel
Subject: AW: [cisco-voip] Errors 18 and 19 on incoming call only through subscriber

Hi Ariel,

what happens when you call a IP-Phone directly from the Gateway? On which CUCM are the IP-Phones registered to? Does the gateway have an Device-Pool with an CUCM Group consisting of both CUCMs? Could you provide detailed CUCM Traces and outputs from debug h225 asn1 and debug h245 asn1? Is the DB-Replication working?

Kind Regards,

Robert



Robert Schuknecht
CCIE VOICE # 32360
System Engineer
Logicalis GmbH

Tel:  +49-2234-95418-746<tel:+49-2234-95418-746>
Fax:  +49-2234-95418-779
Video: robert.schuknecht at logicalis.de<sip:robert.schuknecht at logicalis.de>
E-Mail:  robert.schuknecht at logicalis.de<mailto:robert.schuknecht at logicalis.de>

Max-Planck-Straße 35
D-50858 Köln

www.logicalis.de<http://www.logicalis.de>

Geschäftsführer Markus Brungs
HRB 30173
Amtsgericht Köln, Februar 1998
USt.-Id Nr.: DE191875158
______________________________________________
Business and technology working as one

This email communication does not create or vary any contractual relationship between Logicalis and you. Internet communications
are not secure and accordingly Logicalis does not accept any legal liability for the contents of this message. The contents of this email
are confidential to the intended recipient at the email address to which it has been addressed. It may not be disclosed to or used by
anyone other than this addressee, nor may it be copied in any way. If received in error, please contact Logicalis on the above switchboard
number quoting the name of the sender and the addressee and then delete it from your system. Please note that neither Logicalis
nor the sender accepts any responsibility for viruses and it is your responsibility to scan the email and attachments (if any).
Von: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] Im Auftrag von ROZA, Ariel
Gesendet: Dienstag, 10. Februar 2015 15:06
An: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Betreff: [cisco-voip] Errors 18 and 19 on incoming call only through subscriber


 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150304/d5b1e948/attachment.html>