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!

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

Call Routing Confusion

Status
Not open for further replies.
bad69cat

bad69cat

IS-IT--Management
May 28, 2010
280
US
So let me just say the routing thing is way out of my knowlege relm on these OPT 81/11 machines. Here's the basic config - we have a opt 11 with a tie trunk to the opt 81 (mother ship) and I can call this 710-627-4387 number from it. I get a fast busy from the opt 11 everytime? I can dial the entire number so I'm pretty sure it's not the Opt 11. I got "help" from one of our vendors and they seem to think it's the carriers issue when they helped me track the number going through the 2 switches. I thought I would post up the findings on here to see what you gys might think since I seem to be getting the run around from both sides.....I need help deciphering the call track withtese test calls I did:


Call From the Opt 11C that got Rejected....

DCH 5 UIPE_OMSG CC_SETUP_REQ REF 000009C2 CH 3 19 TOD 10:58:54 CK 13974B27
PROGRESS: ORIGINATING END IS NOT ISDN
PROGRESS: INTERWORKING WITH PRIVATE WORK
CALLING #:8807 NUM PLAN: E164 TON: NATL
CALLED #:17106274387 NUM PLAN: E164 TON: NATL

DCH 3 OMSG CALLPROC REF 00008017 CH 58 23 TOD 10:58:54

DCH 5 UIPE_IMSG CC_STATUS_IND REF 000009C2 CH 3 19 TOD 10:58:54 CK 13974C45
CAUSE: #100 - INVALID IE CONTENTS

STATE:CALL INIT

DCH 5 UIPE_IMSG CC_STATUS_IND REF 000009C2 CH 3 19 TOD 10:58:54 CK 13974C65
CAUSE: #43 - USER INFO DISCARDED
STATE:CALL INIT

DCH 5 UIPE_IMSG CC_PROCEED_IND REF 000009C2 CH 3 19 TOD 10:58:54 CK 13974C8B

DCH 5 UIPE_IMSG CC_STATUS_IND REF 000009C2 CH 3 19 TOD 10:58:54 CK 13974CAA
CAUSE: #43 - USER INFO DISCARDED
STATE:OUTGOING CALL PROCEEDING

DCH 5 UIPE_IMSG CC_SETUP_CONF REF 000009C1 CH 3 23 TOD 10:58:54 CK 139752E0

DCH 5 UIPE_IMSG CC_DISC_IND REF 000009C2 CH 3 19 TOD 10:58:56 CK 139757BF
CAUSE: #16 - NORMAL CALL CLEARING

DCH 5 UIPE_OMSG CC_RELEASE_REQ REF 000009C2 CH 3 19 TOD 10:58:56 CK 139757C0

DCH 3 OMSG DISC REF 00008017 CH 58 23 TOD 10:58:56
CAUSE :NORMAL CALL CLEARING

DCH 3 IMSG RELEASE REF 00008017 CH 58 23 TOD 10:58:56

DCH 3 OMSG REL COMP REF 00008017 CH 58 23 TOD 10:58:56

DCH 5 UIPE_IMSG CC_RELEASE_CONF REF 000009C2 CH 3 19 TOD 10:58:56 CK 1397583
-------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------
Good call from 81c

DCH 5 UIPE_OMSG CC_SETUP_REQ REF 000009D5 CH 3 23 TOD 11:11:02 CK 13AD79EF
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:3198517576 NUM PLAN: E164 TON: NATL
CALLED #:17106274387 NUM PLAN: E164 TON: NATL

DCH 5 UIPE_IMSG CC_STATUS_IND REF 000009D5 CH 3 23 TOD 11:11:02 CK 13AD7B06
CAUSE: #99 - UNIMPLEMENTED IE

STATE:CALL INIT

DCH 5 UIPE_IMSG CC_PROCEED_IND REF 000009D5 CH 3 23 TOD 11:11:02 CK 13AD7B28

DCH 5 UIPE_IMSG CC_STATUS_IND REF 000009D5 CH 3 23 TOD 11:11:02 CK 13AD7B48
CAUSE: #43 - USER INFO DISCARDED
STATE:OUTGOING CALL PROCEEDING

DCH 5 UIPE_IMSG CC_PROGRESS_IND REF 000009D5 CH 3 23 TOD 11:11:04 CK 13AD8C40

PROGRESS: CALL IS NOT END TO END ISDN

DCH 5 UIPE_OMSG CC_DISC_REQ REF 00008A03 CH 3 5 TOD 11:11:06 CK 13AD9C42
CAUSE: #16 - NORMAL CALL CLEARING

DCH 5 UIPE_IMSG CC_RELEASE_IND REF 00000A03 CH 3 5 TOD 11:11:06 CK 13AD9CAF

DCH 5 UIPE_OMSG CC_RELEASE_RESP REF 00008A03 CH 3 5 TOD 11:11:06 CK 13AD9CB0

DCH 5 UIPE_IMSG CC_DISC_IND REF 00000C83 CH 3 7 TOD 11:11:10 CK 13ADC438
CAUSE: #16 - NORMAL CALL CLEARING

DCH 5 UIPE_OMSG CC_RELEASE_REQ REF 00008C83 CH 3 7 TOD 11:11:10 CK 13ADC439

DCH 5 UIPE_IMSG CC_RELEASE_CONF REF 00000C83 CH 3 7 TOD 11:11:10 CK 13ADC492

DCH 5 UIPE_IMSG CC_SETUP_CONF REF 000009D5 CH 3 23 TOD 11:11:14 CK 13ADDC61
PROGRESS: TERMINATING END IS NOT ISDN

DCH 5 UIPE_OMSG CC_DISC_REQ REF 000009D5 CH 3 23 TOD 11:11:20 CK 13AE0AFD
CAUSE: #16 - NORMAL CALL CLEARING

DCH 5 UIPE_IMSG CC_RELEASE_IND REF 000009D5 CH 3 23 TOD 11:11:20 CK 13AE0B63

DCH 5 UIPE_OMSG CC_RELEASE_RESP REF 000009D5 CH 3 23 TOD 11:11:20 CK 13AE0B6



 
Sort by date Sort by votes
Can you post this information:
------------------------
LD 20

REQ: prt
TYPE: TIE
TN Loop 1
DATE
PAGE
-------------------------
LD 21

REQ: prt
TYPE: rdb
CUST 0
ROUT RDB

------------------------

Regards
 
Upvote 0 Downvote
Ok from the opt 11 I dialed from ext 8807 (that's 319-851-8807 actually)

From the Opt 81 i dialed from ext 7576 (that's 319-851-7576)


 
Upvote 0 Downvote
Looks like you need to add a DMI in the opt 11 to add a "9" in front of the number, if you want it to pass through the Opt 81. You will also need to have trunk to trunk transfer allowed on the 81.
 
Upvote 0 Downvote
Hmmm - I can dial any other LD call from that opt 11 though as far as I know. But that is an interesting thought as it seems like there is soemthing either added or missing for sure.......
 
Upvote 0 Downvote
These are prolly CDP Steering codes, and you might find one has a different RLI. Compare one that works with one that does not.

CDP is in LD87

~~
Gene at www.GHTROUT.com
 
Upvote 0 Downvote
Can you make other calls into the 710 area code? I would look at the RLI for 710 in the Opt. 11 and see if there are any deny codes associated with it. I doubt highly that these are CDP issues, this is definitely a BARS issue. If you can make the call from the 81 then it's not a telco issue.
 
Upvote 0 Downvote
The 710 area code is unique in that it's only allowed to have the one number. (It's a government reserved area code actually) i get a fast busy only once the digits have been entered but I really don't know enough about how to trace wheather it's leaving the 11 and being rejected by the 81 or by the carrier. My first try was to the LD carrier and they say they don't see it (but I never asked about the one that does go....)maybe I should ask on that too. As far as I understand the 11 is just using the 81 as a DT provider and link to the telco/carrier. Where would I dig into looking a BARS stuff?


Thanks for the input guys!!
 
Upvote 0 Downvote
You need to monitor the D-channel in the 81 that comes from the 11 and see if the call is getting to the 81.
 
Upvote 0 Downvote
I think that's what my first post is that the vendor captured for me and is telling me it leaves the 81.....I just don't know how to read/parse the info. Example: cause #100 Invalid ie contents looks to me like the message the 11 gets from the 81 but I'm not sure because it looks like it's still progressing through a bunch more steps? IDK? They vendor is saying it's the carrier of course.......
 
Upvote 0 Downvote
How can it be a carrier issue if the call from the 81 works and the 11 uses the same trunks?
 
Upvote 0 Downvote
exactly waht I said and thought! LOL if ya want soemthing done......sigh
 
Upvote 0 Downvote
See if another working LD number and this number have the same RLI in LD 90. If not, change this one to match and test.
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

phonetech2012
  • Locked
  • Question
xeta call acounting
Replies
0
Views
88
phonetech2012
phonetech2012
LittleMaster
  • Locked
  • Question
Call connects but no voice cs1000 with NGN MSAG
Replies
3
Views
199
Firebird Scrambler
Firebird Scrambler
CentralJIM
  • Locked
  • Question
no caller ID on PRI external call
Replies
5
Views
231
CentralJIM
CentralJIM
amyygt
  • Locked
  • Question
External call forwarding Using E1 Pri2
Replies
3
Views
120
Firebird Scrambler
Firebird Scrambler
phonetech2012
  • Locked
  • Question
internal call over tie line sending wrong digits
Replies
2
Views
116
bignose21
bignose21

Part and Inventory Search

Sponsor

Back
Top