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

CAS Trunk dialing issues

Status
Not open for further replies.

gewt

Technical User
Aug 8, 2017
32
US
Hi all,

(pardon any ignorance - this is my second day ever doing Meridian admin stuff...thankfully for hobby)

Finally have my 11c configured to /some/ sort of usable state.

Only have a TMDI card at the moment so my trunk is CAS.

My issue:

1). Phone dials "9 (ACOD for trunk - not BARS)" + number
2). Call is sent to the trunk as "done" (example: 6169542) when I press the first 6.
3). LD80 trace shows:
[pre].18:32:18 10/08/2017
TN 002 0 00 01
KEY 0 SCR MARP ACTIVE TN 002 0 00 01
ORIG 002 0 00 01 0 SCR MARP 0 7001 2008
TERM 001 24 DID RMBR 20 24
DIAL DN 9
MAIN_PM DIAL AUX_PM DDL
TALKSLOT ORIG 8 TERM 8
QUEU 128
CALL ID 0 465


PDCA 1 PAD 0 6 PCML MU MU

KEY 1 NUL IDLE
KEY 2 NUL IDLE
KEY 3 NUL IDLE
KEY 4 NUL IDLE
KEY 5 NUL IDLE
KEY 6 NUL IDLE
KEY 7 NUL IDLE


.18:32:18 10/08/2017
TN 002 0 00 01
KEY 0 SCR MARP ACTIVE TN 002 0 00 01
ORIG 002 0 00 01 0 SCR MARP 0 7001 2008
TERM 001 24 DID RMBR 20 24
DIAL DN 961
MAIN_PM DIAL AUX_PM TEMPPATH
TALKSLOT ORIG 8 TERM 8
QUEU NONE
CALL ID 0 465


PDCA 1 PAD 0 6 PCML MU MU

KEY 1 NUL IDLE
KEY 2 NUL IDLE
KEY 3 NUL IDLE
KEY 4 NUL IDLE
KEY 5 NUL IDLE
KEY 6 NUL IDLE
KEY 7 NUL IDLE


.18:32:20 10/08/2017
TN 002 0 00 01
KEY 0 SCR MARP ACTIVE TN 002 0 00 01
ORIG 002 0 00 01 0 SCR MARP 0 7001 2008
TERM 001 24 DID RMBR 20 24
TDTN 0 SLOT 20 PTY SLOT 8
DIAL DN 961695
MAIN_PM DIAL AUX_PM OUTPULSE
TALKSLOT ORIG 8 TERM 8
QUEU 128
CALL ID 0 465


PDCA 1 PAD 0 6 PCML MU MU

KEY 1 NUL IDLE
KEY 2 NUL IDLE
KEY 3 NUL IDLE
KEY 4 NUL IDLE
KEY 5 NUL IDLE
KEY 6 NUL IDLE
KEY 7 NUL IDLE


.18:32:20 10/08/2017
TN 002 0 00 01
KEY 0 SCR MARP ACTIVE TN 002 0 00 01
ORIG 002 0 00 01 0 SCR MARP 0 7001 2008
TERM 001 24 DID RMBR 20 24
DIAL DN 96169542
MAIN_PM ESTD
TALKSLOT ORIG 8 TERM 8
QUEU NONE
CALL ID 0 465[/pre]

However: the Cisco (bridging T1 to H.323) has received only a "6" as the Called Party.
02:07:39: dpMatchPeersMoreArg: Match Dest. pattern; called (6)
02:07:39: Inside dpMatchCore:
02:07:39: destination pattn: 6 expanded string: 6
(Confirmed passed on as well to H.323 endpoint)

As the call is established long before I finish dialing, any ideas what could be the cause? Config options I've missed? or is the cisco just eager to dial?

Here's the rdb...

[pre]REQ: prt
TYPE: rdb
CUST 0
ROUT 20

TYPE RDB
CUST 00
DMOD
ROUT 20
DES OUTBOUND
TKTP DID
NPID_TBL_NUM 0
SAT NO
RCLS EXT
DTRK YES
BRIP NO
DGTP DTI
DSEL VCE
PTYP DCO
AUTO NO
DNIS NO
ICOG IAO
RANX NO
SRCH LIN
TRMB YES
STEP
ACOD 9
CPP NO
TARG
CLEN 1
BILN NO
OABS
INST
TIMR ICF 512
OGF 512
EOD 13952
DSI 34944
NRD 10112
DDL 70
ODT 4096
RGV 640
FLH 510
GRD 896
SFB 3
TFD 0
SST 5 0
NEDC ORG
FEDC ORG
CPDC NO
DLTN YES
HOLD 02 02 40
SEIZ 02 02
SVFL 02 02
DRNG NO
CDR NO
MUS NO
MR NO
RACD NO
EQAR NO
OHQ NO
OHQT 00
TTBL 0
OHTD NO
PLEV 2
MCTS NO
ALRM NO
ART 0
SGRP 0[/pre]

 
try adding BARS and only pass the number to the CAS when it is complete might work
 
Aww. That means i'd need to fully learn BARS. ;)

I'll give that a shot later today after work.
 
BARS so far is a case of "as soon as I finish dialing the only configured NPA, a "1" is received by the cisco"

I think i'm just gonna wait for my non-TMDI card to arrive...

Unless I can do non-wink for CAS.
 
So your CAS trunk does not send the digits until they are complete or does the LD 80 trace still show them being processed overlap
 
does the Cisco require an access code for out calling?
if so the user on the PBX needs to dial that access code after the 9 and before the number-or if you set it up in BARS then a Digit manipulation entry needs to be created to insert that digit
 
Cisco's not configured to take an access code.

Still sending digits before it's received all of them with the CAS trunk (issue not present with a CO trunk). The Cisco is also ignoring digits after the 1.

Perhaps I'll build a CAS link to the cisco with another system and see if it has the same issue.
 
Sorted out.

Cisco wasn't waiting for me to complete dialing before it started matching dial-peers.

My catch-all dial peer was matching on the first digit.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top