[cisco-voip] CCM - Meridian b-channel lockout

[Ortiz, Carlos]

I have seen calls that loop between both systems because of faulty
"route patterns" cause this issue......

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Fedorov,
Konstantin
Sent: Friday, March 24, 2006 7:50 AM
To: pnowicki at neo.rr.com
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CCM - Meridian b-channel lockout

Ok,

Thank you.

Any others ideas ??



-----------------------
Sincerely Yours,
Konstantin Fedorov

-----Original Message-----
From: pnowicki at neo.rr.com [mailto:pnowicki at neo.rr.com] 
Sent: Friday, March 24, 2006 10:28 AM
To: Fedorov, Konstantin
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CCM - Meridian b-channel lockout

I had a similar issue before on a T1. The issue ended up that I didn't 
have the "isdn channel-id invert extended-bit" command (h.323) or 
the "MCDN Channel Number Extension Bit Set to Zero" box checked (mgcp).

hope this helps!

----- Original Message -----
From: "Fedorov, Konstantin" <kfedor at amt.ru>
Date: Thursday, March 23, 2006 5:46 pm
Subject: [cisco-voip] CCM - Meridian   b-channel lockout
To: cisco-voip at puck.nether.net

> Hi,
> 
> I have gateway, under mgcp control of CCM, which connected via E1 
> PRI to
> the 
> Meridian. Some times Meridian lockouts b-channels.
> I have notice that this happens when CCM doesn't answer to the 1-st
> setup from Meridian, but on the second (the same setup) CCM answer
> channel not available, and after that Meridian lockouts the b-
channel,
> which was reserved in this setup
> 
> 
> For example 
> 12:52:41.396 : ISDN Se1/0:15 Q931: RX <- SETUP pd = 8  callref = 
> 0x462912:52:45.380 : ISDN Se1/0:15 Q931: RX <- SETUP pd = 8  
> callref = 0x4629
> 12:52:57.616 : ISDN Se1/0:15 Q931: TX -> CALL_PROC pd = 8  callref =
> 0xC629
> 12:52:57.632 : ISDN Se1/0:15 Q931: TX -> DISCONNECT pd = 8  
> callref =
> 0xC629 
> Cause i = 0x80A2 - No circuit/channel available
> 
> Does anyone faced with this problem ??
> 
> -----------------------
> Sincerely Yours,
> Konstantin Fedorov
> 
> 
> _______________________________________________
> 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