×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

Two Carriers, CS1K Only Passes One to 2nd PBX

Two Carriers, CS1K Only Passes One to 2nd PBX

Two Carriers, CS1K Only Passes One to 2nd PBX

(OP)
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 distance trunks however incoming calls only go to Asterisk from the local trunk. Incoming calls from the long distance trunk to Asterisk get a fast busy. I see nothing on the Asterisk DCH when a call comes over the long distance trunk so I'm assuming the call is getting dropped because of the Meridian. Calls going from the long distance trunk to a Meridian extension complete successfully. What could be causing this? Here is some info.

Thanks in advance!

Local:

CODE

DES  LIGHTPATH
TN   006 01
TYPE DID
CDEN SD
CUST 0
TRK  PRI
PDCA 1
PCML MU
NCOS 0
RTMB 6 1
B-CHANNEL SIGNALING
NITE
STRI/STRO OWK OWK
AST  NO
IAPG 0
CLS  UNR DTN CND WTA LPR APN THFD HKD
     P10 VNL
TKID
DATE 27 JUN 2014 

Long Distance:

CODE

DES
TN   009 01
TYPE TIE
CDEN SD
CUST 0
TRK  DTI
PDCA 1
PCML MU
NCOS 0
RTMB 4 1
TGAR 0
SIGL EAM
STRI/STRO WNK WNK
SUPN YES
AST  NO
IAPG 0
CLS  UNR DTN CND WTA LPR APN THFD HKD
     P10 VNL
TKID
DATE 15 JUL 2013 

Asterisk:

CODE

DES  ASTERISK
TN   007 01
TYPE TIE
CDEN SD
CUST 0
TRK  PRI
PDCA 1
PCML MU
NCOS 0
RTMB 7 1
B-CHANNEL SIGNALING
TGAR 1
AST  NO
IAPG 0
CLS  UNR DTN CND WTA LPR APN THFD HKD
     P10 VNL
TKID
DATE 16 FEB 2018 

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

(OP)
Here they are:

CODE

DSC  2700
FLEN 4
DSP  LSC
RLI  6
NPA
NXX
DSC  2761
FLEN 4
DSP  LSC
RLI  6
NPA
NXX
DSC  4349
FLEN 4
DSP  LSC
RLI  6
NPA
NXX 

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

(OP)
Here is the RLB, route, and DCH.

RLB:

CODE

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:

CODE

TYPE RDB
CUST 00
DMOD
ROUT 7
DES  ASTERISK
TKTP TIE
NPID_TBL_NUM   0
ESN  NO
CNVT NO
SAT  NO
RCLS EXT
DTRK YES
BRIP NO
DGTP PRI
ISDN YES
    MODE PRA
    IFC  ISGF
    SBN  NO
    PNI  00000
    NCNA NO
    NCRD NO
    CHTY BCH
    CTYP UKWN
    INAC NO
    ISAR NO
    CPFXS YES
    DAPC NO
    INTC NO
DSEL 3VCE
PTYP PRI
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
SRCH LIN
TRMB YES
STEP
ACOD 8907
TCPP NO
TARG 01
CLEN 1
BILN NO
OABS
INST
IDC  NO
DCNO 0 *
NDNO 0
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
     TFD 0
DRNG NO
CDR  NO
MUS  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
TTBL 0
ATAN NO
PLEV 2
ALRM NO
ART  0
SGRP 0
AACR NO 

DCH:

CODE

ADAN     DCH 7
  CTYP MSDL
  CARD 07
  PORT 1
  DES  asterisk
  USR  PRI
  DCHL 7
  OTBF 32
  PARM RS422  DTE
  DRAT 64KC
  CLOK EXT
  IFC  ISGF
    PINX_CUST 0
    ISDN_MCNT 300
  CLID OPT0
  CO_TYPE  STD
  SIDE NET
  CNEG 1
  RLS  ID  **
  RCAP COLP NDI CCBI CCNI PRI DV3I MQC CTI
  PR_TRIGS DIV 2 3
           CNG 2 3
  PR_RTN NO
  MQC_FEAT
  MBGA NO
  OVLR NO
  OVLS NO
  T310 120
  T200 3
  T203 10
  N200 3
  N201 260
  K    7 

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

Has you checked that NCOS and FRL has sufficients rights to pass a route?

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

Remove that TARG entry from the route by doing X1

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

(OP)
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 7 route 7).

This is my FCR:

CODE

CRNO  0
INIT DENY
ALOW 911
     958

CRNO  1
INIT ALOW
DENY 1
     411
     540
     555
     550
     976
     0

CRNO  2

CRNO  3

CRNO  4

CRNO  5
INIT ALOW
DENY 1900

CRNO  6

CRNO  7

CRNO  8

CRNO  9 

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

Have you been administrator for this switch a while? Do you know if you guys use tenant service or have tbar set up? Both could affect trunk to trunk connections. What about TRNX and EXTT in NET_DATA. I've seen those settings cause issues with trunk to trunk connections. Even if the local call passes I would still check. The LD trunk is making the call so the NCOS could be an issue but I see the FRL for the RLI is 0 and that is what the trunk has. If it was a signaling issue seems like you would see something with dchannel monitoring.
And what calls are inbound on the LD T?

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

(OP)
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 only incoming calls on that trunk are from our corporate office (AT&T set this up, it supposedly saves money). All other incoming calls go over Loop 6 (PRI). I am confused as to why incoming calls from Loop 6 successfully transfer to Loop 7 but incoming calls from Loop 9 do not. I see nothing on the dch when a call comes in from Loop 9 to an extension in Asterisk.

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

How are the incoming calls arriving? Are they the exact dns as built in CDP or are they sending 7 or 10 digits? If they aren't the dns you have defined you will need an IDC table or change the dsc to match. Sounds like the switch isn't even attempting to signal the DCH.

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

(OP)
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 go to Loop 7. Asterisk is able to grab Loop 6 and Loop 9 via their ACODs to make outgoing calls. The only thing that does not work properly is incoming calls from Loop 9 to Loop 7.

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

(OP)
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.

CODE

TYPE RDB
CUST 00
DMOD
ROUT 4
DES  ATT
TKTP DID
NPID_TBL_NUM   0
SAT  NO
RCLS EXT
DTRK YES
BRIP NO
DGTP DTI
ISDN NO
DSEL 3VCE
PTYP DCO
AUTO NO
DNIS YES
NDGT 31
WDGT L
DCDR NO
ICOG IAO
RANX NO
SRCH LIN
TRMB YES
STEP
ACOD 7094
CPP  NO
TARG
CLEN 1
BILN NO
OABS
INST
IDC  YES
DCNO 0
NDNO 0 *
DNAM NO
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 NO
HOLD 02 02 40
SEIZ 02 02
SVFL 02 02
DRNG NO
CDR  NO
MUS  YES
MRT  1
MR   NO
MANO 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
TTBL 0
ATAN NO
OHTD NO
PLEV 2
MCTS NO
ALRM NO
ART  0
SGRP 0
AACR NO 

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

I see a whole lot wrong with that RDB or things that look odd

Why is DNIS YES

Why is IDC YES

The NEDC and FEDC should be eth eth

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

I don't think they are sending 4. These numbers are internal only or are they DID? If the are DID I would go ahead and build an IDC for the whole ten and seven digit number xlating to the DSC. Assign that to route and see if it helps. I never trust ATT.

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

what do the inbound dch messages show when trying to contact one of these numbers? if the local works capture that & compare it with the inbound long distance DCH trace, also if these are trunk to trunk shouldn't the CDP type be TSC & not LSC?

Remember if it doesn't work hit it harder

Scott UK

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

also just wondering, what is the route Class of your inbound local & long distance routes

Remember if it doesn't work hit it harder

Scott UK

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

(OP)
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 Asterisk trunk:
UNR DTN CND WTA LPR APN THFD HKD
P10 VNL

I cannot do DCH trace on Loop 9 (long distance) because it is a DTI. Loop 6 (local) inbound loops like this:

CODE

DCH 7 UIPE_OMSG CC_SETUP_REQ  REF 0000010A CH 7 23 TOD   9:16:42
CALLING #:6315592559 NUM PLAN: UNKNOWN   TON: UNKNOWN
CALLED  #:2700 NUM PLAN: PRIVATE   TON: ESN CDP

DCH 7 UIPE_IMSG CC_PROCEED_IND  REF 0000010A CH 7 23 TOD   9:16:42

DCH 7 UIPE_IMSG CC_ALERT_IND  REF 0000010A CH 7 23 TOD   9:16:42
PROGRESS: INBAND INFO OR PATTERN IS AVAIL

DCH 7 UIPE_IMSG CC_SETUP_CONF   REF 0000010A CH 7 23 TOD   9:16:46
PROGRESS: TERMINATING END IS NOT ISDN
CONNECT #:2700 NUM PLAN: NONE  TON: UNKNOWN

DCH 7 UIPE_IMSG CC_DISC_IND   REF 0000010A CH 7 23 TOD   9:16:48
CAUSE: #16 - NORMAL CALL CLEARING

DCH 7 UIPE_OMSG CC_RELEASE_REQ  REF 0000010A CH 7 23 TOD   9:16:48

DCH 7 UIPE_IMSG CC_RELEASE_CONF   REF 0000010A CH 7 23 TOD   9:16:48
CAUSE: #16 - NORMAL CALL CLEARING 

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

the route class = prt, Type: RBD, Rout: x, look for RCLS: INT/EXT

isn't DTI the same sort of thing as our DASS/DPNSS? if so look at LD75, you can use "enl mon X (loop number of the DDSL not the DDCS I think) decd

enl mon 8 decd

Remember if it doesn't work hit it harder

Scott UK

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

(OP)
Route 4 (Long Distance): EXT
Route 6 (Local): EXT
Route 7 (Asterisk): EXT

Unfortunately looks like I can't get into 75:

CODE

>ld 75

DTM007 0 IDA PACKAGE RESTRICTED 

I was able to TRAD a call as it came into Long Distance:

CODE

ACTIVE  TN 009 09
ORIG  009 09  TIE  RMBR  4 9
TERM  NONE
TDTN    0     SLOT    10   PTY SLOT  10
DIAL DN NONE
MAIN_PM  REOR
TALKSLOT  NONE
EES_DATA:
NONE
QUEU  DIAL
CALL ID 0 181

PDCA  1  PAD  0   0   PCML MU  MU 

CODE

ACTIVE  TN 009 09
ORIG  009 09  TIE  RMBR  4 9
TERM  NONE
DIAL DN NONE
MAIN_PM  HALFDISC
TALKSLOT  NONE
EES_DATA:
NONE
QUEU  NONE
CALL ID 0 181

PDCA  1  PAD  0   0   PCML MU  MU 

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

Check these settings

LD 15 REQ: CHG
TYPE: NET_DATA
DITI = YES
EXTT = YES
FTOP = FTLY

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

(OP)
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 with routing from DID to TIE but our local loop is a DID and it routes to Asterisk successfully. I posted a few days ago that I converted Loop 9 (Long Distance) from TIE to DID. So both circuits that handle calls from the outside world are DIDs. Asterisk is a TIE.

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

I was going to suggest the NET data DITI=YES---------not sure why you are not seeing that in your net data.
I would change the FTOP to FRES--that will override any trunk to trunk restrictions---

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

FRES is Fully Restricted, I don't think he wants that

FTOP Flexible Trunk to Trunk Options. basic-23
(FRES) Flexible Trunk to Trunk Connections
Restricted. FTT feature is inactive.
TBFT Trunk Barring Flexible Trunk to Trunk
Connections. FTT adds new restrictions on
connections not barred by TBAR
FTTB Flexible Trunk to Trunk connections Trunk
Barring. FTT lifts TBAR restrictions for routes
barred by TBAR. FTT cannot add any new
restrictions for non-barred routes.
FTLY Flexible Trunk to Trunk Connections Only. All
set based trunk to trunk connections for
Transfer and Conference are controlled by

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

(OP)
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 Loop 9 goes to our NITE DN.

NET_DATA:

CODE

TYPE NET_DATA
CUST 00
OPT RTD
AC2
FNP YES
ISDN YES
  PNI 0
  PINX_DN
  MBG 0
  BSGC 65535
  PFX1 516
  PFX2 357
  HLOC
  LSC
  RCNT 5
  PSTN NO
  TNDM 15
  PCMC 15
  SATD 1
  OCLI NO
TRNX YES
EXTT YES
FTOP FTLY
VNR NO
NIT 8
FOPT 14 

RDR_DATA:

CODE

TYPE RDR_DATA
CUST 00
OPT CFF CFRA PVCD CWRD
FNAD FDN
FNAT FDN
FNAL FDN
CFTA YES
CCFWDN
CFN0 4
CFN1 4
CFN2 2
DFN0 4
DFN1 4
DFN2 2
DNDH NO
MDID YES
NDID YES
MWFB YES
TRCL 0
CRT0 00 00 00 00
CRT1 00 00 00 00
CRT2 00 00 00 00
CRT3 00 00 00 00
DAY0
DAY1
DAY2
DAY3
HOLIDAY0
HOLIDAY1
HOLIDAY2
HOLIDAY3 

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

(OP)
Also, SUPN is "YES" for all 20 Loop 9 DID's (it's a 20 channel DTI).

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

Ok kinda forget where we are but can you try this? The dn that you are trying to pass to Asterisk, can you put that on a set on the CS1000? If you can and it terminates on the set you program it on that will confirm what and how many digits they are sending on the LD route. I hate beating this horse but you need a way to confirm what is arriving to the switch. I also NDGT set to 31. If you are using DNIS then I think that has to be the exact number of digits you're expecting. Not real sure about that though. And that other question I asked about tenant service. That will cause exactly what is happening here. When you build a TN do you have to define TEN in the database? If it were me first thing I would do is make these incoming digits ring on a phone on the CS1k.

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

ld 21
prt
net
cust x

LOOK for DITI in the print out

DITI (no)yes --> DID to TIE connections allowed

As the above post state you have checked that a successful call is terminated on a local set haven't you????

Remember if it doesn't work hit it harder

Scott UK

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

(OP)
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.

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

If it rings through to a Nortel phone then they are sending four. If you don't have to input anything for TEN when building a phone then you aren't using tenant service. I would involve your vendor at this point. Make then escalate to TAC.

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

(OP)
My vendor says they do not know what to do. That's why I came here sad

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

So 3 things to look at in the NET_DATA

DITI = YES
TRNX = YES
EXTT = YES

If those are all set correct, then I have one other suggestion and then I'm out

Change the NCOS on the TIE LD route to 3 on all trunks. I think this may be your issue. I ran across this years ago on a system. Since 0 is a default value I think I ended up make it a 3 and it worked. What do you have to lose? Worth a shot. And if this works, get another vendor

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

(OP)
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.

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

The call that is failing is TIE to TIE and the calls that work are DID to TIE, that is the difference. Just try it. Change the NCOS on the inbound LD Tie Route trunks to a 3 and leave the TIE to Asterisk alone at 0

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

One other thought if the above doesn't work. Change the TIE Route to the Asterisk at the RCLS and make it INT instead of EXT

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

(OP)
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.

CODE -->

BUG4006
BUG4006  : 00198924 00001002 00008218 00001CA0 0000088A 19 00000001 00000001 000
00000 0 0 00002084 0000AAA7 00000000 00000000 00000000 00000000 00000000 00000E
BUG4006  +   1067E808 10629ECA 10629744 101E873C 101DBC6C
BUG4006 + 101DB2AC 101DAD70 101DA25C 1082E364 1082DDC2
BUG4006  + 1051186E 10510EC4 1050F5E8 1050F12C 1050E1CE
BUG4006 + 1050DFCC 108D9D18 108D8B94 108C3FEA 10E65BAC
BUG4006  + 10E6550C 10E65404 10E63080

BUG6246
BUG6246  : 10 0 0 12 7839
BUG6246  +   1067E808 101E4F80 101E4748 101E20CE 101DA250
BUG6246 + 10E6360A 10E63246 10E63128 

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

I wouldn't have changed the ATT to DID, that may cause more issues than you have right now. By changing multiple things you may never know what is causing the issue

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

how can you have a DTI circuit without having the DTI packages?

Remember if it doesn't work hit it harder

Scott UK

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

So maybe try this for a work around. Build a phantom tn with the incoming dn. Set a dcfw to a dsc pointed to the asterisk pri. PITA but if it allows you to pass calls who cares right?

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

And try one other thing just to humor me. Change the FLEN to 0.

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

(OP)
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.

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

(OP)
DITI is PKG 131.

CODE

...
DTI2   129
TBAR   132
... 

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

Didn't think the DITI prompt had anything to do with a certain software package, just thought it was a prompt in the Net_Data you turned off or on

DITI (NO) YES DID to TIE connections allowed

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

(OP)
The phantom worked and changing FLEN to 0 on a DSC also worked. What exactly does FLEN do? My vendor said to set it to 4.

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

FLEN (0)-24 Flexible Length number of digits
Prompted with Flexible Numbering Plan (FNP)
package 160.

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

FLEN basically tells the PBX how many digits to look for before routing the call

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

So you're all set? I've seen FLEN work both ways. Sometimes you have to tell the far end how many digits you're sending and other times you can't tell it.

RE: Two Carriers, CS1K Only Passes One to 2nd PBX

(OP)
Yeah, everything's working fine. Thanks a lot!

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close