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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Inbound call to direct DID number from PRI handoff answers with Busy Signal

Status
Not open for further replies.

Gartech

IS-IT--Management
Jul 12, 2016
19
US
Inbound calls to direct DID number from PRI handoff answers with Busy Signal.
DND is not enabled nor is forwarding.
User has voicemail Pro set up
Internal calls to extension connect without busy tone.

This extension was working properly up until yesterday evening.
 
Default monitor trace will tell you what's wrong.

"Trying is the first step to failure..." - Homer
 
Thanks janni78
I have that running but since I am new to this IPO I am trying to figure out how to troubleshoot with this tool.
 
If you make a test call and post it here we can look at it.

The problem is probably in the ICR matching.

"Trying is the first step to failure..." - Homer
 
Hopefully I captured what is needed to trace the source of the "BUSY" answer below. I am new to the monitor tool and IPO as well.

14:29:22 105204686mS PRN: Q931Trunk: Found QBChannel to match 0.2 --> 1.3
14:29:22 105204686mS CMCallEvt: 0000000000000000 0.7569.0 -1 BaseEP: NEW CMEndpoint f1788f80 TOTAL NOW=9 CALL_LIST=4
14:29:22 105204686mS CMTARGET: ISDN BChannel 2: in-service check = 1
14:29:22 105204687mS CMTARGET: ISDN BChannel 2: in-service check = 1
14:29:22 105204687mS CMCallEvt: CREATE CALL:1530 (f1752ec0)
14:29:22 105204687mS CMCallEvt: 0000000000000000 0.7570.0 -1 BaseEP: NEW CMEndpoint f49833ac TOTAL NOW=10 CALL_LIST=4
14:29:22 105204689mS CD: CALL: 1.19.1 BState=Idle Cut=1 Music=0.0 Aend="Line 1" (1.3) Bend="" [] (0.0) CalledNum=2145744197 () CallingNum=4692239999 (MOBILITY CREDIT) Internal=0 Time=2 AState=Idle
14:29:22 105204689mS CMCallEvt: 0a40100500000013 1.19.1 1530 Q931 Trunk:1 CHAN=2: StateChange: END=A CMCSIdle->CMCSDialInitiated
14:29:22 105204689mS CMTARGET: 0a40100500000013 1.19.1 1530 Q931 Trunk:1 CHAN=2: LOOKUP CALL ROUTE: GID=0 type=0 called_party=2145744197 sub= calling=4692239999 calling_sub= dir=in complete=1 ses=0
14:29:22 105204689mS CMTARGET: 0a40100500000013 1.19.1 1530 Q931 Trunk:1 CHAN=2: SET BESTMATCH: length 10 vs -1 match=2145744197 dest=

********** Warning: Missed 1 packet(s) Total late 0 packet(s) **********
14:29:22 105204690mS CMTARGET: 0a40100500000013 1.19.1 1530 Q931 Trunk:1 CHAN=2: LOOKUP ICR: DDI= CGPN=4692239999 (Destination ) => CDPN=
14:29:22 105204690mS CMTARGET: 0a40100500000013 1.19.1 1530 Q931 Trunk:1 CHAN=2: ADD TARGET (N): number= type=0 depth=1 nobar=1 setorig=1 ses=0
14:29:22 105204690mS CMTARGET: 0a40100500000013 1.19.1 1530 Q931 Trunk:1 CHAN=2: NO INITIAL TARGETS: ??
14:29:22 105204690mS CMTARGET: 0a40100500000013 1.19.1 1530 Q931 Trunk:1 CHAN=2: Fallback() targeting failed
14:29:22 105204691mS CMLOGGING: CALL:2016/07/2114:29,00:00:00,000,4692239999,I,,2145744197,MOBILITYCREDIT,,,0,,"",0,n/a
14:29:22 105204691mS CD: CALL: 1.19.1 BState=Idle Cut=0 Music=0.0 Aend="Line 1" (1.3) Bend="" [] (0.0) CalledNum= () CallingNum=4692239999 (MOBILITY CREDIT) Internal=0 Time=4 AState=Dialling
14:29:22 105204692mS CD: CALL: 1.19.1 Deleted
14:29:22 105204692mS CMLineTx: v=1
CMReleaseComp
Line: type=Q931Line 1 Call: lid=1 id=19 in=1
Cause=17, User busy
14:29:22 105204692mS CMCallEvt: 0a40100500000013 1.19.1 -1 Q931 Trunk:1 CHAN=2: StateChange: END=X CMCSDialInitiated->CMCSDelete
14:29:22 105204692mS CMCallEvt: 0000000000000000 0.7570.0 -1 BaseEP: DELETE CMEndpoint f49833ac TOTAL NOW=9 CALL_LIST=4
14:29:22 105204692mS CMCallEvt: END CALL:1530 (f1752ec0)
14:29:22 105204693mS CMTARGET: ISDN BChannel 2: in-service check = 1
14:29:22 105204693mS CMTARGET: ISDN BChannel 2: in-service check = 1
14:29:22 105204693mS CMTARGET: 0a40100500000013 1.19.1 -1 BaseEP: ~CMTargetHandler f4d82f04 ep f1788f80
14:29:22 105204694mS CMCallEvt: 0a40100500000013 1.19.1 -1 BaseEP: DELETE CMEndpoint f1788f80 TOTAL NOW=8 CALL_LIST=4
14:29:22 105204695mS ISDNL3Evt: v=1 stacknum=1 State, new=NullState, old=Present id=19
 
Looks like you either have no Incoming Call Route for the DDI number (2145744197) OR the incoming trunk ID is wrong OR there is no target set in the ICR
14:29:22 105204690mS CMTARGET: 0a40100500000013 1.19.1 1530 Q931 Trunk:1 CHAN=2: LOOKUP ICR: DDI= CGPN=4692239999 (Destination ) => CDPN=
14:29:22 105204690mS CMTARGET: 0a40100500000013 1.19.1 1530 Q931 Trunk:1 CHAN=2: ADD TARGET (N): number= type=0 depth=1 nobar=1 setorig=1 ses=0
14:29:22 105204690mS CMTARGET: 0a40100500000013 1.19.1 1530 Q931 Trunk:1 CHAN=2: NO INITIAL TARGETS: ??
14:29:22 105204690mS CMTARGET: 0a40100500000013 1.19.1 1530 Q931 Trunk:1 CHAN=2: Fallback() targeting failed
 
yepp, seems like the destination is missing in ICR

14:29:22 105204689mS CMTARGET: 0a40100500000013 1.19.1 1530 Q931 Trunk:1 CHAN=2: SET BESTMATCH: length 10 vs -1 match=2145744197 dest=

"Trying is the first step to failure..." - Homer
 
Thank you for the responses.
I have IPO Manager up now to see how to correct this.
 
1 - look in the trunk for the incoming group ID
2 - look in ICR if the Incoming ID matches the trunk ID
2 - look in ICR if you selected a valid target
 
Well, I looked at the ICR and for some reason the DESTINATION did not have the extension in the drop-down that it once had.
I am sure these values do not just drop out on their own. Could be an oversite by a system co-manager. I have put the correct extension back and calls now route to the extension.

At least I learned something today!

Thanks for everyone's help.
 
The thank you will i know be appreciated but.....Those little pink things(great post) are like getting payment for the engineers who have kindly taken the time to solve your issue for free , try it out it works wonders for further co-op

ACSS (UC/SBCE/SM/SME)

Not that they mean a thing anymore , get a brain dump pass the test crash the system.
 
Manager generates a error on ICRs without a destination and System Status also if a call has arrived on the DDI.
 
the default IPO cfg has an ICR with the incoming DDI blank & a destination of Main

It is a good idea to leave this rout in place, that way any unrecognised DDI's get router to the Main ring group.
this prevents the call being lost & should draw attention to the issue.



Do things on the cheap & it will cost you dear
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top