[cisco-voip] PRI 's Roll

[Fuermann, Jason]

I don't know if anybody else has had success with this, because when we tried to put a channel in OOS or Maint (say the first one in the hunt), any call directed to that channel would get a busy (PSTN to CUCM). ATT confirmed that this is their intended behavior.

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Nate VanMaren
Sent: Wednesday, January 06, 2010 10:18 AM
To: tmdvoip; 'Jason Shearer'; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] PRI 's Roll

On a SIP/H.323 gateway to mess with individual channels, to take a trunk out of service without dropping existing calls:

CHQVG001(config)#int s0/0/0:23
CHQVG001(config-if)#isdn service ?
  b_channel  Specify the B-channel or range of B-channels, 0 for the complete interface.

CHQVG001(config-if)#isdn service b_channel ?
  <0-24>  B channel range or 0 for complete interface

CHQVG001(config-if)#isdn service b_channel 1 ?
  state  Specify the desired state.

CHQVG001(config-if)#isdn service b_channel 1 state ?
  <0-2>  Valid states are 0=Inservice 1=Maint 2=Outofservice

CHQVG001(config-if)#isdn service b_channel 1 state 2 ?
  hard       Change the service state and clear the call.
  immediate  Send the service message right away (default)
  soft       Change the service state once the channel becomes idle.
  <cr>


CHQVG001#sh isdn service 
PRI Channel Statistics:
ISDN Se0/0/0:23, Channel [1-24]
  Configured Isdn Interface (dsl) 0
   Channel State (0=Idle 1=Proposed 2=Busy 3=Reserved 4=Restart 5=Maint_Pend)
    Channel :  1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4
    State   :  2 0 2 2 2 2 2 2 2 2 2 2 2 0 0 0 0 0 0 0 0 0 0 3 
   Service State (0=Inservice 1=Maint 2=Outofservice 8=MaintPend 9=OOSPend)
    Channel :  1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4
    State   :  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2



-----Original Message-----
From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of tmdvoip
Sent: Wednesday, January 06, 2010 9:10 AM
To: 'Jason Shearer'; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] PRI 's Roll

Jason S.

I liked your idea about testing each channel.

These are your words below.

"You can test each channel if you would like by shutting #2 & #3 down and
busying out all channels but one on #1.  Place test call.  Rinse and repeat
till you have tested all channels."

I hate being so ignorant on this topic, but how would I busy out all the
other channels?

For example, just keep dialing in bound calls from various phones?

I do know how to shut down PRI/GW #2 and #3.

Also, let me make sure I have my terminology right.

The PRI/GW contains the channels IE 23 usable for ea PRI.
I have 3 PRI's/GW equals 69 channels. Right?


Thanks, TMD

-----Original Message-----
From: Jason Shearer [mailto:jshearer at amedisys.com] 
Sent: Tuesday, January 05, 2010 3:03 PM
To: tmdvoip; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] PRI 's Roll

Ask these questions:

1) What order are they rolling in?
2) What distribution algorithm are they using?  (top down, circular, etc)

You can test each channel if you would like by shutting #2 & #3 down and
busying out all channels but one on #1.  Place test call.  Rinse and repeat
till you have tested all channels.

I typically request top down from the provider and do just the opposite
outbound.  If they are going top down 1,2,3 I will go outbound bottom up
3,2,1.

Jason

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of tmdvoip
Sent: Tuesday, January 05, 2010 1:56 PM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] PRI 's Roll

Guys:

This is my configuration
CUCM 4.2(3)sr4a (2) Cm in cluster
Cisco Unity 4.0(5.0)
Cisco 2851 Routers


Here is the situation: My client complains that external callers sometime
get an error message from our Telco Provider AT&T saying (all circuits are
busy).

I opened a ticket with the provider and they confirmed that there was a
power outage at one of their locations. Therefore, the Telco Provider AT&T
circuit has no power and our PRI goes down.

My client has 3 PRI's configured and they are supposed to roll from one PRI
to the next as call volume increases. The thing of it is my client has 3
PRI's with 23 channels each that are way-way under utilize. My question is
should the incoming calls just transition to the next PRI in the group? Am I
missing something? Is my Telco sales person says we are configured to roll
to the PRI. Why is it not rolling?

Sincerely,
Thomas Dooley
Cisco Telecommunications Administrator
Triad NC
Desk: 336-917-7125



_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

*** NOTICE--The attached communication contains privileged and confidential
information. If you are not the intended recipient, DO NOT read, copy, or
disseminate this communication. Non-intended recipients are hereby placed on
notice that any unauthorized disclosure, duplication, distribution, or
taking of any action in reliance on the contents of these materials is
expressly prohibited. If you have received this communication in error,
please delete this information in its entirety and contact the Amedisys
Privacy Hotline at 1-866-518-6684. Also, please immediately notify the
sender via e-mail that you have received this communication in error. ***

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


 NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.


_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip