MPS to CS1000 Tie lines

[puckster99]

Does anyone have any config info on how to set up DCH and Routes for connections from a CS1000 to a MPS500.
I am needing to set up one connection as incoming to the MPS from the CS1000 and one outgoing tie connection from the MPS to the CS1000. We are able to make a call into the MPS from the CS1000 but are unable to make an outgoing call from the MPS to the CS1000

Any info would be appreciated.

Thanks.

 

[Avaya911PLM]

Since you have inbound to the MPS working you probably have your DCH pretty close to what you want. If calls are failing into the CS 1000, then you most likely have some other problem outside of the DCH.

The key to solving this is to capture a trace of the DCH message on an inbound call attempt from the MPS.

Commands for DCH monitoring are in LD 96 and I suggest you do this at an off peak time.

One quick tip, if the call the MPS is trying to make is a PSTN call, your inbound trunks are probably set to NCOS 0, and the call is failing in NARS/BARS, this will be indicated by a SWED Switched Equipment Congestion message which you will see on the DCH monitoring. Assign your trunks an NCOS that is sufficient to make the call they are trying to complete.

--
Fletch

Nortel Emergency Services PLM

http://nortel.com/e911

 

[puckster99]

Thanks for the reply,
I need to have the MPS dial through the CS1000 and then out a PRI. I am thinking the problem is that the CS1000 is not recognizing the MPS dial string of 9 NPA NXX XXXX

I am thinking I need to set up an access code in the route instead of the MPS having a 9 in the dial string.

I was thinking of setting up a tie route with INAC as YES, but when I try to config it as NI2, it asks me for CBCR and route number. Not sure what a master route is and why it is needed?

 

[Avaya911PLM]

I can't stress it enough:
The key to solving this is to capture a trace of the DCH message on an inbound call attempt from the MPS.

If you turn on the DCH messaging, you will see exactly why the call is failing.

--
Fletch

Nortel Emergency Services PLM

http://nortel.com/e911

 

[puckster99]

Below is a copy of my DCH trace, DCH 3 is on the tie line from the CS1000 to the MPS, DCH 4 is on the tie line from the MPS to the CS1000.

I entered 5's into the numbers but the numbers in the trace were actual numbers (with no leading 9).

The reject message is "unassigned number" that is why I am thinking I need to have the route insert an access code?



DCH 3 UIPE_OMSG CC_SETUP_REQ REF 000000C0 CH 23 15 TOD 21:59:47 CK 386A2590
PROGRESS: INTERWORKING WITH A PUBLIC NETWORK
CALLING #:6125555555 NUM PLAN: E164 TON: NATL
CALLED #:330000 NUM PLAN: E164 TON: NATL

DCH 3 UIPE_IMSG CC_PROCEED_IND REF 000000C0 CH 23 15 TOD 21:59:47 CK 386A2762

DCH 3 UIPE_IMSG CC_ALERT_IND REF 000000C0 CH 23 15 TOD 21:59:47 CK 386A2776

DCH 3 UIPE_IMSG CC_SETUP_CONF REF 000000C0 CH 23 15 TOD 21:59:50 CK 386A36ED

DCH 4 UIPE_IMSG CC_SETUP_IND REF 00002380 CH 24 23 TOD 21:59:51 CK 386A4316
CALLED #:9525555555 NUM PLAN: E164 TON: NATL
CALLING #:6125555555 NUM PLAN: E164 TON: NATL

DCH 4 UIPE_OMSG CC_REJECT_REQ REF 0000A380 CH 24 23 TOD 21:59:51 CK 386A4317
CAUSE: #1 - UNASSIGNED NUMBER

DCH 3 UIPE_IMSG CC_DISC_IND REF 000000C0 CH 23 15 TOD 21:59:56 CK 386A63E1
CAUSE: #16 - NORMAL CALL CLEARING

DCH 3 UIPE_OMSG CC_RELEASE_REQ REF 000000C0 CH 23 15 TOD 21:59:56 CK 386A63E1

DCH 3 UIPE_IMSG CC_RELEASE_CONF REF 000000C0 CH 23 15 TOD 21:59:56 CK 386A6443

 

[Avaya911PLM]

Yes there is your problem exactly. You can do this a few different ways.

1.) Have the MPS drop in the 91
2.) Use the INST on the route and set it to 91

You can play with INAC, but that may only be for MCDN trunk types. I can't remember off the top of my head how easy that is on NI2.

Did you check you NCOS on the trunks? Will they have a high enough NCOS to make those calls? Once you get past here, that is the next thing that could potentially block you.

--
Fletch

Nortel Emergency Services PLM

http://nortel.com/e911

 

[johnpoole]

i would use a dgt on the rlb to insert ac1, then unless the targs on the two routes match or as posted the ncos of the trunk is to low.. the call should go.. i do a lot of tandem switching here... just realize that an inbound tie trunk is nothing more then an analog station..

john poole
bellsouth business
columbia,sc

 

[fadi2008]

hi puckster99,

Can u send me please the configuration do it on PBX for the rout, dch and ld 73 because i have the same scenario mps connected to option11c but the dch did not come up.

Thanks

 

[mwing]

I have a similar issue and not sure how to proceed. These are the d channel messages I get when I have 91 +AreaCode+PhoneNumber or just 1+AreaCode+PhoneNumber. I'm not sure how to check the NCOS on the trunk. These calls are from an AudioCodes to 61C via PRI.
Thanks for any help that might be provided.
Mike

DCH 20 UIPE_IMSG CC_SETUP_IND REF 0000002E CH 10 4 TOD 15:34:07 CK 0EF96DE7
CALLED #:91714478XXXX NUM PLAN: UNKNOWN TON: UNKNOWN
CALLING #:714704YYYY NUM PLAN: UNKNOWN TON: UNKNOWN

DCH 20 UIPE_OMSG CC_REJECT_REQ REF 0000802E CH 10 4 TOD 15:34:07 CK 0EF96DEB
CAUSE: #42 - SWED EQIP CONGESTION\


DCH 20 UIPE_IMSG CC_SETUP_IND REF 0000002F CH 10 5 TOD 15:35:35 CK 0EFC1985
CALLED #:1714478XXXX NUM PLAN: UNKNOWN TON: UNKNOWN
CALLING #:714704YYYY NUM PLAN: UNKNOWN TON: UNKNOWN

DCH 20 UIPE_OMSG CC_REJECT_REQ REF 0000802F CH 10 5 TOD 15:35:35 CK 0EFC1988
CAUSE: #1 - UNASSIGNED NUMBER

 

[webtensive]

Did you ever get a fix to this?