[cisco-voip] Provider not recognizing my busy PRI?

[Eric Pedersen]

Does this command work on mgcp PRIs with backhauled Q.931?  On our CMM,
"show isdn service" does not reflect the true PRI state. 

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ryan Ratliff
Sent: July 18, 2007 09:31
To: c3voip
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Provider not recognizing my busy PRI?

I believe it's 'isdn busy' under the serial interface for the PRI.

-Ryan

On Jul 18, 2007, at 11:01 AM, c3voip wrote:

It's funny that you say that.  We have 2 providers and one recognizes
when the PRI's are set OOS using ChangeBChannelMaintenance and the other
won't.

What command would I use to set b-channels OOS on a CMM PRI port running
MGCP? Also is there a command to tell which channels are on active
calls?

Thanks,
-C

-----Original Message-----
From: Ryan Ratliff [mailto:rratliff at cisco.com]
Sent: Wednesday, July 18, 2007 10:49 AM
To: c3voip
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Provider not recognizing my busy PRI?

ChangeBChannelMaintenance does not actually set the b-channel busy on
your end.  It just sets it busy internal to CallManager so that CM wont'
use the b-channel.  It's intended to be used with fractional PRIs.

If you want some b-channels busied out use commands on the router to do
so.

-Ryan

On Jul 18, 2007, at 10:28 AM, c3voip wrote:

I have a multi-PRI trunk group from my PSTN provider that rolls to the
next PRI when the first one fills up with incoming calls.  I was doing
some testing last night with the MGCP Change B-Channel Maintenance
Status fields in Service Parameters.  I successfully busied out the
first PRI and then was unable to make inbound calls to my numbers (call
cannot be completed recording).  I then cleared the PRI and was able to
take calls again.  So I shutdown the serial interface and was able to
take calls on the next PRI.



Is there something wrong with my PRI setup that would cause my provider
to not recognize when I busy out my B-channels?  Is there something that
I need to request from my provider in order for them to recognize my
busy outs?





Thanks,

-C



_______________________________________________
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