Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

PRI Problem

Status
Not open for further replies.

pointedout

Technical User
Apr 6, 2010
45
0
0
PK
I have a PRI with Ericson MD110. It was going fine however 4 days back we got an issue. External caller was not able to call on our Operator root (separate group of channels). Incoming call is coming in this manner:


DCH 18 UIPE_IMSG CC_DISC_IND REF 00002FEA CH 18 1 TOD 16:08:36 CK 00D0C348
CAUSE: #16 - NORMAL CALL CLEARING

DCH 18 UIPE_OMSG CC_RELEASE_REQ REF 0000AFEA CH 18 1 TOD 16:08:36 CK 00D0C348

DCH 18 UIPE_IMSG CC_RELEASE_CONF REF 00002FEA CH 18 1 TOD 16:08:36 CK 00D0C3BF


DCH 18 UIPE_IMSG CC_SETUP_IND REF 000030EA TOD 16:09:00 CK 00D18017
CALLED #:8 NUM PLAN: PRIVATE TON: UNKNOWN
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:800030516 NUM PLAN: PRIVATE TON: UNKNOWN

DCH 18 UIPE_OMSG CC_MORE_INFO_REQ REF 0000B0EA CH 18 1 TOD 16:09:00 CK 00D18018


DCH 18 UIPE_IMSG CC_INFO_IND REF 000030EA CH 18 1 TOD 16:09:00 CK 00D180C0
CALLED #:0 NUM PLAN: PRIVATE TON: UNKNOWN

DCH 18 UIPE_IMSG CC_INFO_IND REF 000030EA CH 18 1 TOD 16:09:00 CK 00D181A8
CALLED #:8 NUM PLAN: PRIVATE TON: UNKNOWN

DCH 18 UIPE_IMSG CC_INFO_IND REF 000030EA CH 18 1 TOD 16:09:02 CK 00D1839B
CALLED #:1 NUM PLAN: PRIVATE TON: UNKNOWN

DCH 18 UIPE_IMSG CC_INFO_IND REF 000030EA CH 18 1 TOD 16:09:02 CK 00D1865E
CALLED #:0 NUM PLAN: PRIVATE TON: UNKNOWN

DCH 18 UIPE_IMSG CC_INFO_IND REF 000030EA CH 18 1 TOD 16:09:02 CK 00D188A8
CALLED #:3 NUM PLAN: PRIVATE TON: UNKNOWN

DCH 18 UIPE_IMSG CC_INFO_IND REF 000030EA CH 18 1 TOD 16:09:02 CK 00D18A39
CALLED #:2 NUM PLAN: PRIVATE TON: UNKNOWN

DCH 18 UIPE_IMSG CC_INFO_IND REF 000030EA CH 18 1 TOD 16:09:02 CK 00D18BC8
CALLED #:3 NUM PLAN: PRIVATE TON: UNKNOWN

DCH 18 UIPE_IMSG CC_INFO_IND REF 000030EA CH 18 1 TOD 16:09:02 CK 00D18D68
CALLED #:5 NUM PLAN: PRIVATE TON: UNKNOWN

DCH 18 UIPE_IMSG CC_INFO_IND REF 000030EA CH 18 1 TOD 16:09:02 CK 00D18F0D
CALLED #:1 NUM PLAN: PRIVATE TON: UNKNOWN

DCH 18 UIPE_IMSG CC_INFO_IND REF 000030EA CH 18 1 TOD 16:09:02 CK 00D190ED
CALLED #:0 NUM PLAN: PRIVATE TON: UNKNOWN

DCH 18 UIPE_OMSG CC_PROCEED_REQ REF 0000B0EA CH 18 1 TOD 16:09:02 CK 00D190EE

DCH 18 UIPE_OMSG CC_DISC_REQ REF 0000B0EA CH 18 1 TOD 16:09:04 CK 00D1A039
CAUSE: #31 - NORMAL UNSPECIFIED

DCH 18 UIPE_IMSG CC_RELEASE_IND REF 000030EA CH 18 1 TOD 16:09:04 CK 00D1A1FA
CAUSE: #31 - NORMAL UNSPECIFIED

DCH 18 UIPE_OMSG CC_RELEASE_RESP REF 0000B0EA CH 18 1 TOD 16:09:04 CK 00D1A1FA



**********************************************************



Please guide.
 
looks like a protocol mismatch

Assuming you have reset DCH and T1

verify DCH IFC is correct with far end.

 
I have split 30 channels into 20 + 10. 20 are in one route and 10 are on other. This issue is happening on 10 separate channel. If IFC was the issue, other 20 channels must exhibit the same problem, what you say?
 
IFC for route would have to match DCH so can't imagine routes could have a different IFC.

So one route works ok but other route does not? Wonder if Ericson switch could be setup different for this different trunk group?

What does telco say about those incoming setup messages?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top