Setting up MCDN/SBOC?

[SJCBR]

Hi,
I am trying to get SBOC to function between an OPT11 and OPT61 plus other Tandem OPT switches connected to our network. The problem I'm having is when a call from my switch is routed via our private net - PRI, and a switch along the way does not have it's AC table programed for the LOC (I don't have control of all the switches), the caller gets a busy. The OPT11 will know if the PRI is down and reroute the call via the public network but if the PRI is up and a switch down the line is not programed correctly, the call is lost(busy)and since I'm forcing all company calls to use the net, the call can never get through. From what I have read "step back on congestion" should signal the originating switch using RRO(all switches must have SBOC and RRO set)that a call did not go through and signal the originating switch to reroute the call. I'm probably missing something simple but can't get it to work. Any ideas on what I'm missing?

Thanks,
SJCBR

 

[Avaya911PLM]

The MCDN Alternate Routing feature is triggered at the controlling node when a Call Clearing message (DISCONNECT or RELEASE COMPLETE)is received, and the cause value in the Call Clearing message is supported for the MCDN Alternate Routing feature.

The cause values which activate the MCDN Alternate Routing feature are:

• Cause 3 = No route to destination
• Cause 27 = Destination is out of service
• Cause 34 = No channel/circuit available
• Cause 38 = Network out of order
• Cause 41 = Temporary failure
• Cause 42 = Congestion

You need to confirm in the inbound PRI rejection message at the ORIGINATING NODE that you are in fact receiving one of these Cause codes. Chances are you are getting an INVALID NUMBER or something similar. Remember SBOC is designed to reroute your call around cogested nodes, not ones that are not programmed correctly.

--
Fletch
Visit the Nortel Technical Support Portal at:

http://www.nortelnetworks.com/support

 

[cheppy]

Hey Fletch, thanks for that detailed information! I have been pulling my hair out trying to figure out the same thing. You sure know your stuff on PRI!

 

[SJCBR]

Thanks for the information. I will look at the rejection message (not sure how to look at it but I'll try) and see what it says. I was afraid it would not work when a switch is missing the LOC in its table.
Steve

 

[SJCBR]

I turned on MSGI and looked at the message. It came in as a 16 - unassigned number which looks like SBOC won't do. Are there any other solutions for this?


DCH 5 IMSG CALLPROC REF 00000016 CH 2 22 TOD 10:28:04

DCH 5 IMSG DISC REF 00000016 CH 2 22 TOD 10:28:04
CAUSE :UNASSIGNED NUMBER

DCH 5 IMSG REL COMP REF 00000016 CH 2 22 TOD 10:28:04

 

[Avaya911PLM]

You could try to solicit for a 'Product Improvement" Patch. PI patches may be chargable depending on the situation.

I cannot give an official Nortel position here in the forum, but my 'feeling' is that you are fighting a 'design intent' issue.



--
Fletch
Visit the Nortel Technical Support Portal at:

http://www.nortelnetworks.com/support

 

[SJCBR]

Thank you,
I'll do some checking.

SJCBR