![]() | |
| |||||||||||||||
| |||||||||||||||
| Meridian Systems Welcome to the Nortel Meridian Forums Including Meridian Options 11-81C CS1000M Meridian Mail Call Pilot Companion and Sucession Hospitality OTM MAT MICB RAN NetGateway ..., and all other Applications |
![]() |
| | LinkBack | Thread Tools | Display Modes |
| | #1 (permalink) | ||||||||
| Junior Member ![]()
Location: Utah Rep Power: 0 ![]() | PSTN calls not following correct route...or something We're dealing with an Option 51 here running software version 2821, release 3 (we're phasing this PBX out at the end of the year, thus the neglect). We have a PRI between this option 51 and a Cisco voice gateway. This PRI is for calling to and from and Cisco UCM system and this option 51. We have two 2-way PRIs coming in from our LEC for access to/from the PSTN. When a call destined for the PSTN is made on the Cisco side, the call is routed through the PRIs on the option 51. When a call comes in from the PSTN destined for a DN on the Cisco side, it hits the PRIs on the Nortel side and then routes through the 51<->Cisco PRI. Confused yet? High-level flow of a call to a Cisco DN from PSTN: PSTN->LEC PRI (4 digits)->Option51->CDP DSC->Cisco gateway->Cisco Call Manager->Cisco set with DN Here's the problem. Some calls from the PSTN make it to a Cisco DN fine, but then some calls don't. The calls that don't make it never ring the Cisco set, they just ring our switchboard operator. As far as we can verify, the calls that don't work all are from long distance callers, meaning it's not a local call for the caller, although we can't verify that these are the only calls affected. I have checked that there are no IDC entries getting in the way. When I turn on MSGI and MSGO on the Nortel-to-Cisco trunk, I never see an unsuccessful call come across, which says to me that for some reason, the Nortel PBX isn't using, or has some issue with, the CDP entries. As some of you may know from my other posts, I'm very amateur with these Nortel PBXs. I'm at a loss as to where I should go from here. We're hoping to avoid paying someone to fix this for us, naturally, but may have to regardless. An RDB print out of the Nortel-to-Cisco trunk is below. Any feedback is appreciated. Code: RDB Print out
TYPE RDB
CUST 00
ROUT 7
DES CISCO_TIE
TKTP TIE
NPID_TBL_NUM 0
ESN NO
CNVT NO
SAT NO
RCLS EXT
VTRK NO
DTRK YES
BRIP NO
DGTP PRI
ISDN YES
MODE PRA
IFC D100
SBN NO
PNI 00001
NCNA YES
NCRD NO
CHTY BCH
CTYP UKWN
INAC NO
ISAR NO
CPUB OFF
DAPC NO
BCOT 0
DSEL VCE
PTYP PRI
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
SRCH LIN
TRMB YES
STEP
ACOD 8007
TCPP NO
PII NO
TARG
CLEN 1
BILN NO
OABS
INST
IDC NO
DCNO 1 *
NDNO 1
DEXT NO
ANTK
SIGO STD
ICIS YES
TIMR ICF 512
OGF 512
EOD 13952
NRD 10112
DDL 70
ODT 4096
RGV 640
GRD 896
SFB 3
NBS 2048
NBL 4096
PAGE 002
IENB 5
TFD 0
VSS 0
VGD 6
DRNG NO
CDR YES
INC YES
LAST YES
TTA NO
QREC YES
OAL YES
AIA NO
OAN YES
OPD YES
CDRX NO
NATL YES
VRAT NO
MUS YES
MRT 10
RACD NO
EQAR 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
CBQ NO
AUTH NO
TDET NO
TTBL 0
ATAN NO
PLEV 2
ALRM NO
ART 0
SGRP 0
AACR NO Code: CDP Print out DSC 2665 FLEN 0 DSP LSC RLI 13 NPA NXX | ||||||||
| | |
| | #3 (permalink) | ||||||||
| Junior Member ![]()
Location: Utah Rep Power: 0 ![]() | No, we have about 8 DNs on the Cisco side at this point. They are all affected and all have DSCs. I figured the attendant was the vacant number intercept, but I'm trying to figure out WHY it happens on some calls, but not all. | ||||||||
| | |
| | #6 (permalink) | ||||||||
| Senior Member ![]() ![]() jack has no status.
Location: Chicago -- CENTER OF THE UNIVERSE Rep Power: 12 ![]() | Yeppers that was what I was asking. On the PRI how are the failed calls being presented from the LD carrier, ie how many digits are being sent? __________________ Dogs rollover Phones hunt | ||||||||
| | |
| | #8 (permalink) | ||||||||
| Junior Member ![]()
Location: Utah Rep Power: 0 ![]() | In case anyone is following this thread for whatever reason, we got the problem resolved. We got someone who knows what the hell they're doing involved (READ: Not me). He ended up turning on Network Call Redirect (NCNA) on the trunk and also increased our B-channel bandwidth on all our incoming PRIs. We're not sure which of the two, or if both, fixed the issue, but we're good to go now. Happy hunting (terrible pun intended). | ||||||||
| | |
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
| |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Best way to route calls to Auto-Attendant | Jim | Meridian Systems | 7 | February 19th, 2007 03:38 PM |
| route/trunk to PSTN (BRI) config example | lanperez | Meridian Systems | 1 | January 28th, 2007 12:33 PM |
| Not allow LD calls on one route? | John_In_Dakota | Meridian Systems | 4 | December 6th, 2005 08:01 PM |
| cant transfer pstn calls to h323 endpoints | dixiedogger | Meridian Systems | 1 | September 2nd, 2004 11:24 AM |
| Retrieve parked calls from PSTN trunks | mark@stjoes | Meridian Systems | 1 | February 6th, 2004 03:07 PM |