[cisco-voip] MGCP PRI: Cause i = 0x80AC - Requested circuit/channel not available on Incoming Calls
Nick Matthews
matthnick at gmail.com
Thu Apr 29 12:53:51 EDT 2010
I would take a look at CSCsx67255 and check show voice dsp group all
for allocation failures.
-nick
On Thu, Apr 29, 2010 at 12:03 PM, Ryan Ratliff <rratliff at cisco.com> wrote:
> Did CUCM ever send a CRCX to the gateway after receiving the inbound setup?
> Look for the last status poll (if this option is enabled) in the CCM traces
> for the endpoint and see what it has for channel 14.
> You should see CUCM send a PRI Restart out to the PSTN immediately after
> this call fails.
> -Ryan
> On Apr 29, 2010, at 11:31 AM, Jason Aarons (US) wrote:
>
> Since it's channel 15 is it a E1 ?
>
> show isdn service
>
> Put a loopback plug toward you is that channel good/in service ?
>
>
> ________________________________
> From: cisco-voip-bounces at puck.nether.net [cisco-voip-bounces at puck.nether.net]
> On Behalf Of Robert Schuknecht [rschuknecht at gmx.de]
> Sent: Thursday, April 29, 2010 11:27 AM
> To: 'cisco-voip voyp list'
> Subject: [cisco-voip] MGCP PRI: Cause i = 0x80AC - Requested circuit/channel
> not available on Incoming Calls
>
> Hi,
>
>
>
> i am facing problems with incoming calls on a MGCP PRI Gateway. Some of the
> incoming calls get disconnected with cause code: Cause i = 0x80AC -
> Requested circuit/channel not available. I noticed that this happens only on
> one specific port and B-Channel.
>
>
>
> Sample output of debug isdn q931:
>
>
>
> Apr 29 14:45:25.870 cest: ISDN Se0/0/1:15 Q931: RX <- SETUP pd = 8 callref
> = 0x0071
> Sending Complete
> Bearer Capability i = 0x8090A3
> Standard = CCITT
> Transfer Capability = Speech
> Transfer Mode = Circuit
> Transfer Rate = 64 kbit/s
> Channel ID i = 0xA9838E
> Exclusive, Channel 14
> Calling Party Number i = 0x2183, '160XXXXXXX'
> Plan:ISDN, Type:National
> Called Party Number i = 0xC1, '25XXXXXX'
> Plan:ISDN, Type:Subscriber(local)
> High Layer Compat i = 0x9181
> Apr 29 14:45:25.870 cest: ISDN Se0/0/1:15 Q931: TX -> RELEASE_COMP pd = 8
> callref = 0x8071
> Cause i = 0x80AC - Requested circuit/channel not available
>
>
>
> At nearly the same time I see the following output in CCM Trace:
>
>
>
> CCM|In Message -- PriEuroSetupMsg -- Protocol=
> PriEuroProtocol|<CLID::StandAloneCluster><NID::10.236.3.51><LVL::Significant><MASK::0040>
> CCM|Ie - Ni2BearerCapabilityIe -- IEData= 04 03 80 90 A3
> |<CLID::StandAloneCluster><NID::10.236.3.51><LVL::State
> Transition><MASK::0040>
>
> CCM|Ie - Q931ChannelIdIe -- IEData= 18 03 A9 83 8E
> |<CLID::StandAloneCluster><NID::10.236.3.51><LVL::State
> Transition><MASK::0040>
>
> CCM|Ie - Q931CallingPartyIe -- IEData= 6C 0C 21 83 31 36 30 3X 3X 3X 3X 3X
> 3X 3X |<CLID::StandAloneCluster><NID::10.236.3.51><LVL::State
> Transition><MASK::0040>
>
> CCM|Ie - Q931CalledPartyIe -- IEData= 70 09 C1 32 35 3X 3X 3X 3X 3X 3X
> |<CLID::StandAloneCluster><NID::10.236.3.51><LVL::State
> Transition><MASK::0040>
>
> CCM|Ie - Q931HighLayerCompatibilityIe -- IEData= 7D 02 91 81
> |<CLID::StandAloneCluster><NID::10.236.3.51><LVL::State
> Transition><MASK::0040>
> CCM|MMan_Id= 0. (iep= 0 dsl= 8001 sapi= 0 ces= 0 IpAddr=403ec0a
> IpPort=2427)|<CLID::StandAloneCluster><NID::10.236.3.51><LVL::State
> Transition><MASK::0040>
>
> CCM|IsdnMsgData1= 08 02 00 71 05 A1 04 03 80 90 A3 18 03 A9 83 8E 6C 0C 21
> 83 31 36 30 38 34 39 33 32 36 31 70 09 C1 32 35 35 30 31 34 30 31 7D 02 91
> 81 |<CLID::StandAloneCluster><NID::10.236.3.51><LVL::State
> Transition><MASK::0040>
>
> CCM|MGCPpn9d - S0/SU0/DS1-1 at ostbogw01.XXXXXXXXX.local - Collision Detected
> On PriEuro Interface callphase=
> 9|<CLID::StandAloneCluster><NID::10.236.3.51><CT::2,100,133,1.358133><IP::10.236.3.4><DEV::><LVL::State
> Transition><MASK::2000>
> CCM|Entering default,restarting
> channel|<CLID::StandAloneCluster><NID::10.236.3.51><CT::2,100,133,1.358133><IP::10.236.3.4><DEV::><LVL::State
> Transition><MASK::2000>
>
> CCM|MGCPpn9d::conflictingChannelHandler - Don't Restart this channel since
> it is marked OOS_NE under service parameter:S0/SU0/DS1-1 at ostbogw01.
> XXXXXXXXX.local=00000000000000000000000000000000 or due to MGCP gateway
> hardware
> failure|<CLID::StandAloneCluster><NID::10.236.3.51><CT::2,100,133,1.358133><IP::10.236.3.4><DEV::><LVL::State
> Transition><MASK::2000>
> CCM| |<CLID::StandAloneCluster><NID::10.236.3.51><LVL::State
> Transition><MASK::0040>
>
> CCM|Out Message -- PriReleaseCompleteMsg -- Protocol=
> PriEuroProtocol|<CLID::StandAloneCluster><NID::10.236.3.51><LVL::Significant><MASK::0040>
>
>
>
> I checked the above mentioned CCM Service Parameter and It is not checked.
>
>
>
> Does anybody know how to track down the root cause of this issue?
>
>
>
> Callmanager is running 7.0.2-20000-5
> Gateway is running
> 12.4(22)T4
>
>
>
>
>
>
> ________________________________
>
> Disclaimer: This e-mail communication and any attachments may contain
> confidential and privileged information and is for use by the designated
> addressee(s) named above only. If you are not the intended addressee, you
> are hereby notified that you have received this communication in error and
> that any use or reproduction of this email or its contents is strictly
> prohibited and may be unlawful. If you have received this communication in
> error, please notify us immediately by replying to this message and deleting
> it from your computer. Thank you.
> _______________________________________________
> 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
>
>
More information about the cisco-voip
mailing list