[cisco-voip] mgcp BRI failure
James Jung
James.Jung at telecom.co.nz
Sun Nov 23 13:33:36 EST 2008
Hi Jason,
Thanks for your reply. The IOS that I use is
c2801-spservicesk9-mz.124-17b.bin.
FYI, the roundtrip time to callmanager is only 3 - 4 ms.
________________________________
From: Jason Aarons (US) [mailto:jason.aarons at us.didata.com]
Sent: Friday, 21 November 2008 17:21
To: James Jung
Subject: RE: [cisco-voip] mgcp BRI failure
I would switch them to H323! Sounds like your L2 backhaul is having
communications problems.
What version IOS?
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of James Jung
Sent: Thursday, November 20, 2008 9:29 PM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] mgcp BRI failure
Hi all
I have a problem and it has happened 7 times already this year.
A remote office use 2 BRI circuits controlled by CCM (4.1.3) using MGCP.
No one can make inbound and outbound call when it happens, and the isdn
status shows "Multiple-Frame.... Established" but when I make a test
call from PSTN, the q931 shows
*Nov 21 10:10:54: ISDN BR0/0/0 Q931: RX <- SETUP pd = 8 callref = 0x1A
Sending Complete
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0x89
Signal i = 0x40 - Alerting on - pattern 0
Called Party Number i = 0x80, '2551694'
Plan:Unknown, Type:Unknown
High Layer Compat i = 0x9181
*Nov 21 10:10:54: ISDN BR0/0/0 Q931: TX -> RELEASE_COMP pd = 8 callref
= 0x9A
Cause i = 0x80AC - Requested circuit/channel not available
And after bouncing the bri interface or no mgcp and mgcp command, it
works fine.
Anyone can tell me what would be the cause and how to avoid this
problem?
Thank you very much for your help in advance.
JJ.
________________________________
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20081124/1a5cb9cb/attachment.html>
More information about the cisco-voip
mailing list