I've set FLEN to 0 on one of the DSC's and built a phantom TN. Testing...
I've read that DITI is used internationally. I don't know if that's true or not.
I had our vendor change AT&T to a DID, so both of the outside trunks are DID. Asterisk is still a TIE. RCLS INT and NCOS 3 did not work :(
I did notice these BUGs output every time someone calls in via AT&T, and the call goes to our Automated Attendant. TN 10 12 is a Meridian Mail channel...
I do not have the package for DITI. I believe that requires a specific package.
What could make incoming calls work on Loop 6 and not Loop 9? They are both DID's. I'll try out changing the NCOS.
I do not have the DITI prompt.
Nortel phones work just fine with the DNs on SCR keys. I do not need to make any other changes in the database besides programming the TN itself.
My vendor says AT&T is sending 4 digits and our DNs are 4 digits.
I believe I would need PKG 131 for DITI. Correct me if I'm wrong but isn't this a problem with Loop 9 itself, not the CDB? Loops 6 and 9 are both DID so I wouldn't think it's a trunk-to-trunk setting in the CDB. It's only Loop 9 that's not routing the call. Any call going towards Loop 7 from...
I changed TRNX and EXTT to "YES" in NET_DATA per a previous recommendation. Before that they were both "NO". FTOP was "FRES" and is now "FTLY". I do not see a prompt for DITI in CHG or PRT. Calls from the outside are still going to our NITE DN.
I originally thought the issue might have to do...
Route 4 (Long Distance): EXT
Route 6 (Local): EXT
Route 7 (Asterisk): EXT
Unfortunately looks like I can't get into 75:
>ld 75
DTM007 0 IDA PACKAGE RESTRICTED
I was able to TRAD a call as it came into Long Distance:
ACTIVE TN 009 09
ORIG 009 09 TIE RMBR 4 9
TERM NONE
TDTN 0 SLOT...
When I put an extension on TSC instead of DSC I was unable to call it via local trunk.
Here are the classes on the local trunk:
UNR DTN CND WTA LPR APN THFD HKD
P10 VNL
Here are the classes on the long distance trunk:
UNR DTN CND ECD WTA LPR APN THFD HKD
P10 VNL
Here are the classes on the...
Our vendor just changed Loop 9 from TIE to DID. Now instead of a fast busy to Asterisk DNs we get our attendant, which is what happens when someone dials a DID that's not programmed in the Meridian.
TYPE RDB
CUST 00
DMOD
ROUT 4
DES ATT
TKTP DID
NPID_TBL_NUM 0
SAT NO
RCLS EXT
DTRK YES
BRIP...
The trunks send the last 4 digits and the DNs are defined accordingly. You are correct the DCH is silent when a call comes in over Loop 9. Only calls to Meridian DNs over Loop 9 are routed properly. Calls do come in over Loop 6 to Loop 7. Meridian sets are also able to dial DSC extensions that...
I have administered this system for a few years but we've never had to do trunk to trunk transfers before. We built Loop 7 for Asterisk a few weeks ago. TRNX and EXTT are both set to NO. I set them both to YES but that does not appear to have helped. Loop 9 (DTI) is our long distance trunk. The...
I removed the TARG. My NCOS levels 0 through 7 are 1 to 1 for FRL. I know how NCOS applies to stations but I do not know too much about how it applies to routes. What should I check? The issue I am having only applies when a call is going from my long distance (loop 9 route 4) to Asterisk (loop...
Here is the RLB, route, and DCH.
RLB:
RLI 6
ENTR 0
LTER NO
ROUT 7
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
CNV NO
EXP NO
FRL 0
DMI 0
FCI 0
FSNI 0
SBOC NRR
OHQ NO
CBQ NO
ISET 0
NALT 5
MFRL 0
OVLL 0
Route:
TYPE RDB
CUST 00
DMOD
ROUT 7
DES ASTERISK
TKTP TIE
NPID_TBL_NUM...
I have a CS1000 with three T1's: a DID PRI (NI2) from our local carrier, a TIE E&M from our long distance carrier, and a TIE PRI (QSIG/ISGF) that goes to an Asterisk PBX. I use DSC's to route extensions (4-digit) to the Asterisk TIE. Asterisk can make outgoing calls over the local and long...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.