VOIP IVR 2

[Dougo123]

Moving from a FGDT to VOIP IVR set up. Basically copied the old IVR rdb for the new. 6 PRI span prim and bdch and regular calls come thru fine. With the DNIS I get these errors
ERR183 8988817706 59 3

BUG4269
BUG4269 : 00AB6A57 00000222 00000018 00003B10 00000000 0 00000000 00000000 00AE
3509 0 0000014A 00008898 000077A8 0000006A 00000000 00000000 00000000 8
BUG4269 + 047680D4 04790364 047900DE 04CF8BBA 0DBBA524
BUG4269 + 045F994C 04EC27F0 04EC123E 04EC0314 04EBFAB2
BUG4269 + 04EB6F8A 04EB6CC0 04EB6A14 04EB4C8C 04EB4BC0
BUG4269 + 04C9C168 04C990BC 04C98DF8 04BE61B2 04BE016A

ERR183 8988807706 59 4

This is a Sonus group.
Anyone see something I might haved missed
REQ: PRT
TYPE: TNB
TN 188 1
DATE
PAGE
DES

DES SONUS_1
TN 188 01
TYPE DID
CDEN SD
CUST 0
TRK PRI
PDCA 1
PCML MU
NCOS 0
RTMB 12 1
B-CHANNEL SIGNALING
NITE
STRI OWK
AST NO
IAPG 0
CLS UNR DTN WTA LPR APN THFD HKD
P10 VNL
TKID
AACR NO
DATE 23 FEB 2009


NACT
REQ: END
>LD 21
PT1000

REQ: PRT
TYPE: RDB
CUST 0
ROUT 12

TYPE RDB
CUST 00
ROUT 12
DES SONUS_1
TKTP DID
M911_ANI NO
M911_TONE NO
NPID_TBL_NUM 0
SAT NO
RCLS EXT
VTRK NO
NODE
DTRK YES
BRIP NO
DGTP PRI
ISDN YES
MODE PRA
IFC NI2
CBCR NO
NCOS 0
SBN NO
PNI 00000
NCNA YES
NCRD NO
CHTY BCH
CPFXS YES
CPUB OFF
DAPC NO
BCOT 0
INTC NO
DSEL 3VCE
PTYP PRI
AUTO NO
DNIS YES
NDGT 10
WDGT L
DDLY NO
DCDR NO
ICOG ICT
STEP
ACOD xxxxxxx
PII NO
TARG 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15
CLEN 1
BILN NO
OABS
INST
IDC YES
DCNO 0
NDNO 0 *
DNAM NO
ICIS YES
TIMR ICF 512
OGF 512
EOD 13952
NRD 10112
DDL 70
ODT 4096
RGV 640
FLH 510
GRD 896
SFB 3
NBS 2048


PAGE 002

NBL 4096

IENB 5
VSS 0
VGD 6
DRNG NO
CDR YES
INC NO
LAST YES
QREC YES
OAL YES
AIA YES
OAN YES
OPD YES
CDRX NO
NATL YES
VRAT NO
MUS NO
FRL 0 0
FRL 1 0
FRL 2 0
FRL 3 0
FRL 4 0
FRL 5 0
FRL 6 0
FRL 7 0
OHQ NO
OHQT 00
TTBL 0
ATAN NO
PLEV 2
MCTS NO
ALRM NO
ART 0
SGRP 0
ARDN NO
AACR NO

REQ: END
>LD 22
PT2000

REQ PRT
TYPE ADAN DCH 16

ADAN PRIM DCH 16
BDCH 28
CTYP MSDL
GRP 5
DNUM 12
PORT 2
DES SONUS_1
USR PRI
DCHL 188
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC NI2
ISDN_MCNT 300
CLID OPT0
CO_TYPE ATT
SIDE USR
CNEG 1
RLS ID 1
RCAP COLP NDS
MBGA NO
OVLR NO
OVLS NO
PRI INTERFACE ID
132 3
021 4
059 5
114 6
T310 120
T200 3
T203 10
N200 3
N201 260
K 7
BSRV NO
I know the interface ID should be
133 2
21 3
59 4
114 5

Bdch is on 163 but I didn't think it was cause the errors. I can always rebuild dch 16 because this is still in testing and since regular calls go thru fine dont think it's the issue. I think it's 8988807706. Dont remeber that one. IVR's are so much fun.

 

[GHTROUT]

We've seen that error mentioned a few times... you could putting "ERR183" in this

http://www.tek-tips.com/search.cfm?pid=798

Some results include:

This patch was posted: MPLR15939

Also this thread looked interesting: thread798-1428172

~~~
[©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators

 

[Dougo123]

Gene
thanks but the problem is we still have the FGDT circuits up and when they send the same digits it hits the agent every time. It's only this new VOIP group where we went DTI to PRI. We have another CS1000 that we use Sonus for our outbound. Besides that this group is incoming only and the Dnis everything is the same. Had a couple of problems on the outbound side but was always a carrier Voip protocal issue. This is the first Voip-ISDN-symposium-wan-back to voip sets. I just think something is happening inbound(lost translation) before it hits us. I've gone over my programming 20 times and don't see anything that can cause this. I'll search the err183. Also thanks for the web site and your FAQ's.

 

[GHTROUT]

What if you tried this: Build an IDC table that does nothing. Like "1234 1234" (but using the digits sent in your case) Then assign it to this route.

My thought is to introduce a new step in the system to see if it will "kick" the software into taking a new path of logic.

Of course, this assumes you don't "need" IDC

~~~
[©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators

 

[tnphoneman]

I would try building another IDC table other than 0. I have seen issues although very rare using this table. Creating a new table has always fixed the issue.

Signature===========================================

http://www.greatwhitetechnologies.com

Aastra Authorized Reseller

 

[Dougo123]

I had to add the new table. Everything seems fine now except for the over 600 table entries they're going to hit me with.

 

[tnphoneman]

You don't have to do the entries individually if they are in a sequence.

for instance for 4678 you can convert incoming digit 4 to say 7 and it will only change the first digit and the others will stay the same. It works off the leading digits.

Signature===========================================

http://www.greatwhitetechnologies.com

Aastra Authorized Reseller